Policy Review Dates: How to Stop Them Slipping
It is a Tuesday afternoon and the inspector asks for your safeguarding policy. You find it quickly, which is good. The cover page says it was last reviewed in March 2024 and was due again in March 2025. Nobody has touched it since. The policy itself may be perfectly sound, but that date has just told the inspector something about how the service is run. Policy review dates slip in almost every care business at some point, and it is rarely because anyone stopped caring. The review was never built into a system.
Why policy review dates slip
A review date is a promise: someone will read this document, on or before this day, and decide whether it still describes what the service actually does. In most services that promise lives in one person’s head, usually the registered manager’s, with a diary note as backup. Then a new starter needs inducting, a safeguarding referral takes the afternoon, and the diary note moves to next week. Multiply that by forty or fifty policies and you have a folder where a third are overdue and nobody is quite sure which third.
The other reason is scale. If every policy carries the same twelve-month cycle from the day the folder was bought, they all fall due in the same month, and that is a week of reading nobody can give.
Decide what reviewed actually means
Before fixing the dates, fix the definition. A review is not changing the date on the footer. It is a short, recorded check that the policy still matches current guidance, practice and law, with a note of what changed. If the answer is “no changes”, say so and say why. That sentence is the evidence.
Regulation 17 of the Health and Social Care Act 2008 (Regulated Activities) Regulations 2014 requires providers to have systems that assess, monitor and improve the quality and safety of the service, and CQC’s guidance on that regulation says those systems should be continually reviewed to make sure they remain fit for purpose. The regulation does not set a fixed interval for reviewing policies. That is useful, because it means you can set intervals that reflect risk rather than habit.
Give every policy one owner and one trigger
Every policy should have a named owner who is not always the registered manager. The medicines lead owns the medicines policy. The person who runs recruitment owns safer recruitment. Ownership spreads the reading load and puts the review with the person who knows whether the document still reflects practice.
Each policy also needs a trigger beyond the calendar date. A change in guidance, a serious incident, an upheld complaint or a new service type should each prompt a review regardless of the date on the cover. Write the triggers into the policy register so they are visible, not remembered.
Put your policy review dates where you will see them
This is where most of the slippage is cured. A review date inside a Word document is invisible until someone opens that document. A review date in a register that is looked at every week is a live item. The register should show, for every policy, the owner, the last review, the next review and the status, sorted so the top of the list is always what is due.
In HLTH Manage this is the Policies module. Each policy carries its owner and review date, the dashboard flags anything due soon or overdue, and the manager sees it on the same screen as audits and training rather than in a separate folder. The point is not the software. The point is that the date lives somewhere that gets looked at.
Spread the cycle and review in small batches
Stagger the dates. High-risk policies such as safeguarding, medicines and mental capacity might sit on a six or twelve-month cycle. Policies that rarely change can sit on a longer cycle unless a trigger fires. Then spread the due dates across the year so that no month has more than four or five to do.
Four policies a month is a reviewing habit. Forty in March is a crisis. Put a fixed slot in the management diary and treat it like a supervision: it happens whether or not the week is busy, and if it moves, it moves to a named day rather than to “soon”.
Make the evidence trail automatic
Inspectors want to see that staff know a policy, that it reflects practice and that it changed when something went wrong. So the review record should capture three things: what was checked, what changed and who was told. If a policy changes, the staff who need to know should confirm they have read the new version, and that confirmation should sit alongside the policy rather than in an email thread.
Version control matters here. Keep the previous version available so you can show what changed and when, and take it off the shelf and the shared drive so nobody follows it. A system that holds the current version, the history and the read receipts in one place does this for you. A folder of PDFs does not.
What inspectors are really looking at
The well-led quality statement on governance, management and sustainability begins “We have clear responsibilities, roles, systems of accountability and good governance”. A policy register with named owners, staggered dates, recorded reviews and visible status is a direct answer to that statement. An overdue date on a cover page suggests the system depends on one person’s memory.
None of this needs a heroic afternoon. It needs a register, an owner per policy, a monthly slot and a place where the dates are seen every week. Build that once and the dates stop slipping, because the system is doing the remembering.
If you would like to see how the HLTH Manage policy register, review reminders and read confirmations work together, book a demo and we will walk you through it with your own policy list.