Building an Incident Radio Communications Plan (the ICS-205) for Real Incidents

What the ICS-205 is and why it matters

The Incident Command System (ICS) is the standard, all-hazards management structure used across fire, EMS, and emergency management under the National Incident Management System (NIMS). ICS relies on a family of standardized forms so that people from different agencies can plug into one incident and understand it the same way. One of those forms is the ICS-205, the Incident Radio Communications Plan. It is the single document that lays out how radio communications will be organized for a given operational period.

The reason it matters is simple. Radio is a shared, limited resource. Every scene has more people who want to talk than a single channel can carry cleanly. Without a plan, command traffic, tactical assignments, logistics requests, and mutual aid all collide on one frequency, stepping on each other at exactly the moment clear communication is most critical. The ICS-205 solves that by deciding, ahead of time, which channels or talkgroups belong to which part of the operation.

Think of it as the seating chart for the airwaves. When everyone knows where they are supposed to be talking, the right people hear the right traffic, and the important messages are not buried under routine chatter.

What the plan actually captures

At its core, the ICS-205 is a table. Each row describes one communications channel or talkgroup and how it will be used during the operational period. The exact columns vary by form version, but the plan is designed to answer a consistent set of questions for every channel:

• What is this channel called? A clear, plain-language name or function label that crews can recognize, rather than only a technical designation.
• Who uses it? The function, unit, or assignment the channel is dedicated to, such as command, a division or group, or logistics.
• What is it for? The purpose or type of traffic that belongs on it, so people know what to say there and what to keep off it.
• What are the technical settings? The information radio technicians need to program and verify the channel correctly for the operation.

The plan also typically carries header information that ties it to a specific incident and operational period, along with a space for remarks and a record of who prepared and approved it. That framing is important. An ICS-205 is not a permanent frequency list. It is a snapshot of how communications are set up for one period of one incident, and it is meant to be replaced when the situation changes.

Notice what the form deliberately keeps simple. It is not a technical manual and it is not meant to be read like one. The best plans use plain-language function names so a firefighter stepping off an engine can glance at the assignment and know immediately where command is, where their tactical traffic goes, and how to reach support.

Assigning channels by function

The heart of a communications plan is matching channels to the functions of the incident. Large, complex incidents separate traffic into distinct channels so that no single conversation dominates. Common functional categories include:

• Command. Traffic between the incident commander, command staff, and section chiefs or supervisors. This channel carries strategic direction and status, and it needs to stay clear of routine tactical chatter.
• Tactical. Channels assigned to the divisions, groups, or branches doing the hands-on work. A single command channel might feed several tactical channels, one per operational area, so crews working one part of the scene are not listening to unrelated traffic from another.
• Support and logistics. A channel for resource requests, supply movement, staging, and the behind-the-scenes work that keeps the operation fed. Keeping this off the tactical channels protects the crews doing suppression, rescue, or patient care from interruption.
• Air operations. When aircraft are involved, air-to-ground coordination is kept on its own dedicated channel for obvious safety reasons. Aviation traffic cannot compete with ground chatter.

The exact mix depends on the incident. A structure fire with mutual aid might run command plus a tactical channel and a dedicated fireground safety channel. A wildland incident could run several tactical channels by division plus air operations. An EMS mass-casualty response might separate command, triage and treatment, and transport coordination. The principle is constant: give each major function a place to talk so the important traffic is not fighting for airtime.

How it fits the incident action plan

The ICS-205 does not live on its own. For a planned operational period, it is one component of the broader Incident Action Plan (IAP), the package of documents that lays out objectives, assignments, and support for that period. The communications plan sits alongside the other pieces so that when a crew reads their assignment, they can also see exactly which channels support that assignment.

This connection is what makes the plan operational rather than theoretical. A division supervisor should be able to look at their tactical assignment and, in the same IAP package, find the channel they are supposed to use, the channel command is on, and how to reach support. The communications plan makes the rest of the action plan executable, because assignments mean little if people cannot coordinate them.

Because the IAP is built for a specific operational period, the communications plan is refreshed each period as well. As objectives shift, resources arrive or demobilize, and the geography of the incident changes, the channel assignments are reviewed and reissued. A plan from twelve hours ago may no longer match the incident in front of you.

