Incident Commander

An incident commander (IC) is the single person temporarily in charge of managing a significant incident. The IC does not usually fix the problem personally. Instead they coordinate people, keep a timeline, make priority calls and make sure communication happens.

Why it matters

Without a clear lead, incident channels fill with parallel theories, duplicated work and unanswered questions from stakeholders. Having one coordinator reduces confusion and speeds recovery. The role comes from emergency management practice and is common in large engineering organizations. Smaller teams often combine roles, but naming an IC is still helpful.

Example

During a database outage the roles might be:

Incident commander: Asha (decides, tracks timeline)
Operations lead:    Ravi (runs fixes on the database)
Communications:     Meera (updates status page every 30 min)
Scribe:             Tom (records actions and timestamps)

Asha can hand command to another person at a defined handover point, saying so explicitly in the channel.

Common mistakes

• The most senior engineer takes command and then dives into debugging, leaving nobody coordinating.
• Never handing over during long incidents, which causes exhaustion.
• Unclear authority, so people debate whether to roll back.
• No communications owner, leaving customers with silence.

Related

• Incident
• Severity levels
• Postmortem
• Runbook

This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.