What counts as proof that staff read a policy?
When an inspector asks "who read your medication policy?", the homes that struggle are rarely the ones without a policy — they're the ones without a record. Here's what actually survives scrutiny.
"We emailed it to everyone" is not an audit trail
An email proves distribution. It says nothing about whether the night-shift carer opened it, read the version that mattered, or acknowledged it before the incident happened. Under scrutiny, the gap between "sent" and "signed" is exactly where evidence falls apart.
Inspectors are not asking whether your staff are honest. They're asking whether your system can prove what happened without relying on anyone's memory.
The record that survives scrutiny
A defensible policy acknowledgement record answers five questions, per person, per policy:
The five-question test
- Who was it issued to? Exactly the staff who must read it — with a deadline.
- Did they open it? A timestamp for the moment each person opened the document.
- Did they sign it? A typed or written signature, dated, tied to that person.
- Which version did they sign? The exact text they acknowledged — not "the policy" in the abstract.
- What happened when it changed? A fresh round of sign-off for the new version, with the old signatures preserved as history.
The version question is the one paper systems fail most often. If your medication policy moved from v3 to v4 in March and your signature sheet is undated per-version, every signature on it is ambiguous — and ambiguous evidence reads as no evidence.
Why chasing matters as much as signing
The register is only complete when everyone outstanding has been followed up. A record that shows three staff never signed — and no reminder was ever sent — tells an inspector the system isn't being run. Reminders, and the record of the reminders, are part of the evidence.
Doing this on paper vs. doing it automatically
None of the above requires software — homes have run signature sheets and ring binders for decades. The cost is that somebody has to maintain the matrix by hand, chase by hand, and rebuild the evidence pack every time someone asks. The failure mode isn't dishonesty; it's a busy week.
Warden exists to make the record a by-product of the work: publish a policy and the audit trail — issued, opened, signed, chased, re-versioned — builds itself, exportable to PDF or Word the moment someone asks.
See your policies with a real audit trail
One home, your real policies, your real staff list — inspection-ready in about a week. £99 per home per month, no setup fee, cancel any time.
Book a single-home pilot →Common questions
Is emailing a policy to staff enough evidence for CQC?
An email proves you sent it — not that anyone read it. Inspectors look for acknowledgement: receipt, opening, and a signature tied to the exact version.
What should an acknowledgement record contain?
Identity, policy name and version, issue date, evidence of opening, signature date, and the exact text signed against — with version history kept separate.
How does Warden record this?
Automatically, in five steps: published → opened (timestamped) → signed (typed name against the exact version) → chased (one-tap reminders) → re-versioned (fresh sign-off, old signatures preserved).
This guide is practical operational guidance, not legal or regulatory advice. Always confirm requirements with CQC guidance and your own compliance advisors.