How Registered Managers Evidence Accountability for Poor Incident Learning and Repeat Events
Incidents happen in all services. What matters is what changes afterwards. When the same type of incident repeats, it usually means the original learning was not applied properly. This can include repeat falls, repeated medication errors or recurring behavioural incidents. The Registered Manager is accountable for ensuring that learning is identified, acted on and sustained. The key question is whether the service can show that incidents lead to real change in practice. For more detail, see our Registered Manager accountability guidance, CQC quality statements resources and CQC compliance knowledge hub.
Why this matters
Repeat incidents are one of the clearest indicators of weak governance. They suggest that issues have been identified but not resolved. This increases risk for people using services and creates concern for commissioners and inspectors.
It also affects credibility. If the same issues continue despite previous actions, it becomes difficult to show that management systems are effective. This weakens accountability and confidence in leadership.
Strong Registered Manager oversight means that incidents are analysed, actions are taken and improvements are monitored. It also means that repeat patterns are identified early and addressed.
Clear framework for accountable incident learning
An effective approach to incident learning includes three stages. First, identifying what happened and why. Second, deciding what needs to change. Third, checking whether those changes have worked.
The Registered Manager must be able to show that each stage is completed consistently. This includes linking incidents to care plans, staff practice and governance systems.
Accountability is strongest when incident trends are monitored, actions are followed through and improvements are evidenced over time. This demonstrates that learning is embedded.
Operational example 1: Repeat falls despite previous actions
Step 1. The support worker records a fall, including circumstances, time and immediate response, ensuring all details are documented in the incident form and daily care record.
Step 2. The shift leader reviews the incident, compares it with previous falls and records identified patterns and immediate actions in the handover and incident log.
Step 3. The Registered Manager reviews repeated falls, determines whether previous actions were effective and records findings and required changes in the governance tracker.
Step 4. The care plan and risk assessment are updated to reflect new controls, and changes are recorded clearly in the care planning system with rationale and implementation date.
Step 5. The Registered Manager reviews fall trends regularly, checks for reduction and records outcomes and further actions in governance meeting minutes.
What can go wrong is that falls are treated as isolated events. Early warning signs include repeated incidents and unchanged care plans. Escalation may involve additional assessments or external input. Consistency is maintained through trend analysis and follow-up.
Governance should audit fall frequency, care plan updates and management response. Managers review incidents, the Registered Manager reviews trends and provider oversight reviews patterns. Action is triggered by repeat falls.
The baseline issue is often lack of effective change. Improvement can be measured through reduced falls and clearer care plans. Evidence comes from incident logs, audits and care records.
Operational example 2: Medication errors repeating across shifts
Step 1. The staff member records a medication error, including details of the error, time and immediate action, in the MAR chart and incident form.
Step 2. The shift leader reviews the error, compares it with previous incidents and records identified trends and immediate corrective actions in the handover record.
Step 3. The Registered Manager reviews repeated medication errors, identifies root causes such as training or process issues and records findings in the medication governance log.
Step 4. Actions such as retraining, process changes or increased checks are implemented, and details are recorded in the training and governance tracker.
Step 5. The Registered Manager reviews medication error trends, checks for improvement and records outcomes and further actions in governance meeting minutes.
What can go wrong is that errors are addressed individually without addressing root causes. Early warning signs include repeated errors and unclear processes. Escalation may involve retraining or process redesign. Consistency is maintained through monitoring and review.
Governance should audit error frequency, action effectiveness and staff competency. Managers review errors, the Registered Manager reviews trends and provider oversight reviews patterns. Action is triggered by repeated errors.
The baseline issue is often repeated mistakes. Improvement can be measured through reduced errors and clearer processes. Evidence comes from MAR charts, incident logs and audits.
Operational example 3: Behavioural incidents repeating without change in approach
Step 1. The support worker records a behavioural incident, including triggers, response and outcome, in behaviour monitoring records and daily notes.
Step 2. The shift leader reviews incidents, identifies patterns and records findings and immediate guidance in the handover document.
Step 3. The Registered Manager reviews repeated incidents, determines whether support strategies need updating and records decisions in the behaviour oversight log.
Step 4. The care plan is updated to reflect revised strategies, and changes are recorded clearly in the care planning system with rationale and implementation date.
Step 5. The Registered Manager reviews behaviour trends regularly, checks for improvement and records outcomes and further actions in governance meeting minutes.
What can go wrong is that incidents are recorded but not analysed. Early warning signs include repeated triggers and unchanged strategies. Escalation may involve specialist input. Consistency is maintained through structured review.
Governance should audit behaviour trends, care plan updates and management response. Managers review incidents, the Registered Manager reviews trends and provider oversight reviews patterns. Action is triggered by repeated incidents.
The baseline issue is often lack of learning. Improvement can be measured through reduced incidents and better strategies. Evidence comes from behaviour logs, care plans and audits.
Commissioner expectation
Commissioners expect providers to demonstrate learning from incidents. They want evidence that repeated issues are identified and addressed. This includes clear records and follow-up actions.
They are also likely to assess whether improvements are sustained. A strong service can demonstrate reduced repeat incidents and improved outcomes.
Regulator / Inspector expectation
Inspectors will review incident records to assess whether learning is embedded. They expect services to identify patterns and act on them.
If incidents repeat without change, accountability is weakened. If learning is evident and effective, leadership is easier to evidence.
Conclusion
Repeat incidents highlight whether a service learns from experience. The Registered Manager is accountable for ensuring that learning is identified, applied and sustained.
Strong systems link incident analysis to action and follow-up. They ensure that improvements are implemented and monitored.
Accountability becomes visible when incidents lead to change, trends improve and outcomes are better. This supports safe, effective and well-led services.
Latest from the knowledge hub
- How CQC Registration Applications Fail When Equipment, PPE and Supply Readiness Are Not Operationally Controlled
- How CQC Registration Applications Fail When Quality Audit Systems Exist but Do Not Drive Timely Action
- How CQC Registration Applications Fail When Recruitment-to-Deployment Controls Are Not Strong Enough
- How CQC Registration Applications Fail When Staff Handover and Shift-to-Shift Communication Are Not Operationally Controlled