Product guides
How to review school management, ERP, and SIS
How to review a school management software workflow after launch using evidence from quality, completion, support, access, family experience, and outcomes.
Review the promised workflow
Return to the workflow and outcome the school approved. Inspect the actual path from trigger to result, including the correction, denied-access, family-view, support, and reconciliation cases. A review should explain what people experienced, not only what the system recorded.
Use a controlled sample and a defined period. Name the reviewer, data owner, workflow owner, and decision maker before reading the results.
Check quality and control
Look for duplicates, missing values, stale relationships, corrections, unresolved exceptions, access issues, unapproved publication, and copies outside the intended workflow.
- Is the source of truth still clear?
- Can staff correct errors without bypassing controls?
- Are family and staff views appropriate to their relationships?
- Can support reproduce and resolve common issues?
- Are exports, retention, and deletion still understood?
Interpret measures carefully
Pair usage with completion, quality, support, and the original outcome. High activity can coexist with duplicate entry or poor data. Low activity may indicate a timing, access, training, or workflow problem rather than lack of need.
The U.S. Department of Education data-quality guidance emphasizes business rules, validation, infrastructure, and professional learning. Include those causes when deciding what to change.
Choose a review action
At 30, 60, and 90 days, choose a bounded action: validate a technical issue, improve training, clarify a definition, change a permission, repair a workflow, consolidate a copy, promote a proven path, or hold expansion.
GOV.UK guidance supports attention to data protection, access control, security, subprocessors, incidents, and end-of-contract data handling. Keep those controls in the review rather than treating launch as the end of responsibility.
Make the next step specific
Use this guidance to improve one bounded part of how to review school management software. Name the person who owns the decision, the record or workflow affected, the evidence needed, and the date for review. A short test with real operators is more useful than a broad claim that the whole school has been transformed.
