A crisis team should be designed around decisions, not job titles. The structure must keep strategic direction separate from tactical coordination and operational execution while ensuring information moves quickly between all three levels.
Three-level command model
| Level | Primary purpose | Typical decisions |
|---|---|---|
| Strategic | Protect organizational objectives, stakeholders and risk appetite | Major priorities, external commitments, exceptional expenditure, public position, prolonged disruption choices |
| Tactical | Coordinate the response across functions and translate strategy into work | Resource allocation, recovery sequencing, cross-functional conflicts, SitRep priorities and escalation |
| Operational | Execute response and recovery activities | Task execution, technical workarounds, local safety controls, restoration and status reporting |
Design roles from decisions
List the decisions that may be required during the first hour, first operational period and prolonged response. Assign one accountable role to each decision class and define the threshold at which authority moves upward. A team overloaded with observers but unclear about who can approve a shutdown, customer commitment or recovery exception will perform poorly regardless of the organization chart.
Core strategic roles
The exact titles vary, but the strategic team normally needs a crisis leader, business/operations representation, communications, people, legal or compliance, technology where material, and a coordination or secretariat role. Add specialist advisers only when the scenario requires them. Advisers provide expertise; they should not blur accountability for the final decision.
Deputies and continuity of command
Every critical role needs a named deputy or succession rule. Define how authority transfers, how the incoming role receives the current SitRep and decision log, and whether any decisions require reconfirmation. This matters in prolonged incidents where fatigue and shift changes can otherwise create an invisible command gap.
Information flow
Operational teams should report verified facts, constraints and forecast changes to the tactical layer. Tactical coordination should consolidate this into decision-ready information for the strategic team. Strategic decisions then flow back as priorities, constraints and authorities. The SitRep and decision log are control mechanisms for this flow, not substitutes for leadership.
Span of control and meeting rhythm
A crisis leader should not receive status independently from every recovery team. Group operational streams under tactical owners and set an operating rhythm: information cut-off, tactical consolidation, strategic meeting, decision publication and action follow-up. Urgent exceptions must still have an immediate escalation path outside the normal rhythm.
Worked design example
During a regional technology outage, the strategic team decides which customer services receive priority and approves external commitments. A tactical recovery coordinator sequences identity, network, application and business validation work. Technical teams execute restoration and report evidence. Communications drafts messages but cannot publish material commitments until the authorized strategic role approves them. This separation prevents technical recovery choices from silently becoming business-risk decisions.
Structure acceptance checks
- Each material crisis decision has one accountable role.
- Strategic, tactical and operational responsibilities are distinguishable.
- Deputies and shift handover are defined for critical roles.
- Specialist advisers do not create ambiguous decision authority.
- Escalation thresholds are based on impact or decision type.
- Information flows through a controlled SitRep/decision-log rhythm.
- An exercise demonstrates that the structure works under time pressure.
Related resources
Use the crisis-team RACI resource to allocate detailed responsibilities after the command structure is agreed. Use the SitRep and decision-log resources to operate the information and governance cycle during an incident.
Decision-rights stress test
A command structure is credible only when people can determine who decides under pressure. Test it against decisions that cross normal departmental boundaries: suspending a critical service, accepting a temporary safety exposure, invoking an alternate site, making a public commitment, prioritizing scarce recovery capacity, or operating beyond an approved tolerance. For each decision, record the accountable role, required advisers, evidence expected, financial or legal limits, and the point at which authority escalates. Avoid committees in which everyone participates but nobody owns the decision.
Delegation must survive absence and fatigue. Deputies need the same access to dashboards, decision logs, contact data and approval channels as the primary role. A deputy arrangement that exists only in an organization chart is not resilience. Exercise unplanned substitution during a simulation and verify that decisions continue without informal workarounds.
Span of control and escalation design
Do not route every operational issue to the strategic team. Tactical leadership should aggregate technical and business workstreams, resolve conflicts within delegated limits, and escalate only decisions that exceed tolerance or authority. Define triggers using consequences rather than vague labels: projected breach of an approved RTO, inability to protect a life-safety control, exhaustion of minimum staffing, material regulatory notification, or a customer commitment requiring executive acceptance.
During a prolonged event, establish shift lengths, overlap periods and handover evidence. The incoming command team should receive current objectives, unresolved decisions, assumptions, rejected options, external commitments, resource constraints and the next decision deadlines. This prevents a shift change from resetting the crisis picture.
Evidence that the structure works
Measure more than attendance. Useful evidence includes time from trigger to activation, time to appoint an incident lead, percentage of material decisions with an accountable owner, overdue escalations, decisions reversed because evidence was missing, and actions lost at handover. Review these measures after exercises and real events. A mature structure should make authority clearer and decisions faster without bypassing risk, safety, legal or regulatory controls.
Acceptance test for command design
Run a timed scenario in which information is incomplete, two priorities compete for the same resource, and one decision crosses an executive or regulatory threshold. The structure passes only when participants can identify who owns the decision, what evidence is required, who must be consulted, the deadline for escalation and where the decision is recorded. Capture delays caused by ambiguous authority and update the role cards, delegation rules and handover checklist before closing the exercise action.
Related BCM.Center resources: Crisis Management Team Roles and RACI · Situation Report (SitRep) Governance: Reporting Cycle, Verification and Decision Use.