Article
What "evidence" actually means to a CQC inspector
The word has a specific meaning inside the regulator and a softer meaning everywhere else. What counts, what does not, and the four properties a record needs to do work in an inspection.
A registered manager once told me her service had "loads of evidence" for a Well-led finding. When we looked at what she meant, it was a folder of policies, a binder of meeting agendas, and a memory of conversations the team had had over the previous six months. None of it was evidence in the way an inspector uses the word.
Evidence inside the regulator means something specific. It is what allows an inspector to verify a claim without relying on what anyone tells them. A claim made by the service that cannot be verified independently is not evidence; it is an assertion. The difference between assertion and evidence is the difference between a rating you can defend and a rating you cannot.
The four properties of a record that counts as evidence
A record does the work of evidence when it has all four of these properties. Missing any one and the inspector can challenge it.
Specific.The record names a particular event, person, date, or fact. "Staff are trained in safeguarding" is not specific. "Anjali Patel completed the level 3 safeguarding adults module on 12 March 2026, verified by competency assessment recorded against her staff file" is specific. Specificity lets the inspector trace the claim to its source.
Dated.The record carries a date that shows when the event happened or when the document was created. Undated records cannot be located in time. A policy that says "reviewed annually" without a date stamp is not evidence of a current policy; it is evidence of a policy that someone once wrote.
Sourced. The record names who created it or who owns the fact. An incident write-up signed by the registered manager is sourced; an anonymous note in a shared drive is not. The source lets the inspector ask follow-up questions of the right person.
Independently verifiable.The record exists somewhere the inspector can check it without the service's help. Best case: the inspector can pull it up from your platform in a few clicks. Worst case: it exists only in one staff member's memory or on a single laptop nobody else can access.
What is often mistaken for evidence
Three common categories of artefact that providers point at as evidence and that often fail one or more of the four properties above.
Policies. A policy is not evidence that the policy is followed. The inspector wants to see the policy AND the records that show staff acting in line with it. A clean policy folder with no implementation evidence reads as governance theatre.
Meeting agendas. An agenda shows what was scheduled, not what happened. Minutes (with decisions, actions, owners, dates) are evidence of a meeting. Agendas without minutes are evidence of a scheduled meeting that may or may not have happened.
Memory of training delivered."We trained the team on this last quarter" is not evidence. A signed training register with each attendee's name, the date, the module title, and a competency-check outcome is evidence. The register turns a memory into a verifiable record.
The inspector's test
This is roughly how I tested whether something was evidence when I was inside the regulator. It is a useful self-test you can run on your own records before someone else does.
Pick any claim your service makes about itself. "Our team is well trained in safeguarding". "We respond to complaints within 20 working days". "Our governance meetings happen monthly".
Ask: if a stranger walked into the service today and asked me to prove the claim using records they could read without my help, could I produce the proof in under five minutes?
If yes, the claim is evidenced. If no, the claim is an assertion. The work of becoming inspection-ready is converting assertions into evidenced claims.
Why the framework asks for evidence the way it does
CQC's assessment approach is built around six evidence categories: people's experience, feedback from staff and leaders, observation, processes, outcomes, feedback from partners. The structure exists because the regulator is trying to triangulate the claim a service makes about itself across multiple independent sources. If your processes evidence says one thing and your people's-experience evidence says another, the inspector reads the conflict as a signal. If they line up, the inspector reads consistency as credibility.
The practical implication: a service that is strong on one evidence category and weak on others is reading the framework wrong. The strength comes from coverage across categories, not depth in one.
The product point, briefly
The reason Verivius exists is to make evidence (in the specific regulator sense) cheap to produce. Every record in the platform is automatically specific, dated, sourced, and independently verifiable by the inspector when they have time-bounded access. The platform does not write the evidence for you; it gives the evidence a place to live that satisfies the four properties by default.
Klaudiusz Zembrzuski
Founder, Verivius
Run the inspector's test on your records
Pick three claims your service makes about itself. Try to prove each in under five minutes using only records a stranger could read without your help. Where the test fails, that is your work for next month. Request a 30-minute conversation if you want to walk through how Verivius captures evidence in that shape as a side effect of doing the work.