Ofsted notifications: what you must report, and how fast

Regulation 40 of the Children's Homes (England) Regulations 2015 sets out a specific list of events that a registered person must notify Ofsted about — and, for a defined subset, the relevant local authorities too. It's not a general "tell us if something goes wrong" duty; it's a named list, which means the practical risk isn't usually disagreement about whether to notify, it's forgetting that a particular event is on the list at all.

What's on the list

The categories broadly cover: the death of a child, serious illness or injury, any incident requiring police involvement, allegations of abuse, any event requiring emergency intervention, and significant absences, among others. Several of these carry a "without delay" expectation rather than a fixed number of days — which in practice tends to mean the same day, not "by the end of the week." If you're unsure whether a specific event clears the threshold, we've written separately about that judgement call.

Who else might need telling

Ofsted isn't necessarily the only party expecting to hear about a notifiable event — depending on the category, the child's placing local authority, their social worker, and in some cases the police or other agencies may have their own separate notification expectations running in parallel. It's worth having a clear internal list of who needs telling for each category of event, rather than treating "we told Ofsted" as the end of the job. A notification to Ofsted with no corresponding call to the placing authority can leave a social worker finding out about something that happened to their child from the wrong source, which damages trust well beyond the specific incident.

Where homes actually slip

Where homes tend to slip isn't the serious, obvious cases — those get noticed and escalated fast by instinct. It's the events that are genuinely on the notifiable list but don't feel dramatic in the moment, especially when a busy shift means the notification gets mentally filed as "I'll do that after the incident report" and then genuinely forgotten.

What good notification practice looks like month to month

Beyond individual incidents, it's worth periodically reviewing notifications as a pattern rather than one-off events — how many were sent in the last quarter, whether any were sent late, and whether any incident in hindsight probably should have been notified and wasn't. This kind of retrospective review isn't about catching individual staff out; it's about testing whether the home's own understanding of the notifiable categories is actually accurate and shared, because a mistaken assumption about what counts tends to repeat itself until someone deliberately checks it against the current guidance.

The relationship between notifications and the wider file

A notification sent to Ofsted shouldn't exist in isolation from the home's own internal record of the same event — the incident log it relates to, any Regulation 44 follow-up, and the eventual resolution should all be traceable back to each other. Where these live in genuinely separate systems, it becomes easy for the notification itself to get sent but the wider follow-up to lose the connection to it — which looks, to anyone reviewing the file later, like the notification happened in a vacuum rather than as part of a properly managed response.

It's also worth reviewing, at least annually, whether the home's own list of notifiable categories and contacts is still accurate — a placing authority's preferred contact changes, a category's expected timeframe gets clarified in updated guidance, and a checklist that's never revisited quietly goes stale in exactly the way it was designed to prevent elsewhere in the home's practice.

New managers taking over a home should treat familiarising themselves with the current notification list and process as an early priority, not something absorbed gradually over the first few months in post. A gap in understanding here is invisible right up until the moment a genuinely notifiable event happens and the new manager has to make a fast decision without having properly checked the ground first.

It's a small time investment against a meaningful downside risk — getting a genuinely notifiable event wrong through simple unfamiliarity, rather than a deliberate judgement call, is one of the more avoidable mistakes a new manager can make, and one of the easiest to prevent with a short, deliberate handover.

Building a checklist that actually gets used

A notification checklist that lives in a folder nobody opens under pressure isn't much use. What tends to work better is something short enough to be read in under a minute during a stressful moment — the named categories, who to notify for each, and by when — kept somewhere staff would actually think to look on a bad night, not filed alongside policies that only get read at induction and never again.

• –Keep the notification categories somewhere visible and quick to check, not buried in a policy document
• –Name, for each category, exactly who needs telling — Ofsted, the placing authority, police, parents where appropriate
• –Build the habit of asking "does this meet a notifiable category" as a deliberate step on every incident, not an afterthought
• –Record when a notification was sent and to whom, so it's demonstrably done, not just believed to be done

This post is a starting orientation, not the statutory list itself — Regulation 40 and Ofsted's accompanying guidance are the source to check for the current, complete wording, since notification requirements are the kind of detail that needs to be current, not summarised secondhand.