How to Evidence Incident Learning, Duty of Candour and Post-Incident Review During a CQC Inspection Visit

Incidents are one of the clearest ways inspectors assess whether a service is safe, honest and well led in reality rather than only in policy language. During a live inspection, CQC will review not only whether incidents were logged, but how staff responded at the time, whether relevant people were informed, whether openness and duty of candour were applied where appropriate and whether the service learned anything meaningful afterward. Strong providers can show a visible line from incident to review, from review to action and from action to measurable improvement. This article explains how providers can evidence that well in practice. For broader on-site context, see our CQC inspection guidance and how this aligns with CQC quality statements.

What Inspectors Look for in Incident Response and Learning

Inspectors want to see whether incidents are responded to calmly, recorded accurately and reviewed in a way that improves future practice. They test whether staff know what counts as an incident, when to escalate, when to notify managers or external bodies and how people or families are informed openly after harm or potential harm. They also compare incident forms with daily notes, handovers, safeguarding records, complaints, family feedback, staff supervision and governance review. A common weakness is that services log incidents but stop at administration. If there is no clear analysis, no candour decision, no action owner and no follow-up evidence, inspectors are likely to view the learning culture as weak.

Operational Example 1: Responding to a Fall and Evidencing Clear Same-Shift Review

Context: A person in residential care has an unwitnessed fall in their bedroom with no obvious fracture but visible distress and possible head impact. The baseline issue for the provider had been ensuring that incident records showed not only what happened, but also what checks, communication and learning followed in the same shift.

Support approach: The provider implemented a structured post-fall response pathway because inspectors often choose falls records to test how well a service links immediate safety action, communication, documentation and review.

Step 1: The first staff member responds immediately, checks safety, seeks appropriate clinical input and records the exact time, presentation, location and immediate response in the incident system and daily note during the same shift, rather than relying on later recollection.

Step 2: The shift lead reviews the person’s known falls risk, current care plan, recent mobility changes and whether any same-day safeguarding, clinical escalation or family communication threshold is met. This review and the rationale for each decision are recorded in the incident follow-up section before the shift ends.

Step 3: Where the incident meets duty of candour or family notification thresholds, the manager or delegated lead contacts the appropriate person within required timescales and records who was informed, what explanation was provided and what next steps were agreed in the communication and candour record.

Step 4: The shift lead updates handover and risk information the same shift, recording what later staff must monitor, whether observations are required, what environmental checks must be completed and whether temporary support changes now apply.

Step 5: The Registered Manager reviews the incident within the governance timeframe, records root factors, whether the falls plan was followed, what action is required and how improvement will be tracked through re-audit, observation or plan review.

What can go wrong: Staff may manage the immediate response appropriately but produce records that do not show why decisions were made, who was informed or what changed afterward.

Early warning signs: Incident forms with minimal context, repeated falls with no linked care-plan change or family reports of being told late or inconsistently.

Escalation and response: The first worker acts and records immediately, the shift lead reviews in the same shift and the manager makes and records communication, candour and learning decisions within required timescales.

Consistency and governance: Falls are reviewed through incident audit, care-plan sampling, observation and governance meetings so the service can evidence not just response but measurable learning.

Outcomes and evidence: Improvement is measured through fewer repeat falls, stronger same-shift documentation, quicker communication and better follow-up action closure. Evidence is triangulated across care records, staff practice, feedback and audit findings.

Operational Example 2: Applying Duty of Candour After a Medicines Error

Context: In supported living, a person receives a medicine later than prescribed because of a staff recording and timing error. There is no immediate serious harm, but the event is clinically relevant and may meet internal and external openness thresholds. The baseline risk was that services sometimes recorded the error but did not evidence the candour decision clearly enough.

Support approach: The provider embedded a medicines-error candour pathway so that incident handling would include honest communication, proportionate clinical review and traceable learning. This was chosen because inspectors often test whether a service is open when mistakes occur.

Step 1: The staff member identifies the error, seeks clinical or pharmacy advice where required and records the exact medicine, timing issue, discovered time and immediate protective action in the incident system and MAR-related note during the same shift.

Step 2: The shift lead reviews whether the person has been informed appropriately in the moment, whether additional observation is needed and whether the incident meets manager, family, clinical or candour threshold. The decision and rationale are recorded in the same-shift incident review section.

Step 3: The manager reviews within the required timeframe, records whether duty of candour applies and, if so, documents who was contacted, what explanation and apology were given and what support or follow-up information was offered in the candour communication record.

Step 4: The manager examines underlying factors such as handover weakness, time pressure, MAR design or competency gap, and records the identified contributory factors, corrective action and named owner in the medicines learning tracker rather than closing the matter at “staff reminded.”

