Skip to main content
Formalong
Apology & Diplomacy

How to write a formal apology email

A good apology email does three things quickly: it names what went wrong, it accepts responsibility without a long defence, and it says what happens next. This guide walks through when an email is the right channel, the structure and the reasoning behind each part, wording that reads sincere rather than defensive, and complete examples for a manager, a client, a colleague, and a general workplace slip.

When an apology email is the right move

Send one when the mistake affected someone's work and a record of the correction is useful: a missed deadline, a wrong invoice, a bad data pull, a meeting you did not attend, a reply that came out sharper than you meant. Speak first, then confirm by email when the matter is sensitive, emotional, or involves several people. A written-only apology in those cases can read as avoidance. Do not send one at all when nothing actually went wrong. Apologising for taking a normal amount of time, for asking a reasonable question, or for someone else's scheduling problem trains people to read your apologies as filler. Send it as soon as you know, even if the fix is not finished. "Here is what happened, here is when the correction lands" is a complete apology. Waiting until everything is resolved usually means the other person has already had to chase you.

The structure, and why each part is there

1. Subject line, so the email is findable later and the reader knows the topic before opening it: "Apology for the delayed report". 2. Greeting appropriate to the relationship: "Dear Ms Rahman," or "Dear Bapak Andi,". 3. The apology itself, in the first or second sentence, because a reader who has to hunt for it reads the rest as excuse-making. 4. What happened, one or two factual sentences, so the reader can judge the scope themselves. 5. Responsibility, one sentence, which is the part that actually restores trust. 6. The correction, with a date, because that is what turns an apology into a resolution. 7. Close, forward-looking, so the thread ends on the next step rather than on the mistake. Most formal apology emails work best between 80 and 150 words. If yours is longer, it is usually explanation that can be cut.

Subject lines that work

"Apology for the delayed sales report" "Apology and corrected invoice (INV-2231)" "Apology for missing this morning's stand-up" "Following up on yesterday's error in the client deck" "Mohon maaf atas keterlambatan laporan penjualan" Name the thing, not the emotion. "Sorry!" and "My mistake" tell the reader nothing when they search the thread three weeks later. Avoid dramatising the subject line. "Serious error on my part" makes a small correction look like an incident, and everyone copied in will read it that way before they read the body.

How to acknowledge the mistake specifically

A specific acknowledgement proves you understand the problem. A vague one suggests you are apologising to end the conversation. Vague: "Sorry about the issue with the report." Specific: "The report I sent on Tuesday used February figures instead of March, which meant the growth number was overstated." Name the impact too, in one clause, when there was one: "which meant your team planned around a number that was wrong". Do not overstate it. If the effect was small, saying it was catastrophic forces the reader to reassure you, which reverses the roles. If you do not yet know the full scope, say that plainly: "I am still checking whether the March invoices were affected and will confirm by 4pm today."

Taking responsibility without over-explaining

The reader mainly wants to know that you understand the problem and that it is handled. Give context only when it changes what they should do next. Over-explained: "I had three deadlines that week, and the file server was slow, and my colleague was on leave, so the report was late." Better: "The report was late because I misjudged the review time. I have rescheduled my own checks so the next one arrives a day early." One cause, one correction. That reads more professional than a list of reasons. The test for whether a reason is an excuse: does it change what the reader should do? A genuine cause the reader needs ("the export tool dropped the last row, so any figures pulled before Thursday need rechecking") belongs in the email. A cause only you need ("it was a busy week") does not. Avoid the passive escape hatch. "An error occurred" and "mistakes were made" are grammatically fine and read as though nobody was involved.

Apology wording that works

Direct and appropriate: "I apologise for the error in yesterday's invoice." "I am sorry for the delay in sending the report, and I take full responsibility for it." "I understand the impact this had on your schedule." "Thank you for your patience while I corrected this." Weaker phrasings to avoid: "Sorry if this caused any issues" (conditional, sounds unsure the problem was real). "Sorry you felt that way" (apologises for their reaction, not your action). "Unfortunately the system failed" as the whole message (explains without owning). "I am extremely, deeply, terribly sorry" (intensity is not the same as sincerity). "I hope you can forgive me" (asks the wronged person to do the emotional work). In Bahasa Indonesia, "Saya mohon maaf atas keterlambatan laporan tersebut" carries the same weight as the direct English version, and Bapak/Ibu plus Mohon keeps the register formal.

Too weak, too dramatic, and about right

Too weak: "Sorry for any inconvenience this may have caused." It is conditional, generic, and could be pasted into any email ever written. The reader learns nothing. Too dramatic: "I am truly mortified and cannot express how sorry I am for this unacceptable failure." For a late report this is out of proportion, and it puts the reader in the position of having to comfort you. About right: "I apologise for sending the report a day late. I misjudged the review time, the corrected version is attached, and I have moved my checks forward so the next one is early." Calibrate the language to the actual damage. A one-hour delay gets one plain sentence; a billing error affecting a client's accounts gets a fuller acknowledgement, a stated fix, and a named preventive step.

Offering corrective action

Every apology should end with something concrete. Choose whichever is true: Already fixed: "The corrected invoice is attached and the original has been cancelled." Fix in progress with a date: "The updated figures will be with you by 3pm on Friday." Prevention: "We have added a second check before invoices are issued." Remedy where one is warranted: "We will reissue the delivery at no additional charge." Only promise what you control. A missed second promise costs far more than the original mistake, and it is the point at which people stop reading your apologies as reliable. If you cannot fix it, say what you will do instead: "The window for the March filing has closed, so I have documented what happened and moved the deadline reminder two weeks earlier for the next cycle."

How to close professionally

