What happens at the end of the programme
Rules and figures checked: 2026-07-25. Funding, tenancy and tax rules move — verify before relying on them.
Everything about a degree apprenticeship is heavily structured for four years and then, quite abruptly, isn't. The programme has dates, deadlines, reviews and a defined shape right up until the moment it stops — at which point you're just an employee, and nobody sends you a plan.
The people who came out of it best in my cohort had started thinking about the ending about a year before it arrived. The people who found it stressful mostly hadn't. This article is what's actually coming, in roughly the order it comes.
One note on terminology, because it's changing. What I went through was called end-point assessment. From 2025 through 2027 that's being replaced by "apprenticeship assessment" — assessment that can happen at points during the programme rather than only at the end — with end-point assessment organisations becoming "assessment organisations" and a new Ofqual framework from spring 2026. Existing apprentices stay on their current standard version until a revised one goes live, so if your paperwork says EPA, that's why. The shape of what follows holds either way.
Gateway: the checkpoint before the assessment
Before you can be assessed, you go through gateway — a joint check by your employer and your training provider that you're ready.
What has to be true: you're occupationally competent, you've evidenced or passed any English and maths requirements, you've completed the mandatory training, you've taken any qualifications set out in your standard, and you've met the minimum duration for your apprenticeship.
Two practical things about gateway.
It's where four years of record-keeping gets checked. Everything I said about keeping an off-the-job log in how work-based learning actually works exists for this moment. There is no way to reconstruct a portfolio in the fortnight beforehand, and the people who found this stage calm were, without exception, the ones who'd been boringly consistent about it since year one.
It can slip, and that's usually fine. If your degree results are late, or you're short on something, gateway moves. It's an administrative date, not a verdict.
The assessment itself
What follows varies by standard — your assessment plan sets it out precisely, and you can look yours up on the Skills England site or via our course pages. Common components include a project or portfolio-based piece, a presentation, and almost always a professional discussion: a structured conversation with an independent assessor about your own work and evidence.
The professional discussion is the part people underestimate. It isn't a viva on the academic content — it's someone qualified asking you, in detail, about work you actually did, with follow-up questions. You cannot revise your way through material you never learned, which is the point I made in AI and apprenticeship coursework and which becomes very concrete here.
Preparing for it is mostly re-reading your own evidence and being able to talk about each piece: what you did, why, what you'd do differently. A couple of practice runs with your skills coach are worth more than any amount of solo reading.
And if it doesn't go well: resits and retakes exist, the guidance says grades shouldn't be capped unless there's a justifiable industry reason, and your employer is expected to cover resit costs — apprentices aren't responsible for them. Failing a module, resits and splitting a year covers all of that properly.
The certificate, and how long it takes
Once you've passed, your assessment organisation requests your apprenticeship certificate from the Department for Education, which usually posts it within about ten working days of approving the request.
So there's a gap. You finish, you pass, and then for a few weeks you have nothing physical to show for it. That's normal. Nobody at work is waiting on the certificate — you can say you've completed and passed from the day you get your result.
Your degree comes separately, on the university's timetable, with a graduation ceremony months later. Go to it. The compressed, odd, working version of a degree doesn't come with many ceremonial moments, and I'd have regretted skipping the one it does have.
The employment transition
Here's the thing that confuses people: the apprenticeship ends, and your employment doesn't.
The apprenticeship agreement is a separate arrangement layered on top of your employment contract. When the programme completes, that layer falls away — no more off-the-job training entitlement, no more tripartite reviews, no more skills coach — and what's left is an ordinary employment contract that continues exactly as before.
In practice, you move into a defined role at a defined grade, which is where the substantial pay step happens. What degree apprentices actually earn has the numbers; one publicly advertised programme goes from £22,357 in year one to £44,367 on completion, which is at the dramatic end but not absurd.
Two things worth knowing: check whether anything else changes with your contract at the same time — notice period, benefits eligibility, bonus scheme membership often shift when you come off a programme. And get the new terms in writing before you accept.
Start on the landing role a year out
This is the single most useful thing in this article.
The role you move into is not usually assigned to you by a process. It's shaped by conversations, availability and who's been visibly good at what — and most of that happens in the twelve months before you finish, while you're busy with a dissertation and not paying attention.
What to do, roughly a year out:
Ask the direct question. "What happens to apprentices at the end of this programme, and what roles have people gone into?" Ask your manager, and ask early careers. You'll get a genuinely useful answer, and asking marks you as someone planning rather than drifting.
Work out what you actually want. Four years in, you know which parts of the job you're good at and which parts you'd be happy never to do again. That's real information most 22-year-olds don't have. Use it.
Make it known. If there's a team you want to join, say so, to the person who'd make that decision, well in advance. Roles get filled by people who expressed interest six months earlier.
Get breadth if you're short of it. If you've been in one team for four years, a secondment or a cross-team project in your final year widens the options considerably.
Don't let the degree eat the year. The final academic year is heavy and it's tempting to defer all career thinking until it's over. By then the decisions have been made.
Negotiating
You can negotiate the post-programme offer. Most apprentices don't, because they've spent four years being the junior person and it doesn't occur to them that the number is negotiable.
It is. In one publicly posted account from a finishing apprentice, an initial landing-role offer of around £36,000 was renegotiated to £50,000 for the same role. That's one person on a forum rather than typical, and it establishes the principle: the first number is a proposal.
How to do it without it being uncomfortable:
- Know the market rate for the role you're moving into, not for "apprentice". You're being priced as an employee now. Job adverts for equivalent roles are your evidence.
- Lead with the case, not the ask. What you've delivered, what you know that a new hire wouldn't, and the fact that you require no onboarding.
- Ask once, politely, and be specific. "Based on what similar roles are advertised at, I was hoping for X — is there room?" A single clear question is much more effective than hedging.
- Remember your position is stronger than it feels. You are a fully trained employee who knows the organisation, whom they've invested four years in, and replacing you costs far more than the gap you're asking for.
The worst outcome is a polite no, and asking well doesn't damage anything.
Whether to stay
The default is to stay, and for good reasons — you know the place, you're about to get a substantial rise, and it's comfortable. That default is right for plenty of people. It was for me.
Reasons to stay: the pay step is real, your track record is here and legible, and you'd be starting from zero context somewhere else. Reasons to consider leaving: the biggest salary jumps in most careers come from moving, your bargaining position will never be better than immediately after qualifying, and four years in one organisation at 22 is a narrow base if you have no idea what else exists.
Two things to check before you decide anything.
Clawback clauses. If your employer funded professional qualifications, there may be a repayment agreement tied to a leaving date, as I flagged in professional certifications alongside the degree. Read it before you resign, not after. Apprenticeship training itself is funded through the levy system rather than by your employer directly, so it doesn't usually work this way — but qualifications bolted on alongside frequently do.
Give it a year, if you're unsure. A year in the post-programme role gives you a job title that isn't "apprentice", a salary that reflects it, and a much stronger position in the market. There's rarely a good reason to leave the week after finishing.
And if you do leave — you're not letting anyone down. Employers running these programmes know a proportion of each cohort moves on, and it's priced in. Leave properly, work your notice, and stay in touch; the network you keep is worth more over a career than any individual job.
How the qualification travels
If you leave, what you take is: a degree from a named university, identical to the one anyone else on that course received; a completed apprenticeship at Level 6 or 7; and four years of full-time professional experience.
On a CV, the degree goes under education exactly as a campus degree would, and the four years go under employment. That combination — a 22-year-old with a degree and four years' experience — is unusual enough to be an advantage in most recruitment processes. What the qualification is worth goes into how it's regarded and how to present it.
The one thing worth doing before you leave any employer: keep your own copies. Your certificate, your degree transcript, a copy of your portfolio with anything confidential stripped out, and the contact details of people who'd speak for you. Access to internal systems goes the day you leave.
The bit that's genuinely strange
For four years, something has structured your time. Deadlines, block weeks, reviews, a cohort moving through it with you. Then it stops, and there's a Monday that is just a Monday.
Two things happened that I wasn't ready for.
The cohort disperses properly. People move teams, move cities, move employers, move in with partners. The group that had been the entire architecture of your social life since you were 18 stops being a group. That's a real loss and it arrives at the same moment as the good news, which makes it confusing.
You get your evenings back, and don't know what to do with them. Ten to fifteen hours a week, returned all at once. I spent about two months not really using them. It's worth deciding in advance what those hours are for — a professional qualification, a hobby, a side project, or genuinely just rest, which is a legitimate answer after four years of this.
The overall feeling, though, is odd and good: at 22 you have a degree, no debt, four years of experience, a real salary and an entirely open decade. Almost nobody gets to that point with all four. Whether that trade was worth it is the subject of the last article on this site.