The gap after the counsellor marks a lead won
An admission is not operationally complete because a CRM card moved to a final column. The academic team needs the correct class and academic year. Accounts needs the agreed fee plan. The family needs verified access to the correct child. If each team re-enters the details, the handover can create several versions of the same student.
Design the CRM-to-school-ERP handover as a controlled process with a clear entry condition and a visible outcome. Do not use a marketing status as the only authority for creating financial or academic records.
Agree on the handover gate
The exact gate depends on the school’s policy. Some institutions collect a registration payment before final approval; others allocate a provisional place. Keep provisional, accepted and enrolled statuses distinct so parents and staff receive accurate information.
- Application information has been checked by an authorised employee.
- Required documents or approved exceptions are recorded.
- Branch, programme, class and academic year are confirmed.
- Fee plan and concessions have the correct approval.
- The institution’s admission conditions are satisfied and the approver is recorded.
Move the record through a defined sequence
| Step | Result | Check |
|---|---|---|
| Approve application | A recorded admission decision | Approver and timestamp exist |
| Create or link student | One institutional student identity | Retry cannot create a duplicate |
| Create enrolment | Branch, class and year mapping | The placement is active and valid |
| Apply fee plan | Approved financial schedule | Concessions match the approval |
| Invite parent | Verified access to linked children | No unrelated child is visible |
Do not use a phone number as the student ID
Phone numbers change, siblings share contacts and different guardians may use the same device. Keep institutional student identity separate from contact details. A student can have enrolments in different academic years without becoming a new person every year.
Store the relationship between enquiry, application and student so staff can trace the original source without copying the entire CRM history into every academic screen. Apply the same care to a branch transfer: moving an enrolment should not silently erase the previous history.
Design for retries and partial failures
An admission handover may stop because the connection drops after the student is created but before the parent invitation is prepared. A retry must resume or return the existing result, not create another student. Give staff a visible pending or failed state with a safe retry path.
Make actions that must stay consistent transactional where the platform permits. Keep external notifications separate from the admission decision: a failed email should be retried without repeating the financial or academic operation.
Test the exception cases
Use synthetic applications to test siblings, a changed email address, a rejected concession, a full class, an existing student returning for another programme and a network interruption. Check permissions by signing in as a counsellor, accountant, teacher and parent.
Success means each team sees the information it needs and can explain the outcome. It does not mean every employee can open the complete application or change the fee agreement. A connected workflow should reduce copying while keeping responsibilities separate.
Questions institutions ask
When should the ERP student record be created?
Create or link it after the institution’s defined admission approval gate, while keeping provisional applications distinguishable from active enrolments.
How should a school handle a failed parent invitation?
Keep the approved student record intact and retry the invitation separately. Verify the parent’s identity before granting access to the child.
Editorial note: This is a practical workflow guide. Examples are illustrative, not customer results. Product availability and institution-specific requirements must be confirmed separately.
← Back to all articles