Admissions
Signals teams have outgrown admissions and enrollment
Practical signs that admissions teams have outgrown email and spreadsheets, and how to decide whether the next step is process repair, better controls, or new software.
Look for repeated reconstruction
A team may have outgrown its admissions process when staff repeatedly search email threads, ask one person for the latest status, re-enter applicant data, or maintain a private list of missing documents. The signal is not volume alone; it is the cost of recovering context.
Review a sample of applications from inquiry to enrollment. Count handoffs, duplicate entries, unclear owners, corrections, delayed replies, and cases that cannot be explained from the official record.
Separate process pain from tool pain
A new system cannot repair an undefined status, unclear decision right, poor data rule, or missing support route by itself. Write the desired workflow and control before deciding whether software is the answer.
If the process is sound but the current tool cannot enforce roles, preserve evidence, connect the student handoff, or give families a dependable status, the evidence for evaluating alternatives becomes stronger.
Use a safe threshold for change
Set a threshold based on missed deadlines, correction effort, access risk, family confusion, reporting reliability, and the school’s capacity to implement change. Do not buy because a competitor has more features or because a busy season feels uncomfortable.
GOV.UK procurement guidance recommends minimum necessary data, access control, security, supplier accountability, and end-of-contract responsibilities. Include these controls when assessing whether the current process has become unsafe.
Make the next action clear
Use this guidance to improve one bounded part of signals teams have outgrown 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.
