Advanced 6 topic areas 24+ exercises

Incident Commander

Incident Commanders lead the response to production outages and security incidents. They coordinate engineers, manage multiple communication channels simultaneously, and deliver structured updates to stakeholders ranging from on-call engineers to C-suite executives. Their English must be precise under pressure: no ambiguity, clear ownership, specific timelines. This path builds the language of command, coordination, and post-incident communication.

Start first exercise → Browse all exercises

Topics covered

Incident command structure
Severity classification
Stakeholder updates
Bridge call communication
Post-mortem facilitation
Handoff briefings

Vocabulary spotlight

4 terms every Incident Commander should know in English:

declare v.

To officially announce an incident severity level or resolution, initiating or completing the formal response process

"I'm declaring this a SEV-1 — activate the full on-call rotation and open the bridge."

mitigated adj.

The incident impact has been reduced or stopped but the root cause has not been fully resolved — a temporary fix is in place

"We've mitigated by routing traffic to the secondary datacenter, but root cause investigation continues."

standing down v. phrase

The process of formally releasing responders and closing the active incident command after resolution is confirmed

"We've been green for 30 minutes — I'm standing down the incident team."

SBAR (Situation, Background, Assessment, Recommendation) n.

A structured communication framework for concisely conveying critical information: what is happening, context, your analysis, and what you recommend

"Use SBAR for the CEO update: current impact, what caused it, our assessment, and the recommended action."

Open full glossary →

📚 Vocabulary Reference

Key terms organised by category for Incident Commanders: