Stakeholder interview guide for admissions and enrollment

1. Prepare the interview

Define the decision, journey, phase boundary, calendar, current systems, outcome, and evidence question. Interview admissions, records, finance, leadership, teachers receiving handoffs, families, support, privacy, security, and suppliers as relevant.

Ask for a recent ordinary case and a difficult case. Real examples reveal work that a process diagram often omits.

2. Ask about current work

Where does the journey start and end? Who owns each stage? What values are required? Where do staff copy information, wait for approval, use private knowledge, or keep a second list? What does the family see and do?

Ask how applications, documents, decisions, offers, waitlists, acceptance, enrollment, and withdrawal are corrected, explained, and handed off.

3. Ask about exceptions and controls

Explore duplicate identity, changed guardian, rejected document, late reply, wrong offer, waitlist movement, withdrawal, denied family access, failed notification, and transfer. Ask who can view, create, edit, approve, publish, export, correct, archive, and delete.

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

4. Ask about change capacity

What training, data cleanup, migration, validation, support, communication, reconciliation, monitoring, and peak-period coverage can the school provide? What would make staff or families unable to use the new workflow safely?

Treat concerns about workload, access, status, documents, or family communication as design evidence rather than resistance to dismiss.

5. Record evidence and themes

Capture quote or observation, workflow, affected person, source, date, frequency, consequence, owner, evidence, limitation, and recommended next question. Separate one person’s preference from a repeated operational problem.

Keep legal advice, supplier claims, school responsibility, and measured outcomes distinct. Interview notes should inform a decision, not pretend to prove one.

6. Close the loop

At 30, 60, and 90 days, return to stakeholders with what changed, what remains manual, what was learned, and what decision follows. Ask whether the workflow is easier to perform, explain, correct, and support.

Turn the guidance into an admissions decision

Apply this guidance to one bounded part of stakeholder interview guide 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, the evidence behind it, the remaining limitation, the support route, and the date on which the school will decide whether to continue.