Well-Led Governance & Inspection Readiness Governance Trilogy · Part One
Why Many Audit Systems Fail in Adult Social Care — And How to Get Real Value from Your Audit Cycle
Last updated: April 2026 Reading time: 20 minutes Category: Governance & Inspection Readiness
The first article in Carevia’s governance trilogy. Pro+ members use the Inspection Readiness Dashboard to run audits that actually surface the gaps that matter. Join Carevia Pro+ →
Every service has audits. Yet CQC inspectors keep finding issues that services’ own audits missed. The problem is rarely the absence of audits — it is the quality of the auditing process itself. These ten governance principles help managers move from completing audits to getting real value from them.
Why Audits Fail When They Look Like They’re Working
Audits are one of the most common governance tools used in adult social care. Every service has them — medication audits, care plan audits, health and safety audits, infection control audits, staff file audits. Most providers can produce a folder of completed audits within minutes.
Yet when you read CQC inspection reports, a pattern appears again and again. Inspectors frequently find issues that the service’s own audits failed to identify. You will often see phrases such as:
audits were completed but did not identify issues
actions were identified but not completed
improvements had not been sustained
governance systems were ineffective
In many cases, the service had an audit system in place. The problem was not the absence of audits. The problem was the quality of the auditing process itself.
A completed audit form does not automatically mean a service is well governed. In reality, a poorly executed audit can give leaders a false sense of assurance that everything is fine. At Carevia, we call this the False Assurance Problem — and it is the single most common failure mode in governance across adult social care.
The False Assurance ProblemCarevia concept
A governance artefact — an audit, an action, a policy, a training record — looks complete. The box is ticked, the document is signed, the date is logged. But the completion masks an underlying issue that has not been addressed. Leaders, inspectors, and reviewers see assurance where there is only paperwork. The False Assurance Problem is what produces the CQC inspection pattern of concerns being found in areas the service’s own systems had already reviewed. It runs through the whole of Carevia’s governance thinking, and it is the common enemy of the three articles in the governance trilogy.
Strong governance in adult social care requires more than simply completing an audit schedule. It requires curiosity, critical thinking and a genuine desire to understand what is really happening in practice — precisely because the False Assurance Problem is easier to produce than genuine assurance.
When audits are done well, they become one of the most powerful tools a Registered Manager or Nominated Individual has. They help identify risk early, strengthen quality assurance systems and support continuous improvement. When they are rushed or treated as just another job to do, they quickly become a tick box exercise.
The difference lies in how the audit cycle is approached. Below are ten practical governance principles that can help services get real value from their auditing process.
One of the most common problems with audit systems is that they become reactive. Managers realise that an audit is overdue and rush to complete it quickly so that it appears up to date. This rarely produces meaningful results.
A strong care home audit schedule for CQC compliance should be planned well in advance and integrated into the service’s wider governance calendar. When audits are scheduled properly, managers can prepare the necessary information, allocate appropriate time and ensure the right staff are involved.
Consistency is a key part of demonstrating effective governance under CQC Regulation 17.
A rushed audit is a substandard audit. Many audits are completed quickly between other responsibilities. This approach almost always limits the depth of review and reduces the likelihood of identifying meaningful issues.
Completing a thorough adult social care quality assurance audit takes time. Managers need time to review records, observe practice, speak to staff and reflect on whether care delivery matches documentation.
Without dedicated time, audits quickly become a paperwork exercise rather than a meaningful review of practice.
Mindset plays a significant role in the effectiveness of an audit. If someone approaches the process trying to confirm that everything is compliant, they are unlikely to identify areas for improvement. A stronger mindset is one of genuine curiosity. Instead of asking “Is everything okay?”, ask “What could be better?”
But curiosity, when it is genuinely applied, goes further than that framing suggests. It is not just about whether a document has been completed — it is about what the document is and is not revealing. A curious auditor asks three distinct questions of every record they look at:
Has this been completed? — the compliance question, which is usually the easiest to answer.
Is what is recorded actually satisfactory? — the quality question. Are the entries safe, proportionate, and consistent with good practice, or are they simply present?
Where an entry raised a concern, was it acted on? — the escalation question. Most completed documents record events. Fewer record the response the event should have triggered.
The third question is the one audits most commonly miss, and it is where the most serious governance failures usually live. Consider a medication storage temperature log. Every day’s temperature has been recorded on schedule. The log looks compliant — the cells are filled, the initials are there, the audit tool ticks the box for completion. But when a curious auditor reads across the actual values, they see that for three consecutive days the temperature was above the safe storage range. No escalation was recorded. No action was taken. The manager was not alerted. Medication may have been administered from that storage area during those three days.
On the surface, the check was completed. In reality, a governance failure occurred and went uncaught because the audit looked for completion rather than for meaning. This pattern is not limited to temperature logs. It appears in fluid charts that record intake below safe levels with no follow-up, weight monitoring that shows significant loss over successive weeks without review, incident logs where the same type of incident appears repeatedly without learning being captured, and daily care notes that record a person has been distressed for several shifts without any change in approach.
A completed document can hide an uncompleted action. This is the False Assurance Problem at the level of the individual record, and the curious auditor’s job is to catch it. Without this habit of reading across records — not just down them — audits will continue to produce the “green ticks everywhere, concerns found at inspection” pattern that defines so many Requires Improvement reports.
4. Ensure the Person Completing the Audit Is Competent
This is the principle most often overlooked, and it is arguably the single biggest determinant of whether an audit produces meaningful findings. An audit is only as reliable as the knowledge and competence of the person completing it. A staff member who does not know what good practice looks like cannot be expected to recognise when it is not being achieved — however well-designed the audit tool is.
This principle has a practical consequence many managers resist at first. It is better for an audit to be completed a day late, waiting for the right person to be on shift, than for someone who is not appropriately skilled to complete it on schedule. A schedule that is kept through superficial completion produces a false record of assurance. A schedule that slips by a day in order to be done properly produces something the service can genuinely rely on.
Better still is a service that has built competence across multiple people who can complete the audit. A governance system that depends on one person — usually the registered manager — is a fragile system. When that person is on leave, off sick, or has left the role, the audit cycle either stalls or drops in quality. Distributed competence is resilience.
Building that distributed competence takes deliberate work. Delegating an audit to a senior carer without first developing their understanding of what they are looking for is not delegation — it is abdication. The preparation matters. Someone needs to know what good practice looks like, to have seen it named and modelled, and to have had their own auditing observed and discussed, before they can be trusted to audit independently.
Competence is essential when delivering quality assurance audits in adult social care services. Supervision and workforce development play a key role in strengthening governance systems — but they need to produce evidence of developed competence, not just recorded attendance.
How Carevia supports this in practice. Distributed competence is one of the things Carevia Pro+ is built to operationalise. The Champion Strengths Profile provides a structured way to develop and record competence across nine champion roles — including the quality and governance-adjacent areas that matter most for audits — with progress tracked across reviews and print-ready records for the staff file. The Carevia Pro+ Time Planner includes built-in delegation and competency assurance, so that when a manager delegates an audit, the record of who can competently complete it travels with the task. Together, they make distributed auditing competence something the service can evidence, not just claim.
An audit should rarely end with no actions. Most services will always have opportunities to strengthen practice. Actions identified through audits should be clear, realistic and time limited.
For example:
Poor action: Improve care planning.
Better action: Review all care plans for individuals receiving diabetic care to ensure monitoring guidance is clearly documented by 30 April.
The second action is SMART — specific, measurable, achievable, relevant and time-bound. This is a meaningful step up from the first, and it is where most governance training stops. But a SMART action tells you what needs to happen and by when. It does not tell you whether the change actually worked in practice, or whether it has become embedded in how the team operates. That is why Carevia uses an extended framework: SMART-TE — SMART with Tested and Embedded added as the final two stages. It is the difference between an action that is complete on paper and one that has genuinely closed the loop on the issue the audit identified.
Where timeframes are not met, a new completion date should be set along with a clear rationale and lessons learned.
Another important step is to consider whether the issue identified represents a wider theme. For example, if an audit identifies that one person’s epilepsy care plan or risk assessment is missing important information, it is worth asking whether similar gaps could exist elsewhere in the service.
Looking for patterns across care plans, risk assessments or documentation can help identify wider governance issues before they escalate. Treating audit findings in isolation can sometimes create a false sense of improvement. One record may be corrected while the same issue remains elsewhere.
Applying a themed approach helps ensure improvements are implemented consistently across the service and strengthens assurance ahead of inspection.
Many managers find that identifying the issue is the easy part. The harder part is deciding what the action should actually be and whether it would stand up to scrutiny during an inspection. This is where Ask Carevia+, available inside Carevia Pro+, can help. It acts like a virtual Senior Quality Partner, helping you sense check audit findings, explore potential themes, and develop actions that are clear, proportionate and inspection ready. Used alongside your audit cycle, it can help strengthen governance thinking and ensure improvements are properly embedded across the service.
Reviews are one of the most overlooked elements of a well-functioning audit cycle. Most managers think of a review as the check that happens after an action is complete — a verification step to confirm the box can be ticked. That framing limits what a review can do.
A review is really a point on the timeline to completion, not a verdict at the end of it. It is the window that gives a manager the chance to reflect on whether an action is on track, whether circumstances have changed, and whether the approach needs to be adjusted while there is still time for the adjustment to matter. An action that is six weeks overdue needs a conversation about why. An action that is on schedule but no longer the right action needs a conversation about whether to redirect the effort. Both of those conversations are reviews. Neither is possible if reviews only happen once the action has already closed.
Reviewed well, actions become a live conversation about improvement rather than a static list of commitments. Reviewed poorly, or not at all, actions drift — a completion date passes quietly, the action is forgotten or marked complete without evidence, and the same issue resurfaces in the next audit cycle.
When reviewing progress, there should be clear evidence to support the improvement recorded. This might include updated care plans, completed training records, revised risk assessments, supervision notes or follow up audits demonstrating that practice has changed. Simply marking an action as completed does not always provide assurance that improvement has taken place — and this is the False Assurance Problem at the action level, with actions showing green on the governance log while the underlying issue quietly persists. Strong CQC governance and quality assurance systems include regular action tracking alongside evidence that improvements have been implemented and sustained. Without this, actions can appear complete on paper while the underlying issue remains.
How Carevia supports this in practice. The Inspection Readiness Dashboard — available to Carevia Pro+ members — has reviews built into the action lifecycle itself. Every action logged in the dashboard moves through SMART-TE stages with built-in review points, so reviews happen on schedule rather than being something a manager has to remember to do separately. Combined with RAOF™ reflection prompts at each stage, this turns reviews from a retrospective check into a live governance habit.
Governance cannot sit with one individual. A service where the registered manager is the only person who understands why a particular action was set, what it is meant to change, and how practice needs to adapt, is a service where that action will almost certainly fail to embed. Staff who understand the improvements being made are far more likely to support them — and staff who do not understand them will not sustain them once the audit folder closes.
Effective sharing has three dimensions, and each needs to be addressed deliberately. What the audit identified — told accurately and specifically, not softened into vague reassurance. Why the improvement is needed — linked to the person whose care is affected, not framed as an abstract compliance requirement. How the team can contribute — named concretely, so staff leave the conversation knowing what their shift will look like differently tomorrow.
The harder question is how the sharing actually happens, because in most services there is no single moment when the whole team is together. This is where designated champions become valuable. A medication champion, a dignity champion, a safeguarding champion — each acts as a trusted peer voice who can carry the message from the audit cycle into everyday shifts, handovers, and informal conversations. Actions shared through a champion tend to land differently than actions announced by the registered manager, because champions translate them into language and examples that feel practitioner-led rather than management-imposed.
Beyond champions, practical communication mechanisms include a short standing item on handover, a dedicated five minutes at the start of team meetings, a governance noticeboard in the staff room where current actions are visible, and one-to-one mentions in supervision where each staff member can connect the action to their own practice. No single channel is enough on its own. A team whose members consistently know what the current governance priorities are is a team in which those priorities actually shape practice.
When staff understand the purpose of actions — not just the fact of them — compliance improves naturally. More importantly, the improvement has a chance of being sustained when the manager is not on shift, which is the real test of whether an action has been genuinely shared.
Sharing an action and co-producing an action are different governance moves. Sharing is communication. Co-production is inviting the people closest to the practice to shape what the action should be — because they see the operational realities the audit form does not capture. A new medication protocol designed entirely at manager level may be procedurally correct but practically unworkable. The senior carer who has to apply it at the point of administration knows which parts will create bottlenecks, which wording will be misread under pressure, and which steps will quietly be dropped once the training sessions end.
One of the most effective ways to draw this insight out is through structured small-group work during team meetings. Rather than presenting an action as a finished decision, a manager can share the audit finding, state the governance concern, and then ask staff to work in small groups — typically groups of three, because pairs can polarise and fours can silence quieter voices — with a specific task. “In groups of three, spend ten minutes on this scenario. Here is what the audit identified and why it matters. What would you suggest we put in place to address it, and what would make it actually work on shift?” Each group reports back briefly. The manager synthesises across the groups. The resulting action is recognisably shaped by the team, not announced to them.
What this approach produces goes beyond the action itself. Three things happen:
Realistic improvements emerge — because the people who will implement them have shaped them, the resulting action is far more likely to work in practice than one designed from the office.
Staff engagement increases — being asked to contribute to governance, rather than being told about its outcomes, changes how staff relate to audit cycles altogether. Audits stop being something that happens to them and become something they are part of.
Accountability strengthens across the team — staff feel more ownership over actions they helped design, which is the precondition for the action becoming embedded rather than just implemented.
This connects directly to the difference between a completed action and an embedded one. Co-produced actions stand a much better chance of surviving the transition from the meeting room to the shift floor, because the team already knows why the action exists and what it is trying to achieve. An action that the team helped create is an action the team is more likely to sustain when the manager is not on shift — which is the real test of whether any improvement has taken root.
9. Apply Professional Curiosity to Audits with No Actions
Of all the patterns in this article, this is the one that should make a manager most uncomfortable. An audit cycle that consistently produces few or no actions is not evidence that the service is well run. It is the False Assurance Problem at the system level — and arguably the most dangerous form of it, because it operates at the level of the leadership’s own confidence in the service.
Here is what the pattern looks like in practice. Audits are scheduled. Audits are completed. The completion log is green. The action tracker has only a handful of entries, most of which are low-severity. Governance meetings are brief because there is little to discuss. The manager reports upward that things are going well. The nominated individual is reassured. On paper, everyone in the service feels assured — because the service’s own systems keep telling them so.
Then CQC visits. And finds concerns the service’s own audits had not identified. This is the gap that CQC inspection reports document over and over again: not that services were negligent, but that services were confidently running an audit system that was producing false assurance. The leadership believed they were well-governed. The evidence from inspection said otherwise.
The remedy is not complicated, but it is uncomfortable. If an audit produces no actions, the question to ask is not “great, everything is fine?” — it is “is this audit actually surfacing what needs to be surfaced, or have we built a system that quietly reports everything as compliant?” In most services there will always be something that can be strengthened. An audit that never finds it is either looking in the wrong places, being completed by someone who does not recognise gaps when they see them, or both. Curiosity applied here is not about finding fault — it is about testing whether the system is actually working.
Professional curiosity should also extend to documentation and daily records, where the same pattern appears at a smaller scale. Records that all look fine, shift after shift, can mask drift that a curious reader would notice immediately. A service whose daily notes say “all good” every day for a fortnight is either providing uniformly excellent care or reporting without observing. The curious manager has to ask which.
Finally, the audit process itself should be reviewed — and this is where the whole governance habit becomes reflexive. Every lesson the article has described so far is also a lesson that applies to the auditor’s own work. Managers should take time to discuss the completed audit with the person who carried it out. This conversation is often where the most useful development happens, because it treats the auditor as a professional who is still learning — which is exactly what a good auditor always is.
RAOF — the Read, Ask, Observe, Feedforward framework used throughout this article — gives this conversation a natural structure. Rather than asking general questions about how the audit went, the manager and the staff member can walk the four strands together:
What did you Read? — which records did you look at, and what was the quality of what you were reading? Were entries clear, ambiguous, or incomplete? Did you find yourself reading down a column rather than across a record?
Who did you Ask? — which staff did you speak to about the area being audited, and what did their answers reveal? Did the explanations you heard match the records you read, or did you notice gaps between the two?
What did you Observe? — what did you see on shift that either confirmed or contradicted what the records and conversations suggested? Were there moments where practice looked different from what was documented?
What would you Feedforward? — what would you take into the next audit of this area, next month or next quarter? What would you do differently? What skills, training, or support would help you audit more confidently next time?
Walking RAOF through the audit with the staff member turns what would otherwise be a generic debrief into a structured coaching conversation. The same four strands that made the audit useful in the first place are now being used to develop the person who conducted it. This is RAOF operating reflexively — applied not just to the service but to the work of auditing the service.
Less structured questions still have their place alongside this. “What worked well during the audit? What challenges did you encounter? Were there areas where you felt unsure about what good practice should look like? Is there anything we could strengthen in the process next time?” These sit naturally around the RAOF conversation, helping the staff member reflect on their experience of the process itself.
These conversations are particularly valuable when they take place during supervision. Reflective supervision creates space to explore learning, develop confidence and strengthen professional judgement. Auditing is not just about checking records. It is about developing the ability to recognise risk, identify gaps and understand what good practice looks like. Training alone does not always achieve this. Competence develops through a combination of learning, structured reflection and feedback.
Small improvements to how audits are completed and reviewed can significantly strengthen governance systems over time. The RAOF conversation at the end of each audit cycle is one of the smallest of these improvements — and one of the most durable.
The three articles share a single underlying argument. Each examines a different governance artefact — audits, actions, and policies — but the failure mode is the same across all three. An artefact is put in place. It looks like governance. It produces paperwork. It fills a compliance requirement. But it does not change practice. The service goes through the motions of governance without the discipline that makes governance real.
The answer in all three cases is the same too. Artefacts do not govern; disciplines govern. RAOF™ held as a leadership habit turns audits into learning, actions into improvement, and policies into living documents. Without that discipline, no amount of audit frequency, action tracking, or policy volume will make a service well-led.
Frequently Asked Questions
The most common reasons are rushed completion, lack of curiosity in the auditor, insufficient competence in what good practice looks like, and treating audit findings in isolation rather than looking for wider themes. Carevia calls this broader pattern the False Assurance Problem — governance artefacts that look complete on the surface while masking underlying issues that were not addressed. A completed audit form is not the same as a well-governed service. CQC inspectors tend to find the issues that a genuinely curious audit would have surfaced — which is why the quality of the auditing process matters more than the quantity of audits completed.
Regulation 17 of the Health and Social Care Act 2008 (Regulated Activities) Regulations 2014 requires providers to have effective governance, including assurance and auditing systems that assess, monitor and drive improvement in the quality and safety of services. The regulation does not specify a number or frequency of audits. What it requires is that the audit systems you have actually produce assurance and improvement — not just paperwork. An audit system that never identifies issues or never drives change does not meet Regulation 17, regardless of how many audits are logged.
There is no single required frequency. Different types of audit have different natural rhythms — medication audits often monthly, care plan audits quarterly, infection control audits in response to risk. What matters more than frequency is that audits are scheduled in advance, properly resourced with time, completed by someone competent, and that their findings are acted on and reviewed. A service with a considered audit calendar of ten audits a year that all produce meaningful findings is better governed than a service running thirty superficial audits nobody follows up on.
The person completing an audit needs to understand what good practice looks like in the area being audited. This often means the registered manager, deputy manager, or quality lead — or a trained senior carer for specific audit types. Delegating audits to untrained staff commonly produces the “completed but didn’t identify issues” pattern that inspectors criticise. Auditing is a skill that develops through training, supervision, reflection and feedback — not through being handed a checklist.
A poor audit action is vague, unowned, open-ended, and addresses only the single instance identified. “Improve care planning” is a poor action. A good audit action is specific about what will change, who owns it, when it must be complete, and whether it addresses a wider theme. “Review all care plans for people receiving diabetic care to ensure monitoring guidance is documented, by 30 April” is a better action. Even better is an action that also considers whether the same gap exists elsewhere in the service.
Pause and apply professional curiosity. In most services, there is almost always something that can be strengthened — a record that could be clearer, a process that could be smoother, a staff conversation that needs to happen. An audit that produces no actions is often a sign that the auditor was looking for compliance rather than for improvement. The more useful question is not “is everything okay?” but “what could be better?” A well-conducted audit almost always surfaces something worth acting on.
This is the subject of the second article in the governance trilogy — Why Closing the Loop on Actions Is the Missing Half of Quality Improvement. In short: an action is only genuinely closed when there is evidence it has been tested in practice and embedded across the team — not just marked complete on the action log. Carevia uses the SMART-TE framework (SMART plus Tested and Embedded) to structure this. An action that is “closed” without testing often reappears in the next audit cycle.
The Carevia Governance Trilogy is three linked articles making one underlying argument: governance artefacts — audits, actions, and policies — fail when they are not connected to practice through a living leadership discipline. Each article examines the pattern in a different artefact. This article is the first, focused on audits. The second examines actions and introduces SMART-TE. The third examines policies and introduces the policy–procedure–practice triad. Read together, they articulate the Carevia thesis that artefacts without discipline are worse than no artefacts at all.
RAOF™ — Read, Ask, Observe, Feedforward — is the leadership habit Carevia uses to connect documents to practice. Applied to an audit, it means: reading what the audit documents show, asking the staff closest to the practice, observing what is actually happening on shift, and feeding findings forward into the next governance cycle. A manager who brings the RAOF habit to their audit cycle will surface issues that a desk-based audit would miss, because RAOF treats the audit as a starting point for inquiry rather than an endpoint for paperwork.
Carevia Pro+ includes the Inspection Readiness Dashboard — 34 quality statements, 127 audit prompts across all five CQC domains, SMART-TE action tracking built in, and RAOF™ reflection prompts at every stage. It is designed to operationalise the principles in this article without adding administrative burden. Ask Carevia+, also inside Pro+, acts as a virtual Senior Quality Partner to sense-check audit findings, explore themes, and strengthen actions before they are set. Together, they turn an audit schedule into a governance habit.
Many managers find that the hardest part of auditing is not completing the form. It is knowing what questions to ask and what risks to look for. Carevia Pro+ gives registered managers practical governance tools, the Inspection Readiness Dashboard with SMART-TE action tracking, and Ask Carevia+ — a virtual compliance assistant designed to help leaders reflect on audits, actions and improvement.
