Incidents in 16+ supported accommodation are expected. The young people served have histories, the placements are complex, and the environments, by design, balance structure with independence. What matters is how an incident is reported, because slow or thin reporting means the commissioner cannot see what is happening in time to act. This post is about what good incident reporting looks like.
Timeliness
Reporting timelines should be set against incident severity. Our standard, which we think should be common practice, is:
- Serious incidents: logged within 2 hours. Notified to the Local Authority allocated worker the same day.
- All other incidents: logged within 24 hours. Notified to the allocated worker via agreed reporting channel on the defined cadence.
- Post-incident review: completed within 72 hours, signed off by Operations Lead.
Anything slower means the provider is sitting on something the commissioner should know about, and by the time they hear it may be too late to act.
What an incident report should contain
A good incident report is short, factual and useful. The fields we use, and that commissioners should expect, are:
- Facts: what happened, when, where and who was present, as behaviour rather than interpretation.
- Actions taken: what staff did in the moment. Sequence, timing, rationale.
- Escalation decisions: who was called, when, and what was decided. If a decision was not to escalate, that is recorded too, with reasoning.
- Named owner: the person responsible for post-incident review and follow-up actions.
- Follow-up required: what needs to happen next, by whom, by when.
Post-incident review
Every incident is reviewed, within the timescale, by someone who was not involved in it. The review asks what happened, what worked, what did not and what needs to change. It looks at practice rather than blame, and it ends in actions.
Reviews that consistently conclude "staff did nothing wrong, nothing to change" are either a cultural problem or a review problem. Complex incidents almost always surface something that could be done differently, and good review culture looks for it without turning it into a disciplinary process.
Pattern analysis
Three similar incidents across three placements is a pattern. Good providers look for patterns every quarter across the whole operation: whether certain types of incident cluster in certain properties, shifts, staff teams or young people.
A pattern caught early prevents the next incident.
The escalation matrix
An escalation matrix answers two questions for every incident: who needs to know, and how fast? Serious incidents escalate to the Operations Lead and Local Authority allocated worker the same day. Medium-severity incidents escalate to the Service Manager and are included in the next scheduled report. Low-severity incidents are logged and included in the monthly roll-up.
Every member of staff should be able to say straight away where an incident sits on the matrix. If they cannot, the matrix is not working, and decisions under pressure become guesses.
When to self-refer to safeguarding vs manage internally
This is a judgement call, and it is one of the highest-stakes judgements providers make. Self-referral to statutory safeguarding is appropriate when the concern goes beyond what the provider can manage within its own framework, or where the incident falls within defined safeguarding thresholds (significant harm, risk to a specific young person from an adult, patterns that suggest systemic concern).
Providers who under-refer are protecting themselves at the expense of young people. Providers who over-refer burn through local safeguarding capacity and erode the threshold for future concerns. A good provider has clear thresholds and escalates when the call is close.
TIFA Life's incident reporting model
We log serious incidents within 2 hours and all others within 24 hours. The Operations Lead signs off every review. We notify the Local Authority the same day for serious incidents and in the agreed report for the rest, and the senior team reviews patterns every quarter and tracks the actions to completion.
For the full governance framework see quality and safeguarding. For a related deep dive on safeguarding without CIW regulation, see safeguarding in supported accommodation without CIW. To request our full safeguarding pack, email hello@tifa.co.uk.