Admissions
Lessons from reviewing admissions and enrollment
Lessons from reviewing admissions and enrollment workflows: make ownership, evidence, status, permissions, family communication, and handoffs visible.
A queue is not a process
A long admissions queue may show demand, but it does not explain why cases wait. Review a sample from inquiry to enrollment and mark each handoff, missing value, approval, exception, and family message.
Look for work that happens outside the named workflow. Those hidden steps often explain delays, inconsistent decisions, and repeated questions.
Review the record, not just the screen
Check whether staff can tell which value is authoritative, who changed it, why it changed, and what other workflow depends on it. Review duplicate identities, document status, guardian relationships, offer dates, and enrollment conversion.
Use a controlled sample and record limitations. A clean demonstration case can conceal problems with incomplete applications, late documents, transfers, or changed family circumstances.
Review access and communication together
A family-facing status is both a communication and a permission decision. Confirm that families see only their records, that staff see what their role requires, and that approvals are distinguishable from drafts.
GOV.UK procurement guidance recommends data protection by design and default, minimum necessary data, access control, security, subprocessors, incident notification, and end-of-contract handling.
Turn observations into changes
For each finding, record the owner, correction, evidence, due date, and hold condition. Separate definition changes, data cleanup, training, permission changes, workflow configuration, supplier support, and product gaps.
Review the result after the next admissions cycle. Measure completion, corrections, response time, support demand, family experience, and the school outcome the change was meant to improve.
Make the next action clear
Use this guidance to improve one bounded part of lessons from reviewing 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.
