Radio & Communications Quick Reference
Plain-language radio discipline, emergency traffic, priority levels, unit status, callsigns, and dispatch requests.
Radio & Communications Quick Reference
Status: Current guidance
Last revised: August 24, 2026
Use plain, concise language unless an approved code system is specifically directed. Stratos documentation does not establish a ten-code system.
Callsigns
Use only the callsign assigned for the current character, unit, position, and shift. Identify the unit being called before your own unit.
Example: "Dispatch, 2-Lincoln-12."
Do not invent a supervisory, specialty, or command callsign.
Routine transmission order
When practical, state:
- the unit or position being called;
- your callsign;
- location;
- request or update; and
- significant safety information.
Keep nonessential conversation off an active channel.
Emergency traffic
Use emergency traffic for an immediate responder emergency or another urgent threat requiring the channel to clear.
- State the emergency, callsign, and location first.
- Dispatch should acknowledge immediately.
- Other units should hold routine traffic.
- Provide suspect, vehicle, direction, weapon, patient, fire, or hazard information as relevant.
- The incident commander or dispatch releases the channel when emergency traffic is complete.
Do not use emergency traffic to gain priority for a routine request.
Priority levels
| Priority | General use |
|---|---|
| Priority 1 | Immediate threat to life, active violence, serious fire, or responder emergency |
| Priority 2 | Serious incident requiring prompt response without a confirmed active life threat |
| Priority 3 | Routine report, delayed incident, minor collision, or nonurgent service |
| Priority 4 | Administrative, informational, scheduled, or self-initiated activity |
Dispatch may update priority when conditions change.
Common unit status
Use the status supported by the current CAD or directed by Communications:
- available;
- assigned;
- en route;
- on scene;
- transporting;
- at destination;
- unavailable; or
- out of service.
Update status at meaningful points. Do not remain available while committed to another scene.
Common dispatch requests
Include the facts needed for the request:
- records check: record type and authorized identifier;
- additional unit: location and reason;
- supervisor: location and operational need;
- Fire or EMS: location, patient count, complaint or mechanism, hazards, and scene-safety status;
- BOLO or alert: source, description, last known location, direction, risk, requested action, and expiration condition; or
- channel request: incident, units involved, and reason for separation.
Repeat critical identifiers, locations, weapons, and directions. Treat "no return" as an inconclusive result, not proof of illegality.
For the full policy, see the Dispatch Standard Operating Procedure.
Comments