Incident command for volunteer response.
Muster runs the ICS side of an event: the roster, the posts, the comms plan, the incident log, and the paperwork that has to exist afterwards. It is built around events rather than around a dispatch center, because that is how volunteer organizations actually work.
Medical · heat
Rider off the road at mile 33. Conscious, shaded, water on scene.
The command board during an event. Tactical designators only.
What it does
The real ICS forms
The 205 and 205A fill themselves in from the plan you already built. The 211, 214 and 221 come out of what actually happened. They are the genuine FEMA forms, not a lookalike, because the agency you hand them to knows the difference.
Works when the network does not
Status changes and log entries queue on the phone and send themselves when coverage returns, carrying the time they happened rather than the time they arrived. Radio stays the channel of record. This is the receipt.
Careful with people
Incidents are non-identifying by construction. Volunteer phone numbers reach whoever is entitled to see them and nobody else, and next-of-kin details never reach a printed form.
Who is holding it
- Command
- A laptop at the net desk, often a touchscreen. The whole picture, the board, and the forms.
- Supervisors
- Their division and the people in it. Not the whole roster, because that is not their job.
- Volunteers
- A phone, one hand, one bar of signal. Their assignment, their status, their 214.
- Partner agencies
- A read-only board on a link, with no account and nothing they should not see.
Why it exists
Volunteer response runs on ICS the same as anything else, and most of the software for it is built for agencies with dispatch centers and standing staff. An ARES net, a CERT team and a search callout are all the same shape: people turn out, they are assigned, they are accounted for, and somebody has to be able to say afterwards who was where and when. Muster is that, and nothing else.