The IC Decision Authority

What can the incident commander decide unilaterally? The boundaries.

Can decide

The IC owns reversible technical decisions and the internal comms cadence. Speed matters during incidents; second-guessing the IC during the response burns MTTR. The boundary is reversibility: anything that can be undone if it does not help is in scope.

• Rollback. IC's authority to roll back the suspected change. No approval chain needed; the rollback is itself reversible.
• Failover. IC's authority to flip to standby region or replica. Reversible if it does not help.
• Any reversible action. Undoable steps stay in IC scope. Keeps the response moving without committee.
• Internal comms cadence and content. IC sets the tempo and content of internal status updates. No committee for the war-room cadence.

Must escalate

Some decisions exceed IC authority by design. Customer-facing comms with legal weight, multi-team scope changes, spending past a documented threshold. The escalation list is short and explicit so the IC knows exactly what stays in scope.

• Customer-facing comms. Public statements need legal or marketing review. Separate authority chain by design.
• Multi-team or multi-service scope. Decisions with cross-boundary effects need manager engagement. Coordinate before committing.
• Spending past threshold. Documented dollar limit per org. Above it, finance gets engaged regardless of urgency.
• Documented escalation list. Visible "above my line" list per incident. Keeps the IC focused on what they can decide.

Trust the IC

Empowering the IC is the difference between fast and slow response. Postmortem reviews the decisions after the incident; in the moment, the IC has authority. Trust comes from training and named authority, not from agreeing with every call.

• Empower the IC. Named authority per rotation. Second-guessing during the incident slows response.
• Postmortem reviews decisions. After-action review is where decisions get scrutinised. In the moment, IC decides; later, the team learns.
• IC training pipeline. Per-rotation training and shadow shifts. Trust by competence, not by faith.
• Explicit IC declaration. "I am IC" message visible in the incident channel. Catches dual-IC confusion before it costs minutes.