Step 5: The Registered Manager reviews whether corrective actions changed practice, such as improved timing compliance, observation outcomes or MAR quality, and records whether the action can close or must escalate to broader governance review.

What can go wrong: Services may apologise informally or address the clinical issue but fail to document candour reasoning and learning clearly enough for inspection scrutiny.

Early warning signs: Similar medicines errors recurring, incident logs showing “spoken to staff” with no measurable action or unclear records of whether the person or representative was informed.

Escalation and response: The discovering staff member records immediately, the shift lead reviews same shift and the manager records candour and learning decisions within defined timescales, with action tracked to closure.

Consistency and governance: Medicines incidents are reviewed alongside MAR audits, supervision and incident themes so candour and learning are embedded into operational oversight.

Outcomes and evidence: Improvement is measured through fewer repeated medicines errors, stronger incident analysis and clearer communication records. Evidence is triangulated across incident forms, MAR records, staff practice and audit findings.

Operational Example 3: Converting Repeated Low-Level Incidents Into Service-Level Learning

Context: Over two months, a domiciliary care service logs several low-level incidents involving missed communication after late calls, minor frustration from people using the service and inconsistent records of when updates were given. No single event is severe, but the pattern suggests a wider reliability and communication issue. The baseline challenge was ensuring that repeated smaller events were treated as a meaningful learning theme rather than isolated operational noise.

Support approach: The provider created a thematic incident-learning process because inspectors often ask how leaders identify patterns and prevent repeat issues across the service.

Step 1: The quality lead reviews recent incident logs, complaints, compliments, call-monitoring data and handover records, recording recurring themes, affected teams and the baseline frequency of the issue in the monthly incident-learning dashboard.

Step 2: The Registered Manager analyses whether the theme reflects staffing instability, weak communication expectations, poor documentation or route-planning pressure, and records the likely root factors and operational risks in the governance summary rather than treating each event separately.

Step 3: A service-level action plan is opened with named leads, measurable objectives and time-bound steps, such as revised late-call communication process, call logging checks, targeted supervision and team briefing. These actions are recorded in the quality tracker with review dates and evidence sources.

Step 4: Managers monitor the changes through spot checks, record sampling and feedback gathering over the following weeks, documenting whether staff are now communicating delays correctly, where the evidence is recorded and whether people’s experience has improved.

Step 5: At the next governance review, the Registered Manager compares current incident frequency, feedback and audit findings against baseline, records whether the learning action reduced recurrence and decides whether to close, extend or escalate the improvement plan.

What can go wrong: Providers may manage each small incident politely but miss the fact that repeated minor failings are revealing a wider system weakness.

Early warning signs: Similar wording across multiple incident forms, recurring family frustration, repeated staff reminders with no improvement or incident counts remaining stable despite action plans.

Escalation and response: The quality lead or manager identifies the pattern through review, records service-level action and monitors progress against specific measures and timescales.

Consistency and governance: Thematic incident learning is checked through dashboard review, action tracking, feedback and re-audit so inspectors can see a functioning learning culture rather than administrative logging.

Outcomes and evidence: Improvement is measured through reduced repeated incidents, stronger communication performance and better feedback trends. Evidence is triangulated across incident logs, care records, staff feedback and governance findings.

Commissioner Expectation

Commissioner expectation: Commissioners expect providers to demonstrate honest incident handling, timely communication after harm or error and a clear line from incident review to service improvement and reduced recurrence.

Regulator / Inspector Expectation

Regulator / Inspector expectation: CQC inspectors expect leaders and staff to show that incidents are recorded accurately, reviewed proportionately and used for learning. They are likely to test whether duty of candour decisions, communication and follow-up actions are clearly evidenced and consistent.

How a Registered Manager Evidences This in Practice

A Registered Manager should be able to evidence strong incident learning through incident forms, candour records, investigation notes, action trackers, care-plan updates, re-audit results and governance review. Inspectors are reassured where managers can show exactly what happened, what was said, what changed and how improvement was tested over time.

Conclusion

Incident learning, duty of candour and post-incident review are evidenced during inspection through timely recording, open communication and visible managerial follow-through. Strong providers do not stop at logging the event. They show how immediate safety action, proportionate candour, root-cause review and tracked improvement work together to prevent recurrence and strengthen trust. A Registered Manager can demonstrate this to CQC by triangulating incident records, care notes, communication logs, staff practice and governance review. When those sources align, the service can evidence a culture that is honest when things go wrong, organised in its response and serious about turning incidents into measurable quality improvement.