SERVICE LINE 09 — FIG_109
Incident command structure
Groups usually run three or four incompatible command models — one per division, each inherited from a different consultant. Under load they cannot talk to each other. We install one, top to bottom, and drill it until the vocabulary is shared.
SCOPEGROUP-WIDE
LAYERSFOUR — L1 TO L4
ROTATION24H, STANDING
INTEROPERABILITYSTATE + MUTUAL AID
DURATION8–12 WEEKS
CLASSIFICATIONCOMMERCIAL IN CONFIDENCE
01ONE MODEL, TOP TO SHIFTFIG_H / 4 FUNCTIONS
02METHOD4 STAGES
01One modelA single structure across every division, so a crisis cell in one country is legible to a board in another.
02Fixed rolesRoles are held by function, not by seniority or by whoever is present. No volunteers.
03Rotation designTwenty-four hour operation planned from the first hour, because exhaustion is the second failure.
04Common languageShared terms and reporting formats that interoperate with the state and with mutual aid partners.
03WHAT YOU LEAVE WITH
01Group incident command manual
02Role cards and rotation rosters per layer
03Common reporting formats and log discipline
04Interoperability annex for state and mutual aid
04THE QUESTION WE OPEN WITH
ANSWER IT OUT LOUDIf two of your divisions had to run one incident together tonight, would they be using the same words?CLIENT ANSWER — REDACTED
The plan iswritten beforeit is needed
Initial briefings are held under NDA, at your site or ours. Two hours. No deck.