Who decides the hand‑off when command shifts in an incident?
Imagine a wildfire raging on a windy afternoon. The incident commander (IC) on scene is suddenly called to a briefing miles away. Here's the thing — who tells the crew, “Hey, you’re now in charge”? The answer isn’t a random guess—it’s baked into the very structure of the Incident Command System (ICS).
Below, I break down exactly who designates the process for transferring command, why that matters, and how you can make the hand‑off smooth every time.
What Is the Transfer of Command in ICS
In plain English, a transfer of command is the moment one person hands the reins of an incident to another. It’s not a casual “you take over” chat; it’s a formal, documented step that keeps everyone on the same page.
In the Incident Command System, the Incident Commander (IC) holds the ultimate authority for all operational decisions. Now, when the IC steps down—whether because of shift change, fatigue, a higher‑level authority taking over, or a change in incident complexity—a new IC must be appointed. The process that governs this hand‑off is called the Transfer of Command (TOC) procedure, and it’s built into the National Incident Management System (NIMS) guidelines It's one of those things that adds up..
The Core Pieces
- Authority – The person who can name a new IC.
- Documentation – A written record that the change happened, why, and when.
- Briefing – A concise rundown of the incident status given to the incoming IC.
All of those pieces are prescribed by NIMS, but the who behind the authority is often the source of confusion.
Why It Matters
If the transfer isn’t handled right, you get duplicated effort, conflicting orders, and—worst of all—danger. So one might order a boat out while the other tells the same crew to stand down. In practice, think about a flood rescue where two people think they’re the IC. Chaos.
A clear, pre‑planned hand‑off:
- Keeps the incident’s objectives front‑and‑center.
- Preserves safety for responders and the public.
- Protects legal and liability lines—there’s a paper trail showing who was in charge at any given minute.
In practice, agencies that follow the official TOC process see fewer “command gaps” and smoother shift changes.
How the Designation Process Actually Works
Below is the step‑by‑step flow of who gets to say, “You’re now the Incident Commander,” and how they’re supposed to do it Worth keeping that in mind..
### 1. The Role of the Incident Commander
The sitting IC is the first person responsible for initiating the transfer. NIMS states that the IC must designate a successor before stepping away. That means the current commander identifies the next qualified person, usually based on training, experience, and the incident’s needs.
### 2. The Role of the Agency’s Incident Management Team
Most incidents involve multiple agencies—fire, EMS, law enforcement, public works. Each agency has its own Incident Management Team (IMT). The IMT’s Operations Section Chief (or a designated senior officer) often has the authority to approve the successor if the IC is from a different agency. In multi‑agency incidents, the Unified Command (UC) structure may be in place, and the UC collectively decides on the new IC Most people skip this — try not to..
### 3. The Role of the Incident Commander’s Supervisor
If the IC is a career firefighter, for example, their Fire Chief or Battalion Chief can formally designate the next IC, especially when the change is due to shift rotation. In volunteer or community‑based responses, the Incident Coordinator (the person who initially activated the response) may hold that authority Easy to understand, harder to ignore..
### 4. The Role of the Incident Action Plan (IAP)
The IAP isn’t a person, but it guides who should take over. Because of that, the plan outlines the command structure, and any change must be reflected in the next IAP update. The Planning Section Chief updates the IAP to note the new IC, ensuring everyone sees the change in the same document Simple as that..
### 5. The Role of the Transfer of Command Brief
Once the new IC is identified, the outgoing IC delivers a Transfer of Command Brief. This is a 5‑minute rundown covering:
- Incident objectives and current status.
- Resources assigned and any known constraints.
- Safety concerns and recent incidents.
- Upcoming actions and critical timelines.
- Any pending decisions that need the new IC’s input.
The brief is the final seal of approval—if the incoming IC feels the brief is insufficient, they can request clarification before accepting command.
Common Mistakes / What Most People Get Wrong
Even seasoned responders slip up. Here are the pitfalls I see most often.
### Skipping the Formal Brief
A quick “You’re up” and a nod might work in a backyard fire, but not in a multi‑agency hazardous material spill. Without the formal brief, the new IC can miss a critical safety issue—like a wind shift that could push a plume toward a populated area.
### Ignoring Agency Hierarchy
In a joint response, a fire chief can’t just hand command to an EMS supervisor without the agreement of the Unified Command. Doing so creates a chain‑of‑command conflict that stalls decision‑making It's one of those things that adds up..
### Not Updating the Incident Action Plan
If the IAP still lists the old IC, you’ll see conflicting orders on the radio. The Planning Section must log the change immediately; otherwise, you’ve got a paper trail that says “who was in charge?” and that can become a legal nightmare.
### Assuming the Most Senior Person Is Automatically the New IC
Senior rank doesn’t guarantee the right skill set for the incident’s current phase. A senior officer might be great at strategic planning but lack the tactical expertise needed for a fast‑moving wildfire. The designation should be based on fit, not just seniority.
### Forgetting to Communicate the Change to All Stakeholders
It’s easy to tell the on‑scene crew, but what about the logistics team back at the command post, the public information officer, or the external partners? If they keep talking to the old IC, you get duplicated messages and confusion.
Practical Tips – What Actually Works
Below are the things I’ve found cut the friction out of command transfers The details matter here..
-
Pre‑plan the succession
Before an incident even starts, embed a “succession plan” in your agency’s SOP. List who’s next in line for each shift, and note any cross‑agency agreements. -
Use a standardized TOC checklist
A one‑page checklist (IC name, time, brief points, signatures) keeps the hand‑off consistent. I keep a laminated copy in every command vehicle Turns out it matters.. -
Record the brief on the incident radio log
Even if you’re not required to, jotting down the key points in the log creates an audit trail and helps the next shift catch up quickly And that's really what it comes down to. Less friction, more output.. -
Conduct a quick “situation room” walk‑through
After the brief, have the new IC stand at the command post, look over the resource board, and ask any immediate questions. It reinforces that they’re now in charge Simple, but easy to overlook.. -
Confirm the change with the Planning Section
A quick “Planning, please update the IAP with the new IC” and a verbal acknowledgment seals the deal. -
Notify external partners via a single channel
Whether it’s a joint information system or a shared email thread, send one concise “Command Transfer” notice that includes the new IC’s name, contact, and any immediate actions It's one of those things that adds up.. -
Practice, practice, practice
Tabletop exercises that simulate a command transfer are surprisingly effective. I run them quarterly with all agencies involved in our regional response plan.
FAQ
Q: Can anyone on scene declare a Transfer of Command?
A: No. Only the current Incident Commander, a designated supervisor, or an authorized agency official can initiate the hand‑off. Random crew members can suggest a change, but they can’t enforce it.
Q: How long should the Transfer of Command Brief be?
A: Ideally five minutes. Long enough to cover objectives, resources, safety, and upcoming actions, but short enough to keep the incident moving.
Q: What if the incoming IC refuses the command?
A: The outgoing IC must then identify an alternate qualified person. If no one is available, the next senior authority (e.g., the Operations Section Chief) steps in until a suitable IC is found.
Q: Do I need to file a formal report after every command transfer?
A: Yes, at a minimum a brief entry in the incident log noting the time, outgoing and incoming ICs, and a signature or verbal acknowledgment. The IAP should also be updated Took long enough..
Q: Does the Transfer of Command process differ for small incidents?
A: The core steps stay the same, but you can streamline the brief and paperwork. For a single‑engine fire, a quick verbal hand‑off and a note in the log may suffice.
When the smoke clears, the most important thing is that someone is always in charge—no gaps, no confusion. Knowing exactly who has the authority to designate the Transfer of Command process, and following the steps laid out by NIMS, makes that possible.
So next time you’re on a scene and the shift is ending, remember: the outgoing IC starts the hand‑off, the agency’s management backs it up, the Planning Section records it, and a concise brief seals the deal. Get those pieces right, and you’ll keep the incident moving safely and efficiently And it works..
