Write an apology that names the mistake, its impact, and a practical next step. Keep promises within what you can actually do.
How to use
Sign in and explain what happened and who was affected. Add the action you can take in context. Review the draft for excuses, blame, and unrealistic commitments.
Example
A report arrived one day late. Apologize for delaying the review and offer to send the missing figures by 3 PM.
FAQ
What makes an apology useful?
Acknowledge the specific impact and state a concrete repair. Remove promises you cannot keep.
Related tools
A practical task
Describe the impact from the other person's perspective. If a missed appointment cost them a trip, acknowledge the wasted time before explaining your reason. Offer a practical correction rather than asking the recipient to reassure you.
Another useful question
Should I include an explanation?
Include a short factual explanation when it helps, but do not use it to cancel responsibility. Keep the apology and the repair clear enough to stand without a long defense.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Context and audience | The same fact needs different explanation for a specialist and a first time reader. State the audience, purpose, and terms they already know. Relevant context guides wording more effectively than broad requests to make a text impressive. |
| Tone and commitments | Tone changes the way a message sounds, not the obligations it contains. A friendly version must not invent permission, and a formal version must not invent a promise. Compare commitments as well as style. |
| Supplied facts | A writing request needs the facts the finished draft must preserve. Names, dates, quantities, and policies should come from your source. Missing information is a question to resolve rather than a blank to fill with a plausible invention. |
| A clear next action | A message should make the next action easy to identify: approve a choice, send a file, confirm a time, or answer a question. State the action directly and keep supporting background separate from the request. |
| The recipient's knowledge | A recipient cannot act on references they cannot identify. Replace an unexplained “that file” with a real document name and include the needed context. Omit background they already know when it does not help the decision. |
| Real deadlines | Give an exact date or time only when it is known and needed. Relative phrases such as next Friday can be ambiguous across timezones or a delayed reading. Keep the deadline consistent with the action the message requests. |
| Editorial review | Review facts, names, omissions, and implications before approving a draft. A smooth sentence can still change a condition or attribute a statement to the wrong person. Compare meaning with the source instead of judging fluency alone. |