After a difficult incident, adults often want answers quickly. Young people may need something different: safety, space, reassurance, boundaries that remain calm and time before they can reflect. The period after an incident can either repair trust or deepen conflict.
Make sure everyone is safe
Deal with injuries, immediate safeguarding concerns, missing persons issues, weapons, substances or environmental hazards first. Emotional processing should not compete with urgent safety needs.
Reduce stimulation
After high arousal, some young people need less talking, fewer people and a calmer environment. Avoid crowding them with questions. Follow their plan and known preferences where possible.
Do not demand an immediate apology
Apologies can be meaningful when they are genuine. Forcing one while the young person is still dysregulated may create compliance without reflection. Prioritise calm and understanding first.
Return to the conversation later
When the young person is ready, ask open questions: what was happening for you before this? What helped? What made it worse? What would you like staff to do differently next time? The aim is learning, not prosecution.
Acknowledge impact without shaming
If somebody was hurt or frightened, or property was damaged, the young person should understand the impact. Keep the conversation factual and avoid attacking their character. Accountability and dignity can exist together.
Repair relationships
Where appropriate, restorative conversations can help. This may involve an apology, practical repair, agreeing boundaries or simply clarifying what each person experienced. Do not force face-to-face repair where it would be unsafe or unhelpful.
Update support if needed
If the incident reveals a new trigger, risk or unmet need, update relevant plans. Repeating the same response after repeated incidents may indicate that the plan is not working.
Check staff wellbeing too
Staff who were involved may need debriefing or support. Their emotions should not be processed with the young person, but they do matter. Reflective support helps staff return to the relationship without resentment.
Putting this into practice
The most useful way to apply this to support after an incident is to start with one real, anonymised example from the service rather than trying to redesign everything at once. Choose a recent shift, record, handover, incident or support interaction and walk through what actually happened. Ask staff where they had enough information, where they had to guess, where work was duplicated and whether the young person’s experience was visible. Then identify one change that would make the next similar situation clearer or easier. That might be a better prompt on a form, a clearer handover category, a named action owner, a more consistent phrase for recording observations, or a scheduled management review. Keep the change small enough to test. Large policy rewrites can feel productive while leaving day-to-day practice untouched. A small workflow improvement that staff understand and use consistently is often more valuable. After a week or two, review whether the change improved clarity, reduced repeated questions, helped staff act sooner or made the record more useful. If it did not, adjust it. Good practice develops through observation, feedback and refinement rather than one perfect template. Where the issue touches safeguarding, legal duties, medication, restraint, confidentiality or another regulated process, the service should always check its current policy and relevant professional guidance before changing practice.
Questions for supervision and team discussion
Managers can also use support after an incident as a supervision or team-meeting discussion rather than only a written standard. Ask staff what good practice looks like when the shift is busy, what usually gets missed under pressure and what would make the right action easier. Use examples rather than abstract criticism. If a record is too vague, rewrite one paragraph together. If actions are being lost, trace one action from the moment it was created to the point it was completed. If the young person’s voice is missing, ask what question staff could have asked or what part of the conversation should have been captured. It is also worth asking how the process feels from the young person’s perspective. Do they have to repeat themselves? Do different staff give different answers? Does the record focus mostly on things going wrong? Are decisions explained to them? These questions move quality improvement beyond paperwork and back toward the experience of care. Finally, agree what ‘good enough’ looks like. Staff need practical examples and clear expectations, not vague instructions to ‘record better’ or ‘communicate more’. A shared standard makes feedback fairer and gives new staff something concrete to learn from.
A final reality check
One final check is to ask whether the process remains workable on the busiest shift of the week. Standards that only work when staffing is ideal or the service is quiet will not be sustained. Good practice should be simple enough to use under pressure, clear enough for new staff to understand, and flexible enough to respond to the individual young person. If staff routinely create workarounds, that is useful feedback: either expectations are unclear, the workflow is too complicated, or the tools do not match the reality of the role. Treat those workarounds as signals to investigate rather than automatic evidence of poor attitude.
Key takeaway
The goal after an incident is not simply to return the service to normal. It is to restore safety, understand what happened, repair what can be repaired and use the experience to improve future support.
