Retext

Apology email for a mistake at work: templates

A work apology that rebuilds trust does three things quickly: says what went wrong in plain words, says what you've done to fix it, and says what you'll do differently. It doesn't over-explain or spread the blame. This template follows that order and keeps the apology itself to one sentence, because the fix is what the reader cares about.

Template;em-sorry
Hi Name, I made a mistake on What went wrong, and I'm sorry for the trouble it caused. I've already What you've done. To stop it happening again, I'm What changes. If this caused knock-on problems on your side, let me know and I'll help sort them out. [Your name]
Then type ;em-sorry in any app.

Variations

The same message for a different channel or tone. Copy the one that fits.

Gives your manager what they need to explain it upwards.

To your manager
Hi Name, Heads-up before you hear it elsewhere: What went wrong. That was my error. Impact: Impact. Fixed: What you've done. Next: What changes. Happy to talk it through whenever suits you. [Your name]

More formal, and focused on what the client needs to do, if anything.

To a client
Dear Name, I'm writing to apologise for What went wrong. This was our error. We have What you've done, and you don't need to take any action. Going forward, What changes. Thank you for your patience. Please contact me directly if you have any questions. Kind regards, [Your name]

When to use it

  • A mistake that affected someone else's work: a wrong figure, a missed send, a broken link.
  • Telling your manager about an error before they find out another way.
  • Correcting an error with a client in writing.

What to avoid

  • Don't over-apologise. One clear sorry reads as more sincere than three.
  • Don't blame tools or other people, even if they played a part. Explain later if asked.
  • Don't send it before you know what the fix is, unless the delay would make things worse.

The fields in this template

Retext fills these in when the snippet expands. In plain text they become [brackets] to replace by hand.

Name{fill:Name}
The person you're apologising to.
What went wrong{fill:What went wrong}
The mistake in plain words, e.g. "the figures in Tuesday's report".
What you've done{fill:What you've done}
The fix, e.g. "sent a corrected version to everyone on the list".
What changes{fill:What changes}
The process change, e.g. "adding a second check before reports go out".
Impact{fill:Impact}
Who or what was affected, in one line.
More about dynamic fields

Tips

  • •The manager variant's Impact, Fixed and Next lines are easy to forward, which is what managers usually need to do with it.
  • •For a customer-facing apology about an order or service, the customer-support pack has a template built for that.
  • •If you sent something to the wrong person in Outlook, pair this with the recalled-email follow-up.

Works in Gmail, Outlook and every other app

Retext types the snippet wherever your cursor is. To use a different version in one app, give it the same trigger and limit it to that app with per-app snippets. They go by app, not website, so every tab in your browser counts as one app.

Questions

How do you apologise professionally in an email?

Name the mistake, apologise once, explain the fix and what will change. Keep explanations short and skip the blame.

Should I apologise by email or in person?

For something serious, talk first and follow up in writing. For a small error, a clear email is fine and gives the other person a record.

Type ;em-sorry, get the whole reply

Retext expands your snippets in every Mac app and fills in names, dates and order numbers for you.

Free to start. No account required on the Mac.