Ofsted readiness checklist for education supply agencies

When Ofsted inspects a school, the Single Central Record is one of the first documents reviewed, and any supply staff placed by your agency are covered by it. This checklist is deliberately practical: it is what to actually check, in order, rather than general theory about compliance. Work through it as a genuine audit of your current position rather than a box-ticking exercise, and treat any item you cannot immediately confirm as a live gap to close, not a formality to note and move past.

This matters more for supply agencies specifically than it might first appear, because the school taking the inspection risk is not the one directly employing the staff in question. A head teacher or compliance lead reviewing their SCR ahead of an inspection has to trust that the agencies they work with have done the underlying work properly, and increasingly, schools are not willing to take that on faith without evidence they can point to.

Before any placement goes out

Everything below should be true and evidenced before a candidate is confirmed into a school, not assumed and checked retrospectively:

• Enhanced DBS check with children's barred list check confirmed, with certificate number and date recorded
• DBS Update Service status checked, or a recent certificate obtained where the candidate is not registered
• Right to Work verified, with share code checked and expiry date logged
• Prohibition from teaching check completed for any teaching role
• Identity verified against photo ID
• All of the above recorded against the candidate's record, not just confirmed verbally

For every candidate currently on placement

A placement that was fully compliant on day one is not automatically compliant six months later. This is the check that catches most agencies out, because it requires actively revisiting records rather than trusting the original onboarding was enough:

• DBS status still current. Update Service registered, or re-checked if not
• Right to Work documents not approaching expiry without a re-check scheduled
• No gap between the original check date and the current placement date that has gone unreviewed
• Compliance record complete enough to export on request within minutes

What to have ready for a school at any time

A school preparing for inspection, or responding to one already underway, needs to be able to point to complete records for every supply worker on site. An agency should be able to provide, without delay:

Reading the compliance file the way an inspector would

It helps to physically sit down and review a candidate's compliance record as if you had never seen it before and had no context on the placement. Would the dates make sense to an outsider? Is it obvious which checks are current and which might be stale? Is there a certificate number, or just a note saying a check happened? Agencies that only ever view their own records with the benefit of institutional knowledge, "oh yes, we definitely did that check, I remember it", often do not notice how thin the paper trail actually looks to someone seeing it cold, which is exactly the position an inspector or auditor is in.

This is a useful discipline to apply across a random sample of candidates rather than the ones you are already confident about. The candidates worth stress-testing are the long-running placements that have not been actively reviewed since onboarding, and the candidates who move quickly between multiple schools, since both are where records are most likely to have quietly gone stale.

Doing this cold-read manually means printing or exporting a record and squinting at it as an outsider would; a system like scout. maintains the record in a structured, always-current format so there is no "thin paper trail" to worry about in the first place, the compliance summary is always what an inspector would need to see.

The monthly check, not just the week-before check

Even without a specific inspection looming, running this checklist monthly rather than reactively is the difference between genuine readiness and a scramble. Ofsted inspections arrive with very little notice, which means "we will sort the paperwork before the inspection" is not a viable strategy, by the time you know one is coming, there is no runway left to fix anything substantial.

• Pull the full list of candidates currently on placement across every client school
• Cross-check every one against DBS, Right to Work and prohibition status
• Flag and resolve any gap before the next placement cycle, not after a school asks
• Confirm your audit trail export actually works and produces something a school could hand to an inspector directly
• Spot-check a handful of records at random rather than only reviewing the ones you already suspect are incomplete

Why this is worth treating as routine, not exceptional

The agencies that handle inspections calmly are, almost without exception, the ones that treat compliance tracking as a continuous background process rather than a task that gets attention when a deadline looms. The difference is not extra effort, it is where that effort is spent. A small amount of consistent tracking every week is considerably less costly, in time and in risk, than an intensive scramble every time a school mentions a visit is coming.

This is precisely the workflow scout. automates: candidates are checked continuously rather than at a single point in time, gaps are flagged in the Morning Brief before they become a live problem, and a full audit trail is exportable on demand. See our guides on DBS checks and the Single Central Record for the detail behind each part of this checklist.

What good actually looks like on inspection day

It is worth being concrete about what a well-prepared agency actually experiences when a school it supplies gets an inspection call. A compliance lead is asked for evidence on a handful of current placements. They pull a clean export, check types, dates, certificate numbers, verifiers, for each candidate, in the time it takes to run a search, not the time it takes to reconstruct a paper trail from memory and old emails. The school passes that straight through to the inspection team. Nobody at the agency needed to do anything they were not already doing as part of routine practice.

That is the bar. It is achievable with a genuinely current, centralised compliance record, and it is precisely what falls apart when compliance tracking depends on a spreadsheet that only gets updated when someone remembers to, or a filing system split across several people's inboxes.

Building this into how the agency runs, not just how it prepares

The checklist above works best as a description of ordinary practice, not a special exercise run before a known inspection. Schools cannot always tell an agency an inspection is coming, and increasingly agencies find out only when a school asks an urgent compliance question with a same-day deadline. Treating every day as if that call might come, rather than treating compliance as a task to intensify before a known date, is what actually removes the risk, and it costs less in aggregate effort than periodic scrambles, even though it feels like more work in any given quiet week.