Operations
What small schools should know about student records and enrollment data
What small schools should know about student information systems: proportionate scope, clear ownership, simple controls, limited capacity, and safe growth.
Choose the smallest useful boundary
Start with the decisions the school must support: identity, relationships, enrollment, class placement, attendance, history, contacts, documents, family communication, and reporting.
Name phase-one records, users, calendar, outcome, acceptance tests, and owner before considering a large feature set.
Make one person’s absence survivable
A small team may combine several roles, but the work still needs definitions, backup ownership, correction, approval, support, and leaver access. Document how staff handle duplicate, transfer, changed name, withdrawal, missing value, and family correction cases.
Keep procedures short and available to the person doing the work.
Use proportionate controls
Separate view, create, edit, approve, export, correct, archive, and delete. Control support access, exports, suppliers, incidents, backup, restoration, retention, and disposal.
GOV.UK school guidance emphasises accountable and secure handling. The U.S. Department of Education data-quality guidance connects reliable records with definitions, rules, validation, infrastructure, and professional learning.
Grow on evidence
Review completeness, corrections, duplicates, access exceptions, report confidence, support demand, family experience, staff capacity, and outcome at 30, 60, and 90 days. Add scope only after the smallest useful process works reliably.
Make the next improvement testable
Use this guidance to improve one bounded part of what small schools should know about student information system. Name the owner, record, evidence, correction route, and review date so staff can apply it consistently.
Check an ordinary record and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, validation rule, permission, training note, or support route.
Record what changed, what remains manual, and who reviews the result before the next reporting or enrollment cycle.
Keep the decision beside its evidence so the next operator can understand the rule without relying on informal memory.
Use the review to decide whether the change should be expanded, repaired, narrowed, or held.
