Sincere Apology Email Draft
Write a clear, accountable apology email with a concrete solution and a trust-building close.
Customise & copy
Add the context you have. The prompt updates as you work.
Describe the mistake, delay, or missed commitment and what happened.
Choose how you know the recipient.
State what you are offering to fix the situation or what should happen next.
Select the communication style, not the emotional intensity.
Include deadlines, points that must be mentioned, or anything the email should avoid.
Briefly explain the context if it helps, without turning it into an excuse.
Live prompt
6 fieldsDraft one sincere apology email using the information below. Take clear responsibility without excuses, blame, defensiveness, hype, or excessive politeness. Briefly explain the impact on the recipient, offer the stated solution or next step, and close in a way that supports rebuilding trust. Do not invent facts or request clarification; make reasonable neutral wording choices when details are limited. Match the selected tone and relationship. Situation details: {{situation_details}} Recipient relationship: Client Desired solution or next step: {{desired_solution}} Tone: Direct and respectful Constraints or required points: {{constraints}} Brief background: {{brief_background}} Return only this fixed format, with no commentary: Subject: [clear apology subject line] [complete email draft]
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-10
{
"tone": "Direct and respectful",
"constraints": "Keep it under 150 words and do not imply that the client caused the delay.",
"brief_background": "I underestimated the time needed to validate data from three reporting sources.",
"desired_solution": "I will send the completed report by 3 p.m. tomorrow, include a revised timeline, and schedule a 20-minute review call.",
"situation_details": "I missed the agreed delivery date for the campaign performance report by three days.",
"recipient_relationship": "Client"
}A small ritual that works
How to use it
- 01Describe what went wrong and briefly provide relevant background.
- 02Choose the recipient relationship and email tone.
- 03State the desired solution or next step and add any constraints.
- 04Use the fixed-format email draft with one light edit before sending.
Why it works
The prompt gives the writer a clear communication goal: accept responsibility, acknowledge the recipient’s impact, state a solution or next step, and support trust repair. Its fields separate the situation, relationship, proposed resolution, tone, constraints, and background, which makes the drafting brief easy to complete and keeps important context distinct. The instructions also define boundaries against excuses, blame, defensiveness, invented facts, and unnecessary clarification. A fixed subject-and-email format makes the requested deliverable unambiguous.
Where it fails
The prompt is less suitable when the situation requires careful legal, regulatory, HR, safety, or crisis communication, because it directs the writer to make reasonable neutral wording choices without requesting clarification. Its limited relationship menu may also be too narrow for relationships such as vendors, partners, customers, or public audiences. The instruction to return only a complete email leaves no space for explaining assumptions or flagging unresolved factual gaps.
Customisation tips
Replace or expand the relationship options to match the intended audience. Add fields for the recipient’s name, sender’s name, deadline, delivery method, required subject language, and any approved facts that must be preserved. If the email may involve legal, employment, financial, health, or safety issues, add explicit boundaries for prohibited admissions and a requirement to use approved language. Adjust the tone choices to reflect the organization’s communication style, and make the word limit a separate field if brevity matters.
Watch-outs
- The situation details and desired solution should contain enough factual information for a specific apology; otherwise, the instruction to avoid clarification encourages general wording.
- The background field is intended to provide context without becoming an excuse, so explanations should remain relevant to responsibility and next steps.
- Constraints can override the natural length or structure of the email, so deadlines, required points, and exclusions should be written precisely.
- The selected tone describes communication style rather than emotional intensity; a warmer style does not remove the requirement to take clear responsibility.
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.