Incident Support, Operational Procedures, and Documentation
What this domain tests
Domain 8 is the operational paper trail: how communications are planned inside ICS, who fills which role, and what documentation protects the agency afterwards.
Core rules
- Communications sit inside NIMS/ICS as the Communications Unit, led by the COML and staffed by COMTs, the INCM, RADOs and AUXCOMM volunteers.
- The ICS 205 Incident Radio Communications Plan lists each function (command, tactical, logistics) with its channel, frequency, mode and assignment. The ICS 205A holds contact details; the ICS 217A records available communications resources.
- The Tactical Interoperable Communications Plan documents pre-planned interoperability for a jurisdiction; the COML adapts it to the incident.
- Plain language on shared channels, standard channel naming and radio checks at check-in prevent most on-scene confusion.
- Procedures cover emergency activation, all-call, console patches, priority and preemption, and keeping tactical traffic off the command channel.
- Documentation includes site and maintenance logs, frequency authorisations, encryption key records, interference reports, and an after-action report with an improvement plan.
Worked example
A multi-agency response needs a plan in 30 minutes. The COML assigns command traffic to the agency trunked talkgroup, two tactical channels per division, a logistics channel, and VTAC12 for the incoming out-of-county strike team. Each entry is written on the ICS 205 with plain-language names and the radio template (zone and channel) noted, then read back at the operations briefing. The after-action report later records that the strike team radios lacked VTAC12, prompting a programming change.
Traps
Treating the ICS 205 as a dispatcher-only document, using agency codes on shared channels, failing to record frequency and key authorisations, and skipping the after-action report so the same gap recurs next season.