How do I write an apology that does not sound defensive?

Apologise before you explain, and use active voice. "We sent the wrong invoice" lands as accountability; "an error occurred in the invoicing process" lands as evasion, even when the facts are identical.

Should an apology email explain what went wrong?

Briefly, and after the apology. An explanation offered first reads as an excuse. One sentence of cause followed by one concrete remedy is usually the right proportion.

Which AI model is best for writing an apology email?

All of them handle this; what changes is the packaging. This page shows the same prompt written for Claude, ChatGPT, Gemini. Claude follows XML-delimited structure most reliably, ChatGPT works best with markdown headings, and Gemini prefers the task stated before the material. The content of the prompt is identical in each.

Can I change this prompt for my own situation?

Yes, and you should. Replace the placeholders with your own details, then open it in the builder to add context specific to you. The builder scores what you supply and tells you exactly which missing piece would improve it most.

Why does this prompt include rules I did not ask for?

Because writing tasks carry requirements that experienced practitioners apply automatically and rarely write down. The compiler adds them so the output does not fail on something obvious. Every added rule is listed on the how it works page.

AI prompt for writing an apology email

This is a ready-made AI prompt for writing an apology email, written for Claude and free to copy. Apologies fail through the passive voice and the conditional. "I am sorry if this caused inconvenience" is not an apology, and readers recognise the construction immediately — it makes the situation worse than saying nothing. The prompt below handles that: it is compiled as a writing task, so it carries the structure and the constraints that kind of work needs.

The prompt

Written for Claude. Compiled as a writing task — producing original prose: articles, essays, stories, letters, and long-form copy.

<role>
You are a senior writer and editor with a decade of experience in this exact form.
</role>

<context>
What went wrong: {{what_happened}}. Why it happened: {{cause}}. What I am doing about it: {{remedy}}. What I can commit to: {{commitment}}.
</context>

<task>
Write an apology email to {{recipient}} about {{what_happened}}.
</task>

<constraints>
- Apologise for the impact in the first sentence. Do not explain first.
- Say what happened plainly. Do not use passive voice to obscure responsibility.
- State one concrete thing being done and by when.
- Do not over-apologise. One apology, then action.
- Avoid mistakes were made.
- Avoid i am sorry if.
- Avoid unfortunately.
- Avoid as you know.
- Write in plain, direct prose. Do not restate the prompt, and do not open with a throat-clearing sentence.
- Vary sentence length. Do not begin consecutive sentences with the same word or structure.
- Do not invent facts, statistics, quotations, or attributed opinions.
</constraints>

<output_format>
Respond in Markdown. Use descriptive headings, and keep paragraphs to three sentences or fewer. Length: 150 words. Treat this as a requirement, not a suggestion.
</output_format>

Now, write an apology email to {{recipient}} about {{what_happened}}.

Open this in the prompt builder to add your own context and see what would improve it most.

What makes writing an apology email hard to prompt for

Apologies fail through the passive voice and the conditional. "I am sorry if this caused inconvenience" is not an apology, and readers recognise the construction immediately — it makes the situation worse than saying nothing.

Why this prompt works

Background comes before the instruction: The model reads the situation before it learns what to do with it, which stops the instruction being diluted by everything that follows. The task is then restated as the final line, where models weight it most heavily.
Rules a writing task assumes but nobody writes down: Write in plain, direct prose. Do not restate the prompt, and do not open with a throat-clearing sentence. Vary sentence length. Do not begin consecutive sentences with the same word or structure. These are added automatically because leaving them implicit is the most common reason this kind of output disappoints.

What to replace

Placeholder	What to put there
{{what_happened}}	Your what happened.
{{cause}}	Your cause.
{{remedy}}	Your remedy.
{{commitment}}	Your commitment.
{{recipient}}	Your recipient.

Check the output before you use it

Check the first sentence apologises rather than explains.
Search for passive constructions that hide who did what.
Confirm there is one concrete commitment with a date.

The same prompt for other models

Identical content, packaged the way each model reads most reliably.

ChatGPT

## Role

You are a senior writer and editor with a decade of experience in this exact form.

## Context

What went wrong: {{what_happened}}. Why it happened: {{cause}}. What I am doing about it: {{remedy}}. What I can commit to: {{commitment}}.

## Task

Write an apology email to {{recipient}} about {{what_happened}}.

## Constraints

- Apologise for the impact in the first sentence. Do not explain first.
- Say what happened plainly. Do not use passive voice to obscure responsibility.
- State one concrete thing being done and by when.
- Do not over-apologise. One apology, then action.
- Avoid mistakes were made.
- Avoid i am sorry if.
- Avoid unfortunately.
- Avoid as you know.
- Write in plain, direct prose. Do not restate the prompt, and do not open with a throat-clearing sentence.
- Vary sentence length. Do not begin consecutive sentences with the same word or structure.
- Do not invent facts, statistics, quotations, or attributed opinions.

## Output format

Respond in Markdown. Use descriptive headings, and keep paragraphs to three sentences or fewer. Length: 150 words. Treat this as a requirement, not a suggestion.

Now, write an apology email to {{recipient}} about {{what_happened}}.

Gemini

**Task**

Write an apology email to {{recipient}} about {{what_happened}}.

**Role**

You are a senior writer and editor with a decade of experience in this exact form.

**Context**

What went wrong: {{what_happened}}. Why it happened: {{cause}}. What I am doing about it: {{remedy}}. What I can commit to: {{commitment}}.

**Constraints**

- Apologise for the impact in the first sentence. Do not explain first.
- Say what happened plainly. Do not use passive voice to obscure responsibility.
- State one concrete thing being done and by when.
- Do not over-apologise. One apology, then action.
- Avoid mistakes were made.
- Avoid i am sorry if.
- Avoid unfortunately.
- Avoid as you know.
- Write in plain, direct prose. Do not restate the prompt, and do not open with a throat-clearing sentence.
- Vary sentence length. Do not begin consecutive sentences with the same word or structure.
- Do not invent facts, statistics, quotations, or attributed opinions.

**Output format**

Respond in Markdown. Use descriptive headings, and keep paragraphs to three sentences or fewer. Length: 150 words. Treat this as a requirement, not a suggestion.

Now, write an apology email to {{recipient}} about {{what_happened}}.

Common questions

How do I write an apology that does not sound defensive?: Apologise before you explain, and use active voice. "We sent the wrong invoice" lands as accountability; "an error occurred in the invoicing process" lands as evasion, even when the facts are identical.
Should an apology email explain what went wrong?: Briefly, and after the apology. An explanation offered first reads as an excuse. One sentence of cause followed by one concrete remedy is usually the right proportion.
Which AI model is best for writing an apology email?: All of them handle this; what changes is the packaging. This page shows the same prompt written for Claude, ChatGPT, Gemini. Claude follows XML-delimited structure most reliably, ChatGPT works best with markdown headings, and Gemini prefers the task stated before the material. The content of the prompt is identical in each.
Can I change this prompt for my own situation?: Yes, and you should. Replace the placeholders with your own details, then open it in the builder to add context specific to you. The builder scores what you supply and tells you exactly which missing piece would improve it most.
Why does this prompt include rules I did not ask for?: Because writing tasks carry requirements that experienced practitioners apply automatically and rarely write down. The compiler adds them so the output does not fail on something obvious. Every added rule is listed on the how it works page.

Browse all ready-made prompts, the full prompt library, or read the guides.