Why Closing the Loop on Actions Is the Missing Half of Quality Improvement in Adult Social Care
Last updated: April 2026Reading time: 11 minutesCategory: Governance & Inspection Readiness
Pro+ members track actions through the full SMART-TE lifecycle in the Inspection Readiness Dashboard. See how it works →
Setting an action and closing the loop on an action are two different things. This guide explains why — using a real scenario every registered manager will recognise — and introduces SMART-TE, the Carevia evolution of SMART that builds Tested and Embedded directly into how you track improvement.
Your medication audit flags a gap. Someone has recently been prescribed a PRN painkiller but there is no protocol in place — no guidance on when to give it, how to monitor, or when to escalate. You set the action, assign it to the right person, the protocol gets written, and you sign it off as complete.
Three months later, the local authority visits. They ask to see your recent medication audits. They complete their own. And they find that another person has recently been prescribed a painkiller — with no protocol in place.
This is the beginning of an uncomfortable conversation.
The manager fixed the issue. But they fixed it in isolation. They updated one protocol for one person. They did not ask why no protocol existed in the first place, or who was responsible for ensuring every new PRN prescription triggers a protocol, or whether there was a regular system to check that all PRN medications were covered. The original action was complete. The underlying problem was not.
The action was done. The loop was not closed.
This distinction — between completing an action and genuinely closing the loop — is one of the most significant gaps in how adult social care services manage quality improvement. It is why the same issues keep appearing in audits. Why CQC inspectors find concerns that a service’s own governance systems had already identified. Why improvement plans grow longer without services actually improving.
This article explains what closing the loop actually requires — and introduces SMART-TE, the Carevia evolution of the traditional SMART framework that builds the two missing steps directly into action planning.
The SMART acronym — Specific, Measurable, Achievable, Relevant, Time-bound — has been a fixture of action planning for decades. It is a reasonable starting point.
But in adult social care governance, SMART has a significant limitation.
A SMART action tells you what needs to happen and by when. It does not tell you whether it actually worked.
Consider this action:
Example SMART action: Update the medication administration record template to include a second signatory field for high-risk medications — by 30 April.
That action is SMART. It is specific. It is measurable. It is time-bound. But answering ‘yes, completed’ does not tell you whether staff are actually using the field, whether the rationale has been communicated, or whether the change has reduced risk in practice.
This is the gap that SMART, on its own, cannot close. The action may be complete. The issue may not be resolved. In adult social care, where the consequences of unresolved governance gaps can directly affect the wellbeing of people receiving care, this distinction is not academic. It is the difference between governance that provides assurance and governance that only appears to.
Introducing SMART-TE: Tested and Embedded Carevia Framework
At Carevia, we use an evolution of the traditional SMART framework: SMART-TE. The additional two letters stand for Tested and Embedded. They represent the two steps that most action planning stops short of — and the two steps that determine whether an action has genuinely driven improvement.
Letter
What it asks
S
Is the action Specific — clear enough for anyone to understand and act on?
M
Is it Measurable — will you know when it’s done?
A
Is it Achievable — realistic given the resources and timescale?
R
Is it Relevant — does it actually address the root issue?
T
Is it Time-bound — does it have a clear deadline?
T
Has it been Tested — does evidence confirm it worked in practice?
E
Has it been Embedded — is the improvement sustained and consistent across the team?
These final two letters shift the question from did we do the thing to did the thing make a difference. That shift is significant. It requires leaders to go back. To observe. To check. To ask. And that is exactly where many governance systems currently stop short.
SMART-TE is built into the Carevia Inspection Readiness Dashboard. Carevia Pro+ members can track every action through the full SMART-TE lifecycle — from Not Started through Completed to Tested and Embedded — with built-in RAOF™ prompts that guide you through verification before you close an action. Find out how the dashboard works →
Testing an action means gathering evidence that the change has worked as intended. It is not enough to review the updated document. Testing means going one step further and checking whether the change has translated into practice.
Type of action
What testing looks like
A care plan update
Did you review whether staff are working from the updated plan? Did you check recent daily notes to see whether they reflect the change? Did you speak to the staff member most likely to have used it?
A training intervention
Did you observe whether the training has influenced how staff carry out the relevant task? Did you discuss it in supervision and ask what the person actually took away from it?
A process change
Did you check whether the new process is being followed consistently — not just by one member of staff but across the team?
Testing an action is not about distrust. It is about taking quality improvement seriously enough to verify it. In practice, testing often reveals one of three things:
The change worked as intended — and you now have evidence to support it
The change worked partially — which tells you what the next action needs to address
The change was not followed — which tells you something important about communication, training, or culture
All three of those outcomes are valuable. None of them are visible without testing.
Tested asks: did it work this time? Embedded asks: is it still working — consistently, without the manager having to check every time?
An action is embedded when the improvement has become part of the everyday rhythm of the service. Staff do not need to be reminded. The updated process is what everyone does, not what some people do when they remember. This does not happen automatically. Embedding requires:
Communication — staff understanding not just what has changed but why. People sustain changes when they understand the reason behind them.
Consistency — the same standard is expected every shift, not only when the manager is present. If practice changes when the manager walks in and reverts when they leave, the action is not embedded.
Reinforcement — the improvement is reflected in supervision conversations, handovers, spot checks, and future audits. It becomes part of how the service talks about and monitors itself.
A useful test: If you were to check the same area in your next audit cycle — six or eight weeks from now — would the improvement still be visible? If the honest answer is ‘probably not’, the action has not yet been embedded.
The RAOF™ framework — Read, Ask, Observe, Feedforward — provides a structured way to test and embed actions rather than simply recording their completion. Each strand of the cycle maps directly onto the process of closing the loop.
RAOF™ strand
Applied to closing the loop
Read
Review the action, the context it came from, and what evidence currently exists. What does the documentation tell you?
Ask
Speak to the people closest to the change. Do staff understand why the action was set? Have they encountered barriers to implementing it?
Observe
Go and see. Look at practice, not just paperwork. Is what you read and heard reflected in what is actually happening?
Feedforward
Use what you found to inform the next step. If the action is tested and working, record that evidence. If not yet embedded, set a next action and feed learning forward.
RAOF™ is a leadership habit, not another audit. It does not treat the governance cycle as a one-way process that ends when an action is set. It treats quality improvement as a habit held by the leader — one that only closes the loop when there is genuine assurance that practice has changed.
Stop marking actions complete. Start closing the loop.
The Carevia Inspection Readiness Dashboard is built around SMART-TE. Every action you log moves through a lifecycle — Not Started, In Progress, Completed, Tested, Embedded — with RAOF™ reflection prompts at each stage that push you to verify the change before you close it. It is the only governance tool in adult social care built specifically around this principle.
34 CQC quality statements — 127 audit prompts across all 5 domains
SMART-TE action tracking — Tested and Embedded statuses with evidence prompts
RAOF™ Test & Embed panel — structured verification before sign-off on every action
Team Question Set export — distribute audit prompts across your team to demonstrate distributed governance
Ask Carevia+ — sense-check governance decisions against CQC expectations
Understanding why actions fail to close is as important as understanding how to close them. Go back to the PRN scenario from the opening. The manager did everything that was expected of them. So why did the local authority find the same gap three months later? These are the patterns that explain it — and they will be familiar to any manager who has ever watched the same issue reappear in a subsequent audit.
The action addressed the symptom, not the cause. The missing PRN protocol was written. But the question that needed answering was different: why did a new prescription not automatically trigger a protocol being created? Without answering that, the system remains unchanged. The next new prescription will carry the same risk. One person’s protocol was fixed. The process that should have caught it in the first place was not.
The action was communicated to the wrong person. The manager knows a protocol now exists. The staff member administering medication at the weekend, or the senior covering a night shift, may not know where to find it, what it says, or that the expectation has changed. The document was created. The practice did not follow.
The timescale was met, but the check was not done. The protocol was signed off on the due date. No one went back to check whether staff were using it, whether it was accessible at the point of administration, or whether the person’s needs had changed since it was written. Completion was recorded. Verification was not.
The improvement depended on the manager’s presence. When the manager is on shift, things are done correctly. When they are not, practice reverts. The protocol exists but has not been understood or owned by the team. It was complied with, not embedded.
The learning never fed forward. The action closed. No one asked whether other people in the service had PRN medications without protocols. No one checked whether the same gap existed elsewhere, or whether the audit tool needed amending to catch this category of risk more systematically. One record was corrected while the wider theme was left unexamined.
The pressure to report numbers over outcomes. This is the pattern that is least often named, but it is one of the most corrosive. Many registered managers work within provider structures where governance reporting asks: how many actions did you complete this month? Reporting fifteen completed actions sounds strong. It looks strong on a dashboard. It satisfies a line manager reviewing the governance summary.
But if those fifteen actions were each fixed in isolation — a protocol written, a care plan updated, a checklist amended — without any of them being tested or embedded, the service is not fifteen improvements stronger. It is fifteen actions closer to the same issues resurfacing at the next audit, or the next inspection, or the next local authority visit.
The quantity pressure is real and it is not going away. But chasing completion numbers without closing loops means you are permanently inside a cycle of recurring actions. The same themes. The same findings. A governance log that gets longer without the service actually improving. SMART-TE does not remove the pressure to complete actions — it changes what completion means.
“The service is not fifteen improvements stronger. It is fifteen actions closer to the same issues resurfacing at the next audit.”
Return to the PRN scenario one more time. The manager’s action log shows the protocol was written and signed off on time. From a governance reporting perspective, that action is green. Complete. Done.
But when the local authority arrives and checks a different person’s medication, what they find is not a completed action. What they find is a service that fixed one instance of a problem without changing the conditions that allowed the problem to exist. The action log said complete. The evidence said otherwise.
This is the difference between a partially closed action and a fully closed one — and it is a difference that CQC inspectors, local authority reviewers, and internal auditors are increasingly trained to look for.
What a partially closed action looks like
What a fully closed action looks like
Action marked complete on the date agreed
Action marked complete with supporting evidence recorded
Action owner confirmed the task was done
Evidence includes observation, spot check, or follow-up audit
No further reference to the issue
Follow-up visible in supervision notes or team meeting minutes
Next audit may find the same gap
Next audit shows improvement sustained across the team
A CQC inspector, local authority or internal auditor finds issues that had been marked as complete
The same people see clear evidence of completion, testing and sustained improvement
The strongest evidence packages show a clear narrative: issue identified, action set, practice tested, improvement embedded, evidence that it remains in place. That narrative is visible in governance meeting minutes, supervision records, follow-up audits, and daily practice. When it is consistent across all of those sources, it is compelling. When it is not, the gaps become visible the moment someone looks carefully.
It is worth being direct about what the two approaches actually produce over time.
If you use SMART, you will complete actions. Your governance log will show progress. Your line manager will see numbers moving. But you will likely find the same issues recurring in subsequent audits. You will set similar actions again. You will have uncomfortable conversations with inspectors, local authority reviewers, or your own senior leadership about why the same themes keep appearing. The actions were completed. The service did not change.
If you use SMART-TE, you will still complete actions — but you will not mark them complete until there is evidence they worked. Actions will pass testing. Improvements will become embedded in how the team operates. The same issues will be significantly less likely to recur. Each closed loop builds genuine quality into the service rather than adding another line to an action log. Over time, your governance tells a different story — not a list of things that were done, but a record of practice that changed.
If the second scenario sounds like where you want your service to be, the Carevia Inspection Readiness Dashboard is built around exactly this principle — with SMART-TE action tracking built in across all 34 CQC quality statements. See how it works →
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. SMART-TE is what makes sure the actions that flow from those documents are tested and embedded, not just closed on paper. Without that discipline, no amount of policy volume, audit frequency, or action tracking will make a service well-led.
A Practical Self-Check for Registered Managers
Before accepting that an action is complete, these five questions are worth applying.
1What evidence do I have that this action worked — not just that it was done?
2Have I observed practice to check whether the change has been followed — or am I relying on the word of the person who made the change?
3Do staff understand why this change was made? Could they explain it to an inspector?
4If I checked this area in the next audit cycle, would I expect to find the same improvement still in place?
5Has the learning from this action fed forward? Have I considered whether this issue represents a wider theme?
If you cannot answer confidently, the loop is not yet closed. These questions are not about creating extra work. They are about making the work you are already doing count.
Closing the loop means going beyond the completion of an action to verify that it has achieved its intended outcome in practice. An action may be marked complete — the task was done, the document was updated, the training was booked — but if practice has not changed, the issue has not been resolved. Closing the loop requires testing that the change has worked and confirming that it has become embedded in everyday practice, not just delivered as a one-off task.
SMART-TE extends the traditional SMART framework — Specific, Measurable, Achievable, Relevant, Time-bound — by adding two additional criteria: Tested and Embedded. Tested asks whether evidence confirms the action worked in practice. Embedded asks whether the improvement has become a consistent part of how the service operates, not just a one-time correction. These two additional steps address the most common failure in action planning: completing a task without verifying whether it drove the intended change.
Recurring issues almost always indicate that actions were completed but not embedded. The task was done — a document was updated, a conversation was had — but the root cause was not addressed, the change was not tested, or the improvement was not communicated in a way that changed practice across the team. SMART-TE helps identify this gap by requiring evidence of testing and confirmation of embedding before an action is considered genuinely complete.
RAOF™ — Read, Ask, Observe, Feedforward — is a reflective leadership habit that supports genuine assurance rather than paperwork completion. Applied to action planning, it means: reading the evidence that an action is supposedly done, asking the people closest to the change whether it is working, observing practice to verify that improvement is visible, and feeding what you find forward into the next governance cycle. This prevents actions from closing prematurely and ensures improvement is real rather than recorded.
Strong evidence of an embedded action might include a follow-up audit demonstrating the improvement is sustained, supervision records that reference how the change was discussed and applied in practice, observation or spot-check notes confirming the change is being followed consistently, and governance meeting minutes that track the action from identification through to verified embedding. The key is consistency — the same picture across multiple sources of evidence.
Well-Led governance requires more than setting actions. Inspectors will look for evidence that improvements were actually implemented, that learning was embedded in practice, and that governance systems are genuinely effective rather than producing completed paperwork. Services that can demonstrate closed loops — with evidence that actions produced real change — are far better placed to demonstrate effective governance under Regulation 17 and the Well-Led quality statements. See also: What Good Looks Like for Well-Led.
Start by reviewing your most recent action plan and applying the five self-check questions above to each open or recently completed action. For any where the loop has not been genuinely closed, set a new action that explicitly includes a testing step and a date by which you will confirm embedding. Inside Carevia Pro+, the Inspection Readiness Dashboard includes SMART-TE action tracking with RAOF™ evidence prompts designed to support this process exactly.
Ready to move from setting actions to closing them?
Carevia Pro+ gives registered managers access to the Inspection Readiness Dashboard with built-in SMART-TE action tracking, the full RAOF™ leadership habit framework, and Ask Carevia+ — a virtual quality partner to help you sense-check audit findings, test the strength of your actions, and build the evidence that Well-Led governance requires.
Inspection Readiness Dashboard — all 5 domains, 34 quality statements, built-in SMART-TE action tracking with Tested and Embedded statuses
