Topic
Withdrawals, breaks and restarts
How leaving is recorded, why the date matters as much as the fact, and where the line falls between a break in learning and a withdrawal.
Enough detail to do the job and hold a sensible conversation with MIS or Finance.
- Official requirement: Stated by the official funding document named in the sources for this page.
- FEFunding explanation: Our plain-English explanation. Helpful, but the official document is the rule.
- Worked example: An illustration of how the rule applies in one situation. Not a universal rule.
- Recommended good practice: Operational advice from FEFunding. Not itself a funding requirement.
The date matters as much as the fact
When a learner leaves, two things are recorded: that they left, and when.
The date has to be the learner's real last date of attendance, not the date somebody noticed or the date the form was processed.
The date closes the funding period for the aim, so a later date claims more funding. It can also change which achievement rate cohort the aim falls into.
Using the notification date rather than the attendance date is a systematic overstatement, and it is visible because the register says something different.
When a withdrawal is recorded changes both the funding earned and whether the aim counts in the achievement rate. Recording a withdrawal late is not a neutral administrative delay.
A learning delivery carries both a planned end date and, once the learner finishes or leaves, an actual end date. The planned date describes the intention at the start; the actual date records what happened.
Populate the actual end date with the genuine last date of attendance, set the completion status to the withdrawal value and record the withdrawal reason.
Measure the gap between actual end date and the date the record was updated, by curriculum area. That single measure turns an abstract data-quality problem into an operational one with an owner.
Break or withdrawal
A break in learning means the learner is expected to come back. A withdrawal means they are not.
The test is what is genuinely intended at the time, and whether there is evidence of it.
A break pauses earnings and preserves the aim so it can restart. A withdrawal ends earnings and enters the aim into the achievement rate as a non-achievement.
Where a break has run well beyond any realistic expectation of return, it has become a withdrawal that has not been recorded. Reviewing open breaks monthly is the control that prevents this.
A break in learning and a withdrawal are different events with different funding consequences. A break pauses the apprenticeship with the intention that the learner returns; a withdrawal ends it.
Record a break as a temporary withdrawal using the treatment for the stream, and record the restart when the learner returns so the aim is not treated as a new start.
An unflagged restart distorts start numbers, duration and the achievement rate cohort.
The notification problem, which is the real problem
Almost every withdrawal problem is a communication problem rather than a data problem.
Somebody in the college knows the learner has gone. The question is how long it takes that fact to reach the person who records it.
The measure that exposes this is simple: the gap in working days between the actual last date of attendance and the date the record was updated, reported by curriculum area. Most colleges have never produced it, and producing it once usually changes the conversation entirely.
A weekly report of learners with no attendance recorded for a defined period, sent to curriculum leads for confirmation, closes the loop from the other direction. It finds the learner who has quietly stopped coming without anybody raising it.
Both controls cost very little and between them they prevent the single most expensive data error in further education.
The corollary matters too: when a withdrawal is finally recorded with the correct earlier date, earnings restate across every affected period. Telling Finance before they see the movement is part of the job.
When a withdrawal is recorded changes both the funding earned and whether the aim counts in the achievement rate. Recording a withdrawal late is not a neutral administrative delay.
Each ILR return is a complete restatement of the funding year to date, not an increment. Every return replaces the last, which is why an error introduced late can change earnings already reported.
Instrument the gap between LearnActEndDate and the record update timestamp. Report the median and the tail by curriculum area, monthly. The tail is where the money is.
Pair it with a no-attendance report driven from the register system, so learners are identified by absence rather than only by notification. The two controls catch different failures.
Worked examples
Worked example
Six weeks late
A learner stops attending on 3 March. The withdrawal is recorded on 14 April with the date of recording.
- The overstatement. Six weeks of funding claimed for a learner who was not there.
- The evidence. The register shows no attendance after 3 March, directly contradicting the record.
- The correction. Reset the actual end date to 3 March. Earnings restate across the affected periods.
- The control. A weekly no-attendance report to curriculum leads would have caught it in week one.
A small, avoidable overstatement that an auditor would find immediately.
The funding effect depends on the stream and whether a qualifying period applies.
Common pitfalls
Using the notification date
What goes wrong: The actual end date is set to when the withdrawal was processed.
Consequence: Funding is overstated and the record contradicts the register.
Prevention: Always use the genuine last date of attendance from the register.
What this means for your role
Curriculum manager or head of department
Your register is the evidence. The date on it is the date that must be recorded.
- Notify within days, with the real last date of attendance.
See it play out
Scenario
An adult learner withdraws in week six
A learner on a fully funded adult qualification stops attending six weeks in. Follow it from the tutor noticing to the audit test.
Work through itScenario
An apprentice goes on long-term sick leave
An apprentice is signed off work indefinitely. Deciding between a break in learning and a withdrawal is a funding, performance and evidence decision all at once.
Work through itScenario
An apprentice changes employer mid-programme
An apprentice moves to a new employer and wants to continue the same apprenticeship. Several records have to change together.
Work through itScenario
A learner transfers to a different course in October
A learner decides the course is not right for them and moves to a different one. Two aims have to be handled correctly.
Work through itKnowledge check
Knowledge check
Withdrawals and breaks
3 questions. Nothing is recorded unless you are signed in, and there is no time limit.
Sources
These are the official documents this page rests on. Where a figure, a deadline or an exact rule matters, the document is the authority and this page is the explanation.
Content reused from GOV.UK is Crown copyright, used under the Open Government Licence. FEFunding is not endorsed by the Department for Education.