How work-based learning actually works

Rules and figures checked: 2026-07-25. Funding, tenancy and tax rules move — verify before relying on them.

About four months in, someone from the university sat down with me and my manager for a review, and asked me to talk through my off-the-job training hours. I had a vague idea that this was a thing. I had logged approximately none of it. What followed was a fairly gentle conversation and then an extremely unpleasant weekend reconstructing four months of my own life from a work calendar.

Everyone does this once. This article is my attempt to stop you doing it at all, because the mechanics of a degree apprenticeship — the part that makes it an apprenticeship rather than a part-time degree with a job attached — run on paperwork that nobody explains properly at induction.

One important note before anything else: the rules here changed in August 2025, and they had already changed once since I started in 2021. If you're reading this a year from now, check the current position rather than trusting me. I've said where to look.

The three-legged thing

A degree apprenticeship is a deal between three parties, and understanding that shape explains almost everything else.

You. Employee and student simultaneously. You have a contract and a student number.

Your employer. Pays you, gives you the work the learning is based on, and is required to release you for training.

Your training provider. Usually the university, sometimes a university plus a separate provider. They deliver and evidence the training, and they're accountable for the funding that pays for it.

That third party is the one people underestimate. Your provider has a direct financial interest in you meeting the training requirements, because funding depends on it. Which means that when something goes wrong on the employer side — you're not getting study time, your work has nothing to do with your standard — your provider is not a neutral bystander. They're the party with leverage. I'll come back to that.

The deal is written down in a document called the training plan, sometimes still called the commitment statement, agreed between all three of you at the start. It sets out what you're learning, over what period, what your employer has committed to, and how reviews work. Read yours. It arrives in the induction pile that everybody skims, and it's the only document that says in writing what your employer owes you.

Off-the-job training, and what it actually is

The central mechanism. An apprenticeship isn't just a job you happen to have while studying — a minimum amount of your paid working time has to be spent on training that teaches you new things related to your standard, rather than on doing your job.

Three parts to that definition, all of which matter:

New learning. It has to teach you knowledge, skills or behaviours that are part of your apprenticeship standard. Getting better at your existing job by doing it doesn't count.

Relevant to the standard. Your standard is a published document listing the knowledge, skills and behaviours (everybody calls them KSBs) you're expected to have by the end. Training has to map to it.

In your paid working hours. This is the protection people don't realise they have. Off-the-job training happens during your normal working hours as part of your paid time. If it has to happen outside them, you should be paid for it or given the time back. It is not something you do in your own evenings out of goodwill.

The last one is worth repeating because it's the single most misunderstood thing about the whole model. Your study time isn't a favour your manager is doing you. It's a condition of the funding your employer's apprenticeship is drawing on.

How much, and where to find your number

This is the bit that changed.

Until recently the requirement was expressed as a rate: a full-time apprentice had to average at least six hours a week of off-the-job training over the programme. For apprentices starting from 1 August 2025, that's been replaced by a total number of hours set individually for each apprenticeship standard. It's a fixed figure for the whole programme rather than a weekly rate, and providers have more freedom about how they spread it.

So the useful question isn't "what's the rule" any more. It's "what's the number for my standard", and you can look it up. Every standard's page on the Skills England apprenticeship search shows its minimum hours for compliance, alongside the level, funding band and typical duration. Our own course pages pull from the same source if you'd rather browse by level.

To give you a sense of scale: across the Level 6 and 7 standards currently approved for delivery, the minimum ranges from a couple of hundred hours to over two thousand, with most multi-year degree apprenticeships landing somewhere between about 550 and 1,000. The digital and technology solutions standard, a common four-year Level 6 route, sits at 1,022 hours over a typical 48 months.

Do that division, because it's clarifying. A thousand-odd hours across four years is roughly 250 hours a year, or something in the region of five to six hours in an average working week. That is the floor, and it is nowhere near enough time to do a degree in. The rest comes out of your evenings, your weekends and, at exam time, your annual leave. Anyone who tells you a degree apprenticeship fits neatly inside working hours has not done one.

There's also a floor on reductions: if you've got relevant prior learning — a foundation degree, relevant qualifications, real experience — your hours can be reduced, but not below 187 hours of evidenced delivery or eight months of actual duration. For a school leaver starting at 18, this almost never applies.

If you want the underlying rules rather than the summary, they're in the apprenticeship funding rules on GOV.UK, which are republished each academic year.

What counts and what doesn't

This is where people lose hours they've genuinely earned, by not realising something counted.

Generally counts:

• Lectures, seminars, workshops and residential block weeks
• Time spent writing assignments and doing the reading behind them
• Shadowing someone doing something you don't yet know how to do
• Structured mentoring or coaching on the KSBs in your standard
• Relevant e-learning and professional training courses
• Industry events, site visits and conferences relevant to your occupation
• Practical training in a new skill, even at your own desk, as long as it's training rather than production

Generally doesn't count:

