COML Role: ICS-205 and ICS-210 in Plain Language
The COML owns the comms plan — not just a channel list. ICS-205 is the frequency assignment form; ICS-210 is the broader Communications Unit Plan tying org chart, PACE, and assignments together. Confusing the two produces radios programmed for yesterday's period while ICS-203 shows new COMT names.
Use COML planner hub, ICS-205, and the ICS-210 lite form. Export CHIRP CSV from ICS-205 when you are programming field radios. All forms save locally and roll into the incident workspace close-out packet.
ICS-205 in plain language
ICS-205 answers: who transmits where, on what tone, for which function. Each row is a channel assignment — tactical, command, logistics, air-to-ground as applicable. COML coordinates with the frequency coordinator and agency spectrum manager when incidents scale.
On small incidents, one sheet may cover the entire op period. On multi-day events, expect a new ICS-205 each period — version them in the incident name field.
ICS-210 in plain language
ICS-210 is the COML's narrative and organizational glue: PACE summary, reference to the current ICS-205, COMT/NCS assignments, and notes for shadow positions. Field techs read ICS-210 to know which digital contingency is actually authorized.
Typical planning sequence
- ICS-201 / ICS-202 — situation and objectives drive comms needs.
- PACE — layers before frequencies.
- ICS-208 — safety message may restrict channels or power.
- ICS-205 — assign freqs and tones.
- ICS-210 — publish COML plan for the period.
- ICS-217 — track comms assets as they arrive and demob.
COML vs COMT
COML plans; COMT executes. On large incidents they are separate people. On small county activations one volunteer may wear both hats — still produce both documents so demob does not conflate roles. See COMT hub for execution tools.
Export and programming
CHIRP CSV export from ICS-205 reduces programming errors. Hand field techs a printed go-bag sheet from local go-bag plus incident-specific rows. Test every programmed channel before the net opens — "should work" is not an on-air check.
Working with the frequency coordinator
Large incidents may need inter-agency frequencies beyond club repeater pairs. Document coordinator contact on ICS-210 notes. If you are not the coordinator, do not improvise federal channels — that is how fines and interference happen.
Shadow COML and deputies
Multi-period incidents rotate COML staff. Each rotation should produce a fresh ICS-205/210 pair or explicit "unchanged from prior period" notation signed by IC. Ambiguous handoffs lose channels mid-net.
Digital assets on ICS-210
List Meshtastic node IDs, DMR talkgroups, Winlink RMS accounts, and satellite terminals as named resources — not vague "we have mesh". COMT reads this section to know what is authorized vs experimental.
Quality control before release
Read ICS-205 aloud to another ham before publishing: channel name, RX, TX, tone, function. One wrong tone silences a shelter net. Export CHIRP and test with a field tech who did not write the plan — fresh eyes catch errors.
Further reading on KI4TQN
This site is built for operators who practice before the storm. Bookmark the deployment workflow, install the PWA once on Wi‑Fi, and run the same drill quarterly. Offline tools only help if you opened them at least once while online — cache what you will need when LTE is gone.
East Tennessee operators should keep regional net times in the same note app as family emergency contacts. When the next wind event arrives, you will not have time to search PDFs for PL tones.
If this article helped, share the link with your club EC or neighborhood group. Written plans beat heroic improvisation — and documented tests beat both when the after-action review happens.
← All articles · Start here · Just licensed · Free downloads · Newsletter