Re-issuing a policy: why version 2 needs fresh signatures
Updating a policy is routine. What happens to the signatures is where homes get caught: if version 2 quietly inherits version 1's acknowledgements, the record now says staff signed words they never read.
The quiet failure
A policy changes — a new safeguarding contact, a revised medication step, a tightened visitor rule. The document gets replaced in the folder, and the sign-off sheet stays stapled to the front. Six months later an inspector reads the current version, checks the signatures, and asks the only question that matters: which version did these people actually sign? If the answer is "the old one", the home is now explaining why its evidence says otherwise.
What the record has to keep
A version-safe acknowledgement record
- The exact wording each person signed against — not just a filename.
- Version 1's signatures preserved as history, never deleted, never blended into v2.
- A fresh round of sign-off opened automatically when v2 is issued.
- A live list of who has and hasn't signed the current version.
The re-issue workflow that doesn't rely on memory
The workable version of this is boring on purpose: update the policy, and the system re-issues it to exactly the staff who must read it, with a deadline. Anyone outstanding gets chased automatically — one tap resends to everyone overdue. Nobody has to remember to start a new sheet, because the new round starts itself.
How Warden records it
Warden keeps the full chain on every notice, automatically: published (who it went to, with what deadline), opened (the moment each person opens it, with device and IP), signed (typed name against the exact version read), chased (reminders to anyone outstanding), and re-versioned — a fresh round for v2 while v1's acknowledgements stay intact as history. Every register exports to PDF or Word for the inspector.
Run the single-home pilot — inspection-ready in about a week →