Incident Management Frameworks

Systematic Framework

8-Step Process

Hildebrand · Noll · Yvorra

A cyclical, systematic framework built around deliberate pre-action analysis and structured decision-making. Emphasizes hazard and risk evaluation before committing personnel or resources. Designed to loop — conditions change mid-incident, and the process re-enters at the appropriate step.

Site Management & Control

Establish command, isolation perimeter, zones

Identify the Problem

Product ID, container type, behavior, quantity

Hazard & Risk Evaluation

What are the hazards? What is the actual risk to people?

Select Personal Protective Equipment

PPE level driven by hazard/risk evaluation

Information Management & Resource Coordination

Notifications, reachback, mutual aid, documentation

Implement Response

Execute selected tactical options

Decontamination

Personnel and equipment decon before leaving hot/warm zone

Termination

Debriefing, documentation, critique, cost recovery

Widely taught at the technician level and closely aligned to NFPA 470 structure, but adopted across responder levels in different jurisdictions. Its cyclical structure and depth of pre-action analysis make it well-suited for complex incidents at any level. Always follow your AHJ's framework and protocols.

Field Framework

5-Step Process

A linear, field-action framework built around five clear steps. Straightforward structure makes it easy to follow under pressure. Adopted across jurisdictions at varying responder levels — always apply it within your training and AHJ authority.

Isolate

Secure the area, evacuate, establish perimeter

Identify

Product ID using ERG, placards, shipping papers

Notify

Dispatch, hazmat team, agencies, CHEMTREC

Mitigate

Actions within the scope of your training and AHJ authority

Terminate

Scene turnover, documentation, after-action

Audience varies by jurisdiction — adopted at operations level in some departments, technician level in others. Its linear structure and field-action orientation make it adaptable across responder levels. Always follow your AHJ's framework and protocols.

Side-by-Side Comparison

Phase-by-Phase Matrix

Each row represents a phase of the incident. Select any row to see how each framework addresses that phase — including where they diverge, overlap, or where one framework leaves a gap the other fills.

Key Distinctions

What Separates These Frameworks

Scope of Authority

Who Is This Built For?

The 8-Step is structured around a systematic, cyclical process suited to complex incidents where multiple disciplines and resources are in play. The 5-Step is built for a more linear, field-action flow that scales to the responder's training level and AHJ authority. Both frameworks can be applied by responders at different levels — the difference is in depth, structure, and how much pre-action analysis is explicitly built in.

Structure

Linear vs. Cyclical

The 5-Step is linear — each step leads to the next. Simple to follow under stress. The 8-Step is cyclical — conditions change mid-incident, and the process re-enters at the appropriate step. Hazard evaluation happens again after decon, and again after resources change. The loop is intentional, not a flaw.

Risk Evaluation

Depth of Pre-Action Analysis

The 8-Step dedicates an entire step to hazard and risk evaluation — separate from product identification. That distinction matters: hazard is what the product can do, risk is the probability it will do it to you given current conditions. The 5-Step embeds this thinking inside Identify and Isolate without explicitly naming it.

Notification

Where Notifications Live

The 5-Step makes notification its own dedicated step — third in sequence. This reflects an early-response priority: calling the right people may be the most impactful action taken in the first minutes. The 8-Step addresses notifications in Step 5 (Information Management) — later in the process, after risk evaluation and PPE selection have begun. Notifications in the 8-Step run as a parallel track while other actions proceed simultaneously.

Decontamination

Explicit vs. Embedded

The 8-Step makes decontamination its own step — Step 7 — ensuring it cannot be skipped or assumed. The framework establishes the principle that decon should be set up before the first entry, not improvised when the team exits. The 5-Step does not name decon as a standalone step. Whether formal decon is required depends on what happened during Mitigate — not which framework was used.

Termination

Both End the Same Way

Both frameworks close with a termination step covering scene turnover, documentation, critique, and after-action review. This step is often skipped in field practice — and when done well, it is among the most valuable for long-term team performance. Its presence in both frameworks reflects its importance regardless of how the incident was managed.