De-escalation and Crisis Response
How to Run a Post-Incident Debrief with Your Team
A simple structure supervisors can use to debrief staff after a critical incident, support the team, and improve practice.
What happens after an incident matters as much as the response itself. A good debrief supports the people involved, captures what was learned, and helps prevent the next one. A poor debrief, or none at all, leaves staff carrying it alone.
Two kinds of debrief
The immediate check-in happens the same shift. It is short and focused on people: Is everyone physically okay? Does anyone need to step away? Who is finishing the report?
The operational debrief happens within a few days, once people have had time to settle. This is where the team reviews what happened and what to change.
A simple structure
- What happened? Build a shared timeline from the facts. Let each person add what they saw.
- What went well? Name specific actions that helped. People repeat what is recognized.
- What was hard? Ask what made the response more difficult: staffing, layout, communication, unclear roles.
- What will we change? Agree on one to three concrete actions, each with an owner and a date.
Ground rules
- The purpose is learning, not blame.
- Everyone who was involved is invited, including security and front desk staff.
- What is shared about personal reactions stays in the room.
- Performance concerns are handled separately, in private.
Look after people
Incidents affect staff differently, and reactions can show up days later. Check in again the following week. Make sure staff know what support is available, such as supervision or an employee assistance program.
Do not forget the client
Follow up with the client involved and with any clients who witnessed the incident. Repairing the relationship is part of the work.
Close the loop
Record the agreed changes and report back to the team when they are done. Learning how to lead this process is part of our Crisis Intervention Training for leadership.