• Your ordinary productive work, however much you learn from it
• English and maths qualifications up to Level 2 — these sit on top of your off-the-job hours, not inside them
• Progress reviews and the administrative machinery of the apprenticeship itself
• Initial assessment and general onboarding — the first-week induction stuff in your first week as a degree apprentice is mostly not training in this sense
• Training unrelated to your standard, however good it is
• Anything you did in your own unpaid time

That final exclusion is the one that stings, because it means the Sunday you spent on an assignment doesn't help your compliance figure even though it absolutely happened. The answer isn't to stop doing Sunday work — you will do Sunday work — it's to make sure the hours you're entitled to during the week actually get taken and logged, rather than quietly surrendered to a busy period.

Grey areas exist and vary by provider. Ask your skills coach where the line sits at your institution, early, once, and then apply it consistently.

The evidence log, and the twenty minutes that save you

You'll be given an e-portfolio system. There are a handful of the same products in use across the sector, and they are all, without exception, a bit clunky. Into it goes a running record of your off-the-job hours: what you did, when, how long, and which KSBs it relates to.

Everything about that system is designed for the person auditing it, not for you, which is why nobody keeps up with it. Here's what actually works, and it's the single most useful habit on this list:

Twenty minutes, same slot, every week. Mine was Friday afternoon, when the work had gone quiet. Log the week while you can still remember it. Twenty minutes weekly is about fifteen hours across a four-year degree. Reconstructing it retrospectively costs far more than that and produces worse evidence.

Some things that make those twenty minutes better:

• Write it in the language of the standard. Not "went to a workshop" but "attended a workshop on X, which developed K4 and S7 because…". The person reviewing it is mapping to KSBs; do the mapping for them.
• Say what you learned, not what happened. "Shadowed a colleague" is worth nothing. "Shadowed a review meeting and learned how the sign-off process handles exceptions" is evidence.
• Keep your own copy. A plain document in your own storage, alongside the official system. Portfolio platforms change, providers change, access gets revoked when you finish. Your record shouldn't live only in someone else's software.
• Save artefacts as you go — anonymised. This is where the apprenticeship collides with your employment contract, and it matters. Real client names, real figures and internal documents do not go into a system your university can see. Strip identifying detail properly. Your contract's confidentiality rules run straight through your coursework, and getting this wrong is a genuinely serious problem rather than an academic one.

Tripartite reviews

Every couple of months you'll sit down with your manager and someone from the provider — a skills coach, a practice tutor, a work-based learning tutor, the title varies. This is the tripartite review, and it exists to check the deal is being honoured on all three sides.

They'll look at your hours, your progress against the KSBs, how the academic side is going, and whether your work is actually giving you the experience the standard requires. Then everyone signs something.

It's tempting to treat these as a box-ticking interruption. Two reasons not to.

First, it's the formal, minuted place where you can raise a problem. If you aren't getting your study time, if your role has drifted somewhere the standard doesn't reach, if you're drowning — this is the meeting designed to catch that, with the one person in the room whose organisation has an interest in fixing it.

Second, the review record is your paper trail. If something goes wrong in year three, the existence of a documented pattern is worth a great deal more than your recollection of it.

Come with a number, a couple of examples, and one thing you want changed. Fifteen minutes of preparation makes you look like the most organised apprentice on the programme, which is a very cheap reputation to acquire.

When your employer doesn't give you the hours

It happens, and pretending otherwise would be dishonest. Busy period, short-staffed team, a manager who's never had an apprentice before and quietly believes the studying is your own business. Usually it isn't malice; it's a manager who was never briefed.

Handle it in this order.

Ask directly, and put it in the calendar. Most of the time this is the entire fix. A recurring blocked slot in your work calendar, agreed with your manager, is worth more than any amount of intention. "Which afternoon works for you?" is a better question than "would it be alright if…".

Escalate to early careers. If your employer runs a cohort, there is a team whose actual job is the apprenticeship working. They talk to managers about this constantly and it's not a complaint, it's their remit.

Tell your provider. This is the leverage. Your provider is accountable for you meeting the training requirements, and a systematic failure to release you is their problem as much as yours. Raise it at a review.

What not to do is absorb it silently for a year and then discover at gateway that you're short. The hours are a condition of the funding, not a nice-to-have, and the system genuinely does have teeth — but only if someone knows.

Where all this is heading

Everything above is building towards one moment. At the end of the practical period you go through gateway — a check that you've completed the required training, hit your hours, and are ready — and then into the end-point assessment, which is the formal, independent assessment against your standard. That, not the degree, is what makes you a qualified apprentice. What the qualification is worth explains how the two sit together, and how it all looks on a CV afterwards.

Which is the reason to care about a clunky logging system in year one. Gateway is where four years of evidence gets checked, and there is no way to reconstruct a portfolio in the fortnight before it. The people who found the end of the programme calm were, in every case I saw, the people who'd spent twenty minutes a week for four years being slightly boring about it.

Twenty minutes. Same slot. Start in week one, before there's anything to write down.