CQC inspection readiness for independent providers

CQC assesses your service against the five key questions: safe, effective, caring, responsive and well-led. Under each sits evidence, and readiness means that for each key question the recent record exists, is current, and has a named owner. The good-governance duty in Regulation 17 of the Health and Social Care Act 2008 (Regulated Activities) Regulations 2014 is the spine that runs through all five: it asks whether you operate an effective system for monitoring quality and risk, and whether you act on what that system shows.

In practice, readiness is the sum of ordinary trails being up to date. Incidents logged, investigated and closed with the learning captured. Complaints answered with the change to practice recorded, not just the apology. Safeguarding referrals made and their outcomes tracked. Statutory notifications sent inside the window. The risk register reviewed on its cadence rather than the week before. Training current against the matrix. Audits running on a cycle rather than resurrected for the visit. Each of these is a readiness signal, and each is something an inspector can sample without warning.

Across the inspections Klaudiusz ran over more than a decade inside CQC, unreadiness rarely looked like a service doing bad work. It looked like a service that could not evidence the good work it did. Three patterns showed up again and again.

One: readiness is treated as an event, not a state. The preparation starts when the inspection is announced, or when a peer nearby gets inspected. Records are pulled together, documents refreshed, a folder built. The trouble is that a freshly assembled evidence pack reads as exactly what it is. An inspector who sees three years of thin activity followed by a fortnight of intense tidying does not conclude the service is well-led; they conclude the opposite.

Two: the document exists but is stale. The policy is there, dated three years ago, with no review since and no sign anyone has read it. The risk register exists but has not been touched since the last inspection. The document being present is not the point; readiness is evidence that the system behind the document is live.

Three: the action has no owner or date. The improvement everyone agreed on sits in a set of minutes with no name against it and no due date. A year later the same issue surfaces, unactioned, and now it is a pattern rather than a one-off. Readiness is not just knowing your gaps; it is being able to show each one is owned and moving.

The way out of the scramble is to make readiness a side effect of the daily work rather than a separate project. When incidents, complaints, safeguarding cases, statutory notifications, risks and audits are captured as they happen, each with an owner and a date, the evidence trail is already there on any inspection day. There is nothing to assemble, because nothing was ever allowed to go missing. That is what Verivius is built to do: hold the governance trail continuously so the state an inspector wants to see is the state you are already in.

Read what Verivius actually does for the platform context. The risk register and clinical audit pages show two of the continuous engines behind that trail.

Two readiness checks sit alongside the daily platform, and they are different things. The procedure and audit checklists let you self-assess against what an inspector samples, for free, whenever you want. The Mock Inspection is a deeper, consultant-led calibration: an ex-CQC inspector, engaged as a Verivius consultant, reads your actual records and gives you a provisional judgment in writing against the five key questions. The checklist is a self-test you run often; the Mock Inspection is an outside judgment you take around once a year.