Admissions
What to measure after launching admissions and enrollment
What to measure after launching admissions software: completion, corrections, data quality, family experience, permissions, support, capacity, and the original outcome.
Return to the original outcome
Start with why the school changed the process: clearer status, fewer correction loops, faster document review, safer access, or a dependable enrollment handoff. Keep the original baseline, population, period, owner, and limitations.
Do not replace an outcome with a count of logins or records entered. Activity can rise while understanding or quality falls.
Measure completion and quality
Track completed applications, document review, decision approval, offers, acceptance, waitlist actions, enrollment, withdrawals, duplicates, missing values, corrections, and case age.
The U.S. Department of Education data-quality guidance connects business rules, validation, infrastructure, and professional learning. Investigate whether repeated corrections signal a rule, training, permission, or workflow issue.
Measure people and control
Review family questions, wrong messages, access exceptions, support demand, training gaps, temporary work, reconciliation, staff capacity, and supplier or integration issues.
GOV.UK procurement guidance recommends minimum necessary data, access control, security, suppliers, incidents, and end-of-contract handling. Include control measures rather than treating them as separate from performance.
Use a review cadence
At 30 days, fix obvious defects. At 60 days, improve definitions, support, training, or permissions. At 90 days, decide whether to expand, repair, narrow, consolidate, refresh, or hold. Record the evidence behind the decision.
Make the next action clear
Use this guidance to improve one bounded part of what to measure after launching 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.
