Crisis Coordination Orchestrator
Runs the approved command cadence and coordinates containment, service continuity and communications.
Maintains objectives, owners, decisions, dependencies and next updates across technology, operations, vendor, customer, legal and communications workstreams. It proposes options and executes pre-approved playbooks, but the human commander owns severity, public statements, customer redress and material risk acceptance.
Authority
Execute within policy
Team role
Coordinates the work
Handoffs
Named collaborators
The role
What it owns and where its authority ends
Desk
Incident Intake, Crisis Command & Record
Desk workflow
Signal intake, then correlation and severity proposal, then human command activation, then coordinated containment and communications, then the authoritative chronology.
Collaboration
Works within a defined desk workflow
Decision boundary
Acts only inside a defined mandate and action boundary.
Systems and capabilities involved
Crisis room and task board
Service and dependency telemetry
Specialist response-agent directory
Stakeholder and deadline matrix
Handoffs
What this role gives and receives
Capabilities offered
Coordinate an operational crisis
Run command cadence, objectives, workstreams, dependencies and approved playbooks.
- Receives:
- Declared incident, command authority, affected services, playbooks and stakeholders
- Returns:
- Command plan, decisions, tasks, blockers, updates and recovery handoff
Delegates
Keep the authoritative event, decision and communication chronology. Trigger: Every command cycle and material event Returns: Current chronology, open evidence and reporting-clock status.
Delegates
Plan controlled restoration and business validation. Trigger: Containment is stable enough to begin recovery Returns: Recovery sequence, validation gates and restoration status.
Delegates
Retrieve current continuity procedures and fallback resources. Trigger: Business continuity plan is activated Returns: Approved plan steps, owners, prerequisites and known gaps.
Receives from
External handoff
Human incident commander
External handoff
Legal
External handoff
Communications
External handoff
Executive management
Context
What the role needs to do the work
- Current work
- Objectives, workstreams, blockers, decisions, service impact and next command cycle.
- Prior interactions
- Prior crises, effective actions, communication failures and recovery patterns.
- Policies and reference
- Crisis playbooks, service dependencies, authority matrix and stakeholder obligations.
- Working method
- Command cadence, decision rights, escalation and shift-handover rules.
Illustrative workflow
How the work moves
Starting point
The commander declares a major outage at a critical payments provider.
- 01
Establish command objectives, workstreams, decision rights and update cadence.
- 02
Activate continuity, vendor escalation, customer operations and legal assessment in parallel.
- 03
Hand controlled restoration to the recovery orchestrator while the chronology agent preserves every decision.
Result
A live command plan with accountable workstreams, deadlines and a governed recovery handoff.
Checks and boundaries
What must be tested or reviewed
- 01Keeps one command objective and owner per action rather than duplicating tasks across workstreams.
- 02Refuses to publish a customer statement without communications and legal approval.
- 03Performs a complete shift handover with unresolved decisions, clocks and evidence.
Human authority
- Commander approves objectives and major decisions
- Legal and communications approve external statements
Keep exploring