What does good work-based learning design look like?

Work-based learning is moving to the front of the conversation in police L&D, partly because the January 2026 White Paper signals a deliberate move away from classroom-only training. But 'work-based learning' is loosely used, and most of what's labelled work-based learning isn't designed at all. This piece sets out what good design actually involves: the structural components, the supervisor capacity required, and the practical considerations for operational environments.

The training simplification direction in the January 2026 White Paper has pushed work-based learning to the front of the conversation. Forces are being asked to deliver more learning in operational settings; suppliers are being asked to design for it. The direction is sound, but the execution is harder than it looks.

What work-based learning is (and isn't)

Work-based learning is structured learning that happens through, and as part of, real work. The 'structured' word matters. Three things distinguish it from unsupported on-the-job experience:

• Designed encounter with new material, not just repetition of what the learner already does
• Structured reflection points that turn experience into learning
• Active support from someone (usually a supervisor or experienced colleague) who knows what the learner should be noticing

Without all three, what's happening is exposure rather than learning. Officers who do a thousand stop and searches without structured reflection don't necessarily get better at stop and search; they get more practised at how they currently do it.

The classical experiential learning models (Kolb, Schön, Lave and Wenger) all converge on the same principle. Doing the work generates the raw material. Reflection, supported by someone who can frame what's there, turns that material into capability. Without the second part, the first part doesn't accumulate.

This is not a difficult concept. It is, however, regularly missed in implementation — not because people don't inherently understand that reflection is important — but in a sector where you are rarely, if ever, in control of demand, time to reflect is often the first thing that comes under pressure to be dropped in the face of operational need — which is entirely understandable — but is a serious design constraint that should guide all design decision-making.

The design considerations that actually matter

Five things determine whether a work-based learning programme delivers.

1. The work has to contain the right challenges. Learners need genuine exposure to the kinds of situations the learning is meant to develop. If a programme on vulnerability awareness puts a learner in a role where they encounter one safeguarding case a quarter, the rate of practice is too low for the learning to land. The work environment is part of the design surface, not a neutral backdrop to it.

2. The reflection has to be protected. Time for structured reflection has to be in the schedule, not on top of it. If reflection only happens when operational pressure allows, it stops happening. Examples of structured reflection that work: a fortnightly twenty-minute conversation between learner and supervisor, anchored by two or three set questions about specific situations the learner has handled; a written reflective log reviewed monthly; a peer-paired conversation cycle. The forms vary. What matters is that the time, the structure, and the supervisor engagement are designed in rather than assumed.

3. The supervisor has to be equipped. First-line supervisors (sergeants, team leaders, mentor practitioners) are the critical component. They need to know what the learner is supposed to be learning, how to recognise it in practice, and what questions to ask. Equipping supervisors usually costs more time and design attention than equipping the learners.

4. The assessment has to look at outcomes, not inputs. What evidence will the programme look for to know it's working? Number of reflection sessions completed is an input. Change in how the learner handles particular situations is an outcome. The assessment design tells the participants what the programme is actually about.

5. The accreditation has to recognise what the learner has done. If the programme leads to a qualification or licence (relevant given the white paper's Licence to Practise direction), the evidence requirements need to be designed alongside the learning programme rather than bolted on at the end. Retrofitting evidence requirements onto work-based learning is the most expensive way to do it.

The supervisor layer

Most work-based learning programmes succeed or fail at the first-line supervisor level. The supervisor is what makes work-based learning structured rather than incidental.

This is the bit that most operational organisations under-resource. The implicit theory is that supervisors will absorb the supporting role into their existing job. They don't. Without time, structure, and their own learning support, supervisors revert to the operational priorities they're judged on, and the learning support drops out.

When a force commissions a work-based learning programme without commissioning supervisor capacity alongside it, the programme will almost always under-deliver. This is not a comment on the quality of the learning design. It is a comment on the commissioning gap.

A useful commissioning question: who is going to support the learners, and what is the supervisor preparation programme that goes alongside? If the answer is 'their existing line manager, no extra preparation,' the programme has a structural weakness before delivery starts which needs to be supportively addressed.

How to know if work-based learning is actually happening

Three quick tests.

Ask a learner what they did differently last week as a result of the programme. If they can describe a specific change, the programme is working. If the answer is general or generic, the reflection layer isn't doing its job.

Ask a supervisor what they noticed about the learner in the last fortnight that they wouldn't have noticed without the programme. If they can name something specific, the supervisor layer is engaged. If they can't, the supervisor layer isn't actually there.

Look at the operational metric the programme is meant to influence. Work-based learning that doesn't change the work signal is not working, regardless of how engaged the participants feel.

What this means in practice for policing

The white paper's direction is right. The classroom-only model is not how most adults best build operational capability. Moving more of police development into work-based formats is sound in principle.

The risks lie in implementation. Three are worth naming.

First, 'work-based' will be used by some forces, often as a result of a highly challenging fiscal environment, to mean 'we no longer pay for the classroom time, the learning happens by osmosis.' That is not work-based learning. That is reduced training, presented as a method. This creates real risks.

Second, the supervisor capacity required to make work-based learning work is substantial, and the white paper acknowledges first-line supervision as an issue without yet resourcing it. The success of work-based learning in policing will depend in large part on whether forces invest seriously in the sergeant and inspector layer.

Third, work-based learning is not cheaper than classroom learning. It often costs more, because the time of multiple operational staff is involved alongside the learner's time. The argument for it is quality of outcome, not unit cost. Procurement processes that treat it as a cheaper alternative will produce thinner programmes.

Designed well, work-based learning produces better operational change than classroom-only training. Designed badly, it becomes a cheaper way to deliver less. The white paper direction is sound; whether forces and providers can land it in practice will depend on how much honesty there is about what good design actually requires.