What international schools should verify about admissions and enrollment

Separate global and local needs

List global standards such as applicant identity, core stages, security, reporting, and support. Then document local variation in calendar, curriculum, language, currency, documents, assessments, family communication, and legal requirements.

A shared platform is useful only when the school can explain what is central, what is local, and how the boundary is governed.

Test the cross-campus case

Test an applicant or student moving campus, a changed guardian, local evidence, a different academic period, an offer in another currency, and a family requiring another language. Record source, owner, status, permission, message, and handoff.

Ask what is shared, isolated, inherited, overridden, audited, exported, and supported. “Multi-campus” is a claim to verify, not an acceptance criterion by itself.

Verify data movement and support

Ask what crosses borders or supplier boundaries, why it moves, who can access it, how it is secured, which subprocessors are involved, and how incidents, exports, retention, and deletion are handled.

GOV.UK guidance recommends minimum necessary data, access control, security, supplier accountability, incident notification, and end-of-contract handling. The U.S. Department of Education checklist connects quality, access, security, lifecycle, sharing, disposal, and monitoring.

Keep local evidence visible

Assign campus and central owners, time-zone support, training, language review, calendar review, change approval, and escalation. Review transfer success, family experience, quality, access, support, and outcome at 30, 60, and 90 days.

Make the next action clear

Use this guidance to improve one bounded part of what international schools should verify about school admissions software. Name the owner, affected record, evidence needed, and review date. Keep the test small enough for admissions staff to complete and specific enough for a later audit.

Check both an ordinary application and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, training note, permission rule, or support route before calling the next step ready.