Serious Incident Notifications to CQC: Getting Thresholds, Timelines and Evidence Right

Serious incidents test a provider’s systems under pressure. Decisions about whether to notify, when to notify, and what to include are often made while facts are incomplete and teams are stretched. Inspectors therefore look less for perfection and more for defensible judgement: clear thresholds, timely action, and a traceable rationale. This article sits within Notifications, Statutory Reporting & Duty of Candour and links directly to how providers demonstrate consistency and learning against the CQC Quality Statements & Assessment Framework in practice.

Many organisations improve regulatory confidence by using the adult social care regulatory compliance knowledge hub as an ongoing resource.

Why serious incident notifications are a high-risk inspection area

CQC scrutiny of notifications is rarely about a single missed form. It is about patterns: repeated delays, inconsistent thresholds, or evidence that managers are uncertain about what constitutes serious harm. Inspectors commonly triangulate notifications against:

• incident logs and safeguarding referrals
• complaints and whistleblowing concerns
• serious incident reviews and governance minutes
• family testimony about how incidents were handled

If an incident appears serious but no notification was made, providers must be able to explain why, clearly and confidently.

Defining seriousness: moving beyond vague definitions

Policies often restate regulations but do not help staff decide under pressure. Strong providers operationalise seriousness by defining:

• Harm criteria: physical injury, psychological harm, neglect, abuse, or significant deterioration.
• Avoidability: whether reasonable controls failed or were absent.
• System impact: whether the incident exposes wider service risk (e.g. training gaps, staffing models, interface failures).

These criteria should be embedded into incident reporting tools so that managers are prompted to consider notifiability every time.

Managing evolving information without delaying notification

A common error is waiting for “all the facts” before notifying. CQC expects providers to notify based on information available at the time, then submit follow-up information as reviews progress.

Operationally, this means:

• making an initial notification once seriousness thresholds are met
• recording what is known and what is still being investigated
• updating internal records as new information emerges
• linking notification decisions to safeguarding and review outcomes

Delays caused by internal uncertainty are rarely viewed favourably.

Operational example 1: fall resulting in delayed diagnosis

Context: A person falls during the night and reports pain but no obvious injury. Staff monitor and record observations. Two days later, the person is diagnosed with a fracture following hospital admission.

Support approach: The service escalates medically, reviews night-time checks, and initiates a serious incident review.

Day-to-day delivery detail: The Registered Manager reviews incident notes, handover records and pain management documentation. They assess whether staff followed escalation guidance and whether earlier referral would reasonably have been expected. The notification decision is made once serious injury is confirmed, with a clear rationale explaining the timing.

How effectiveness is evidenced: Learning actions include refresher training on post-fall monitoring, updated escalation thresholds in night protocols, and audit results showing improved documentation and earlier GP contact in similar cases.

Operational example 2: safeguarding concern escalating to police involvement

Context: A safeguarding allegation initially appears low-level but escalates when police decide to investigate potential criminal neglect.

Support approach: The provider cooperates with safeguarding and police processes, implements protective measures, and reassesses notifiability.

Day-to-day delivery detail: The manager updates the incident record to reflect escalation, documents discussions with safeguarding partners, and submits a CQC notification once seriousness thresholds are clearly met. Internal communications ensure staff understand why the decision changed.

How effectiveness is evidenced: Governance minutes show how escalation triggers are reviewed, and subsequent incidents demonstrate earlier recognition of police involvement as a seriousness indicator.

Operational example 3: restrictive practice leading to hospital admission

Context: During an episode of severe distress, physical intervention is used. The person sustains an injury requiring hospital treatment.

Support approach: Immediate safeguarding, clinical escalation and family contact occur, alongside notification consideration.

Day-to-day delivery detail: The service reviews PBS guidance, staff training records and de-escalation attempts. The notification records both the injury and the use of restrictive practice, with a clear explanation of context and immediate risk reduction steps.

How effectiveness is evidenced: The provider tracks restrictive practice frequency, injury rates and staff competency, showing reduced reliance on physical intervention following targeted learning.

Commissioner expectation

Commissioner expectation: Commissioners expect serious incidents to be recognised early, escalated proportionately and reviewed transparently. They look for evidence that notifications link directly to learning, service improvement and risk mitigation across contracts.

Regulator / Inspector expectation (CQC)

Regulator / Inspector expectation (CQC): Inspectors expect providers to demonstrate confidence in their thresholds, timely notification once seriousness is identified, and a clear audit trail explaining decisions. They also expect learning to reduce recurrence, not just satisfy reporting requirements.

Embedding confidence into everyday management

Providers that perform well treat serious incident notification as a routine management task, supported by clear prompts, peer checking and governance oversight. When managers can explain why they notified or did not notify, systems are usually working as intended.

---