You ever watch a fire crew show up, get the scene under control, and then someone new takes the radio and suddenly everything stutters? That gap — the handoff — is where good work falls apart. And it's not just firegrounds. Any team running an emergency operation lives or dies by how the outgoing incident commander passes the baton.
The short version is this: to ensure a smooth transfer the outgoing incident commander has to do more than say "I'm leaving, you're up." They have to hand over context, not just command. Most guides treat this like a checkbox. It isn't Less friction, more output..
What Is The Outgoing Incident Commander Handoff
Let's be clear about who we're talking about. Now, the incident commander (IC) is the person in charge of an emergency response — the one making the calls, owning the plan, and accountable for what happens. When their shift ends, or they get relieved, or the incident scales past their level, someone else takes over. But that someone is the incoming IC. The person stepping away is the outgoing incident commander.
The handoff is the moment of transfer. It's a conversation, a briefing, sometimes a written record, and often a quiet walk around the perimeter. But really, it's the outgoing IC loading the incoming IC's brain with everything that matters That's the part that actually makes a difference. That alone is useful..
Not Just A Radio Call
A lot of people think the transfer is: "Command transferred to you, good luck." That's a joke. In practice, the handoff is a structured exchange of situation, resources, risks, and intent. The outgoing incident commander knows where the bodies are — literally and figuratively. They've seen the building shift. Think about it: they know the rookie on the roof. They know the hydrant that doesn't work.
Why The Role Exists
The IC role exists because someone has to be in charge. The outgoing incident commander is the bridge. Without them doing the transfer right, the incoming IC is flying blind for the first ten minutes. When that someone changes, continuity is the only thing standing between a managed scene and chaos. And ten minutes is forever in an incident.
This is where a lot of people lose the thread.
Why It Matters
Why does this matter? Or rush it. Because most people skip it. Or do it badly Surprisingly effective..
I've read after-action reports where a building collapsed because the new commander didn't know a secondary search was underway. Or he said it while walking to his truck. " He didn't. The outgoing incident commander "thought he said it.Real talk — that's how people die.
When the transfer is smooth, the incoming IC picks up the thread. They don't re-learn the map. They don't re-deploy companies that are already spent. Here's the thing — they don't repeat the mistake of sending a crew into the wing that's about to flashover. Think about it: the operation stays continuous. The risk drops.
And here's what most people miss: a bad handoff doesn't just hurt the new commander. It confuses every subordinate. This leads to if the firefighters on scene hear two different stories in five minutes, they stop trusting either. Command presence evaporates.
Turns out, the handoff is also where accountability lives. Even so, what's the name of the safety officer? Who requested the extra alarm? Where's the staging area? If the outgoing incident commander doesn't pass that, the whole system gets fuzzy.
How It Works
So how do you actually do it? To ensure a smooth transfer the outgoing incident commander needs a repeatable method. Not a script — a method. Here's the meaty part Easy to understand, harder to ignore. Turns out it matters..
Step 1: Know It's Coming
The outgoing IC should never be surprised by relief. Plus, if you're running an incident past your stamina or your jurisdiction, you should already be thinking about who takes over. In practice, good commanders broadcast "I'm preparing to transfer" before they're tired. They start organizing their thoughts while the incident is stable, not when they're collapsing.
Step 2: The Face-To-Face Brief
This is non-negotiable when possible. The outgoing incident commander and incoming IC should stand together. Not over the radio. Because of that, not via text. Eye contact And that's really what it comes down to..
- What happened before they got there
- What's happening now
- What's likely to happen next
- Who is where, and who is spent
- What the plan was, and why
Look, a map helps. But the map doesn't tell you the wind just shifted. The person does.
Step 3: Use A Transfer Template
Most agencies use something like the ICS 201 or a transfer-of-command briefing sheet. The outgoing incident commander should fill it or verbally hit these blocks:
- Incident name and location
- Current situation status
- Objectives established
- Tactical operations in progress
- Resource assignments
- Safety concerns
- Communications plan
- Weather or environmental factors
- Outstanding requests (alarms, utilities, police)
- The outgoing IC's gut feel
That last one isn't on the form. It should be. "My gut says the back wall goes in twenty minutes" is worth more than a clean spreadsheet.
Step 4: Confirm Understanding
Here's the thing — the outgoing incident commander should make the incoming IC repeat it back. That said, not like a test. Like a sanity check. Still, "So what are your first two moves? " If the answer is wrong, that's on the outgoing IC for not being clear.
Step 5: Stay Until Released
Don't walk off the moment you say "you have command." Be there to answer it. "Hey, which engine is on water supply?On the flip side, " The outgoing incident commander should stay available for a few minutes. They always do. The new IC will have a question. Then leave.
Step 6: Document It
Write it down. Worth adding: the transfer should appear in the command log. Day to day, time, names, what was said. To ensure a smooth transfer the outgoing incident commander makes the paper trail so the next shift after that isn't lost either.
Common Mistakes
Honestly, this is the part most guides get wrong. They list "communicate" as if that's a insight. Let's talk about what actually goes sideways.
One big one: the outgoing IC dumps data but not judgment. They'll say "two engines, one truck, staging on Oak." They won't say "the truck company is beat, don't trust them on another climb." That judgment is the gold Practical, not theoretical..
Another: timing. The outgoing incident commander is exhausted, dehydrated, and snappy. They hand off mumbling. Or they transfer too early because they're bored and the fire's out — but overhaul is where firefighters get hurt. People transfer too late. Walking away then is a mistake.
And the classic: no face-to-face. The incoming IC can't see what the outgoing IC sees. Because of that, radio handoffs are for when the building is on fire and you're three blocks away. On the flip side, "I transferred command on the radio, that counts. " It doesn't. Not for a planned shift change in the parking lot Took long enough..
I know it sounds simple — but it's easy to miss the part where the outgoing IC doesn't introduce the incoming IC to the staff. The ops chief, the safety officer, the liaison — those people need to hear "this is your new boss" from the old one. Otherwise they keep reporting to a ghost Less friction, more output..
Practical Tips
What actually works in the field? A few things I've seen separate good handoffs from messy ones.
First, the outgoing incident commander should keep a running "transfer note" from minute one. This leads to not a full log — a scratch sheet of the stuff the next person needs. Because of that, updated quietly during lulls. By the time relief shows, it's half done No workaround needed..
And yeah — that's actually more nuanced than it sounds.
Second, rehearse the brief in your head during the incident. The outgoing IC who can give a 90-second clear transfer without flipping pages is the one who slept after. The one who fumbles costs the team an hour Practical, not theoretical..
Third, watch the incoming IC's face. Because of that, if they look lost, stop. In real terms, the outgoing incident commander isn't done because they finished talking. They're done when the other person gets it.
Fourth, name the dangers plainly. In real terms, "North side is compromised. Here's the thing — " "Weird odor, hazmat pending. Also, " Don't soften it. The incoming IC can't prepare for a threat they didn't hear about.
Fifth, own the awkward silence. Worth adding: ask: "What do you need from me before I go? If the outgoing IC hands off and the new one says nothing, don't fill it with small talk. " That question fixes more handoffs than any form That's the part that actually makes a difference..
FAQ
**
Do I need to stay on scene after the handoff is complete?
Yes — but only as long as it takes for the incoming IC to stabilize. A clean rule: the outgoing incident commander stays within reach for ten to fifteen minutes after transfer, available for quick clarifications but not issuing orders. Day to day, if something was missed in the brief, that window catches it. After that, leave. Lingering in the command post sends mixed signals to crews about who's in charge.
This is the bit that actually matters in practice The details matter here..
What if the incoming IC is junior and clearly overwhelmed?
Slow the handoff down. In practice, then explicitly state the plan they were following so the junior IC has a rail to hold. Think about it: the outgoing incident commander should strip the brief to essentials: life safety status, current resource assignments, and the top two threats. In practice, offer to stay an extra few minutes if protocol allows. Never hand a complex scene to someone drowning and walk away That's the whole idea..
Worth pausing on this one.
Is written documentation enough if the radio handoff was clear?
No. And the judgment calls, the tone of the room, the unspoken risk on the south side — those only travel in person. On top of that, paper supports the conversation, it doesn't replace it. Here's the thing — the written transfer note is a backup for details — apparatus tags, medical runs, utility shutoffs. Treat the document as a receipt, not the transaction.
Good command handoff isn't a formality or a box to check before you clock out. It's the moment where one person's clarity becomes another person's footing. Keep the judgment, face the person, name the danger, and stay until they actually have it. The incidents that go sideways after a shift change almost never fail because the fire changed — they fail because the story of the fire didn't travel with it. That's the whole job in the last five minutes.
