Admissions
What families expect from admissions and enrollment
What families expect from admissions software: clear status, simple next actions, dependable deadlines, safe documents, accessible communication, and human help.
Families expect to know what happens next
A family should not need to email several people to learn whether an application was received, what document is missing, when a decision is expected, or what an offer requires. A status should answer the next practical question.
Define status, next action, deadline, message, sender, reply route, and correction path. Avoid labels that make sense only to internal staff.
Families expect safe and respectful handling
Applications can contain identity, guardian, document, assessment, financial, or welfare information. Families expect that the school will request only what is needed, protect it, and explain who can access it.
GOV.UK procurement guidance recommends data protection by design and default, minimum necessary data, access control, security, supplier accountability, incident notification, and end-of-contract handling.
Families expect exceptions to be possible
Test changed guardians, siblings, international contact details, inaccessible documents, late submissions, withdrawn applications, waitlist movement, and a family that cannot use the normal channel. Provide a human support route without encouraging uncontrolled email copies.
The U.S. Department of Education data governance checklist connects quality, access, security, lifecycle, sharing, disposal, and monitoring. Family experience and data governance should be designed together.
Measure the experience
Review unanswered questions, repeated requests, wrong messages, incomplete applications, access problems, support demand, response time, and the intended outcome at 30, 60, and 90 days. Do not infer satisfaction from portal logins alone.
Make the next action clear
Use this guidance to improve one bounded part of what families expect from 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.
