Critical Incident Debriefing Report

Use it after critical incidents involving law enforcement, fire, EMS, dispatch, emergency management, or other public safety operations. It is designed for events where command decisions, tactical actions, and interagency coordination need to be reviewed. It works best when the incident had a clear operational response and a need to capture lessons learned. It is not meant for routine shift notes or informal after-action comments.

Complete it after each qualifying critical incident, ideally while details are still fresh and before informal recollections drift. Many teams use it as a same-day or next-shift debrief, then finalize it after collecting radio logs, dispatch records, and supervisor input. For major events, you may also run a second review once all reports and recordings are available. The template supports both an immediate debrief and a final documented version.

A supervisor, incident commander, training officer, or designated after-action reviewer usually owns the report. The best practice is to have one person facilitate the debrief and assign sections for timeline, decisions, and action items. Subject-matter contributors can add their own observations, but the final document should have a clear owner. That keeps the report consistent and easier to follow later.

Yes. The structure is meant to capture what happened, why decisions were made, and what outcomes followed, so the record is useful for review and accountability. Include the context behind each major decision, the alternatives considered, and any blocker that affected execution. Action items should name an owner and due date so follow-up does not disappear after the meeting. That makes the report more useful than a freeform narrative.

It can support internal review, training, and documentation, but it should be completed according to your agency’s records policy and legal guidance. Keep the language factual, avoid speculation, and separate observed facts from opinions or lessons learned. If the incident may become part of an investigation, litigation hold, or public records request, preserve source materials and follow retention rules. This template is not a substitute for legal advice or official reporting requirements.

The biggest mistake is writing a narrative without a clear timeline, decisions, or action items. Another common issue is mixing facts, assumptions, and blame in the same section, which makes the report harder to trust. Teams also forget to assign owners and due dates, so lessons learned never turn into follow-up. This template is built to prevent those gaps by separating context, outcome, and next steps.

Add the fields your organization already tracks, such as incident number, unit identifiers, command roles, mutual aid partners, or dispatch references. You can also tailor the sections to match your review process, such as adding a safety review, communications review, or equipment review. Keep the core structure intact so the report still captures timeline, decisions, outcomes, and action items. That balance makes it easy to adopt without losing consistency.

Yes, it can be linked to incident reports, radio logs, CAD records, training records, or a task tracker for follow-up. If your workflow uses a separate action register, copy the action items into that system and keep the debrief as the source of context. You can also connect it to a knowledge base so recurring lessons learned are searchable. The key is to preserve the debrief as the narrative record and route tasks elsewhere.