The communications unit leader role

On a growing incident, someone has to own communications. In the ICS structure, that responsibility sits in the Logistics Section, and the position most associated with building the ICS-205 is the Communications Unit Leader. This is the person who plans how the incident will communicate, coordinates the setup and distribution of radios and equipment, and prepares the radio communications plan for each operational period.

On smaller incidents, there may be no formal communications unit at all, and the incident commander or a designated officer handles the same thinking on a smaller scale. The function still exists even when the title does not. Someone is deciding where command talks, where tactical talks, and how support reaches out, whether that is written on a formal ICS-205 or worked out verbally at a two-engine call.

The value of naming the role is accountability. When one person owns the communications plan, channels get assigned deliberately, conflicts get resolved, and the plan gets briefed and updated rather than drifting. On a large or long-duration incident, that ownership is the difference between a coherent radio picture and a free-for-all.

A simplified version for small departments and planned events

It is easy to assume the ICS-205 is only for large, complex incidents with a full command structure. In practice, a simplified version is one of the most useful tools a small department has, both for routine operations and for planned events.

For routine operations, many departments run a standing, simplified communications plan: a dispatch channel, a fireground or tactical channel, and a way to reach mutual aid. Writing that down, even as a one-page reference, means that every member, including new hires and mutual aid partners, knows the standard channel assignments before anything goes wrong.

For planned events, a lightweight ICS-205 shines. A parade, a fair, a football game, a controlled burn, or a community festival all benefit from deciding channel assignments in advance. Who is on command, which channel handles medical, how event security reaches you, and which channel you would move to if a real emergency developed. These are decisions best made at a planning table, not on the fly.

• Keep it to what you actually use. A small department does not need ten channels on paper. Two or three well-assigned channels, clearly labeled, beat an elaborate plan nobody follows.
• Use plain function names. "Command," "Fireground," and "Medical" are easier to act on under stress than technical designations alone.
• Build from your standard operations. Start with how you already work day to day, then adjust for the specific event or incident.

The goal is not paperwork for its own sake. It is that everyone, including partners who do not normally work with you, arrives already knowing where to talk.

Distributing, briefing, and updating the plan

A communications plan that stays in the command vehicle helps no one. The plan only works if crews actually know their channels, which means distribution and briefing are as important as the plan itself.

Distribute it where crews will see it. On a formal incident, the communications plan travels with the IAP and is handed out at the operational briefing. On smaller incidents, it may be as simple as command announcing channel assignments over the radio and confirming that units acknowledge. Whatever the method, the assignments have to reach the people who need them before they need them.

Brief it in plain language. A good briefing tells crews where command is, which channel carries their tactical traffic, where to route support requests, and where air operations lives if aircraft are involved. Keep it short and concrete. People remember three or four clear assignments far better than a dense table read aloud.

Confirm crews can reach their channel. Assigning a channel is not the same as verifying radios are programmed and working. Early in an operation, a quick radio check on each assigned channel catches programming gaps before they become safety problems.

Update it as the incident grows. This is where many plans fail. An incident that starts as a single tactical channel may need a second division channel an hour later, or a dedicated support channel once logistics ramps up. When the plan changes, the change has to be communicated and, on formal incidents, reissued for the next operational period. A stale communications plan is worse than none, because people trust it and act on outdated assignments.

Takeaways

• The ICS-205 Incident Radio Communications Plan is standard NIMS/ICS material that assigns channels and talkgroups to the functions of an incident, so command, tactical, support, and air operations each have a place to talk.
• Its core job is to answer, for every channel, what it is called, who uses it, and what belongs on it, in plain language crews can act on under stress.
• The plan is part of the broader incident action plan and is refreshed each operational period as the incident changes.
• On growing incidents, the Communications Unit Leader in the Logistics Section owns the plan; on small ones, the incident commander or a designated officer performs the same function.
• Even small departments benefit from a simplified, standing version for routine operations and planned events, built from how they already work.
• Distribution, briefing, radio checks, and timely updates are what turn a written plan into crews who actually know their channels.
• Always confirm the current ICS forms and your regional or agency communications plan before building one for a real incident.