Decision matrix for admissions and enrollment

1. Define the decision

State whether the matrix supports investigation, pilot, purchase, configuration, integration, expansion, or replacement. Define journey, users, campuses, data, calendar, phase, outcome, and deadline.

Separate non-negotiable gates from weighted preferences. A convenient interface should not conceal a failed identity, privacy, access, family-visibility, recovery, or data-return test.

2. Use the same scenarios

Test incomplete application, duplicate, changed guardian, rejected document, decision approval, offer acceptance, waitlist, withdrawal, family access, and student handoff with every option.

Record expected behavior, observed behavior, manual work, owner, evidence, limitation, support route, and unresolved risk.

3. Score governance and delivery

Assess identity, data quality, roles, documents, approvals, publishing, exports, retention, deletion, recovery, suppliers, incidents, migration, training, support, and school capacity.

GOV.UK procurement guidance recommends minimum necessary data, access control, security, supplier accountability, incidents, and end-of-contract handling. The U.S. Department of Education checklist connects quality, access, security, lifecycle, sharing, disposal, and monitoring.

4. Score cost and reversibility

Include subscription, setup, migration, integration, payment, training, support, growth, internal effort, exports, retention, and contract-end costs. Ask whether the school can pause, export, correct, migrate, or replace the option safely.

5. Review after selection

At 30, 60, and 90 days, compare the selected option with the matrix using completion, quality, access exceptions, family experience, support demand, capacity, and the original outcome. Update the decision when evidence changes.

Turn the guidance into an admissions decision

Apply this guidance to one bounded part of decision matrix for school admissions software. Define the applicant or student journey, the people involved, the source of each value, the permission boundary, the evidence required, and the condition that pauses the next step.

Test a complete case and meaningful exceptions such as an incomplete application, changed guardian, duplicate student, withdrawn applicant, late document, waitlist movement, or transfer. Record what happened, who corrected it, and how the applicant received a clear status.

Keep vendor capability, school responsibility, legal advice, and measured outcome separate. If evidence is incomplete, narrow the claim and the rollout rather than treating an assumption as a promise.

Review the decision at 30, 60, and 90 days. Look at completion, data quality, response time, access exceptions, family experience, support demand, and the original outcome. Decide whether to expand, repair, consolidate, or hold.

Before approval, ask an accountable reviewer to challenge the strongest claim. Replace broad language with the exact evidence, population, date, and limitation the school can verify.

Make the final record readable to an admissions operator and a reviewer who was not in the project. State what passed, what remains manual, what is deferred, who owns the unresolved item, and how a family receives help without creating an uncontrolled copy of applicant data.

Keep the approved record beside its acceptance tests, support guidance, and change history. A new campus, role, field, calendar, supplier, or family-facing output can change the risk even when the original workflow appears unchanged.

Document the handoff to the next owner in plain language. A reviewer should be able to identify the approved definition, evidence, remaining limitation, support route, and date on which the school will decide whether to continue.

Keep a short record of what was tested and what was not. Ideal data and a successful screen do not establish readiness for transfers, changed guardians, late documents, staff absence, payment exceptions, or a new academic period. Name the next test and its owner.