ThinkWithPrompt by SynotticThinkWithPrompt

Write a work apology email that owns the mistake without over-explaining

Drafts a professional apology that takes responsibility, states the fix, and rebuilds trust without groveling or excuses.

Email & Workplace CommunicationRTFStandardEmailLegalWriteExplain & Teach

The prompt

Help me write an apology email for a mistake at work. What happened: [THE MISTAKE, plainly] Who was affected and how: [PEOPLE, CUSTOMERS, OR TEAMS; THE IMPACT] My share of responsibility: [WHAT WAS MINE vs. OUTSIDE MY CONTROL] What I've already done to fix it: [ACTIONS] What I'll do to stop it happening again: [CHANGES] Recipient: [WHO, and the relationship] The email should follow this order: 1. Own it - a clear apology in the first sentence, using "I" (or "we" if it was genuinely a team failure). 2. Name the impact on them, briefly and specifically. 3. The fix - what's been done and what's still in progress, with dates. 4. Prevention - one or two concrete changes. 5. Close - an offer to talk, without asking for forgiveness. Rules: - Under 150 words. - No excuses, blame-shifting, or "sorry if you were upset". Context only if it helps them understand the fix, in one sentence at most. - Don't over-apologize or repeat "sorry" more than twice. - Don't promise things I haven't listed. Return the email, a 2-line Teams or Slack version, and a note on anything in my notes that reads as defensive. If the mistake has legal, contractual, or regulatory consequences, tell me to check the wording with my manager or legal before sending.

Highlighted [brackets] are blanks to replace with your own details.

Fill in the blanks and use this promptMore Email & Workplace Communication prompts

What to fill in

  • THE MISTAKE, plainly
  • PEOPLE, CUSTOMERS, OR TEAMS; THE IMPACT
  • WHAT WAS MINE vs. OUTSIDE MY CONTROL
  • ACTIONS
  • CHANGES
  • WHO, and the relationship

How this prompt is built

This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.

Related prompts

Find more prompts like this