DISCUSS YOUR SITUATION →
← Services/Incident command structure

SERVICE LINE 09

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.

SCOPE
GROUP-WIDE
LAYERS
FOUR — L1 TO L4
ROTATION
24H, STANDING
INTEROPERABILITY
STATE + MUTUAL AID
01

ILLUSTRATIVE
L1L2L3L4BOARDCRISIS CELLSITESITESITESHIFT LEADSHIFT LEADSHIFT LEADNAMED DEPUTYDECIDES AT ONCEUNREACHABLEONE MODEL ACROSS THE GROUPTHE SAME ROLES, NAMES AND LANGUAGE AT EVERY SITEROLE HOLDER CANNOT BE REACHEDAUTHORITY PASSES TO A NAMED DEPUTY — NO DECISION WAITS
02

4 STAGES

  1. One model

    A single structure across every division, so a crisis cell in one country is legible to a board in another.

  2. Fixed roles

    Roles are held by function, not by seniority or by whoever is present. No volunteers.

  3. Rotation design

    Twenty-four hour operation planned from the first hour, because exhaustion is the second failure.

  4. Common language

    Shared terms and reporting formats that interoperate with the state and with mutual aid partners.

WHAT YOU LEAVE WITH

  1. 01Group incident command manual
  2. 02Role cards and rotation rosters per layer
  3. 03Common reporting formats and log discipline
  4. 04Interoperability annex for state and mutual aid

THE QUESTION WE OPEN WITH

ANSWER IT OUT LOUD
NEXTPost-event recoverySequenced restart, workforce return, claims and forensic record.

Written, tested,and left readyto execute

Not advice and not a document. The plan is installed, rehearsed on shift, and handed over in a state it can be run in.

DISCUSS YOUR SITUATION→