The Closed Action That Wasn’t Closed
A safety action can be marked complete while the evidence behind implementation remains partial, localised or unreviewed.
Synthetic scenario. Illustrative only — does not describe any real organisation, supplier, patient, programme or event.
Scenario at a glance
- Industry context
- NHS acute trust; patient safety governance; clinical governance; committee and board assurance
- Primary persona
- Head of Patient Safety
- Trigger event
- A second deterioration event reveals that a previous safety action was closed without complete evidence of implementation.
- Assurance failure type
- Learning-to-action failure; action closure without evidence; committee assurance based on incomplete records.
- Scenario shape
- Weak signal → missed ownership → unclosed action → missing evidence → assurance failure → business impact
What happened
Northvale NHS Foundation Trust is a fictional medium-sized acute and community trust with a central patient safety team, divisional governance leads, ward-level safety huddles, a Quality and Safety Committee and a board-level Quality Committee.
Formal incident reporting is handled in a dedicated incident-management system. Safety actions, improvement evidence, risk themes, meeting updates and committee papers are tracked across spreadsheets, shared drives, emails, divisional action logs and meeting packs.
A patient on an acute medical ward deteriorated overnight and was transferred to ICU after delayed escalation. The initial review found that escalation guidance existed, but staff were inconsistent in using the deteriorating-patient checklist and escalation call process. The review also noted that a family member had raised concerns twice before escalation occurred.
The trust created three safety actions: refresh deteriorating-patient escalation guidance, confirm staff briefing and local simulation across acute wards, and audit recent escalation cases to confirm that family concern had been documented and considered.
At the next Quality and Safety Committee, the update said that escalation guidance had been refreshed, ward briefings were underway and audit would follow. Two months later, the action log showed all three actions as closed.
Three months after that, a similar deterioration event occurred on a different ward. The patient survived but required unplanned ICU admission, and the family submitted a formal complaint.
When the patient safety team tried to reconstruct the assurance trail, they found that guidance had been reissued by email but not embedded into ward-level practice. Several ward briefings had no attendance record. The audit had been completed in only two wards, not across all acute wards. The action had been marked closed because a divisional governance lead confirmed “implemented,” but supporting evidence had not been linked.
The board had been told that deteriorating-patient escalation learning had been addressed. The underlying evidence did not support that level of confidence.
What it cost
Patient and family impact
The event caused serious escalation, distress and loss of trust. The family expected a clear explanation of what had been learned and what had changed.
Operational impact
The trust had to conduct an urgent review, interview staff, reconstruct documents, audit acute wards, re-brief teams and revalidate the escalation process.
Governance impact
The Quality and Safety Committee escalated the issue. Board members challenged whether previous assurance could be relied on, and the trust had to distinguish action closure from evidence of change.
Regulatory and audit impact
The organisation faced possible external scrutiny if the pattern proved wider, with increased evidence burden for committee papers, audit response and family communication.
Remediation impact
Closed actions had to be reopened. The trust introduced stronger closure criteria and an evidence review gate before future closure.
Where the assurance chain broke
| Broken link | What was missing | Why it mattered |
|---|---|---|
| Weak signal capture | Family concern and delayed escalation were recorded in the incident review but not treated as reusable safety signals. | The concern stayed tied to one event instead of becoming a monitored theme. |
| Ownership | Actions were assigned to one broad divisional owner, but ward-level owners and evidence owners were unclear. | No one could show which ward had completed which action or which evidence was missing. |
| Action tracking | Status moved from in progress to closed without a clear evidence threshold. | Closure became administrative, not proof of implementation. |
| Evidence | Briefing records, simulation records, audit results and review notes were not linked to the action. | The trust could not defend the claim that learning had changed practice. |
| Review | Committee reporting showed completion but not evidence quality, partial implementation or unresolved wards. | Leaders received a clean summary but not the uncertainty beneath it. |
| Escalation | Incomplete implementation did not escalate before the second event. | Leadership did not see the gap early enough to challenge or intervene. |
| Assurance | Board assurance relied on a completed action log rather than a connected evidence trail. | The board could not confidently show what had changed, what remained open or what was unsafe to rely on. |
What should have been visible earlier
Known signals
- Original delayed-escalation incident.
- Family concern documented in the review.
- Repeated theme of delayed escalation.
- Ward variation in use of escalation guidance.
- Previous action plan with incomplete evidence.
Unowned actions
- Trust-level action assigned to one divisional lead.
- Ward-level delivery not assigned to named local owners.
- Audit ownership not separated from action ownership.
- Evidence review ownership not assigned.
Stale or missing evidence
- Guidance reissued but not confirmed as embedded.
- Briefing completion asserted but not consistently evidenced.
- Audit plan created but not completed across all relevant wards.
- Committee summary not updated to reflect incomplete implementation.
Missing review points
- No evidence gate before action closure.
- No committee view of actions closed without evidence.
- No distinction between complete, partially evidenced and impact reviewed.
- No formal review of whether action completion had changed practice.
How STREAM® Cloud could help
Make incomplete assurance visible earlier
STREAM® Cloud could help create structured records for the safety signal, learning response, action plan, ward-level implementation tasks, evidence items and committee review points.
Assign ownership across levels
STREAM® Cloud could help assign named owners at trust, division, ward, evidence review, committee sponsorship and board assurance levels.
Track action follow-through
STREAM® Cloud could help track due dates, action status, overdue items, partial completion, dependencies, review status and escalation status.
Link evidence to the action
STREAM® Cloud could help link evidence directly to the safety action, including guidance updates, ward briefing records, simulation records, audit results, committee review notes and board assurance items.
Distinguish closed from evidenced
STREAM® Cloud could help show which actions were overdue, unevidenced, partially evidenced or awaiting review.
Support ward-to-board assurance
STREAM® Cloud could help provide committee-ready views of open safety actions, actions closed without evidence, actions overdue by division, repeat safety themes and board-level assurance items with incomplete supporting detail.
Reduce manual reconstruction
STREAM® Cloud could help reduce the manual burden of reconstructing the story after a repeat event by keeping linked records, status changes, evidence references and review notes in one structured chain.
Related use case
Patient Safety & Clinical Governance
Want to see how STREAM® Cloud supports evidence-backed assurance?
STREAM® Cloud helps teams connect records, actions, evidence, review status and assurance outputs in a configurable workspace.