A text message on a Friday afternoon
The apprentice texts their coach: they have handed in their notice and their last day is next week. Or the employer emails to say the apprentice has been dismissed. Or, most often, nobody says anything. The learner stops logging hours, misses two reviews and stops answering the phone.
Whichever way it starts, the coach now has to tell the data team, update the e-portfolio, speak to the employer, confirm the last day of learning, and let finance know if the employer is invoiced. Some of these happen that week. Some happen when the monthly data check spots the learner has been inactive. The date recorded as the last day of learning ends up being whenever someone got round to it.
Why leavers are handled differently every time
- There is no single form or trigger. Each coach tells people in their own way.
- The steps involve several teams, and each assumes someone else has done theirs.
- The last day of learning is a judgement, and the evidence for it is scattered.
- Learners who drift away are never formally withdrawn until a report catches them.
- Nobody records the reason in a consistent way, so patterns across employers or standards go unseen.
Why slow withdrawals matter
Learners who have left but still show as active make your caseload numbers wrong and can put wrong data into your returns. Coaches carry learners they cannot contact, which hides their real workload. Finance may keep invoicing an employer for an apprentice who left, which does your relationship no good.
There is a lost learning opportunity too. If you cannot see why learners leave, you cannot spot the employer where apprentices keep leaving in the first months, or the standard where learners drop out before gateway. How you set the withdrawal date and what follows for funding is for your policy and your adviser; the system makes sure the facts are recorded promptly.
What we build for withdrawals
What we build is a single route for every leaver, started by whoever hears first.
- A short withdrawal form: learner, how you heard, the proposed last day of learning, the evidence for it (last logged activity, last review, employer confirmation) and a reason from your own list.
- The form pulls the learner's last activity dates from your e-portfolio and hours log, so the coach sees the evidence while choosing the date.
- A checklist is created with an owner for each step: MIS update, e-portfolio closure, employer confirmation, finance notification, learner exit contact.
- The employer gets a message asking them to confirm the leaving date, with a one-click reply.
- Each owner gets their task, and the manager sees any withdrawal with steps still open after a set time.
- Reasons are reported by employer, standard, coach and time in learning, so patterns show up.
| Step | Owner | Evidence kept |
|---|---|---|
| Withdrawal raised | Coach or whoever heard first | Form with source and proposed date |
| Last day of learning agreed | Coach and manager | Last activity dates and employer reply |
| MIS updated | Data team | Date updated and by whom |
| E-portfolio closed | Coach | Status change |
| Finance told | Finance | Invoicing stopped or adjusted |
A cleaner way to say goodbye
When a learner texts to say they are leaving, the coach fills in the form in a few minutes. By the end of the day the employer has been asked to confirm, the data team has a task, and finance knows. The manager can see all current withdrawals and which step each is waiting on.
Learners who drift are caught earlier, because inactivity raises a prompt to the coach to contact them and, if they cannot, to start a withdrawal. Each quarter your managers look at the reasons report and see which employers and standards need attention.
Could this be you?
- Withdrawn learners still appear as active in your MIS.
- Each coach handles leavers differently.
- The recorded last day of learning is often a guess.
- Employers are invoiced after their apprentice has left.
- You cannot easily say why learners leave.