Article
How to read a CQC inspection report properly
Reading another service's inspection report is one of the cheapest learning opportunities in CQC governance. What to look at, in what order, and the parts most readers skip that hold the real signal.
Inspection reports are public. Anyone can read them on the CQC website. Most providers I talk to have read their own most-recent report and one or two from their immediate peer group, and that is roughly it. The reports of services in your sector that recently moved from Requires Improvement to Good, or from Good to Outstanding, are some of the most useful documents in the field, and reading them takes about thirty minutes each. This article is how to extract the value.
The headline ratings are the least interesting part. The metadata around the rating tells you more about how the inspection actually went, and the evidence cited inside the narrative tells you what the inspector was actually looking for.
Start with the metadata
Skip the executive summary on a first read. Go to the front matter that almost nobody reads carefully.
When was the on-site visit? Inspection reports are published weeks or months after the fieldwork. A report published in March may describe a service as it was in November. If you are using the report to learn about a current peer, the timing matters.
Was the inspection announced or unannounced? Announced inspections give the service time to prepare; unannounced inspections do not. A Good rating from an unannounced inspection is a stronger signal than the same rating from an announced one.
How long was the fieldwork? A two-day visit produces a more complete picture than a half-day visit. The length of fieldwork tells you how much weighting to give the report.
How many staff were interviewed? Reports often note this. A service where twenty staff were interviewed produces a more robust evidence base than one where four were. The first is harder to game.
Read the must-do and should-do items first
Every report identifies improvement actions, broadly split into must-do (regulatory breach found) and should-do (improvement opportunity short of breach). Read these before the narrative.
For each must-do, look at the specific regulation cited. That tells you what category of failure the inspector found. Then read the supporting paragraph in the narrative; that tells you the concrete fact pattern that triggered the finding. The combination (regulation + fact pattern) is the unit of learning. The same fact pattern in your service would produce the same finding.
For each should-do, the value is in the gap between adequate and good. The service is not breaching anything; the inspector is suggesting they could do better. That gap is often where the difference between Good and Outstanding lives.
Read the well-led section carefully
Well-led tells you what the inspector thought about the management of the service, which is harder to assess objectively than the other four key questions. The evidence cited in well-led often shows what the inspector looked at when forming the judgment. Common phrases to notice include "governance meeting minutes evidenced", "action plan from the previous inspection was visible in", "staff supervision records showed". Each of these is a category of evidence the inspector tested.
If a report says well-led was Good and you want to know why, the evidence trail in this section is the answer. Take what they cited and ask whether your service has the equivalent.
Notice what the report does not say
Reports are bounded by what the inspector saw and what the service could produce. Two things to look for in the silences.
Categories the inspector did not look at. A focused inspection covers some of the five key questions; not all of them. If a report rates the service on three of the five questions, the other two carry over from the previous inspection. That can mean a Good rating overall is older than it looks.
Evidence the service could not produce. Phrases like "the registered manager was unable to provide", "we were not given", "the service could not evidence" are inspector code for "you should have had this and you did not". These usually map directly to should-do or must-do items.
Compare prior and current reports for the same service
Reading one report tells you the snapshot. Reading two tells you the direction of travel.
Take the previous report and the current one side by side. For each must-do or should-do from the previous report, find the corresponding paragraph in the current one. The current report will either show the finding closed (with evidence of the action), still open (with evidence of partial progress), or repeated (with evidence that nothing changed). The pattern of closures across the two reports tells you how the service responds to feedback. That pattern is one of the strongest predictors of where the next inspection will land.
How to use this on your own next inspection
Pick three peer-service reports published in the last twelve months. Read each one using the structure above. For each must-do or should-do, ask: could this happen at our service? For each piece of evidence cited under well-led, ask: do we have the equivalent?
The exercise takes about ninety minutes for three reports and produces a focused list of work for your service. None of the work requires anyone to inspect you; the inspector has already done it at the peer service and written down what they found.
Klaudiusz Zembrzuski
Founder, Verivius
Want a structured way to act on what you find?
When you finish reading peer reports, the list of must-haves you find for your own service is exactly the kind of working register Verivius is built for. Each item gets an owner, a deadline, and a closure record. Request a 30-minute conversation if you would like to walk through how it works.