Student data backpack displays across schools

Summary#

SB 294, “Student Achievement Backpack,” would amend Utah Code section 53E-3-511. It failed and is not law. Its design is to give authorized users a continuing view of student information across schools and participating programs, while keeping the underlying data in the systems that already hold it.

  • The State Board of Education would have to use existing state and local education agency (LEA) systems to make the Backpack available by July 1, 2027. LEAs would have to work with the board to make it available for each student enrolled in them.
  • The board would have to procure a provider for the statewide system. The system must use a display-only interface, work across vendors and systems without favoring one, and generally not transfer or store student data. The bill allows limited transient processing or storage if the board expressly authorizes it and no existing system holds the information.
  • The Backpack would show information in five areas: enrollment, attendance, academics, student supports, and transcripts. Examples include contact details, absences, grades and assignments, test results, IEP and Section 504 status, credits, and progress toward credentials.
  • Authorized users would include students, parents while the student is enrolled, staff of an LEA providing instruction, and other users the board authorizes, including policymakers, subject to privacy laws. The board must limit staff access to information relevant to their role and lawful purpose.
  • The bill would make the originating LEA responsible for the accuracy and correction of its data. The board could not change or correct it, and a Backpack would not replace LEA reporting duties or student information systems.

What it means for you#

  • Students and parents: If enacted, students who are or have been enrolled in an LEA could access their Backpack; parents could access it while the student is enrolled. Parents could ask the LEA or school for help getting access.
  • Students and families: The display could include sensitive support information, as well as attendance, grades, assessments, and transcript details. The bill does not require families to apply for a service or make changes to existing reporting duties.
  • Teachers and LEAs: Staff at an LEA providing instruction could use relevant Backpack information to support instruction. LEAs would have to work with the state board to make the system available for their enrolled students. A data error would have to be referred to the LEA that supplied the information.
  • The State Board of Education: The board would have to maintain the Utah Student Record Store to support Backpack access and transfers between LEAs, put privacy and security measures in place, and procure a statewide system provider.
  • Vendors: A provider would be selected through Utah’s procurement process, but the system must not give a vendor or platform preference, exclusivity, or a technical advantage.

Money#

The bill appropriates no money, but it requires procurement and work by the state board and LEAs; no cost estimate is available.

  • The bill does not state the cost of the provider, staffing, implementation, or LEA work. No publicly available information about those costs is included in the supplied materials.
  • It does not set fees, fines, or a new tax.

What is unclear#

  • The current Utah Code was not supplied separately, so the comparison here relies on changes shown in the bill text and cannot be independently checked against current law.
  • The bill does not specify which postsecondary institutions or programs would participate, or how their information would be included.
  • The board may authorize limited transient processing or storage in a stated circumstance, but the bill does not set criteria or limits for that authorization.
  • The bill lists broad types of information, but does not explain how generated summaries or recommendations would be produced or checked.
  • It does not set detailed rules for access approval, user review, appeals, or reporting on privacy and security. The bill was not enacted, so its requirements are not in force.

Case for#

  • A display that draws from existing systems could give students, parents, and educators a broader view without creating another central store of student records.
  • A continuous view across LEAs and participating programs could make it easier to see a student’s progress when they change schools or pursue different programs.
  • Requiring the system to work across vendors and not favor one could reduce dependence on a single platform.
  • Keeping corrections with the originating LEA could preserve a clear source for resolving errors.

Case against#

  • The required display could bring together highly sensitive information, including support classifications, writing samples, attendance, and academic records. The bill leaves many access and oversight details to later decisions.
  • The bill requires a provider and work by public agencies without stating the cost or how those expenses would be covered.
  • A display-only system depends on the source systems for accuracy and updates. If information is missing or wrong there, the board cannot correct it through the Backpack.
  • The bill does not explain how participating institutions will supply information or how a user’s access will be limited across the many listed data types.