Skip to content
Tailboard
SOP-320Apparatus & EquipmentSOP

Radio Communications

Channel assignments, plain language, tactical benchmarks, Mayday priority.

Read before using

This is a template. It is not your department's policy.

Tailboard templates are drafted as generic starting points aligned to national standards. They are nota substitute for your department's own review or for adoption through your Authority Having Jurisdiction (AHJ). For topics carrying significant exposure (use of force, medical scope, civil rights), route through qualified counsel before adoption.

Every placeholder marked [BRACKETED] must be completed before adoption. Every section must be reviewed against your department's staffing, apparatus, water supply, EMS scope, geography, and the specific laws of your state. What applies to a career department in a city may not apply to a volunteer department in a rural jurisdiction, and vice versa.

Standards, regulations, and best practices are updated regularly. Verify the current edition of every standard cited before adopting this document. Once adopted, this document becomes your department's responsibility — not Tailboard's.

Want this tailored to your department?

Open it in the Policy Builder. Answer a few questions about your staffing, apparatus, and conditions — we'll adapt every section to match.

Number

SOP-320

Version

1.0

Last reviewed

2026-01-01

Next review

2027-01-01

Summary

This SOP governs [DEPARTMENT NAME] radio communications. Clear, consistent radio discipline is what lets a multi-company, multi-agency incident function. This document defines channel use, terminology, message structure, and priority.

Definitions

Dispatch Channel
The channel on which incidents are dispatched and status is communicated to the comm center.
Tactical (Fireground) Channel
A channel assigned to a specific incident for on-scene operations. Also called "fireground" or "ops" channel.
Plain Language
Standard, common words used instead of jargon, codes, or 10-codes. NIMS-required for interoperable incidents.
Tactical Benchmark
A significant milestone report transmitted to Command (e.g., "water on the fire," "primary search complete").

Purpose

To ensure radio communications are clear, efficient, and consistent across every [DEPARTMENT NAME] operation and every mutual-aid incident.

Scope

Applies to every member using a department radio at every incident, training evolution, and administrative communication.

Channel Assignments

Channel assignments are documented in a department channel map attached to this SOP. The map includes dispatch, tactical, mutual-aid, and administrative channels.

  • Dispatch: [CHANNEL NAME] — unit status, dispatch, and coordination with the comm center.
  • Fireground Tac 1–N: [LIST] — on-scene tactical operations.
  • Mutual-aid interoperability: [LIST] — regional channels for multi-agency incidents.
  • Administrative: [LIST] — non-emergency coordination.

Plain Language

  • Plain language is used on all tactical channels and at all multi-agency incidents.
  • 10-codes and agency-specific jargon are prohibited on tactical channels.
  • Status language (responding, on scene, available, out of service) is standardized.

Message Structure

Every radio transmission follows a consistent structure:

  1. Who you are calling.
  2. Who you are.
  3. Wait for acknowledgment.
  4. Deliver the message.
  5. Await confirmation or response.

Arrival Reports

The first-arriving unit transmits an initial radio report on arrival. Content: unit, address, conditions observed, strategy, and assumption of command.

  • Example: "Engine 1 on scene at 123 Main Street. Single-story single-family with fire showing Side A. Offensive strategy. Engine 1 is Main Street Command."

Tactical Benchmarks

Report the following benchmarks to Command on the tactical channel:

  • Water on the fire.
  • Primary search complete (by floor/area).
  • Fire under control.
  • Loss stopped.
  • Secondary search complete.
  • Any change in conditions, strategy, or crew location.

CAN Reports

Conditions, Actions, Needs. Standard format for progress reports on request or when conditions change. Brief, specific, actionable.

  • Conditions: what you see and feel.
  • Actions: what you are doing.
  • Needs: what you need.

Mayday Priority

Mayday supersedes all other fireground traffic. On a Mayday declaration, all units cease non-essential radio traffic until Command clears the air. Mayday procedures are detailed in the Mayday SOG.

Dispatch Status Reports

  • Responding / en route.
  • On scene.
  • Available / in service / clear.
  • Out of service (with reason).
  • Quarters.

Radio Discipline

  • Keep transmissions short.
  • Listen before transmitting.
  • Do not talk over other traffic.
  • Personal conversations are not conducted on tactical channels.
  • No profanity on the air.

Equipment Operation

  • Radios are checked as part of the daily apparatus check.
  • Spare batteries are carried on all portable radios in service.
  • Members are trained on their assigned radio, including channel changes, emergency button function, and zone switching.

Responsibilities

Incident Commander

  • Announce the tactical channel.
  • Maintain disciplined channel use.
  • Manage channel changes if incident complexity warrants.

Company Officers

  • Monitor the tactical channel.
  • Ensure crew members are on the correct channel.
  • Transmit tactical benchmarks and CAN reports.

All Members

  • Use plain language.
  • Limit transmissions to operational content.
  • Acknowledge directed transmissions promptly.

Training Requirements

  • Initial radio training at onboarding.
  • Annual refresher on channel map, plain language, and Mayday radio procedures.
  • Officer-level training on tactical channel management.

References

  • NFPA 1221Standard for the Installation, Maintenance, and Use of Emergency Services Communications Systems
  • NIMS / ICSFederal requirement for plain-language interoperable communications
  • FEMA IS-700 / IS-200ICS / NIMS communications requirements

Adapt this template

Before this template becomes your department's policy, review the following items and adjust accordingly. Anything else that does not match your operation should be updated as well.

  • Attach your department's channel map as Appendix A.
  • Specify your dispatch status-code convention.
  • Cross-reference Incident Command, Mayday, and Accountability SOGs.

Adoption signature

Adopted by (Name, Rank)
Signature
Effective date
Next scheduled review

Before adoption checklist

  • ☐Replace [DEPARTMENT NAME] throughout the document.
  • ☐Complete every [BRACKETED] placeholder.
  • ☐Confirm the current edition of every cited standard.
  • ☐Check against your state statutes and state fire marshal rules.
  • ☐Route for chief review. Topics with significant exposure (use of force, medical scope) also go through qualified counsel.
  • ☐Confirm alignment with any mutual-aid agreements.
  • ☐Schedule a training plan for the new policy before effective date.
  • ☐Announce adoption in writing to all members. Archive the prior version.
  • ☐Set the next review date — annually at minimum.