Building a Department Communications SOP From Scratch

Why a written comms SOP matters

Most departments run on habit. The senior members know the channels, the dispatchers know who covers what, and new people learn by listening and getting corrected. That works until it does not. Habit lives in people's heads, and heads leave. When a long-tenured member retires, a piece of your communications plan walks out the door with them. When you take in a probationary member, a transfer, or a mutual-aid company that has never worked your ground, there is nothing to hand them.

A written communications SOP does three things a verbal tradition cannot. First, it makes the plan portable. Anyone can read it, including people who do not work here yet. Second, it forces you to make decisions before the incident instead of during it. Deciding where command talks, where the interior crews talk, and where you push emergency traffic is a calm-morning decision, not a burning-building decision. Third, it gives you something to train and test against. You cannot drill a plan that only exists as folklore.

You do not need a hundred pages. A communications SOP that a new member can read in fifteen minutes and actually follow beats a binder nobody opens. Aim for clear over complete. You can always add detail later, but you cannot fix confusion during a mayday.

The channel and talkgroup plan

This is the backbone of the document. Everything else references it. The channel plan is a plain list of every channel or talkgroup your members can select, what it is for, and where it lives in the radio programming. Write it so a member holding a radio can match what they see on the display to what they read on the page.

For each channel or talkgroup, capture the same handful of facts every time:

• The name as it appears on the radio display, spelled exactly.
• The zone or bank it lives in, and the position in that bank.
• Whether it is repeated (works through infrastructure) or simplex (radio to radio, no repeater).
• Its intended purpose, in one sentence. Dispatch, fireground tactical, command, EMS, staging, mutual aid, and so on.
• Whether it is monitored by a dispatch center, and if so which one.

Keep the standardized interoperability channels straight from your own local channels. National and regional interoperability channels follow a standardized naming convention specifically so that agencies who do not normally work together can find common ground quickly. Reference those channels by their standardized names, not by a local nickname. A nickname means nothing to the department coming from two counties over, and the whole point of interoperability naming is that it means the same thing everywhere.

Who talks where, by incident type

A list of channels does not tell anyone how to use them. The next section maps talking to doing. For each common incident type your department runs, spell out which channel each function uses. This is where you turn a pile of channels into an actual plan.

Work through your call types one at a time. A structure fire, a medical call, a vehicle crash with extrication, a wildland or brush incident, a hazardous materials response, and a large or long-duration incident each have different traffic needs. For each one, answer a small set of questions:

• Where does the responding unit talk to dispatch?
• Once on scene, where does command operate?
• Where do the tactical crews (interior, exterior, water supply, and so on) talk?
• Where does EMS or transport traffic go so it does not step on fireground traffic?
• When the incident grows, what is the plan for splitting traffic across more than one channel, and who assigns it?

The governing idea is that command traffic and tactical traffic should not share a channel on anything beyond the smallest incidents. A company officer trying to give a progress report should not be fighting a water-supply request for airtime. On a routine call, one channel is fine. On a working incident, you separate command from tactical, and you say so in writing so nobody has to invent the split under load.

Do not over-engineer this. Most departments run the same handful of call types over and over. Nail those. Write the common cases clearly, add a short paragraph on how you expand for the big or unusual incident, and stop there. A plan that covers ninety percent of your calls perfectly is more useful than one that tries to script every scenario and becomes unreadable.

Radio discipline and plain language

Good channels do not help if the traffic on them is a mess. The discipline section sets the expectations for how members actually key up. It is short, and it is one of the parts new members most need in writing, because bad radio habits are contagious and hard to unlearn.

Commit to plain language. The move away from coded signals and toward plain, everyday words is a settled expectation across the fire and EMS world, and it matters most at exactly the moments a code is likely to be misheard or misremembered: multi-agency incidents, high-stress traffic, and anyone working outside their home system. Codes save a second or two and cost clarity. On a communications SOP, clarity wins every time. Say what you mean in words anyone on the channel will understand.

Lay out the basic mechanics of a transmission so a new member has a pattern to copy:

• Listen before you key. Make sure the channel is clear.
• State who you are calling, then who you are. The unit you want hears its own name first and starts listening.
• Wait for acknowledgement before passing your message. Do not talk to a radio that has not answered.
• Keep it short. One thought per transmission. Long monologues get stepped on and forgotten.
• Use clear, standard words for confirming and correcting. Pick your department's standard terms and use them the same way every time.
• Acknowledge orders in a way that proves you understood, not just that you heard. Repeating the key instruction back closes the loop.

Name unit and function consistently. If a crew is assigned to search the second floor, they are addressed by their assignment for the duration. Consistent naming is what lets command track who is where without a scorecard in their head.

Mayday and emergency traffic procedures

This is the most important section in the document, and it is the one you write most carefully. When a member is in trouble, or when conditions change in a way that threatens everyone on the fireground, the radio has to do exactly one job flawlessly. The SOP defines two distinct situations and keeps them separate: a mayday, which is a member in distress, and emergency traffic, which is an urgent scene-wide warning such as a change in structural conditions or an order to evacuate.

For the mayday, write down the answers to these questions and make sure every member can recite them:

