How Providers Evidence Safe Management of Incidents and Near Misses During a CQC On-Site Assessment

Incidents and near misses are key indicators of how a service manages risk in real time. During a CQC on-site assessment, inspectors often review incident records, ask staff how they respond to unexpected events and check whether learning is applied consistently. They may compare incident logs with care records, audits and governance summaries to test whether the service responds quickly and effectively. For more context, see our CQC inspection guidance articles, CQC quality statements resources and CQC compliance knowledge hub.

Strong providers evidence incident management by showing that events are recognised early, recorded clearly and followed through with appropriate action. They also demonstrate that near misses are treated seriously, not ignored. Inspection confidence usually increases when the service can show both immediate response and longer-term learning.

Why this matters

Inspectors often use incidents to understand how well a service manages risk under pressure. A well-handled incident can demonstrate strong leadership and safe practice, while a poorly managed one can highlight gaps in awareness, communication or decision-making.

Services also become vulnerable when near misses are not captured. These events often provide early warning of risk, and if they are not recorded or analysed, the service may miss opportunities to prevent more serious incidents later. Inspectors often test whether providers recognise and learn from these early signals.

Good preparation helps providers show that incident management is structured, timely and consistent. It allows them to evidence how staff respond, how managers review events and how learning is shared across the service.

Clear framework for inspection-ready incident management

A practical framework begins with immediate response. Staff should know how to ensure safety, provide appropriate care and report the incident quickly. This ensures that risk is reduced at the earliest stage.

The second stage is recording and escalation. Incidents and near misses should be documented clearly, with accurate detail and appropriate escalation to senior staff or external bodies where required. This allows for effective review and accountability.

The final stage is learning and prevention. Providers should be able to show what changed after the incident, whether actions were effective and how similar risks are prevented in future. This is what gives incident management real governance strength.

Operational example 1: A medication error occurs and must be managed safely and transparently

Step 1. The staff member identifies a medication error, ensures the person’s immediate safety and records the details of the error, timing and initial response in the incident report and care record.

Step 2. The senior on duty reviews the situation, determines whether medical advice is required and records the escalation and any advice received in the clinical communication log.

Step 3. The Registered Manager is informed of the incident, reviews the initial information and records the decision on further investigation and reporting requirements in the incident management system.

Step 4. The deputy manager investigates the incident, identifies contributing factors and records findings and recommended actions in the investigation report.

Step 5. The audit lead reviews whether actions have been implemented and records outcomes and learning in the governance summary.

What can go wrong is that the error is corrected quickly but not fully investigated, leading to repeated mistakes. Early warning signs include similar incidents, incomplete records and unclear understanding of what went wrong. Escalation may involve clinical review, safeguarding referral or provider notification depending on severity. Consistency is maintained through structured reporting, investigation and follow-up.

Governance should audit incident frequency, investigation quality, action completion and repeat patterns. Managers should review incidents promptly, deputies should track investigations and the Registered Manager should review trends monthly. Action is triggered by repeated incidents, weak investigations or delayed responses.

The baseline issue is often incomplete follow-through rather than initial response. Measurable improvement includes fewer repeated errors, stronger investigations and clearer learning. Evidence comes from incident reports, care records, investigation logs, audits and governance summaries.

Operational example 2: A near miss is identified but risks being overlooked

Step 1. The staff member identifies a near miss, such as a missed dose caught before administration, and records the event, potential risk and corrective action in the near miss log.

Step 2. The senior on duty reviews the near miss, considers whether it indicates a wider issue and records the initial assessment in the risk review sheet.

Step 3. The deputy manager reviews similar events, checks for patterns and records whether the near miss reflects a recurring risk in the quality tracking system.

Step 4. The team leader implements a targeted action, such as briefing or process adjustment, and records the change and staff understanding in the team communication record.

Step 5. The audit lead reviews whether near miss frequency has reduced and records outcome and further action in the governance tracker.

What can go wrong is that near misses are seen as minor and not recorded or reviewed, allowing risk to build unnoticed. Early warning signs include repeated informal corrections, lack of documentation and staff uncertainty about reporting expectations. Escalation may involve reinforcing reporting requirements, widening review or increasing oversight. Consistency is maintained through clear expectations and regular review.

Governance should audit near miss reporting rates, pattern identification, action effectiveness and staff awareness. Deputies should review logs regularly, managers should monitor trends and the Registered Manager should review outcomes monthly. Action is triggered by under-reporting, repeated near misses or lack of improvement.

The baseline issue is often under-recognition of near misses. Measurable improvement includes increased reporting, better pattern identification and reduced recurrence. Evidence comes from logs, audits, staff feedback and governance reports.

Operational example 3: Inspectors test whether incident learning is shared across the service

Step 1. The Registered Manager selects a recent incident with identified learning points and records the key findings and required actions in the service learning log.

Step 2. The deputy manager shares the learning with relevant staff through briefing or supervision and records attendance and understanding in the staff communication register.

Step 3. The team leader checks whether the learning has been applied in practice and records observed changes or gaps in the practice monitoring record.

Step 4. The quality lead reviews whether similar incidents have reduced following the learning and records the outcome in the reassessment report.

Step 5. The Registered Manager reviews whether learning has been embedded across the service and records conclusions and further actions in the governance summary.

What can go wrong is that learning is identified but not embedded, so the same issues reoccur. Early warning signs include repeated incidents, staff unaware of previous learning and limited evidence of change. Escalation may involve additional training, supervision or wider service review. Consistency is maintained through structured sharing and follow-up checks.

Governance should audit learning dissemination, staff understanding, impact on incident rates and repeat patterns. Managers should review learning regularly, deputies should check practice impact and the Registered Manager should review trends monthly. Action is triggered by repeated incidents, weak learning uptake or lack of improvement.

The baseline issue is often limited follow-through of learning. Measurable improvement includes reduced incident recurrence, stronger staff awareness and clearer evidence of change. Evidence comes from learning logs, communication records, monitoring notes, reassessment reports and governance summaries.

Commissioner expectation

Commissioners usually expect incident management systems to be robust, responsive and focused on improvement. They want confidence that incidents are managed safely, that near misses are captured and that learning leads to measurable change.

They are also likely to expect transparency. Strong providers can show how incidents are recorded, reviewed and used to strengthen practice across the service.

Regulator / Inspector expectation

Inspectors will usually expect incident management to align across records, staff knowledge and governance review. They may test whether staff understand reporting processes and whether learning is applied consistently. If these elements align, the service appears safe and well led.

They will also expect proactive learning. Strong inspection evidence shows that providers do not wait for serious incidents but act on early warning signs and near misses.

Conclusion

Evidence of effective incident and near miss management during a CQC on-site assessment depends on more than recording events. The strongest providers can demonstrate that incidents are managed safely, investigated thoroughly and used to improve practice.

Governance gives this evidence strength. Incident logs, investigation reports, learning records and follow-up actions should all support the same account of continuous improvement. When they do, leaders can show that risk is actively managed and reduced.

Outcomes are evidenced through fewer repeated incidents, stronger learning and clearer accountability. Consistency is maintained by applying the same reporting, investigation and review processes across all events so inspection evidence reflects everyday practice rather than isolated responses.