What boarding schools should verify about admissions and enrollment

Separate admissions from residential work

Boarding admissions may include application, assessment, interviews, guardian information, residential preference, welfare or medical evidence, offer, deposit, acceptance, house placement, arrival, and withdrawal.

Map which record belongs to admissions, records, finance, boarding, family communication, welfare, support, or another accountable owner. Do not combine sensitive information because it concerns one applicant.

Define relationships and access

Record parent, legal guardian, emergency contact, sponsor, and residential contact as distinct relationships where their access or communication differs. Test changed guardians, multiple contacts, international families, and inaccessible documents.

Specify view, create, edit, approve, publish, export, correct, archive, and delete rights for admissions, boarding, families, support, campuses, and suppliers.

Protect sensitive evidence

Ask how documents are collected, classified, reviewed, stored, corrected, retained, exported, and deleted. GOV.UK procurement guidance recommends minimum necessary data, access control, security, supplier accountability, incidents, and end-of-contract handling.

The U.S. Department of Education data governance checklist connects quality, access, security, lifecycle, sharing, disposal, and monitoring. Use qualified local advice for welfare, safeguarding, and privacy obligations.

Test arrival and support

Test offer acceptance, payment handoff, student creation, house placement, changed arrival, withdrawal, waitlist movement, missing evidence, family communication, and term or holiday support. Review quality, access, family experience, and support at 30, 60, and 90 days.

Make the next action clear

Use this guidance to improve one bounded part of what boarding 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.