• What word does a member in trouble say? Use one, short, unmistakable word, said three times, so it cuts through anything else on the channel.
• What information does that member try to pass? A simple, memorable format for reporting who they are, where they are, and what they need gives a stressed person a script to hold onto.
• What does command do the instant a mayday is heard? Acknowledge it, quiet the channel, and manage the rescue while keeping the rest of the incident running.
• Does the mayday and its rescue stay on the current tactical channel, or move? Decide in advance and write it down. Making the choice mid-mayday wastes the seconds you do not have.

For emergency traffic, define the signal command uses to seize the channel, the way that warning is announced, and the expected response from every crew, including how they confirm they got the message and are acting on it. If your evacuation signal includes an audible tone or a horn pattern, describe it here alongside the radio procedure, because members under stress will latch onto the sound faster than the words.

Simplex fallback and degraded-mode operations

Every radio system fails eventually. A repeater loses power, coverage drops out in a basement or a large structure, infrastructure gets overloaded, or you simply drive into a dead spot. A communications SOP that only works when everything works is not finished. The degraded-mode section is your plan for talking when the normal plan is gone.

The core fallback is simplex, radio to radio, with no repeater in the middle. Simplex has shorter range and no help from infrastructure, but it does not depend on anything that can be turned off. Members must know which channels are simplex, when to switch to them, and what changes about how they operate once they do. Because simplex range is limited, portable-to-portable communication across a large or shielded structure may not carry, and your plan should acknowledge that and account for relays or repositioning.

Spell out the triggers and the actions:

• How a member recognizes they have lost the repeater. Failed transmissions, no acknowledgement, a distinct tone, or a coverage warning on the radio.
• The specific simplex channel to switch to for fireground work.
• Who announces the switch and how the rest of the incident is told to follow.
• What accountability looks like when range is short. More frequent check-ins, tighter crew integrity, and members positioned to relay traffic.
• When to fall all the way back to non-radio methods: hard-wired communications, runners, hand signals, and pre-arranged sound signals.

Practice this part or it will not exist when you need it. Degraded-mode operations feel unnatural because members almost never use them, which is exactly why they have to be trained deliberately rather than discovered on a bad night.

Roles, accountability, and radio maintenance

Traffic needs someone responsible for it, and radios need someone responsible for them. This section covers both the people side and the equipment side.

On larger or longer incidents, name a function responsible for the communications picture. Under an incident command structure, this is a defined role that manages channel assignments, sets up any additional talkgroups, and serves as the point of contact for radio issues so the incident commander does not have to also be the switchboard. On a small department this may be a hat the incident commander wears until the incident grows, and that is fine, but the SOP should say at what point the role gets handed off and to whom. The value of a standardized command structure is that the function exists whether or not you have a spare person, so members know the job is being done and who is doing it.

Cover mutual aid and interoperability explicitly. When outside companies work your ground, they will not know your local channels, and you will not know theirs. Decide in advance which standardized interoperability channel is your common tactical channel, who assigns incoming units to it, and how you brief an arriving company on the plan in one short exchange. Interoperability is a decision you make before the call, not a scramble you run during it.

The maintenance and accountability side keeps the hardware trustworthy:

• A regular check that every portable and mobile radio powers on, holds a charge, and is on the correct default channel at the start of a shift or duty period.
• An assignment record so you know which radio is with which member or apparatus, which matters when you are tracking who is transmitting.
• A battery plan: charging routine, spare batteries staged and rotated, and a way to swap on a long incident.
• A clear path for reporting a radio that is damaged, weak, or behaving oddly, so it comes out of service before it fails on a call.
• A note on who is responsible for programming and for keeping every radio's channel lineup identical, because a radio programmed differently from the rest is a hazard hiding in a pocket.

Writing it plainly, keeping it current, and training to it

A communications SOP is only as good as its readability and its upkeep. Three practices keep it alive.

Write it so a new member can follow it. Assume the reader has never worked here and is not a radio expert. Use the same word for the same thing every time you refer to it. Number your steps for anything that has to happen in order. Put a short glossary at the front for the handful of terms that matter. Lead each section with what to do, then explain why if the reason is not obvious. Read it out loud when you finish; if you stumble, so will they. And test it on an actual new member before you finalize it, because they will find the confusing parts you have gone blind to.

Keep it current. Channel lineups change, mutual-aid partners come and go, and radio programming gets updated. An out-of-date comms SOP is worse than none, because it teaches the wrong thing with authority. Put a revision date and a version on the cover. Assign one person to own the document. Review it on a set schedule, at least once a year, and trigger an off-cycle review any time the radio programming changes, a new partner agency comes online, or an incident review surfaces a communications problem. When you change the SOP, make sure the quick-reference cards in the apparatus change with it, or you will have two plans fighting each other.

Train to it. A written plan that lives only on a shelf is a compliance artifact, not a working tool. Walk new members through the channel plan and have them find each channel on an actual radio. Drill the mayday and emergency-traffic procedures until the response is automatic, not looked-up. Run at least one exercise a year in degraded mode, on simplex, so the fallback feels familiar instead of foreign. Include the communications plan in your incident debriefs and feed what you learn back into the document. The goal is not that members have read the SOP. The goal is that they do not have to, because the plan is already in their hands.