Why “just checking in” emails fail during incidents

During an outage, readers scan for time boundaries, blast radius, and the next decision point. A vague check-in consumes attention without reducing uncertainty. Replace pleasantries with a timestamped fact line and a single ask.

Use a two-line pattern: (1) what changed since the last update, (2) what you need from the reader, with a default if they cannot respond. This mirrors the structure we teach in Technical Email & Status Updates.

Close with where artifacts live: ticket ID, log slice, or dashboard link. If you lack a link, say so explicitly. Honest gaps read as more professional than implied certainty.