Product guides
A plain-language look at school management, ERP, and SIS
A plain-language explanation of school management software, the records and workflows it may connect, and the questions a school should still answer itself.
Start with the school’s work
School management software is easier to understand when it is described through work rather than a catalogue of modules. A school receives an application, creates or confirms a student record, assigns classes, records activity, manages fees, communicates with families, and reviews outcomes. Software can support parts of those journeys, but the school still defines the rules and owners.
The first question is therefore not “Which system has the most features?” It is “Which recurring decision should become clearer, safer, or less repetitive?” That question creates a useful boundary for evaluation.
Understand the connected record
A connected record does not mean that every user sees every field. It means the school can state which record is authoritative, which values are reused, when a change becomes effective, and how a correction is recorded. A teacher, finance user, administrator, and family may each need different views of the same student relationship.
Ask where identity, class, academic period, fee, attendance, assessment, document, and communication values originate. Then ask who may view, edit, approve, publish, export, or archive them.
Separate capability from responsibility
A platform may provide a workflow, while the school owns data preparation, policy, permissions, training, support, and reconciliation. A vendor answer that says “yes” does not explain how the school will operate the result on a busy day.
- Available now, or dependent on configuration?
- Connected to another system, or manually re-entered?
- Who approves a change or published result?
- What happens when data is incomplete or duplicated?
- What evidence will prove the workflow works?
Use evidence before making a claim
GOV.UK procurement guidance recommends data protection by design, minimum necessary data, access control, security measures, supplier responsibilities, incident handling, and end-of-contract data management. The U.S. Department of Education’s data governance materials provide useful prompts on quality, access, security, lifecycle, sharing, disposal, and monitoring.
These sources help a school ask better questions; they do not prove that a particular product meets local requirements. Keep product claims, legal conclusions, and measured outcomes separate until each has been reviewed.
