What counts as a critical incident for firefighters? A list, and a sample SOG for tracking them
Every fire department agrees that a line of duty death is a critical incident. The arguments start further down the list. Is a failed pediatric code critical if the crew has run three this year? What about a fatal crash on the interstate, or a call to a neighbor's house? The answer decides who gets a call from peer support and who's left to sort it out alone, so it shouldn't be left to whoever's on shift.
This guide is for fire chiefs, health and safety officers and peer support coordinators. It gives a working critical incident definition, a master list built from published fire department SOGs, a two-tier model for which events trigger outreach automatically, and a sample SOG you can adapt for recording them and activating your CISM team.
For the wider program, from thresholds to exposure records, see our guide to best practices for tracking critical incidents and firefighter wellness.
What is a critical incident? The short answer
A critical incident is any call or event that causes unusually strong emotional reactions with the potential to interfere with a firefighter's ability to function, at the scene or later. Most fire department SOGs name the same core events: death or serious injury of a member, a member's suicide, the death of or violence to a child, a mass casualty incident, a civilian death caused by department operations, and a patient lost after a long rescue. Most also let any member declare one.
Treat the core list as automatic: record it against every member on the call and notify your CISM team every time. Leave the rest to an officer's judgment or the member's own request. Essential Personnel, built by two firefighters, lets any member mark an incident as critical, records it on each responder's wellness profile and alerts peer support when a department-set threshold is crossed.
The critical incident definition fire departments use
Ask what is a critical incident, and almost every published fire department SOG answers with a version of the same critical incident definition, which traces back to the critical incident stress management model taught by the International Critical Incident Stress Foundation. Three recent examples:
- El Cerrito and Kensington Fire in California (2025): "Any situation that causes unusually strong emotional reactions that have the potential to interfere with an individual's ability to function."
- Hawai'i Fire Department (2022): "An incident that exposes personnel to unusually strong emotional involvement," adding that "any incident may illicit a strong emotional response and therefore qualify for a CISM activation."
- Carroll County, Maryland (2023): "stressful events which have the potential to overwhelm one's usual coping mechanism."
Notice what the critical incident defined in these SOGs isn't. It isn't a category in your records management system, and it isn't the same as a big fire. It's defined by the effect on the people who responded. That's why every good SOG pairs a list of named events with a catch-all that lets a member say "that one got to me."
The master list: critical incidents in published fire department SOGs
Across five published fire service documents, eight events appear again and again: death or serious injury of a member, suicide, death of or violence to a child, mass casualty incidents, civilian death caused by department operations, a patient lost after a prolonged rescue, a victim the responder knows, and heavy media attention. Most also cover "any incident" a member or officer flags.
| Critical incident | Hawai'i FD | Carroll Co., MD | El Cerrito, CA | Mt. Lebanon, PA | Florida Fire Chiefs |
|---|---|---|---|---|---|
| Death or serious injury of a member | Yes | Yes | Yes | Automatic | Yes |
| Suicide of a member, or a suicide call | Yes | Yes | Yes | ||
| Death of or violence to a child | Yes | Yes | Yes | Automatic | Yes |
| Mass casualty incident | Yes | Yes | Yes | Automatic | Yes |
| Civilian death or serious injury caused by department operations | Yes | Yes | Automatic | Yes | |
| Patient lost after a prolonged rescue or resuscitation | Yes | Yes | May need | ||
| Victim known to the responder | Yes | May need | Yes | ||
| Heavy or negative media attention | Yes | Yes | May need | Yes | |
| Threat to responders, such as a hostage situation | Yes | ||||
| Responder crash with traumatic injuries | Yes | ||||
| Any incident a member or officer flags | Yes | Yes | Yes |
Sources: Hawai'i Fire Department CISM SOP 12002.02; Carroll County Department of Fire and EMS SOP 3.28; El Cerrito and Kensington Fire CISM SOG; Mt. Lebanon Fire Department SOG 110; and the Florida Fire Chiefs' Association Mental Health Resource and Response Guide. A blank cell means that document doesn't name the event; it doesn't mean the department would ignore it.
A few more show up in single documents and are worth considering for your own list: child drowning or near-drowning (Evansville, Indiana), an officer-involved shooting and an off-duty death or suicide (Florida Fire Chiefs), and "unusually distressing sights and sounds" (Hawai'i). The NIOSH traumatic incident stress guidance adds exposure to dead bodies or body parts and severely injured adults.
Two tiers: which critical incidents trigger outreach automatically
Split your list into two tiers. Tier 1 events always trigger notification of the critical incident stress management team coordinator and are recorded against every member on the call. Tier 2 events are recorded and reviewed, and outreach follows if an officer or the member asks for it. Mt. Lebanon Fire Department's SOG uses exactly this split.
Mt. Lebanon's wording is the clearest of any published SOG: these are "incidents that will automatically trigger notification of the CISM Team Coordinator and a defusing or debriefing to be offered." A second list "may need" a defusing or debriefing. Pembroke Pines Fire Rescue in Florida uses a similar "automatic call out" list. Here's a two-tier list built from the master table:
Tier 1: automatic
Death or serious injury of a member. Suicide of a member. Death of or violence to a child. Mass casualty incident. Civilian death or serious injury caused by department operations, including an apparatus crash.
Tier 2: judgment or request
Patient lost after a prolonged rescue. A victim the responder knows. Threats or violence against crews. Heavy media attention. Unusually distressing scenes. Any call a member asks to have recorded.
A critical incident definition alone doesn't tell a captain what to do at the end of a call. The tiers do, and they keep the system honest. Automatic triggers mean nobody has to decide, at three in the morning, whether a call was bad enough. The judgment tier keeps the list short enough that the CISM team isn't activated for every fatal call, which is how alerts start getting ignored.
Cumulative stress: when ordinary calls add up to critical incidents
Most firefighters will run critical incidents, not just one. In a study of 390 full-time Canadian firefighters, 96.4 percent reported exposure to a critical incident over their careers. A U.S. Fire Administration Executive Fire Officer paper from Bend Fire and Rescue in Oregon found an average of 77.7 percent of surveyed firefighters had responded to an emotionally upsetting incident in the previous two years, and noted that neither department studied tracked critical calls for analysis.
The Florida Fire Chiefs' guide builds this into its definition: a debilitating critical incident "can be a single acute incident or the cumulative effect of multiple traumatic incidents." The IAFF says the same about calls involving children and violence. Yet none of the published SOGs says how to count cumulative stress per member.
So the practical question isn't only what is a critical incident, but how many a member has run lately. Write that rule yourself. A simple one: any member with three Tier 2 incidents in 90 days gets the same outreach as a Tier 1 event. That number is a starting point for your department to adjust, not a standard. Watch who it flags for a quarter, then change it.
Who activates the critical incident stress management team, and how fast
Most municipal fire department SOGs let any member request activation of the critical incident stress management team, offer a defusing before the crew goes off shift, hold a debriefing within 72 hours, and follow up weeks or months later. Wildland CISM guidance waits longer, starting no sooner than 48 to 72 hours after the incident, and bases intervention on need rather than the event alone.
| Step | What the SOGs say | Source |
|---|---|---|
| Who can activate | Any member, through the team coordinator, battalion chief or supervisor; or through the emergency communications center's call-down list | Hawai'i, El Cerrito, Carroll County |
| Defusing | Before those involved complete their shift, typically within 8 to 12 hours; otherwise the next shift | Hawai'i |
| Debriefing | Within 72 hours, preferably within 24 | Hawai'i, Mt. Lebanon, El Cerrito, Evansville |
| Follow-up | Weeks or months after the incident, for delayed or prolonged reactions | Hawai'i |
| Wildland model | "Early psychological intervention should be based on recognition of need, not strictly the occurrence of an event"; processes start no sooner than 48 to 72 hours | BLM CISM call-out guidelines |
The two models aren't as far apart as they look. Same-shift contact is a check-in and a chance to defuse, not therapy. Formal group sessions come later, and the National Interagency Fire Center says participation in critical incident stress debriefing "is voluntary and attendance should never be mandatory." Some fire SOGs, such as Hawai'i's, make attendance mandatory but participation voluntary. Pick one, write it down, and tell members before the next call.
NIOSH notes that reactions can show up "weeks or months later," which is why the follow-up contact matters as much as the first one. Hawai'i's SOP adds a line every department should copy: "Under no circumstance will any leave of absence following a critical incident be interpreted as being disciplinary in nature."
What to put in a critical incident report, and what never to record
A critical incident report exists to start outreach and keep a reliable history for each member. It's the thinnest part of most SOGs. Only Carroll County and El Cerrito say what gets recorded, and both are clear about what doesn't. El Cerrito's SOG: "Only basic incident information is logged for program tracking. No personal information or session content is recorded."
| Record this | Never record this |
|---|---|
| Date, time and incident number | What a member said to peer support or a clinician |
| Tier and incident type from your list | Diagnoses, symptoms or screening results |
| Every member on scene and their role | Notes from a defusing or debriefing |
| Whether the member declared it critical themselves | Anything that belongs in a medical file |
| Who was notified, and when | |
| Contacts offered and made, with dates |
Keep the report out of the personnel file and away from discipline, and limit who can see it to the people doing outreach. Carroll County's SOP says its program "operates under the same privacy limits as HIPAA," with exceptions only for danger to self or others and abuse. Members decide quickly whether a critical incident report is there to help them, and they stop declaring incidents the first time one reaches a supervisor's desk.
Sample fire department SOG: identifying critical incidents and activating the CISM team
This fire department SOG puts your answer to what is a critical incident in writing, using the critical incident definition above. It's a starting point built from the published SOGs. Adapt the tiers, contacts and timelines with your peer support team, your clinician and your labor partners.
Sample SOG
1. Purpose. To identify critical incidents consistently, record them against every member involved, and make sure the critical incident stress management (CISM) team offers support to those members on time.
2. Scope. All career and volunteer members, on and off duty.
3. Definition. A critical incident is any incident that causes unusually strong emotional reactions with the potential to interfere with a member's ability to function at the scene or later. Any incident may qualify.
4. Tier 1 incidents. The following always require notification of the CISM team coordinator and an offer of a defusing or debriefing: death or serious injury of a member; suicide of a member; death of or violence to a child; a mass casualty incident; civilian death or serious injury caused by department operations.
5. Tier 2 incidents. The following shall be recorded and reviewed by the company officer, who will request CISM team support when needed: a patient lost after prolonged rescue or resuscitation; a victim known to a responder; threats or violence against crews; heavy media attention; unusually distressing scenes.
6. Member declaration. Any member may declare an incident critical for themselves, without giving a reason. The declaration is recorded and treated as Tier 1 for that member.
7. Activation. The company officer or any member contacts the CISM team coordinator or the on-duty battalion chief as soon as practical. Contacts are posted at every station and in the department's resource library.
8. Timeline. Defusing is offered before affected members complete their shift. Debriefing, if held, is offered within 72 hours. A peer support member contacts each affected member again within 30 days.
9. Attendance and participation. Participation in any defusing or debriefing is voluntary. Members may be placed out of service or relieved for the rest of the shift. No leave or relief following a critical incident is disciplinary.
10. Critical incident report. The company officer completes a critical incident report before going off shift, listing every member on scene. The report records the incident, the tier, members involved, notifications and contacts. It never records what was said in a peer support contact or any clinical information.
11. Confidentiality and access. Critical incident records are kept separate from personnel and disciplinary files and are visible only to the CISM team coordinator, the health and safety officer and any contracted clinician.
12. Cumulative review. A member with three or more Tier 2 incidents in any 90 days receives the same outreach as a Tier 1 incident. The health and safety officer reviews this threshold each quarter.
13. Program review. The CISM team coordinator reports annually to the fire chief on incidents recorded by tier, time from incident to first contact, and follow-up contacts completed, without identifying members.
The 30-day follow-up and the 90-day cumulative rule are recommended settings, not requirements from any standard. The rest of the structure appears, in some form, in the published SOGs.
Where NFPA standards fit
NFPA's occupational health standards are being consolidated. The 2025 edition of NFPA 1580 combines the former NFPA 1581, 1582, 1583 and 1584, and NFPA 1500 has long required fire departments to give members access to a behavioral health program. Drafts of NFPA's newer health and safety standard put more weight on peer support, including a written policy for how it's activated after a potentially traumatic event. Check the current editions of the standards your department follows before you adopt this SOG, and cite them in it.
Tracking critical incidents in software: how Essential Personnel does it
Essential Personnel was founded in 2020 by two Wilmington, North Carolina firefighters. Their Safety and Wellness suite records traumatic calls, injuries, use of force, motor vehicle accidents and exposures against each member, sends Critical Incident Alerts to the people you designate, and lets the department set the number, type and timeframe of events that trigger an automatic alert.
Once your SOG settles what is a critical incident for your members, the software has to apply it the same way every time. That maps onto the sample SOG directly:
- Member declaration (section 6): any member can mark an incident as critical for themselves.
- Tier 1 notification (section 4): Critical Incident Alerts notify designated people when a traumatic or critical incident is recorded.
- Cumulative review (section 12): Automated Alert Triggers apply your count and window to every member continuously.
- Confidentiality (section 11): Specialist Role Permissions limit critical incident detail to the people you name, including clinicians from outside the department.
- Resources (section 7): the Resource Library holds peer support contacts, documents and videos members can reach from any station.
Statesville Fire Department in North Carolina had no formal critical incident tracking before they adopted Essential Personnel. Logging each incident against the members who responded showed them when the same crew had run two pediatric fatalities within a few weeks, and the Center for Public Safety Excellence cited their tracking as an industry best practice during reaccreditation.
"Having timely notifications and insights at our fingertips is one of the most significant benefits of EP. Using threshold alerts, it enables the department to keep the health and wellbeing of our team as one of our top priorities."
Deputy Chief Kyle Bell, Statesville Fire DepartmentSafety and Wellness is published at $40 per user per year on the pricing page, or $175 per user for the full platform, plus a one-time $3,000 startup fee. More detail is on the Safety and Wellness page and the fire and EMS overview. To compare systems, see our ranking of critical incident and exposure tracking systems for fire departments.
Turn your critical incident list into outreach that happens every time
We'll set up your tiers, alert routing and thresholds with you, for a department your size. Talk it through with someone who's worked a shift. Call (910) 390-0011 or email info@essper.com.
Frequently asked questions
Start with the events nearly every fire department SOG names: death or serious injury of a member, a member's suicide, the death of or violence to a child, mass casualty incidents, and civilian deaths caused by department operations. Treat those as automatic. Then add a judgment tier for long failed rescues, victims a responder knows and heavy media attention, and let any member declare an incident critical.
A critical incident is any situation that causes unusually strong emotional reactions with the potential to interfere with a responder's ability to function, either at the scene or later. Fire departments define it by its effect on the people who responded, not by the size of the call, so most SOGs pair a list of named events with a rule that any incident may qualify.
Define your critical incidents in writing, record each one against every member on the call the same shift, set thresholds for cumulative stress, route alerts only to peer support and clinicians, and record contacts but never what was said. Essential Personnel does this on one member record, with Critical Incident Alerts and department-set thresholds, and Statesville Fire Department's tracking on it was cited as an industry best practice.
Most municipal fire department SOGs offer a defusing before the crew goes off shift, usually within 8 to 12 hours, and a debriefing within 72 hours, preferably within 24. A follow-up contact weeks later matters too, because reactions often appear later. Wildland CISM guidance waits at least 48 to 72 hours and bases the response on need rather than the event alone.
The date, time and incident number, the incident type and tier, every member on scene and their role, whether a member declared it critical, who was notified and when, and the peer support contacts offered and made. Never record what a member said, symptoms or diagnoses. Keep the report separate from personnel and disciplinary files, visible only to the people doing outreach.
A CISM team, or critical incident stress management team, is a group of trained peers, often backed by a licensed clinician and a chaplain, who support members before and after critical incidents. They offer defusings, debriefings and one-to-one contact, and refer members to clinicians or an employee assistance program. Many fire departments train their team in the International Critical Incident Stress Foundation model.
Yes. The Florida Fire Chiefs' Association defines a debilitating critical incident as a single acute incident or the cumulative effect of several. Few SOGs say how to count it, so set your own rule, such as outreach for any member with three judgment-tier incidents in 90 days, and adjust it once you see who it flags. That number is a department choice, not a standard.
Some use the incident module of their records management system, which logs the call but not each member's history, and some use spreadsheets kept by peer support. Others use personnel software with a wellness module, such as Essential Personnel, which records critical incidents against each member, alerts peer support on thresholds the department sets, and limits access to named people.
About this article
Written by Scott Monroe, Chief Executive Officer & Co-Founder, Essential Personnel. Published 26 October 2026.
Essential Personnel makes the software described here, and the product screenshot is from the platform. The master list and timelines are taken from the published SOGs and guides linked above, read in October 2026. The sample SOG is original and adapted from them; the 30-day follow-up and the 90-day cumulative rule are recommended settings, not requirements. The Statesville details and quote are from the published customer story. This article is general guidance and isn't medical or legal advice.
