You're running a structure fire. On the flip side, three engines, two trucks, a battalion chief. The IC has been on scene for twenty minutes. Things are stabilizing — primary search done, fire knocked down, ventilation coordinated. Then the deputy chief pulls up.
Now what?
If you've been in emergency services long enough, you've seen this go smoothly. m.Even so, the difference usually comes down to one thing: whether everyone actually understands how transfer of command works — not in theory, but in practice, at 2 a. And you've seen it turn into a mess. , with adrenaline still spiking.
The official docs gloss over this. That's a mistake That's the part that actually makes a difference..
What Is Transfer of Command
Transfer of command isn't a promotion ceremony. It's not about ego. It's a formal, structured process where incident command authority moves from one person to another — typically someone with higher qualifications, more experience, or specific jurisdictional authority.
In the Incident Command System (ICS), this is baked into the doctrine. But doctrine and reality don't always shake hands.
The incoming IC doesn't just walk up, grab the radio, and start barking orders. That's how you get freelancing, duplicated efforts, or — worse — critical tasks falling through the cracks because both people thought the other had it No workaround needed..
The Legal and Policy Side
Most agencies have SOPs or SOGs that spell out when transfer happens. Sometimes it's automatic: a chief officer arrives, they assume command. Sometimes it's discretionary: the current IC briefs the incoming officer, and they decide whether to transfer.
Know your policy. On top of that, not "kinda know it. " Know it cold. Because when the deputy chief's vehicle lights wash over the command post, nobody has time to dig through a binder.
Qualifications vs. Rank
Here's where it gets sticky. Rank doesn't always equal qualification. A newly promoted battalion chief might have less fireground time than the captain who's been running the show for the last hour.
ICS says the most qualified person should fill the IC role. But "qualified" gets defined differently depending on who you ask. Certifications? In real terms, years on the job? Worth adding: specific incident type experience? On the flip side, the policy should clarify this. If it doesn't, you're improvising — and improvising at a working incident is a bad habit Not complicated — just consistent. That alone is useful..
Why It Matters
You might think, "It's just a handoff. How hard can it be?"
Hard enough that NIMS identifies poor transfer of command as a recurring factor in after-action reports. Hard enough that people have died because accountability got lost in the shuffle.
Continuity of Operations
The incident doesn't pause for the handoff. That said, fire keeps burning. Patients keep crashing. On the flip side, hazmat keeps off-gassing. If the new IC doesn't have a complete picture the second they take the radio, decisions get made on bad information.
That's how you get a crew sent into a collapse zone that the previous IC already wrote off. Or a defensive strategy flipped offensive without a PAR. Or two divisions working at cross-purposes because nobody told Division B that Division A changed tactics Which is the point..
Accountability and Safety
The personnel accountability report (PAR) is only as good as the person tracking it. Consider this: every name. When command transfers, the accountability system must transfer intact. Worth adding: every assignment. Every last-known location.
I've seen a transfer where the outgoing IC handed over the tactical worksheet but forgot to mention the two firefighters doing overhaul in the Bravo exposure — because they'd been assigned after the worksheet was last updated. Thirty minutes later, the new IC called a PAR. Even so, two names missing. Hearts stopped until they walked out clean.
And yeah — that's actually more nuanced than it sounds.
That's on the transfer. Not the fire.
Jurisdictional and Legal Authority
Sometimes transfer isn't optional. In real terms, a state police lieutenant arrives at a highway incident. A federal agent shows up at a terrorism scene. The county sheriff pulls rank at a multi-agency search.
When legal authority shifts, command must shift with it — cleanly, documented, witnessed. Because later, in a deposition or a coroner's inquest, "I thought he was running it" doesn't hold up.
How It Works
The mechanics aren't complicated. Doing them under stress, consistently, every time — that's the discipline Most people skip this — try not to..
Step 1: The Incoming Officer Sizes Up — Quietly
Before a single word hits the radio, the incoming officer observes. So reads the tactical worksheet. Even so, watches the fireground. Also, listens to the radio traffic. Talks to the safety officer, the operations chief, the division supervisors.
They're building a mental model. In real terms, what's the progress? In real terms, *What's the strategy? What are the hazards? What resources are committed, and what's staged?
This takes two minutes. And it absolutely does not happen while standing next to the current IC asking "So what's going on?Maybe five. It does not take twenty. " over the roar of a master stream.
Step 2: The Briefing — Structured, Not Conversational
The outgoing IC gives a formal briefing. Some agencies use a standard format — the "ICS 201" style or a local equivalent. Minimum elements:
- Current strategy and incident objectives
- Tactical deployment by division/group
- Resource status (committed, staged, en route)
- Safety concerns and hazard zones
- Accountability status — including exceptions
- Significant events to date (collapse, mayday, victim removal, etc.)
- Current and anticipated needs
No war stories. No "we almost lost a crew earlier but it's fine now." Just the facts the new IC needs to command effectively Small thing, real impact..
Step 3: The Formal Transfer
Once the briefing is done and the incoming IC confirms understanding, the transfer is announced. On the radio. Clearly.
"Command is transferring from Captain Ruiz to Battalion Chief Chen. Battalion Chief Chen is now Incident Command. Time 02:47 Not complicated — just consistent. Took long enough..
That timestamp matters. It goes in the CAD log. It goes on the tactical worksheet. It becomes the official line between his decisions and yours Easy to understand, harder to ignore..
Step 4: The Outgoing IC Doesn't Vanish
This is the mistake I see most often. The outgoing officer hands off the clipboard and walks away to get coffee or talk to the press.
Don't.
Stay available. You hold institutional memory of the last hour — the why behind decisions that might not be obvious on the worksheet. Still, "Why did we pull the line from Side C? Stay visible. Plus, the new IC will have questions. " "Was that victim removal confirmed by Division 2 or EMS?
Be there to answer. For at least one operational period. Longer if the incident is complex That's the whole idea..
Step 5: Rebrief the Team
The new IC should hit the radio within minutes — not to change anything, but to confirm.
"All divisions, this is Command. I've assumed command from Captain Ruiz. Report any concerns or needs. Current assignments unchanged. Strategy remains offensive. Command out.
That transmission does two things: it tells everyone the handoff is done, and it opens the door for someone to speak up if something isn't right.
Common Mistakes
The "Drive-By" Transfer
Chief pulls up, grabs the radio: "I've got command.Which means no worksheet. " Keeps driving to the next meeting. Because of that, no briefing. No PAR confirmation.
The captain on scene is left wondering: *Does he know about the basement fire? The missing civilian? The low water pressure?
He doesn't. And now nobody's clearly in charge.
The Reluctant Handoff
The current IC doesn't want to give it up. Maybe they're invested
The Reluctant Handoff
The current IC doesn't want to give it up. Maybe they’re invested in the mission, or they’re afraid their own mistakes will be blamed on the new commander. In practice, they might leave the radio on, let the new IC try and “take over” on their own, and then quietly step back when the fire chief asks to see the incident command post. That half‑handed approach is a recipe for confusion. The IC must actively release authority, not just let it evaporate.
The Incomplete Handoff
An IC who simply hands a stack of papers and says, “You’ve got everything you need,” is assuming the new commander will read between the lines. That’s dangerous. Also, the new IC must see the situation, not just read it. A brief walk‑through of the command post, a quick demo of the incident map, a rundown of the current status of each resource—all these small gestures pay off when the next decision is made.
The “I’ll Be Back” Transfer
Sometimes the outgoing IC is busy with a press conference, a briefing to the mayor, or a debriefing with the agency’s executive. They might say, “I’ll be back in ten minutes.So ” Meanwhile, the new IC is left in a vacuum. If the outgoing IC is truly unavailable for a period, they should officially hand over the radio channel and give the new commander a “no‑call” period. The outgoing IC can then circle the incident in their own way, but the new commander must have the authority to act independently.
The Human Element
Once the paperwork and radio chatter are done, the real work begins: building trust. And the new IC must show that they respect the work already done, but also that they’re ready to make their own decisions. Worth adding: a quick “I’ve reviewed the last 30 minutes of the log, and I’ve got the picture. Let’s keep moving.” goes a long way toward easing the nerves of a team that may have been in a state of constant micro‑command for hours.
Communication is the glue. The new IC should keep the channel open, encourage updates, and remind everyone that the incident is a shared mission. “We’re all here to get this incident under control, not to argue who’s in charge,” is a mantra that helps keep the focus on the incident, not on the title.
When the Incident Gets Complex
In a large, multi‑agency incident, the handoff can be more than a single radio call. It may involve:
- A formal handoff meeting with all team leaders present.
- A shared digital dashboard that shows real‑time resource status.
- A backup plan where the outgoing IC remains the technical advisor for a predetermined period.
- A joint review of the incident’s strategic objectives to ensure alignment.
The key is that the new IC must have immediate access to all critical information and the authority to enforce it That's the part that actually makes a difference..
The Final Piece of the Puzzle
The most often overlooked component of a successful handoff is follow‑up. The outgoing IC should schedule a brief debrief with the new commander after the first shift change. This isn’t a “who did what” audit; it’s a chance to clarify any lingering questions, to confirm that the new IC feels confident and supported, and to cement the continuity of command.
Conclusion
A command handoff is not a mere formality; it’s a lifeline that keeps the incident moving forward. Still, the outgoing IC must provide a concise, fact‑based briefing, officially transfer authority on the radio with a timestamp, remain available for the immediate transition period, and confirm the new commander’s authority with a quick broadcast to the whole team. Avoid the pitfalls of a “drive‑by” transfer, a reluctant handoff, or an incomplete handoff, and always remember that the ultimate goal is a seamless, unified effort to protect life and property.
Honestly, this part trips people up more than it should.
When the new Incident Commander steps into the role, they should feel the confidence of the team and the weight of responsibility balanced by the knowledge that they have the full support of their predecessor. That balance is what turns a chaotic scene into a controlled, mission‑focused operation—and it’s the hallmark of professional incident command.
