Hearing an order and understanding it look like the same thing from the command post. They aren’t. Somewhere between the officer’s mouth and the firefighter’s hands, a lot of good plans quietly turn into something else.

The gap nobody sees

Picture a busy evolution. The officer calls for a second line to the B side. The radio is crowded, the pump is loud and the crew is already moving. Somebody hears “second line.” Somebody else hears “B side.” Nobody hears both. Two minutes later the line is going somewhere, just not where the officer pictured it.

Nobody did anything wrong on purpose. The message went out, and everybody assumed it landed. That’s the trap. On a fireground, silence after an order usually gets treated as agreement. Most of the time it just means nobody said anything.

Every instructor has watched this play out on a training ground. The debrief starts, and the officer and the crew describe two different plans. Both of them are sure they were clear.

What closed-loop actually means

Closed-loop communication is simple. It has three parts, and all three have to happen:

1. The sender gives the message. Who it’s for, what needs to happen, and where.
2. The receiver repeats it back. Not “copy,” not a thumbs-up. The actual task, in their own words.
3. The sender confirms it or corrects it. “That’s correct,” or “Negative, B side, not C side.”

That third step is the one that gets skipped. The repeat-back is only useful if somebody is actually listening to it. If the officer is already on to the next thing, the loop never closes, and a wrong repeat-back sails right through.

Once the task is done, close it again. “Second line in place, B side, flowing.” Now the officer knows the job is done instead of guessing. That last report is what lets them stop thinking about it and move on to the next problem.

Aviation, medicine and the military all lean hard on read-backs for the same reason we should. When a misunderstood instruction can hurt someone, you don’t leave understanding to chance.

“Copy” is not a repeat-back

Ask any officer who’s done this a while how much they trust the word “copy” on the radio. It sounds like confirmation. It isn’t. All it really proves is that the radio worked.

If you tell a crew to ventilate and they say “copy,” you have no idea whether they heard ventilate, which side, or whether they’re waiting on your call to start. If they say “Ladder 2 copies, horizontal vent, Alpha side, on your order,” you know exactly what’s in their head. If it’s wrong, you can fix it before it becomes a problem instead of after.

This works face to face, too. On the ramp or in the yard, a quick repeat-back takes about three seconds. Have the nozzle firefighter say the assignment back before they go. Have the pump operator repeat the pressure they’re setting. It feels a little formal the first few times. After that, it just becomes how your crew talks.

Build it into every drill

Closed-loop communication doesn’t show up on a real incident because somebody put it in an SOP. It shows up because crews have done it a few hundred times when nothing was on fire.

That means instructors have to demand it on every evolution, not just the communications drill. If a student answers an assignment with “got it,” stop and make them say it back. If an officer gives an order and walks away before the repeat-back, call it out. Put it in the debrief: Were the orders clear? Did every one get repeated back? Did anybody report when they finished?

You can make it a drill on its own, too. Run a scenario with the radio traffic deliberately heavy. Give some assignments with a detail missing, and see who catches it. Give one that’s flat-out wrong, and see who questions it. A crew that’s comfortable saying “say again” or “confirm, you want the C side?” is a crew that won’t run with a bad assumption when it counts.

Officers, this one starts with you. If you get irritated when someone asks you to repeat yourself, your people will stop asking. Make it clear that a repeat-back or a clarifying question is never an interruption. It’s the job.

What to do Monday

Pick one evolution this week and hold everyone to it. Every assignment gets repeated back. Every repeat-back gets confirmed. Every finished task gets reported. Don’t accept “copy.” Then talk about it in the debrief, and notice how much smoother the next rep runs. Clear communication isn’t a soft skill. It’s what turns one officer’s plan into a crew that’s all working the same fire.

Stay safe, and train like it matters.

Eric Makowski