Leadership Crisis Communication Email
Turn confirmed incident details into a calm, transparent leadership email with clear ownership and recovery steps.
Customise & copy
Add the context you have. The prompt updates as you work.
Describe what happened, when it began, and the confirmed operational impact.
Name the groups or teams affected and describe the relevant impact.
State the approved or proposed response and who owns execution.
Provide confirmed times, milestones, or the next update commitment.
Provide the person’s name, role, and contact method exactly as they should appear.
Live prompt
5 fieldsCompose one calm, transparent crisis email for leadership communication using only the information provided below. Do not invent facts, causes, impacts, commitments, contact details, or recovery milestones. Avoid defensive language, blame, hype, and unnecessary jargon. Take clear ownership without assigning blame. Use this exact plain-text structure: Subject: [concise subject line] Hello [appropriate audience], Situation and impact: [Direct explanation of what happened and who is affected.] Our response: [State ownership and summarize the proposed solution.] Next steps and recovery timeline: [List the immediate actions and the expected recovery timeline.] Contact: [Name and contact details of the primary contact person.] Regards, [Leadership team or organization] Inputs: Situation description: {{situation_description}} Affected stakeholders: {{affected_stakeholders}} Proposed solution: {{proposed_solution}} Recovery timeline: {{recovery_timeline}} Primary contact person: {{primary_contact_person}} Return only the completed email, with no analysis, notes, placeholders, or markdown formatting.
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-10
{
"proposed_solution": "Engineering will roll back the configuration, validate authentication across all EU services, and add an approval check for similar production changes. The incident commander owns coordination.",
"recovery_timeline": "Rollback begins at 10:00 UTC, service stabilization is expected by 10:30 UTC, and the next stakeholder update will be sent at 11:00 UTC.",
"affected_stakeholders": "EU customers, customer support, sales operations, and the regional leadership team. Support queues are increasing and some customer workflows are delayed.",
"situation_description": "A database configuration change caused intermittent login failures for customers in the EU region beginning at 09:20 UTC. Authentication requests are timing out, while other regions remain operational.",
"primary_contact_person": "Maya Chen, Incident Commander, maya.chen@example.com"
}A small ritual that works
How to use it
- 01Describe what happened, when it began, and the confirmed operational impact.
- 02Name affected stakeholders and describe the relevant impact.
- 03Provide the proposed solution, owner, recovery timeline, and next update commitment.
- 04Enter the primary contact's name, role, and contact method exactly as they should appear.
Why it works
The prompt gives the email a fixed leadership-communication structure: situation and impact, response, recovery timeline, contact, and sign-off. Its instructions to use only supplied information, avoid blame and hype, and take ownership establish clear boundaries for tone and content. The input fields map directly to the sections of the email, while the required plain-text format and instruction to return only the completed email reduce extra commentary and formatting drift.
Where it fails
The prompt cannot resolve uncertainty that is already present in the supplied information. If the situation, affected stakeholders, proposed response, timeline, or contact details are incomplete or not confirmed, the structure provides no basis for filling those gaps without violating its instruction not to invent facts. It is also limited to crisis updates that fit the specified leadership-email format.
Customisation tips
Adjust the opening audience, sign-off, and section labels if the communication is intended for customers, employees, regulators, or another group. Add an input for incident severity, data-sensitivity status, or update cadence when those details must be communicated consistently. If the organization uses a required terminology guide, include those terms in the instructions. Keep each added input tied to a specific section so the prompt remains easy to complete and predictable to format.
Watch-outs
- The recovery timeline field should contain confirmed times, milestones, or update commitments rather than tentative language.
- The contact field is designed for exact presentation, so the supplied name, role, and contact method should already be checked for accuracy.
- The prompt separates the proposed solution from the recovery timeline; combining them may make ownership, actions, and timing less clear.
- The instruction to avoid invented information means missing operational details cannot be safely supplied by inference.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Want to make AI useful across your team? Explore Atul's training.