Close forward-looking, not apologetic again. Any of these work: "Please let me know if you would like anything adjusted." "I am happy to walk you through the corrected version whenever suits you." "Thank you for your understanding." Then a standard sign-off: "Kind regards," "Best regards," or in Indonesian "Hormat saya," followed by your name and role. Avoid ending with a second apology, and avoid ending with nothing at all. On recipients: copy the people who need the correction, not everyone who saw the mistake. Widening the circle turns a fix into an event.

Short version or detailed version

Use the short version, three or four sentences, when the mistake was small, contained, and already fixed. Apology, cause in a clause, fix, close. "Dear Rina, I apologise for sending the wrong attachment earlier. The correct file is attached. Please let me know if anything is missing. Kind regards, Adi." Use the detailed version when money, a client, a deadline that cannot move, or several people were affected. It adds two things: a factual account of scope, and a named preventive step. When in doubt, write the detailed version, then delete every sentence that does not tell the reader what happened, who owns it, or what happens next. What remains is usually the right length.

Common mistakes

Apologising three times in one email. Opening with the excuse instead of the apology. Using passive phrasing like "mistakes were made" to avoid ownership. Promising a fix with no date. Apologising on behalf of someone else without being asked to. Copying in more people than the situation needs. Adding a defence at the end after a clean apology, which cancels the apology. Sending it hours later than you could have. A short, prompt apology beats a polished, late one.

Try it now

Free · no sign-up · English and Bahasa Indonesia.

Examples

General workplace example · Input
hey sorry i totally forgot to send the sales report yesterday, been swamped. will get it to you asap
Result
Subject: Apology for the delayed sales report

Dear Ms Chen,

I apologise for not sending the sales report on Wednesday as agreed. I misjudged how long the final review would take, and that is on me.

The completed report is attached, and I have moved my review step forward so the next one reaches you a day before the deadline.

Please let me know if you would like anything adjusted.

Kind regards,
Daniel Wirawan
Sales Operations
Apology email to a boss or manager · Input
sorry i missed the standup this morning, my alarm didn't go off
Result
Subject: Apology for missing this morning's stand-up

Dear Mr Hartono,

I apologise for missing this morning's stand-up. There was no good reason for it, and I should have set a reminder the night before.

I have read the notes from Priya and picked up the two items assigned to me, both of which will be done by Friday. I have also added a recurring reminder so it does not happen again.

Thank you for your understanding.

Best regards,
Sari Mahendra
Apology email to a client · Input
hi, really sorry about the wrong invoice we sent. we'll fix it. sorry again for the trouble
Result
Subject: Apology and corrected invoice (INV-2231)

Dear Mr Alvarez,

I am sorry for the error in invoice INV-2231, which listed the wrong quantity for the March delivery. The mistake was ours, and I understand it created extra work for your finance team.

A corrected invoice is attached, and the original has been cancelled. We have added a second check before invoices are issued so this does not recur.

If anything in the corrected version needs adjusting, I will handle it the same day.

Kind regards,
Nadia Iskandar
Account Manager
Apology to a colleague, after a sharp reply · Input
hey, sorry about how i replied in the thread earlier, came out harsher than i meant. was stressed about the deadline
Result
Hi Bima,

I want to apologise for how I replied in the launch thread this morning. It came out sharper than I intended, and that was not a fair way to raise the point.

The concern about the timeline still stands, but I should have raised it directly with you rather than in front of the group. I have added a note in the thread clarifying that the delay was not on your side.

Happy to talk it through this afternoon if that would help.

Best,
Adi
Short version, minor and already fixed · Input
sorry, sent you the old version of the file by mistake
Result
Dear Rina,

I apologise for sending the earlier version of the deck. The current file is attached, and the figures on slide 6 are the ones to use.

Please let me know if anything else looks out of date.

Kind regards,
Adi

Frequently asked questions

How do you start a formal apology email?
With a subject line that names the issue, a formal greeting, and then the apology itself in the first or second sentence. For example: "Dear Ms Chen, I apologise for the delay in sending the sales report." Do not open with the explanation.
How long should a formal apology email be?
Usually 80 to 150 words. That is enough to apologise, state the facts, take responsibility, and give the next step. Anything longer is normally explanation the reader did not ask for.
How do you apologize professionally for a mistake at work?
Name the specific mistake, own your part in one sentence, say what you have done to correct it, and give a date if a fix is still pending. Skip the reasons unless they change what the reader needs to do.
What is a good subject line for an apology email?
One that names the topic so the email is findable later: "Apology for the delayed report", "Apology and corrected invoice (INV-2231)", or "Apology for missing this morning's stand-up". Avoid vague lines like "Sorry!".
Should I explain why the mistake happened?
Only if the reason changes what the reader should do. A cause that affects their work belongs in the email; a cause that only explains your week reads as an excuse. One sentence is the limit either way.
Is it unprofessional to say sorry too much?
Repeating the apology weakens it. Apologise once, clearly, then spend the rest of the email on the correction. Habitually apologising for normal things also makes the sincere apologies harder to hear.
How do you end an apology email?
With a forward-looking line such as "Please let me know if you would like anything adjusted", then a formal sign-off like "Kind regards" and your name. Avoid repeating the apology in the closing.
Should I apologise by email or in person?
For minor, work-process issues, email is fine and often preferred because it leaves a record of the correction. For anything sensitive or personal, a short conversation first and a brief confirming email afterwards usually lands better.
Who should I copy in?
The people affected by the mistake and anyone who needs the corrected version. Copying in a wider audience turns a routine correction into an incident and rarely helps the person you are apologising to.
Does the tool work in Bahasa Indonesia?
Yes. It never translates, so Indonesian input stays in Indonesian with polite forms such as Bapak/Ibu and Mohon.

The tool behind this page

FormalizeTurn casual writing into polished professional text.

More in Apology & Diplomacy

View all →