Admissions
How multi-campus teams coordinate admissions and enrollment
How multi-campus teams coordinate admissions and enrollment through shared standards, local ownership, transfers, permissions, calendars, support, and evidence.
Set the coordination boundary
Decide which standards are central and which are local. Shared identity, core stages, security, reporting, and support may be central; calendars, documents, languages, currencies, assessments, and messages may vary by campus.
Write the boundary beside the applicant journey so teams know who decides, who operates, and who receives the handoff.
Coordinate the transfer
Define how an applicant or student moves campus, what follows, who approves it, how guardian relationships are handled, and how documents, offers, decisions, and communications are preserved.
Test duplicate, changed guardian, transfer, withdrawal, waitlist, late evidence, and local-calendar cases. Record source, owner, permission, status, and reconciliation.
Coordinate people and support
Assign campus admissions, central records, leadership, family communication, privacy, security, integration, training, and support owners. Include time zones, leave, peak intake, incident communication, and change approval.
GOV.UK guidance recommends minimum necessary data, access control, security, suppliers, incidents, and end-of-contract handling. The U.S. Department of Education data-quality guidance connects rules, validation, infrastructure, and professional learning.
Coordinate evidence
Keep local test results, exceptions, approvals, and unresolved risks beside central decisions. Review completion, quality, access, support, family experience, transfer success, and outcome at 30, 60, and 90 days.
Make the next action clear
Use this guidance to improve one bounded part of how multi-campus teams coordinate 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.
