You fixed it. They’re still worried.
The incident is resolved. Systems are back up. Your team did great work.
But your client’s CEO is still anxious. They don’t understand what happened. They don’t know if it will happen again. Technical resolution without clear communication leaves a trust gap that competitors exploit.
The scenario:
You need to write a post-incident client update that explains what happened and what’s changing.
The prompt:
You’re writing a post-incident executive summary for a client.
Context: [paste the incident timeline, root cause, and remediation steps]
Write a one-page summary that:
Opens with current status (confirmed resolved, monitoring in place)
Explains what happened in plain language (no jargon, no acronyms)
States root cause honestly without blame
Lists 3 specific changes being implemented to prevent recurrence
Includes a timeline for each change
Offers a follow-up briefing in 2 weeks
Tone: Calm, competent, transparent. The CEO should feel safer after reading this, not more worried.