Out of sight for six months
An apprentice goes on maternity leave, or has a long illness, or their employer pauses the programme during a restructure. The coach agrees a break in learning, the data team records it, and the learner leaves the active caseload.
Six months later the learner emails to say they are back at work and ready to continue. The coach who agreed the break has moved on. Nobody knows what was agreed about the return date or what the learner had left to do. The training plan needs revising, the planned end date needs moving, the employer needs to confirm, and the e-portfolio has to be reopened. Other learners on break have not emailed at all, and are still sitting in a list nobody looks at.
Where breaks fall through the gaps
- Once on a break, the learner no longer appears in the coach's caseload view, so there is nothing to prompt contact.
- The expected return date is noted in the MIS or an email, but nothing acts on it.
- Coaches change, and the reason and agreement for the break go with the old coach.
- Restart needs several updates across systems, and there is no standard list of them.
- Employers are not asked whether the learner is coming back, so a quiet withdrawal looks like a break for months.
The cost of forgotten breaks
Learners who return to a disorganised restart lose confidence, and some leave for good. Learners who were never coming back sit in your data as on a break when they should have been withdrawn, which makes your numbers less reliable. And the rush to rebuild a training plan when a learner turns up unannounced takes coach time you had not planned.
Whatever your rules on breaks and their length, those decisions stay with your team and your funding adviser. The problem we address is the one of memory and follow-up.
How we build break tracking
- A break form records the reason category, the start date, the expected return date, what the learner had left to do, and the agreement with the employer, with any signed documents attached.
- Learners on a break appear in a separate list for each coach and for managers, sorted by expected return date.
- Check-in messages go to the learner and employer at intervals you choose, asking whether the return date still stands, with simple replies.
- A set time before the expected return, the case goes to the current coach with the notes, so the restart is planned rather than improvised.
- Returns follow a restart checklist: revised training plan, updated planned end date, employer confirmation, MIS and e-portfolio updates.
- If replies suggest the learner is not coming back, the case moves to your withdrawal process instead.
| Stage | What the system does | Who is involved |
|---|---|---|
| Break agreed | Records reason, dates and outstanding work | Coach, data team |
| During the break | Periodic check-ins | Learner and employer |
| Before expected return | Case raised with notes | Current coach |
| Restart | Checklist of plan and record updates | Coach, employer, data team |
| Not returning | Hands over to withdrawal workflow | Coach and manager |
What a return looks like with this in place
A few weeks before the learner's return date, their current coach gets the case: why the break was taken, which units were done, what was left and what the employer said. The coach books a restart meeting. The training plan revision is drafted from the notes, signed by all parties through the usual flow, and the data team gets a task to update the MIS on the agreed date.
Managers see all breaks in one list. When a check-in reply says the employer no longer has the role, the manager starts the withdrawal instead of finding the learner in an audit a year later.
Does this describe your breaks?
- You are not sure how many learners are currently on a break.
- Learners on a break sometimes return with no warning.
- The original reason for a break is hard to find.
- Restarts take weeks of back and forth.
- Some learners on a break have really left.