Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Student Backpack topic
No spam. Unsubscribe anytime.
USBE demos student‑achievement "backpack," cites successful PowerSchool test and FY25 roadmap
Summary
USBE product staff described the legislative student backpack that would transfer assessment and cumulative data between LEAs, reported a successful assessment data pass with PowerSchool, and invited LEAs to working groups to shape FY25 operational scenarios and API refinement.
Mark Wadobs, USIMS student domain product owner, briefed attendees on the "student achievement backpack," a legislatively created digital cumulative file intended to move with students across LEAs. "The student achievement backpack is meant to move with the student," he said, describing the backpack as a digital cumulative file that can carry assessment data and other records from one SIS to another via API calls.
Wadobs referenced a legislative citation during his overview (spoken in the session as "per 53 e dash 3 dash 5 11") and said the project has completed engine work in FY24 and demonstrated the ability to send RISE assessment data through the backpack and allow an SIS (tested with PowerSchool) to retrieve that information. He characterized FY24 work as building the engine and said the FY25 roadmap is to "put the engine in the car," meaning operationalize the capability across scenarios and workflows.
The backpack’s dataset currently includes high‑level assessment scores (RISE, Utah Aspire Plus, ACT where applicable, and third‑grade reading measures), and staff said the intent is to surface longitudinal assessment history so LEAs can better understand incoming students’ needs. Wadobs encouraged LEA staff to join student‑focused working groups and a functional advisory board meeting planned for July (staffer Katrina was offered as an invite contact) to help refine exchange scenarios and the EdFi API implementation.
Next steps: USBE will continue testing with SIS vendors, invite LEA participation in working groups for FY25 planning, and seek feedback on functional details ahead of broader rollout.
