Map the family’s journey before choosing screens.
Start with the stages your school actually uses: inquiry, follow-up, application, document review, assessment or waiver, offer, acceptance, enrollment and student-record handoff. Name the owner, expected evidence and next action for each stage. This reveals repeated data entry, informal approvals and unnoticed delays before the software is configured.
Owner
Who is accountable for moving the record forward, and who covers an absence?
Evidence
What must be complete, verified and time-stamped before the next stage?
Decision
Which outcomes are allowed, who can approve them and when is a reason mandatory?
Next action
What does the family or staff member need to do, by when, and through which channel?
Make progress mean evidence, not a label.
Swipe for more columns →
| Stage | Minimum evidence | Control question |
|---|---|---|
| Inquiry | Enquiry source, programme, relevant consent and next action with a due date | Can duplicate families be reviewed without silently losing history? |
| Application | Required fields, declared information and submission receipt | Does the application clearly identify the intended institution and programme? |
| Document review | Which document was supplied, review status, reviewer and any rejection reason | Can staff distinguish missing, pending, accepted and rejected evidence? |
| Assessment or waiver | Outcome, reviewer authority and waiver reason where applicable | Can an offer be blocked until the required decision exists? |
| Offer and acceptance | The terms accepted, earlier versions, decision, expiry and acknowledgement | Do revisions preserve earlier evidence instead of overwriting it? |
| Enrollment | Final checks, one student identity without duplicates and confirmation of the handover | Are the student record and enrolment link created together, so an incomplete enrolment cannot be recorded as complete? |
Test the difficult cases before go-live.
Most workflow failures occur when something does not go as expected. Ask teams to rehearse a duplicate application, unreadable document, assessment waiver, expired offer, changed programme, withdrawn acceptance and reversal of an enrolment. Define which actions are reversible, which require approval and what evidence must remain after a correction.
- Keep rejection and correction reasons structured enough to review later.
- Separate “needs information” from a final rejection.
- Prevent staff from bypassing stage requirements through direct actions.
- Require approval and a reason for reversing an enrolment or correcting a person’s identity.
- Never expose one institute’s applicants, files or exports to another institute.
Protect the boundary between admissions and student operations.
Enrollment is not complete when an application is merely marked successful. Confirm that the student identity, guardian relationships, programme placement and required documents reach the authorized student-record workflow together. The handoff should prevent duplicate creation, retain its source application and produce evidence that staff can audit without reopening sensitive data broadly.
- Confirm the accepted offer still matches the intended programme and intake.
- Resolve duplicate student candidates before creating a second identity.
- Create the student record and enrollment link as one controlled action.
- Record the actor, time, source application and resulting student reference.
- Verify the next operational owner can see the record within their institute and role.
Use a short readiness scorecard.
- Every open record has a named owner and dated next action.
- Every stage states what is needed to start, what must be complete to move on and how problems are handled.
- Approvals are enforced by authority, not shared instructions.
- Corrections preserve earlier evidence and reasons.
- Access limits between institutions apply to searches, files, downloads and automatic background tasks.
- Enrollment creates one complete, traceable student handoff.
If any answer depends on a spreadsheet, private message or one person’s memory, capture that gap as an implementation requirement before agreeing an implementation date.