Utah’s USIMS ‘student backpack’ aims to move core student records between districts; single-state SIS and Utrecht replacement remain multi‑year questions

Katrina Brinkley, chief product owner and program manager for the Utah School Information Management System (USIMS), and the student product owner Mark Wadops described a phased plan to allow student records to move between local education agencies (LEAs) using a new “student backpack.” The feature is intended to carry a persistent set of student information when a student enrolls at a new LEA.

"The purpose of the backpack is to win a student, let's say Johnny or Sarah moves from LEA 1 to LEA 2, that key information about that student moves with the students," Mark said, describing the design goal of a consistent, portable core record. He said the team is building the capability with a microservices approach and an initial interoperability standard, Ed‑Fi, to exchange data with certified SIS vendors such as Skyward and PowerSchool.

Why it matters: LEAs currently face duplicate records and mismatches when students move; presenters said the backpack aims to reduce duplication and make a consistent, auditable handoff. Mark noted efforts to identify whether records across LEAs belong to the same student and to trigger data movement when a student enrolls at a new LEA.

Presenters repeatedly stressed that the backpack is a subset of state reporting functionality, not an immediate replacement for the state’s legacy Utrecht processes. "It's a stepping stone towards us getting there," Mark said, adding that wholesale replacement will require phased testing and coordination with LEAs and vendors. Katrina said, "Cactus will go away," referring to another legacy component, but clarified the transition will be incremental and not an abrupt cutover.

Attendees pressed how state-to-LEA and LEA-to-state transactions will work; staff answered that the current approach prioritizes LEA-source edits and that auditing or state-side editing was intentionally scoped carefully to avoid creating data conflicts. Cliff (in the room) added that the backpack is primarily a reporting/source view and that source edits should remain at the LEA to avoid divergence.

Board process and policy questions surfaced: participants raised whether Utah should move to a single statewide SIS. Staff said the idea originated in an audit recommendation and will be discussed by the Board; a finance committee recommendation (reported as passing 3–1 at committee) will be presented to the full Board. A presenter explained a likely procurement approach would be a public RFP and vendor hosting rather than the state hosting a vendor platform directly.

Next steps: USIMS staff said they will continue beta testing university‑recommend workflows and the backpack features, run focused working groups and report monthly through regular PMRs. Staff flagged a legislative/implementation deadline tied to backpack rollout and asked LEAs to engage in ongoing focus groups so the phased rollouts meet reporting and compliance needs.