The Communications Failures That Bite Small Departments (and How to Prevent Them)

Most radio problems on the fireground are not exotic. They are the same handful of preventable failures showing up again and again, usually at the worst possible moment. This is a candid catalog of what goes wrong in small departments and the low-cost fixes that stop it. Read it as a checklist you can self-assess against this week.

In this guide
  1. Dead batteries and no spare discipline
  2. Radios not programmed alike across the fleet
  3. Nobody knows the channel plan
  4. Dead spots nobody mapped and no backup path
  5. Mutual aid that cannot talk to you
  6. Sensitive information broadcast in the clear
  7. Portables left in trucks and untested gear
  8. The knowledge walks out the door
  9. Takeaways

Dead batteries and no spare discipline

The most common radio failure is the simplest one. A portable dies mid-incident because its battery was never fully charged, was years past its useful life, or was quietly holding a fraction of its rated capacity while still showing a full icon. Batteries are consumable. They age whether you use them hard or leave them sitting.

Why it happens. Small departments rotate volunteers and part-timers through the same handful of radios, and nobody owns the charging routine. Old batteries never get retired because they still power on. There is no habit of grabbing a spare before walking into a structure.

The real-world consequence. A firefighter working interior loses the radio at the exact moment coverage matters most. Command loses accountability of a member. A transmit that should have been a routine progress report becomes silence, and silence on the fireground is treated as a problem until proven otherwise.

The low-cost prevention. Build a battery routine that does not depend on any one person remembering.

A one-minute self-check

Pick any three portables in your fleet right now and look at the batteries. Can you tell how old each one is? If not, you have no way to know which ones are about to fail, and neither does the person who carries them into a fire.

Radios not programmed alike across the fleet

When two radios in the same department have different channels in different positions, or one is missing a talkgroup another has, crews cannot count on the knob. What is channel 3 on the engine may be something else entirely on the portable a mutual-aid firefighter borrowed from your rig.

Why it happens. Radios get programmed one at a time over years, by different people, sometimes by a vendor and sometimes by whoever had the software that day. A new radio comes in and gets a slightly different template. Nobody keeps a master copy of what correct looks like.

The real-world consequence. A member switches to a channel by position, out of habit, and ends up somewhere nobody is listening. Under stress, people default to muscle memory, and inconsistent programming turns muscle memory into a liability.

The low-cost prevention. Standardize the fleet to a single template.

Nobody knows the channel plan

Even a perfectly programmed fleet fails if the people carrying the radios cannot say which channel to use for dispatch, for fireground tactical, for command, or for talking to the next department over. A channel plan that lives only in the chief's head is not a plan.

Why it happens. The plan was never written down, or it was written down once and never taught. New members learn by watching, which means they inherit whatever bad habits are in the room.

The real-world consequence. Crews step on each other on the wrong channel. Command asks for a resource on tactical and gets no answer because half the assignment is monitoring dispatch. Time that should go to the incident goes to sorting out who is where.

The low-cost prevention. Make the plan short, visible, and taught.

The test that matters

Stop your newest member in the bay and ask, without notes, which channel they would go to for fireground operations at a working structure fire. If the answer is a pause, the plan does not exist where it needs to, which is in their head.

Dead spots nobody mapped and no backup path

Radio coverage is not uniform. There are basements, stairwells, big-box interiors, and low areas of your district where portables simply do not reach the repeater. Two failures compound here: nobody has mapped where those dead spots are, and there is no plan for when the repeater or its power fails entirely.

Why it happens. Coverage gets assumed rather than tested. Departments trust that if it worked at the last call, it works everywhere. The repeater is treated as always on, so no one plans for the day it is not, whether from a power outage, a storm, or a site failure.

The real-world consequence. A member transmits from a dead spot and hears nothing back, not knowing whether the message got out. When a repeater drops, a department that only ever operated through it can lose the ability to coordinate across an incident in an instant.

The low-cost prevention. Know your gaps and have a fallback.

Mutual aid that cannot talk to you

The mutual-aid company that rolls in to help you is worth far less if their radios and yours cannot find a common channel. Interoperability is not automatic. Different systems, different frequency bands, and different talkgroups mean two departments can be standing on the same lawn unable to hear each other.

Why it happens. Departments plan their own communications in isolation and only discover the gap during a real incident. Shared or regional interoperability channels exist in many areas but are never loaded into the radios or never practiced.

The real-world consequence. Two crews from two departments work the same building on separate channels with no shared picture. Coordination happens face to face or not at all, which is slow and dangerous.

The low-cost prevention. Solve it before the tones drop.

Sensitive information broadcast in the clear

Radio traffic is public in a way that surprises new members. Scanners and apps let anyone listen. Patient names, medical details, home addresses tied to a person, and tactical specifics said in the clear can end up in front of the wrong audience, including the subject of the call.

Why it happens. People treat the radio like a phone call. Under pressure, it is easy to say more than the situation requires. Nobody set the expectation of what stays off the air.

The real-world consequence. A privacy complaint, an embarrassed patient, or a tactical detail reaching someone it should not. On sensitive calls, broadcasting the wrong information can escalate a scene rather than manage it.

The low-cost prevention. This one is a habit, and habits are cheap.

Portables left in trucks and untested gear

A radio only helps the person holding it. Portables left in a charger in the bay or a cup holder in the cab do nothing for a firefighter who walked into a building without one. And equipment that is never tested between calls fails silently, so the first time you learn a radio is broken is the moment you need it.

Why it happens. Grabbing a portable is not yet automatic. Testing is skipped because the gear worked last time. There is no checkoff that forces someone to key up each radio and confirm it transmits and receives.

The real-world consequence. A member is out of contact because the radio stayed in the truck. Accountability breaks down. A radio that quietly died on the charger goes to a call dead, and nobody knew until it mattered.

The low-cost prevention. Make carrying and testing routine, not optional.

Two checkoffs, one habit

Battery status and a live radio check belong on the same daily checklist as your air and your tools. If a radio check is not on the list, it is not happening consistently, no matter how sure you are that your crews do it anyway.

The knowledge walks out the door

In a lot of small departments, exactly one person understands the radios: which channels are which, how the code plug is built, who the vendor is, and how the whole thing fits together. When that person leaves, retires, or is simply unavailable during an incident, the knowledge leaves with them. Closely related is the crew that has never trained on a mayday, so when a member is in trouble the process falls apart under stress.

Why it happens. Institutional knowledge lives in one head because writing it down feels less urgent than the next call. Mayday training gets deferred because it is uncomfortable and takes time, and departments assume it will go fine on instinct.

The real-world consequence. A radio problem no one else can solve, a channel plan no one else can explain, and a mayday that turns to confusion because the crew never practiced the sequence: declare, identify, transmit the emergency, and account for the member.

The low-cost prevention. Get it out of one head and into the department.

Takeaways

Where RunBoard fits

Most of these fixes come down to a habit written down and checked off. RunBoard gives a small department one place to keep its channel plan and comms SOPs, build radio and battery checks into the daily apparatus checkoff, and log equipment failures so the same problem radio does not keep coming back. The knowledge stays with the department instead of walking out the door with the one person who knew it.