Most incident write-ups are written for engineers: a timeline, a root cause, a list of tickets. The person who actually reads the email after a client's checkout was down for 40 minutes is usually not an engineer. It's an operations manager who has to explain it to their boss before lunch.
This post is the template I'd use for that email, plus the part that usually goes wrong: the second incident, weeks later, when nobody remembers what the client asked for the first time. (Disclosure: I build Maildoer, an email-based assistant, and I'll mention where it fits once near the end. The template works without it.)
The scenario below is a labelled hypothetical, not a customer story.
Say you're the on-call developer at a small agency
You maintain an online shop for a client in Germany. On a Tuesday evening, payments fail for a while.…