Mid-Incident Stakeholder Update Template

30 minutes in: what's the update look like? The template.

Structure

The structure has four sections in fixed order. Stakeholders learn the shape and skim consistently; the predictable form lets readers find what they need without re-reading.

• Summary. One-sentence current state per update; "what is happening, right now"; opens the message.
• Progress. 2-3 bullets per update on what has been done; concrete actions, not narrative.
• Next. 1-2 bullets per update on what is coming; the IC’s stated next moves.
• ETA. Best-estimate resolution time per update; honest, even when uncertain; "we don’t know yet" is acceptable.

Avoid

The failure modes are explicit. Long prose loses the reader; false precision damages trust; blame language poisons the postmortem before it begins.

• Long explanation. No-narrative rule per update; stakeholders skim; bullets work; paragraphs do not.
• False precision on ETA. Rounded estimate per update; "in the next hour" beats "47 minutes"; precision implies certainty.
• No-blame language. System-not-person framing per update; supports calm comms and protects the postmortem.
• No promises. "Current best estimate" caveat per update; catches over-commitment that damages trust later.

Rhythm

Same template every 30 minutes. Predictable cadence is itself a calming signal; stakeholders learn to expect updates and stop asking for them.

• Same template every 30 minutes. Consistent shape per incident; stakeholders know what to expect.
• Predictable, expected, calming. The rhythm itself is comfort; the cadence signals control even when content does not.
• Named author. IC or named comms lead per update; supports continuity across long incidents and shift changes.
• Visible posting time. Timestamp per update; missed update windows are detectable, not silent.