Product guides
What boarding schools should verify about school management, ERP, and SIS
What boarding schools should verify in management software across residential, academic, family, finance, and sensitive workflows.
Start with the boarding journey
Boarding operations connect settings that are often managed by different teams: admissions, academics, residence, health or safeguarding, family communication, activities, transport, and finance. A software review should follow a student through the relevant journey rather than assume that a common record makes every field visible to everyone.
Define the phase first. List the records, relationships, decisions, and outputs the school actually needs, then identify what must remain restricted or local.
Test relationships and boundaries
Ask what happens when a student changes house, guardian, class, campus, or status. Test the normal path and a correction. Record which team may view, edit, approve, publish, or export the information.
- Student and guardian identity
- Residential and academic assignment
- Family and emergency communication
- Fees, receipts, and reconciliation
- Sensitive data access and escalation
Verify high-pressure operation
Rehearse arrivals, departures, evening support, staff absence, changed guardians, payment exceptions, unpublished results, and family questions. The useful answer includes a controlled temporary route and later reconciliation, not a suggestion to share accounts or bypass permissions.
GOV.UK procurement guidance recommends data protection by design, minimum necessary data, access control, security, subprocessors, incident notification, and data return or deletion. The U.S. Department of Education data governance checklist adds lifecycle, quality, sharing, disposal, and monitoring prompts.
Keep claims evidence-led
Do not describe a product as a complete boarding or safeguarding system without verifying its actual scope. Record native behavior, configuration, integrations, manual work, roadmap, and unknowns. Obtain qualified local privacy and safeguarding advice before approving a release.
Make the next step specific
Use this guidance to improve one bounded part of what boarding schools should verify about school management software. Name the person who owns the decision, the record or workflow affected, the evidence needed, and the date for review. Keep the test small enough for operators to complete and specific enough for a later audit. Record the result, the next action, and the condition that would make the team revisit the decision.
