What international schools should verify about school management, ERP, and SIS

Verify what is truly shared

A common brand does not mean every campus uses the same academic periods, curriculum, fee process, language, family communication, or data rule. List global standards separately from local requirements before comparing vendors.

A shared student identity can be valuable, but only when the school can explain which data follows the student, which remains local, and who approves a transfer or correction.

Test the cross-campus edge case

Ask the vendor to show a student changing campus or academic period. Include a changed guardian, archived record, fee or currency difference, local family view, and transfer. Record which campus can see, edit, approve, publish, or export each value.

• Identity and relationship ownership
• Calendar and period mapping
• Local and central permissions
• Family communication and language
• Transfers, exports, retention, and support

Verify privacy and support locally

GOV.UK procurement guidance recommends checking responsibilities, security measures, staff access control, subprocessors, breach notification, and deletion or return. Adapt those questions with qualified advisers to every jurisdiction in which the school operates.

Ask who supports each campus and time zone, how a local issue reaches central support, how a central change reaches local owners, and how an incident is communicated. A global contract does not prove a local operating model.

Keep evidence by campus

Store local test results, exceptions, owners, and approval beside the global decision. Review the records at each phase gate. This avoids forcing every campus into an unsafe rule or allowing every campus to create an undocumented private system.

Make the next step specific

Use this guidance to improve one bounded part of what international 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, next action, and condition that would make the team revisit the decision.

Check the result against an ordinary case and one meaningful exception. If either case depends on undocumented knowledge, add the missing definition, training note, permission rule, or support route before calling the change ready.