
Building an Audit Schedule You Will Actually Keep To
It is the last Friday of the month and the audit tracker says six audits are due. Two are done. The medication audit is half finished because the senior who owns it has been covering shifts, the infection control audit was last completed in July, and nobody can remember whether the care plan audit was meant to be monthly or quarterly. The audit schedule looked sensible in January. By now it is a list of things the service has not done.
Almost every registered manager has lived some version of this. The problem is rarely effort. It is that the schedule was built for the service you hoped to run rather than the one you actually run. Here is how to build one that holds up when the month gets busy.
Why audit schedules slip
Audit schedules usually fail for three reasons. The first is volume: a template downloaded from somewhere lists thirty audits, so thirty go on the calendar, and the service never had the hours to do thirty. The second is ownership: audits are assigned to a role, or to “the management team”, and so belong to nobody on the day they fall due. The third is that the audit exists only as a tick in a spreadsheet. Nothing happens to the findings, so completing it feels pointless and it quietly stops.
Regulation 17 of the Health and Social Care Act 2008 (Regulated Activities) Regulations 2014 asks providers to assess, monitor and improve the quality and safety of the service, and CQC’s guidance names regular audits as one of the systems it expects to see. It does not say how many. A short schedule that is completed every time is far stronger evidence than a long one with gaps.
Start with the risks, not the template
Sit down with the service’s last twelve months in front of you: incidents, complaints, safeguarding referrals, medication errors, staff turnover, anything that has gone wrong or nearly gone wrong. Those are the areas that need the most frequent checking. Then add the areas CQC’s quality statements will always ask about, such as medicines, care planning, infection prevention, safeguarding, staffing and training, and governance itself.
From that list, decide on a frequency for each audit based on how fast the risk moves. Medicines move quickly, so a monthly audit is usually right. The environment and fire safety move slowly, so quarterly may do. Be honest about the hours available. If the schedule needs more than the service can give, shorten the audits or stretch the frequencies rather than pretending.
Give every audit one named owner
An audit owned by a job title is an audit owned by no one. Put a person’s name against each one, agree the date it is due, and make sure that person knows what “done” looks like: the tool completed, findings recorded, actions raised. Spread ownership across the team rather than loading it all onto the registered manager and the deputy. Seniors auditing their own areas builds competence, and you still review their findings.
HLTH Manage is built around this idea: each check is allocated to a named person with a due date, the dashboard shows what is outstanding across the service, and reminders arrive before the date rather than after it. That reminder is the difference between an audit done on the Tuesday it was planned for and one remembered on the Friday after.
Make the findings go somewhere
An audit without actions is a survey. Every finding should become an action with an owner and a date, and those actions should live in the same place as the audit so you can see, at a glance, what is open and what is overdue. This is where inspectors look hardest under the Well-led key question: not at whether an audit was completed but at whether anything changed because of it. CQC’s guidance on Regulation 17 is explicit that providers must monitor progress against their plans to improve quality and safety.
Review open actions in your monthly governance meeting and record that you did. Then, three months on, re-audit the same area and note whether the problem has gone. That loop, from finding to action to re-check, is what good governance looks like on paper, and it is what the Well-led quality statement on governance, management and sustainability is describing.
Build in slack
A schedule that only works when everyone is in is a schedule that fails in August and again over Christmas. Spread the heavier audits across the year rather than stacking them in one month. Keep at least one week in every month with nothing due, so a slipped audit has somewhere to land. Agree in advance what happens when the owner is off: who picks it up, or whether it moves a week with a note explaining why.
Record those decisions. A schedule with a documented, reasoned adjustment is still a kept schedule. A silent gap is not.
Review the schedule itself
Twice a year, look at the schedule as a whole. Which audits consistently found nothing? They may be running too often. Which found the same thing every time? The action is not working. Which were missed, and why? Adjust the frequencies, the owners and the tools, and keep the old versions so you can show an inspector how the schedule has evolved. Keeping the live schedule, the completed audits, the action log and the governance minutes together in HLTH Manage means that story is already told when someone asks for it.
A simple test
An audit schedule is a promise about attention. Make fewer promises and keep every one. If you can open your tracker on any day of the year and see every audit completed on time, every finding turned into an action, and every action closed or on its way, the schedule is working. If you cannot, cut it back until you can, then grow it from there.
If you would like to see how HLTH Manage keeps audits, actions and governance evidence in one place, book a demo with the team.
