How Registered Managers Demonstrate Accountability for Poor Incident Review and Lack of Learning

Incidents happen in all services. What matters is what happens next. When incidents are recorded but not properly reviewed, the same risks can occur again. Patterns are missed, and opportunities to improve are lost. This creates a cycle where issues repeat without clear explanation. The Registered Manager is accountable for ensuring incidents lead to learning and change. The key question is whether incidents are used to improve care or simply recorded and closed. For further guidance, see our Registered Manager accountability guidance, CQC quality statements resources and CQC compliance knowledge hub.

Why this matters

Without proper review, incidents become isolated events. Staff may respond in the moment but fail to understand underlying causes. This increases the risk of recurrence.

It also weakens governance. If incident data is not analysed, it cannot be used to evidence improvement. This affects inspection outcomes and commissioner confidence.

Strong Registered Manager oversight ensures incidents are reviewed, understood and used to drive change. It also ensures that learning is shared across the service.

Clear framework for accountable incident review

An effective system moves beyond recording incidents to analysing them. This includes identifying causes, reviewing actions and implementing improvements.

The Registered Manager must be able to show that incident trends are monitored and addressed. This ensures that learning is consistent and visible.

Accountability is strongest when incident review leads to measurable improvement in practice.

Operational example 1: Repeated falls not analysed for underlying cause

Step 1. The staff member records a fall, including circumstances, location and immediate response, in the incident form and daily care record.

Step 2. The shift leader reviews the incident, identifies any immediate risk factors and records initial findings and actions in the handover record.

Step 3. The senior staff analyses multiple fall incidents, identifies patterns such as timing or environment and records findings in the incident analysis log.

Step 4. The Registered Manager reviews analysis, determines required changes and records decisions and actions in the governance tracker.

Step 5. The Registered Manager reviews fall trends regularly and records outcomes and improvements in governance meeting minutes.

What can go wrong is that each fall is treated separately. Early warning signs include repeated incidents in similar circumstances. Escalation may involve specialist input. Consistency is maintained through analysis.

Governance should audit incident patterns, analysis and actions. Managers review cases, the Registered Manager reviews trends and provider oversight reviews patterns. Action is triggered by repetition.

The baseline issue is often lack of analysis. Improvement can be measured through reduced incidents. Evidence comes from logs, audits and care records.

Operational example 2: Incident actions identified but not embedded into practice

Step 1. The incident review identifies required actions, which are recorded clearly with responsibilities and deadlines in the incident action log.

Step 2. The manager communicates actions to staff, ensures understanding and records communication and attendance in team meeting or supervision records.

Step 3. Staff implement changes in practice and record actions taken and outcomes in care records and task logs.

Step 4. The Registered Manager reviews whether changes are being followed and records findings in the governance tracker.

Step 5. The Registered Manager reviews effectiveness of actions over time and records outcomes in governance meeting minutes.

What can go wrong is that actions are agreed but not applied. Early warning signs include repeated issues and inconsistent practice. Escalation may involve supervision or training. Consistency is maintained through monitoring.

Governance should audit action implementation, compliance and outcomes. Managers review practice, the Registered Manager reviews trends and provider oversight reviews patterns. Action is triggered by non-compliance.

The baseline issue is often poor follow-through. Improvement can be measured through consistent practice. Evidence comes from records, audits and feedback.

Operational example 3: Incident trends not shared across the service

Step 1. The Registered Manager identifies trends in incident data and records findings and key themes in the governance report.

Step 2. The manager shares learning with staff, explains implications for practice and records communication and attendance in meeting records.

Step 3. Staff apply learning in care delivery and record actions and changes in care records and task logs.

Step 4. The Registered Manager reviews whether learning is applied consistently and records findings in the governance tracker.

Step 5. The Registered Manager reviews incident trends over time and records improvements and outcomes in governance meeting minutes.

What can go wrong is that learning remains within management. Early warning signs include repeated issues across teams. Escalation may involve wider communication. Consistency is maintained through sharing.

Governance should audit learning dissemination, staff understanding and outcomes. Managers review communication, the Registered Manager reviews trends and provider oversight reviews patterns. Action is triggered by repetition.

The baseline issue is often poor communication. Improvement can be measured through reduced incidents and improved practice. Evidence comes from audits, records and feedback.

Commissioner expectation

Commissioners expect incidents to lead to improvement. They want evidence that services learn from issues and reduce risk over time.

They are also likely to assess whether incident data is used effectively. A strong service can demonstrate clear learning and outcomes.

Regulator / Inspector expectation

Inspectors will review incident records and governance systems. They expect analysis and learning.

If incidents are not reviewed properly, accountability is reduced. If learning is clear, leadership is easier to evidence.

Conclusion

Incident review is a key part of Registered Manager accountability. It ensures that risks are understood and addressed. Without it, services can repeat the same mistakes.

Strong systems ensure that incidents are analysed, actions are implemented and learning is shared. They also provide clear evidence of governance.

Accountability becomes visible when incident review leads to measurable improvement and safer care. This supports effective leadership and service quality.

---