Inspection readiness is not the same as quality culture

Header Image
SHARE

In this article: Why inspection readiness shouldn't be the goal in itself. We cover why evidence of activity isn't evidence of impact, the shift from quality assurance to quality improvement, inclusion as part of everyday practice, and where AI fits into quality oversight. | 6 minute read.



A provider that starts changing its processes because an inspection might be approaching has already put itself on the back foot. The problem isn't that the changes are wrong, it's that inspectors aren't simply checking whether a process exists. They are checking whether it's established, understood, applied consistently, and making a difference to learners. That last part, having an impact on learners, is difficult to demonstrate at short notice.

Inspection readiness isn't something a provider switches on a few months before an inspection window opens. The strongest providers are effectively ready all the time, not because they are constantly preparing for Ofsted, but because quality is embedded in how they normally operate.

Quality before Ofsted

The framing matters more than it might seem. If staff talk about quality activity internally as "getting ready for Ofsted", they will tend to treat it as a project with an end date. A more useful set of questions doesn't mention Ofsted at all. What does genuinely high-performing provision look like? What does sustainable quality look like, as opposed to quality that only holds up under scrutiny? How do leaders know whether the learner experience is improving, and how do they know where it still needs work?

The sector has been making improvements in recent years. Ofsted's chief inspector reported in his first annual review that apprenticeship quality is improving, with 81% of providers judged good or outstanding at their most recent full inspection or monitoring visit, 5% higher than at the same point in 2023. This is a genuinely encouraging sign, but it's also a lagging measure, reporting on judgements made after the fact. It says nothing about whether the improvement it captures was embedded or assembled for the occasion. Handled well, a strong inspection outcome becomes something that follows from the work, rather than the reason the work was done.

Embedded practice matters more than recent evidence

Take the example of an established quality board. It is not enough for an inspector to see the most recent set of minutes; what they are really after is a longer history of the board's activity, and beyond that, some sense of what impact it has had on the learner experience.

That's a distinction worth applying far beyond quality boards: evidence that something happened is not the same as evidence that it worked. A quality process only has value if it changes something for learners, and providers that focus their energy on documenting activity rather than tracking impact will struggle when asked the harder question.

That same gap between activity and impact also explains a pattern that can catch good providers off guard. A new initiative, even a well-designed one, may sit somewhere between "meeting expected standards" and "needing attention" simply because it hasn't had time to prove its impact yet. That isn't necessarily a sign that the initiative is wrong, it can simply be a reminder that impact takes time to show up, which is itself an argument for continuous improvement over reactive preparation.

From quality assurance to quality improvement

This is a distinction worth being precise about, because the two activities can look similar from the outside while pulling in different directions. Quality assurance is necessary, as it asks whether processes are being followed, however, it's backward-looking.

Quality improvement asks a different question, and that is, how good is the learner experience? What needs to improve? What are we changing? Did the change work? What do we improve next? This works as a continuous cycle rather than a periodic exercise: improve the learner experience, measure it, review it, and repeat. Providers that run this as an ongoing loop tend to find inspection uneventful, because inspection is simply someone else looking in on a cycle that was already turning before they arrived.

Let self-assessment do the honest work

Self-assessment reviews and continuous improvement plans are what drive this cycle. Used properly, they should identify what is working, where the weaknesses remain, what action is being taken as a result, and whether that action is producing impact. That fourth point is the one that some providers skip.

It changes the question leadership and governance should be asking themselves. Not simply "are we good?", but perhaps "how well do we understand where we could be better?" Few boards enjoy sitting with that question for long, and it's a reasonable line for a governance agenda in its own right.

Inclusion as part of quality rather than separate from it

Inclusion increasingly appears both as its own area of evaluation and as a thread running through the rest of the framework, which means it shouldn't be treated as a bolt-on exercise. This has been a consistent theme in Ofsted's recent reporting on apprenticeships, where strong overall quality judgements have sat alongside a clear steer that inclusion needs sharper attention. In everyday quality improvement, that means asking whether individual barriers to learning are properly understood, whether tutors are adjusting time, format, language, or delivery to the learner in front of them rather than delivering a standard session, and whether personal circumstances are being recognised in practice rather than worked around.

Knovia Group has introduced learner experience reviews that look across different stages of the learner journey, rather than relying on a single observed teaching session. It raises a question worth sitting with for any provider: it's easy to believe you're doing good things for learners, but how do you know how good they are?

AI creates new quality questions rather than removing them

AI-assisted marking and feedback tools can save real time, and that's a genuine gain for providers and learners, however, they don't remove the need for human quality oversight. AI-generated feedback can be inaccurate, wrong in tone, or insufficiently tailored to the individual learner and their learning programme. Good AI governance is the foundation of responsible innovation in this sector, not an afterthought bolted on once a tool is already live. The opportunity isn't to automate quality judgement away, it's to use the time freed up to focus more closely on accuracy, appropriateness, personalisation, and the specific needs of the learner in front of you.

Which brings us back to the idea running through this whole piece. Technology won't build a quality culture, and neither will an inspection. Both can only show you whether one already exists, which is exactly why the work has to happen long before either one arrives. 

 

 

 

<