The Chain of Command Is a Fireground Tool. The Office Runs on a Faster Clock.
Robert Grand · Battalion Chief who still runs calls
“Hey Chief, Bill said he’s good to work at M10 and I’m good at M11. That way we both stay in our own stations.”
I get some version of that text almost every shift. And here’s the thing: my answer is always yes. Always. The members found their own coverage, matched the seats, kept both stations staffed, and saved the city money on roving. They also saved the oncoming crew from waiting around for morning relief. By the time that message reaches me, the problem is already solved.
So what am I actually approving?
Nothing. I’m a delay in someone else’s decision.
The Chain Made Sense When Paper Was the Network
The fire service runs on chain of command, and on the fireground it should. Command structure under time pressure is a life safety system. It manages risk, accountability, and span of control when seconds matter and information is incomplete. I will defend that structure all day.
That same structure drifted into the office a long time ago, and for most of that history it worked fine. Back when a question moved on paper, routing it up through a Captain and a Battalion Chief cost almost nothing, because everything moved at the speed of the interoffice envelope anyway. The chain wasn’t slowing anyone down. It was just how information found the person who could answer.
What changed isn’t the chain. It’s the clock. A benefits question that once took three days to reach the right desk is now one email away from an answer. When the payroll clerk can reply in five minutes, sending that same question up two ranks first doesn’t add control, it just spends time nobody gets back. The structure didn’t go wrong. The world got faster than the structure was built for.
Elon Musk made a version of this point in a 2018 email to Tesla (CNBC, https://www.cnbc.com/2018/04/18/elon-musks-productivity-rules-according-to-tesla-email.html). Pick common sense as your guide, he wrote, let communication travel the shortest path that gets the job done, and let people talk directly and just make the right thing happen. Fire service leaders read the Silicon Valley version and bristle, and on the fireground they’re right to. But strip the bravado and the idea holds in our world too. In routine situations, people deserve a fast answer, and the person with the answer is usually one message away.
The skill is knowing which world you’re standing in.
Management by Exception
Here’s what I’d rather do with those swap texts.
If the answer is always yes, the approval is theater. So publish the criteria that make it a yes. Same rank or qualifications for the seat. No overtime triggered. Both members agree. Both stations hold minimum staffing. Write it down once, as policy.
Now anything that meets the criteria approves itself. What reaches me is the exception: a probationary firefighter trying to cover a medic seat, a trade that creates an overtime liability, a member on light duty. My judgment gets reserved for the five percent that actually needs judgment. The other ninety five percent resolves in seconds instead of waiting on my phone.
Notice what didn’t happen there. My authority wasn’t removed. It was expressed once as written policy instead of repeatedly as text messages. That’s still command intent. It’s just command intent that scales.
And the accountability argument, the first one people raise, actually flips. A structured request with the rule check attached, a disposition, and a timestamp is a better record than a thread of “hey chief” texts will ever be. Nothing got less accountable. It got more documented.
Where the Software Earns Its Place
This is where technology earns its place in the firehouse, and it’s not by replacing the chain of command. It’s by encoding the chain’s intent into rules so the chain doesn’t have to touch routine traffic.
A swap request should be a transaction, not a conversation. The system checks quals, staffing minimums, and overtime impact, then either clears it or routes the exception to the Battalion Chief for a one tap decision. Conservative departments can start with everything routing to the chief. Progressive ones can turn on auto approval for requests that pass every check. Either setting beats a text thread, and the approval data eventually makes the argument on its own. When your log shows a ninety nine percent approval rate on swaps, the case for automating the yes writes itself.
Thirty Seconds Is What Actually Moves the Needle
Here’s why I care about minutes at all, and it isn’t really about swap approvals. I sat down with my fire chief last week and pulled turnout numbers out of Dark Horse Emergency, the data analysis software we use. The question underneath it is the one every department is trying to answer: what actually gets us to more fires inside the NFPA 1710 response-time standard? The process work we’d put in had our crews out the door about thirty seconds faster, alarm to wheels rolling. Thirty seconds.
Now set that against the move most departments reach for first when they want faster response: relocate a station, or build a new one, to shave drive time. In our modeling a new station ran about ten million dollars and improved response-time compliance by roughly thirty five percent. The thirty seconds of turnout, found in process for a rounding error next to that check, did more. Same staffing, no concrete, better numbers. That still surprises people, and it shouldn’t.
And here’s the part that reframes the whole conversation: the fix wasn’t more people. A four-person crew is a real gain on the fireground, where more hands do more work, and I’ll argue for it all day. But a fourth firefighter doesn’t get the apparatus out the door or down the road any faster. Response time is its own problem, and the cheapest lever on it is the thirty seconds we were already giving away in the station.
That’s the whole case for minutes, and it doesn’t stop at the apparatus bay. The same thirty seconds hides in every loop we route the long way around. Nobody is going to relocate a station to speed up a shift swap. But free the minute there, and the minute in the payroll question, and the minute in the meeting that didn’t need to happen, and you’ve done for the whole department what the process fix did for turnout. You moved the needle without moving a building.
Two Tools, One Job
Chain of command belongs to the fireground, to discipline, to grievances, the places where authority under pressure is the whole point. Everything routine deserves the shortest path to an answer. Those are two different tools, and the only real leadership question is knowing which one you’re holding.
Draw that line and publish it, so it’s doctrine and not mood. Then go find the thirty seconds wherever they hide, in the swap, in the payroll question, in the meeting that ran long for no reason. Every one you win goes back to the drillground, to the crew, to being ready for the call that needs all of us at our sharpest. That’s the trade worth making, and it’s how you make the next response better.
Robert Grand is a Battalion Chief at Eugene Springfield Fire with 24 years of service. He writes Frontline Intelligence, a newsletter on operational doctrine, technology, and leadership in Fire & EMS.
If this landed, share it with someone in Fire & EMS who needs to hear it.
Subscribe
From the floor, not the vendor booth. Two times a week.