Writing Progress Reviews That Hold Up Under Ofsted Scrutiny

Last updated: 23 May 2026

Why most progress reviews fail Ofsted scrutiny

Progress reviews are the most-written, least-respected artefact in an apprentice's file. Most providers run them every 8–12 weeks, tick the compliance box, and move on. Then an Ofsted inspector pulls 10 learner files in a deep dive, opens the reviews, and the quality-of-education judgement quietly slides toward Requires Improvement.

The cause is almost never that learners aren't progressing. It's that the review on paper doesn't show that they are. Inspectors read reviews looking for evidence of genuine, KSB-linked progress against the apprenticeship standard. What they typically find is a friendly pastoral conversation written up as bullet points — how the apprentice is feeling, what they did at work last month, whether they're enjoying the programme. Pleasant, but not evidence.

This guide is the framework we use with providers preparing for inspection. It works for any standard, any sector, and doesn't require new software — just a different idea of what a review is for.

What Ofsted actually checks

Inspectors don't read every review in every file. They sample. In a typical apprenticeship deep dive, they'll pull 8–12 learners across different standards and stages, then look at the last 2–3 reviews for each. What they're triangulating against the rest of the file:

• Are KSBs being meaningfully assessed — or just listed as "covered"?
• Are SMART targets set at each review, and were the previous review's targets followed up?
• Is the employer involved — not just signing the form, but contributing to the conversation about progress?
• Does the review reference the standard, or just the apprentice's current work situation?
• Is there evidence of stretch and challenge, or has the bar dropped as the programme has progressed?

The most damaging finding is when reviews are uniformly positive across the whole cohort but achievement data tells a different story. A file that says "on track, working well" at every review — followed by a learner who fails gateway or withdraws — is a credibility problem for the whole quality assurance function.

The four parts of a credible review

Strip away the templates and a defensible progress review has four parts. Skip any of them and the review weakens.

1. KSB progress: what's been demonstrated

Not what's been covered. What's been demonstrated. The distinction matters. "We covered K3 in this period" tells the inspector you had a session on K3. "The learner demonstrated K3 by independently designing the configuration walkthrough for two new starters and writing it up in their portfolio" tells the inspector the learner actually has the knowledge.

For each review, name 2–4 specific KSBs the learner has progressed against in this period. Cite the evidence: which portfolio submissions, which workplace artefacts, which observations. Then make a qualitative judgement — is the demonstration secure, developing, or surface-level?

2. SMART targets: where the learner is heading

Targets should be specific to this learner, measurable, anchored to the standard, realistic given the time to the next review, and time-bound to the next review date. The most common failure is writing targets that are activities rather than outcomes — "complete unit 3" is an activity, "demonstrate competence in unit 3 KSBs K7–K10 through workplace evidence" is an outcome.

And at the next review: every previous target must be revisited. Met, partially met, slipped, dropped — the inspector wants to see the loop closed. A review that sets targets and never references them again is worse than no targets at all.

3. Employer voice: what the workplace adds

The employer is not a signature collector. The strongest reviews record what the employer actually said — about the apprentice's work, about gaps the assessor wouldn't otherwise see, about workplace changes affecting the apprenticeship. If your reviews quote the employer ("Lead engineer noted increased confidence in client conversations"), that's a credible record. If they just have an employer signature in a box, the inspector has to assume the employer was a rubber stamp.

4. Off-the-job training: what was logged and what it produced

OTJ hours don't belong in the review summary, but the review should reflect on them. Is the learner on track to meet the fixed hours for their standard? Have OTJ activities translated into competence in the period — or has the learner been ticking time without progressing? An honest note here ("OTJ hours are on track but the connection between the e-learning modules and workplace application is weak") catches problems early.

Language that fails — and what to write instead

The single biggest improvement most provider review chains can make is at the level of language. Inspectors are sensitive to formulaic phrases because they signal box-ticking rather than reflection.

The learner is on track and working well. Targets discussed and agreed.

This is the modal review — and the one Ofsted hardens against. It says nothing specific. It doesn't tell you which learner this is. It would read identically on any file in the cohort.

Replace with:

1. "On track" → on track for what. Name the gateway date, the OTJ target, or the specific KSBs they're behind on.
2. "Working well" → describe what, specifically, has changed in the apprentice's work since the last review.
3. "Targets discussed and agreed" → write the targets in the review. Don't reference them elsewhere — have them visible in the review itself.
4. "Pleased with progress" → whose view is this, and on what basis? The reviewer, the employer, the apprentice? Attribute it.

The tripartite sign-off problem

ESFA funding rules require the apprentice, the employer, and the provider to all sign off the review record. In practice, the employer sign-off is the weakest link in most provider operations. Signatures get collected days or weeks after the review, often by email screenshot, often without the employer having read the substantive content.

Inspectors increasingly probe this. Expect them to ask the employer directly during interviews:

• "Did you discuss this review with the apprentice and their assessor?"
• "What targets were agreed for this period?"
• "What's the apprentice working on in their off-the-job training?"

If the employer can't answer, the signature is decorative. Two practical fixes: schedule the review meeting to include the employer (not just collect their signature afterwards), and write into the review what the employer specifically said. Both are cheap to do and both strengthen the review chain materially.

A working review structure

Below is the structure we recommend providers adopt — sector-agnostic, evidence-led, and aligned to what inspectors look for. You can drop it into any e-portfolio platform.

1. Review period and basic info — date, period covered, attendees (apprentice, assessor, employer representative, names not just roles).
2. Last review's targets — revisited — each target listed, met / partially met / slipped, with a sentence of evidence.
3. KSB progress this period — 2–4 KSBs the learner has progressed against, with named evidence (portfolio item, workplace artefact, observation).
4. Off-the-job training reflection — hours logged vs. target, plus one sentence on whether the activities are producing the intended competence.
5. Employer voice — what the employer specifically said about progress, gaps, or workplace context. Quoted, not paraphrased generically.
6. New SMART targets — written into the review, anchored to specific KSBs and the next review date.
7. Welfare, safeguarding, English & maths checkpoint — concise but real. "No concerns raised" is acceptable here if true; vagueness elsewhere is not.
8. Tripartite sign-off — with date the employer actually engaged, not the date the form was returned.

Reviewing your own reviews

Once a quarter, run a short IQA exercise specifically on review quality. Take five recent reviews from across the team and read them side by side. Ask:

• Could I tell these reviews apart if the apprentice names were redacted?
• Does every target from the prior review have a status update?
• Is the employer present as a voice, not just a signature?
• Are KSBs cited specifically, with named evidence?
• Is anything weak or slipping acknowledged honestly, or is the tone uniformly positive?

If five reviews from your team read interchangeably, that's the signal. Train the team on specificity before the next inspection cycle, not after. Reviews are the only artefact in the learner file written entirely in your own words — which means they're the cleanest indicator of how seriously your delivery team takes the standard. Inspectors know this.

Get them right and they become your strongest evidence. Get them wrong and they become the file Ofsted opens first.