Material Filed Against the Student Record That Governs It

What you can do together

• File material against the student, class or term it belongs to, so access follows the record rather than the folder.
• Map staff roles to what each is entitled to see, rather than granting library access broadly.
• Let retention apply from the district's own schedule, expressed in terms PowerSchool already holds.
• Assemble what a records request needs with a workflow reading the record.

How it connects

Student, course and term records would come across from PowerSchool over its API, arriving as attributes on the media so an item belongs to a student, a class or a term. That is what lets access follow the record: material about a student is visible to the staff entitled to that student rather than to anyone who can reach the library.

Retention follows the same logic. A district's schedule is written in terms PowerSchool holds, so filing against those records lets retention apply on its own rather than being enforced by whoever remembers.

PowerSchool would stay the student information system. An engagement would settle two things specific to K-12 before anything is built: which staff roles map to which access, because a teacher, a counsellor and a district administrator are entitled to different things about the same student; and whether any of this material is a student record in the regulatory sense, since that changes what may be retained and who may see it. Both are policy questions rather than technical ones, and they belong at the start.