The Firefighter Stays. The Friction Goes.
Robert Grand · Battalion Chief who still runs calls
Every generation meets a machine it is afraid of. Ours happens to be artificial intelligence. The fear is familiar, and so is the question underneath it: if a machine can do the work, what happens to the people who used to do it?
It is a fair question. It is also the wrong one. The better question, the one that history actually answers, is this: what happens to an industry when someone finally builds a repeatable process around the work? Because that is what AI is. Not a replacement for people, but the next tool for removing friction from the work people do.
Let me make the case with two industries you already know, and then bring it home to the one most of us live in.
Ford did not replace the worker. He removed the waste.
On December 1, 1913, Henry Ford installed the first moving assembly line at his Highland Park plant. Before that line, building a Model T chassis took more than twelve hours. After it, the same chassis took roughly an hour and a half.
People remember that as a story about speed. It was really a story about process. Ford broke the build into 84 discrete tasks, trained workers to master one, and let the work come to them instead of making them chase it around the floor. He did not invent a machine that built cars by itself. He invented a system that let humans build cars with far less wasted motion, far less error, and far more consistency.
Notice what did not happen. The autoworker did not disappear. Ford’s workforce grew. The job changed, the pay changed (the five dollar day arrived a few months later), and the output became something an ordinary family could afford. The human stayed in the loop. The friction came out of it.
McDonald’s did not invent the cook. They built the line.
Thirty five years later, two brothers in San Bernardino did the same thing to food. In 1948, Richard and Maurice McDonald introduced what they called the Speedee Service System. A limited menu. Standardized portions. Assembly line production behind the counter. The result: a meal that used to take thirty minutes arrived in thirty seconds.
Here is the part worth sitting with. When the brothers later explained where the idea came from, they pointed straight back to Detroit. They modeled their kitchen on Ford’s assembly line. One industry’s process became another industry’s blueprint.
And again, the people stayed. The cook did not vanish. The work got organized. A repeatable process produced a consistent result, and because it was repeatable, it could be tweaked. A little faster here. A little cleaner there. Better over time, because the system was stable enough to improve.
That is the pattern. Across a century and across industries that have nothing to do with each other, the move is always the same: take the work, build a repeatable process around it, reduce the human error factor, free the people to do what only people can do. AI is not a break from that pattern. It is the newest expression of it.
The error factor is the whole point.
In manufacturing, error means a part out of spec. In a kitchen, error means a cold order. Annoying, recoverable, rarely fatal.
In our world, error means something else. A missed dose. A transposed number on a controlled substance log. A unit that is out of service when the tones drop because the paperwork from the last call is still sitting in someone’s pocket. A trend in our cardiac arrest survival data that nobody catches because the data lives in six systems and no human has the hours to reconcile it.
When people hear “limit human error with a repeatable process,” they sometimes hear “treat people like machines.” It is the opposite. The repeatable process is what protects the people. It catches the slip on the worst night, after the third call, at 0300, when a tired medic is doing math they have done a thousand times and the thousand and first is the one that bites. The system is not there to replace judgment. It is there so judgment never has to compete with paperwork for attention.
That is the promise of AI with a human in the loop. Not autonomy. Assistance. The machine handles the repeatable part so the human can own the part that requires a human.
Fire and EMS is the industry technology forgot.
Walk into most firehouses and you will find a paradox. We trust our lives to engineering that is borderline miraculous: the thermal imaging camera, the SCBA, the cardiac monitor that can see a heart better than the best clinician of fifty years ago. And then we document the whole call on a system that feels like it was built in 1998, run reports by exporting to a spreadsheet, build the schedule by hand, and chase compliance deadlines through email and memory.
The clinical edge of our profession is advanced. The operational core has been left almost untouched. That gap is not a sign that technology cannot help us. It is a sign of how much room there is.
And here is the line that matters, the one worth saying plainly to anyone afraid AI is coming for the job.
No Model Pulls Ceiling
You cannot replace the firefighter with AI. You cannot replace the medic. The work is physical, it is human, it happens on the end of a charged line in a zero visibility hallway, on a pitched roof with a saw, in someone’s living room at the worst moment of their life. It requires hands, presence, judgment, and the kind of calm that only a trained person carries into a chaotic room. No model pulls ceiling, forces a door, or makes the call to go interior. No model does that. No model will.
What AI can do is everything around the work that currently steals time from the work.
Consider where the friction actually lives in a shift:
-
The pre-incident intelligence that should reach the crew before they reach the building. Construction type, roof system, hydrant locations and flows, stored hazardous materials, knox box and utility shutoffs. Today that lives in a binder that is out of date, or in nobody’s hands at all. A system could surface the relevant plan for the address the moment the tones drop, so the first due officer is sizing up with information instead of guessing.
-
The narrative that takes fifteen minutes to write after a complex call, whether it is the NFIRS report on a structure fire or the patient record on a code, when the structured facts already exist and a draft could be waiting for the officer or medic to review, correct, and sign.
-
The fire inspection and code enforcement backlog: the occupancies overdue for a visit, the violations that were never closed out, the target hazards nobody has walked in two years. A system can track what is due, flag what slipped, and put the company officer in front of the buildings that actually matter instead of a spreadsheet.
-
The QA process where a supervisor reads every report by hand looking for the few that need a second look, when a system could surface the outliers and let the human spend their attention where it counts.
-
The protocol or pre-plan question at 0200 that gets answered from memory because nobody wants to dig through a binder, when the current answer could be one question away.
-
The scheduling puzzle that eats a chief officer’s morning, the certification or apparatus check that lapses because no one was tracking it, the trend in response times or turnout times that nobody sees until it becomes a headline.
None of that is the work. All of it is friction around the work. Every hour AI gives back is an hour returned to training, to readiness, to the company officer actually leading the company instead of feeding the database.
Human in the loop is not a hedge. It is the design.
Be precise about what “assist” means, because this is where the fear usually hides. AI in our world should never be the one making the call. It drafts; the medic signs. It flags; the supervisor decides. It surfaces a trend; the chief sets the strategy. The human stays accountable, in command, and in the loop, every time.
That is not a limitation to apologize for. It is the correct architecture. Ford’s line still needed the worker. McDonald’s system still needed the cook. The process removed the waste, not the person. Built right, AI in fire and EMS does exactly that: it takes the repeatable, error prone, time stealing tasks off the plate of a professional so that professional can spend more of the shift being a professional.
The fear is real. The conclusion is wrong.
It is reasonable to be wary of a powerful new tool. Skepticism is a virtue in a profession where the cost of being wrong is measured in lives. So do not adopt AI because it is new. Adopt it the way we adopt everything else: tested, with a human accountable, inside a process you can audit and improve.
But do not mistake caution for a verdict. The verdict, written across a hundred years of industry, is clear. The assembly line did not end the autoworker. The service system did not end the cook. The tool that removes friction does not remove the people. It frees them to do the part that was always theirs.
We are not the exception to that history. We are its next chapter, in an industry that has waited a long time for its turn. The firefighter stays. The medic stays. The work stays human. What changes is how much of the shift we get to spend on it.
That is not a threat. That is the point.
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.