Serious incident notifications: what counts, and when to report

Regulation 40 sets out categories of event that must be notified to Ofsted, several of which carry an expectation of being reported without delay — commonly understood as the same day, not within a few working days. The clearest categories — the death of a child, serious injury, a fire, an allegation of abuse against a staff member — tend not to be where mistakes happen, because their seriousness is obvious in the moment.

The judgement calls that actually cause problems

The harder judgement calls sit lower down the severity scale: an incident requiring police attendance that resolves quickly, a significant unauthorised absence, an injury that's serious but not obviously life-threatening. These are exactly the cases discussed in incident vs notifiable event — where a tired, busy team can reasonably disagree about whether the notifiable threshold has been met, and where having a clear, written internal escalation process, rather than relying on individual judgement in the moment, makes the biggest practical difference.

When in doubt, escalate

A workable approach many homes use: when there's genuine doubt, escalate as if it is notifiable and let a manager make the final call, rather than defaulting to "probably not" under time pressure. Over-notification has a cost, but it's a far smaller one than a genuinely notifiable event going unreported because nobody was sure and nobody wanted to be wrong. That decision is easier to make well when it's built on a clean, timely incident record in the first place.

Who should actually make the notification decision

In most homes, the frontline decision to flag something as possibly notifiable sits with whoever's on shift, but the final call on whether it meets the threshold and how it's worded should sit with the registered manager or an on-call senior with the authority and experience to make that judgement consistently. Splitting the responsibility this way — anyone can raise the flag, one person makes the final call — avoids both extremes: junior staff being left to make a judgement they're not equipped to make alone, and genuine concerns being quietly dismissed by someone reluctant to escalate.

A realistic borderline example

Consider a young person who's involved in an altercation off-site that draws police attendance, but is resolved on the spot with no arrest, no charges, and the young person back at the home within the hour, apparently unharmed. Nothing about that outcome is dramatic, and it's genuinely understandable that a busy team might not immediately think of it as notification-worthy. But police attendance itself is one of the more commonly cited notifiable triggers, regardless of how the incident resolved — which is exactly the kind of case where the outcome quietly, and wrongly, ends up deciding the notification question instead of the nature of the event itself.

A useful discipline for cases like this is separating the question "was this serious" from "does this meet a notifiable category" entirely — they're related but not the same question, and a team that only asks the first one will consistently under-notify events that resolved well but still technically qualify.

Reviewing decisions after the fact

It's worth periodically reviewing a sample of past incidents that weren't notified, specifically to check whether that call still looks right in hindsight, with a bit of distance from the moment. This isn't about second-guessing every decision staff make under pressure — it's about testing whether the home's shared understanding of the threshold is actually accurate, and catching a systematic misunderstanding before it repeats across several similar incidents rather than just the one being reviewed.

It's a genuinely useful exercise to run with the whole team present rather than just the manager reviewing alone — hearing how different staff independently reasoned through the same borderline case tends to reveal exactly where shared understanding is solid and where it quietly isn't.

Keeping this current as staff and guidance change

New staff need this covered explicitly during induction, not picked up gradually from colleagues over their first few months, since the gap between joining and genuinely understanding the notification threshold is exactly when a borderline case is most likely to be handled by instinct alone. Refreshing the whole team's understanding periodically, not just at induction, also matters, since Ofsted's own guidance and the regulations themselves can be updated and a team's collective understanding can quietly drift out of date if nobody revisits it.

A short, recurring slot in team meetings — even five minutes, a handful of times a year — to walk through a real or hypothetical borderline case keeps this genuinely current, far more effectively than a policy document nobody opens between inductions.

Getting the harder, borderline calls right consistently is ultimately what separates a home that merely has a notification policy from one that's genuinely built good judgement into its everyday practice.

What a workable escalation process looks like on a bad night

• –A clear, always-available route to reach a decision-maker out of hours — not dependent on one specific person being reachable
• –A short, written prompt staff can check against in the moment, rather than relying purely on memory of training
• –A default of raising it rather than sitting on it, with no culture of penalising a reasonable over-notification
• –A same-day or next-morning review of any borderline call, to build shared judgement for next time

As with the wider notification requirements, the specific, current list of what counts sits in Regulation 40 and Ofsted's own guidance — this post is an orientation to the shape of the requirement, not a substitute for checking the current statutory wording.