An apology email is judged on two things. The reader wants to know you understand the mistake was yours, and what you’re doing about it. Those two carry most of the repair. How sorry you sound comes a long way behind them. And those two are the parts most apology emails leave out.
What gets over-supplied instead is regret. A paragraph of it, in three registers, with the cause left out and the fix tucked into a clause near the bottom. It feels sincere to write. It reads as evasive to receive. The person opening it is working out one thing: whether they can still plan around you.
- The reader is deciding one thing: whether this happens again.
- Saying sorry and saying it was yours are two different moves, and the grammar is where the difference shows.
- The strongest line in an apology is nearly always the one about what happens next, with a date on it.
- Almost everything people add to sound more sorry makes them read as less reliable.
This guide is about the message you send after something went wrong. How much of your tone reaches a reader at all, and why the courteous version asks least of them, is taken apart in the polite reminder email. If what you owe is an answer they were hoping to avoid, that’s how to say no in an email. And if the apology is really the opening line of a second attempt at something that went quiet, the message you want has a different shape. It’s in the follow-up email that gets answered.
What the reader is actually deciding
Open a real apology as its recipient. Something has already cost you a morning, a number, a launch date, or a promise you made to somebody else. What you want from the message is information. How bad is this? Whose was it? What’s being done? And do I now have to build a workaround into everything that follows?
That last question is the whole of it. An apology is a forecast. The other person is deciding how much of their own planning they can still hang on you. Every sentence you write either firms that up or loosens it. “I feel terrible about this” loosens it, because it’s about you and it predicts nothing. “The figure came off the September file instead of the October one, the corrected report is attached, and the September file is out of the folder so it cannot be picked up again” firms it up. Somebody who can say precisely what went wrong is somebody who went and looked.
Which is why specificity does more work in an apology than warmth does. Vagueness reads as guessing. A reader who thinks you’re guessing has to assume it happens again, whatever you say about how badly you feel.
There’s a second reader, and people forget about them while they’re writing. An apology email is a document. It gets forwarded to somebody’s partner, pasted into a group chat, filed with the contract, and read again in six months by a person deciding whether to renew you. Occasionally by somebody deciding something more serious than that. Writing for both readers at once is easier than it sounds. The version that repairs the relationship today is almost always the version you’d be happy to have read back to you later.
The two parts that carry the repair
The ranking here has been tested. Most people write to a different one.
Roy Lewicki, Beth Polin and Robert Lount Jr. published two studies in Negotiation and Conflict Management Research in 2016. They took the apology apart into six components. Then they had people rate versions built from different combinations of them, across 755 participants: 333 adults recruited online and 422 undergraduates. The scenarios were hiring situations involving an error on a tax return, which is about as ordinary a professional mistake as you could pick.
The six components:
- an expression of regret
- an explanation of what went wrong
- an acknowledgment of responsibility
- a declaration of repentance
- an offer of repair
- a request for forgiveness
Two findings matter. The first is that “apologies with more components were more effective than those with fewer components”, which is easy enough to predict. The second is the ordering, and the ordering is the surprise. On Lewicki’s account of it, “the most important component is an acknowledgement of responsibility. Say it is your fault, that you made a mistake.” Second came the offer of repair, because “by saying, ‘I’ll fix what is wrong,’ you’re committing to take action to undo the damage.” Expression of regret, explanation, and declaration of repentance were essentially tied for third. Bottom of the list was the request for forgiveness: “that’s the one you can leave out if you have to.”
Hold the study at its actual size. People rated written apologies inside a scenario, rather than receiving one from somebody they had a relationship with. What got measured was judged effectiveness, rather than what anybody went on to do. So it tells you how an apology reads, which is genuinely the thing you control while you’re typing one. What a client does in the morning is a separate question.
Even so, put the ranking next to a real apology email and the mismatch is uncomfortable. The typical one is component one, four times over. Responsibility and repair are both missing. Quite often there’s a closing line hoping to be forgiven, which is the component the research says you can drop. It’s the exact inverse of what the reader is grading.
That’s an argument about order rather than length. All five of the components worth having fit in five short sentences:
Hi Leah,
The quarterly report went to your board with last quarter’s revenue line in it, and that was my error. I pulled the numbers from the wrong source file and did not check them against the ledger before sending.
The corrected version is attached. I have written to Owen and Marisol directly with the same correction so nobody is working from the old one.
From now on the revenue line gets checked against the ledger before anything goes out, which is a two-minute step that was not in the process and now is.
I am sorry. It was avoidable and I know what it cost you in that meeting.
Regret appears once, at the end, where it holds up nothing. Everything before it is fact.
Sorry is not the same as responsible
Two sentences carrying the same information:
I’m sorry the report went out with the wrong figures.
I sent the report with the wrong figures, and I’m sorry.
The first makes the report the subject and leaves the author blank. It’s technically an apology, and it reads as a weather report. The second has you in it. The reader knows that you know, because you said so.
This one is worth spelling out, because it reverses the rule that governs the message you write when somebody else is late. There, what works is to name the state of the thing and leave the person out of the sentence, since a person in the grammar lands as an accusation however you soften it. That rule and the sentences it produces are in the polite reminder email. In your own apology it runs the other way, and for the same reason. The accusation is the point of the message, and it’s aimed at you.
The constructions that hide the author are worth knowing by sight. They arrive on their own, before you’ve chosen them:
- “I’m sorry if this caused any problems.” The word “if” makes the harm hypothetical. The harm is real, or you’d be writing something else today.
- “I’m sorry you feel that way.” This apologizes for the other person’s reaction, which moves the fault onto them. It’s the single most reliably resented sentence in professional email.
- “Mistakes were made.” This sentence gets written about mistakes somebody has decided to hold at arm’s length.
- “The invoice didn’t get sent.” Same shape, smaller scale, and easy to type on the way past.
- “There seems to have been a mix-up.” The mix-up takes the blame, and “seems” says you’re still guessing at what happened.
There’s a matching decision about “I” and “we”. If one person did it and that person is you, “I” is the honest pronoun, and reaching for “we” reads as hiding behind your own staff. If the failure belonged to the firm, a missing process or a handoff that belonged to everybody, then “we” is accurate. “I” there reads as somebody absorbing a hit for a system that will produce the same fault next quarter. Clients can tell the difference, and they mostly care because it tells them which one is being fixed.
The reason, and where it becomes an excuse
One sentence of cause. The test for whether it belongs is simple: does the explanation make the fix more credible, or does it move the blame somewhere else?
“I pulled the numbers from the wrong file” is a cause. It makes the fix credible, because you can see how the fix attaches to it. “We have been slammed since the filing deadline moved” is an excuse, and it costs you more than silence would. It describes a condition that’s still running. Any explanation still true tomorrow is a forecast that this happens again, which is the one thing the reader wants ruled out.
The order matters as much as the content. The reason goes after the acknowledgment. A cause placed ahead of the admission reads as a run-up, and the reader starts discounting the rest before you reach the part that counts.
Three things stay out of it. Keep an individual on your own side out of a client’s message: whatever happened internally, the client bought the firm. Keep the client’s own contribution out too, even when it’s accurate and even when it’s most of the cause, because a mixed message is a rejected one and you’ve just canceled the thing you sent. If their part genuinely needs saying, it’s a separate conversation on a separate day. And give a reason only once you’ve verified it. A cause that turns out to be wrong forces a second apology about the first one, which costs several times what the original did.
Some causes are dull, and dull is fine to state plainly. “I forgot” is a complete sentence and an oddly reassuring one. It’s specific, it points at a person rather than a system quietly failing, and it ends the argument. It’s also the honest answer far more often than the paragraph people write instead.
The fix, and the date on it
Repair came second in the ranking, and it’s the part most often missing entirely, usually because the writer thinks the point of the email is the apology. The point of the email is the repair. The apology is the frame it arrives in.
It has three levels, and a good message uses whichever ones are available.
Undo it. The corrected file, the reissued invoice, the amended return, the call to the printer to stop the run. Say what’s already done rather than what will be, wherever the timing allows.
Offset what the fix leaves behind. Most mistakes leave a residue the correction reaches past: the meeting where a client presented your wrong number, the two days their team lost, the fee they paid to expedite something. Name the specific consequence and say what you’ll do about it. Offering to write to the third party yourself is often worth more than money, and it’s rare enough that it lands.
Stop it recurring. One concrete change, in one sentence, and only where you’re going to make it. A prevention promise that fails a second time costs more than silence would, because the second failure proves that you say things to close conversations.
Put a date on all of it. “I’ll get this fixed” is a mood. “The corrected version is with you by four this afternoon” is repair, and it hands the reader something they can plan around, which is the thing they lost.
On money. Offer it when the mistake cost money, and name the number rather than promising to make it right. Keep money out of it when the cost was time and goodwill, because an offer invites the reader to put a price on the relationship, and the price they arrive at is rarely one you like. Where you do credit something, credit it and stop. A discount presented as an apology, then defended over three emails, ends up costing more than the write-off.
Then there’s who else gets the message. Four people were working off the same wrong number, and the apology went only to the one who complained. That’s the next incident already in motion. Work out who’s holding the bad version, and write to all of them the same day.
And speed. Send it the day you know. An apology loses value faster than almost anything else you write. The gap between the mistake and the message is itself information about how seriously you took it, and the reader can measure that gap exactly. The one thing worth waiting for is the facts. While you’re still finding out, send two lines today. Say what you know, say you’re checking, and say when you’ll come back. Then send the real one once you can name the cause. A fast apology that turns out to be wrong about why costs you a second one.
How much apology the thing is worth
Failures run in both directions, and the small one is more common.
Reflexive apologizing is the tax most people pay on the quiet. “Sorry for the late reply” on a message answered in two days. “Sorry to be a pain” in front of a normal question. “Apologies for the delay” at the top of something that arrived on time. Each one is a small report that you have failed, volunteered about yourself, in a message the reader had already moved past. Do that a hundred times and you’ve described yourself as unreliable a hundred times. You’ve also spent the word so freely that it’s empty on the day something actually goes wrong.
The repair is usually a thank you in its place, which turns the same courtesy into something pleasant to receive. “Sorry for the slow reply” becomes “thanks for your patience on this.” “Sorry for the long email” comes out altogether, and you shorten the email.
A rough scale for the rest of it. A nuisance gets one clause, and then you get on with the substance, because a paragraph of apology about a nuisance turns the nuisance into an event. Something that cost the other person something real gets a proper apology with the repair in it. And anything that goes to trust, whether you’re reliable, whether you were honest, whether you can be left alone with something, is a phone call first and a written one after.
The mismatch cuts the other way too. A mistake that cost a client four thousand dollars, answered with “apologies for the mix-up”, lands worse than silence. The size of the message is itself a statement about how large you think the harm was. A small message about a large harm reads as a second insult.
One counterweight, because it’s real and it points the other way. Alison Wood Brooks, Hengchen Dai and Maurice Schweitzer studied what they call superfluous apologies, meaning “expressions of regret for an undesirable circumstance for which the apologizer is clearly not responsible”. It ran in Social Psychological and Personality Science in 2014. Their field study is the memorable one. Over two days in November 2010, a confederate worked a large Northeastern train station in steady rain. They approached 65 strangers and asked to borrow a cell phone, half the time opening with an apology about the weather. With the apology, 47 percent handed the phone over. Without it, 9 percent did.
Two limits before you take anything from that. It’s 65 people, one small favor, and strangers rather than clients. And across the wider set of studies the boost showed up in benevolence-based trust and in liking. Competence was a different story: in two of the studies the apology had no significant effect on whether people thought the apologizer was any good at anything.
Which is exactly the useful distinction. Apologizing for a bad circumstance outside your hands reads as noticing what the other person is dealing with, and that’s worth having. “I’m sorry you got caught in the middle of that” is a real sentence, and it’s free. The one to watch is the apology about yourself for existing. “Sorry, I’m hopeless with dates” is a forecast, and the reader files it as one.
Ten apologies, written out
Most of these sit on the thread the problem arrived in. A subject line appears only where the message genuinely starts something.
One. A deadline you missed. The date is stated plainly, and the new one is real.
Hi Theo,
The draft was due with you Monday and I did not send it. No good reason: I misjudged how long the data section would take and did not tell you when I realized on Friday, which is the part I would most like back.
It is with you by noon tomorrow, finished rather than partial.
If that puts your Thursday review at risk, tell me and I will work to whatever time actually helps.
Two. An error in work you already delivered. The cause is one line, specific enough to be checkable.
Hi Nina,
There is an error in the report I sent Tuesday. The headcount figure on page four is 214 and it should be 187. I read it off the pre-adjustment tab.
Corrected version attached, with the two paragraphs that referenced it rewritten. Nothing else in the report is affected and I have checked every other figure against source.
I know it went to the board with my name on it. I am sorry.
Three. Sent to the wrong person. Fast, factual, and it says what’s been done rather than how it felt.
Hi Gabriel,
I sent your engagement letter to the wrong address this morning. It went to one contact at Calder, not to anyone outside your organization, and I have asked them to delete it and had that confirmed in writing.
The letter contained your fee schedule and scope. It did not contain financial statements or any personal data.
I have changed how the address is populated on that template so it cannot autofill from a previous client again. Happy to talk it through today if you want more detail than this.
Four. A meeting you missed entirely. It skips the explanation and goes straight to the repair.
Hi Hana,
I missed our ten o’clock and I have no excuse for it. You held the time and I was not there.
Whenever suits you this week, I will take whatever slot is least inconvenient, including early or late.
I am sorry to have wasted your morning.
Five. A slow reply on something that mattered. The apology is one clause. Everything after it is the answer they wanted eight days ago.
Hi Wes,
Eight days is too long on a question about your own filing, and I am sorry.
The answer is yes, the depreciation election can still be made on the amended return, and there is no additional fee for doing it that way.
I have put the amendment in for the 19th. Nothing needed from you unless the vehicle date has changed since we spoke.
Six. A message you should not have sent. The mood stays out of it. The commitment is behavioral.
Hi Cara,
My reply yesterday about the timeline was sharp and unfair, and it was aimed at you when the problem was not yours.
You were right to flag the dependency. I should have said thank you and dealt with the schedule.
I have gone back to the thread and answered it properly. Nothing you need to do with this message.
Seven. Your supplier failed and the client only sees you. The third party stays out of the cause, because from where the client sits, it’s you.
Hi Devon,
The install did not happen yesterday and that is on us. The cabinets were not delivered, and we should have checked that the day before rather than the morning of.
The new date is the 14th, which I have confirmed rather than been told. Your team is booked for it.
The two days your fitters lost are ours to cover. I have taken them off the next invoice and the credit note is attached so you can see it rather than take my word for it.
Eight. Something you can’t fix, which cost them money. The number is named, and the repair stands on its own.
Hi Imani,
The extension was filed a day late and the penalty is $438. That was my error, and I am not going to dress it up as anything else.
I have paid it directly rather than credit it, so nothing lands with you and there is nothing for you to reclaim. The confirmation is attached.
I have also moved every extension deadline for the practice into a shared calendar with a two-week lead, which is the change that should have been made a year ago.
There is nothing you need to do here. If you want to talk about it, I am around all week.
Nine. On behalf of your team, where somebody else made the mistake. The firm owns it, and the individual stays out of it.
Subject: The Oakhurst valuation, and what went wrong here
Hi Peter,
The valuation you got on Friday used the wrong comparison set, and it went out without a second pair of eyes on it. That is a gap in how we work rather than one person’s bad afternoon, and it is mine to fix.
A corrected valuation is with you Wednesday. I will walk you through what changed rather than send it cold.
Reviews are now required on anything going to a lender, and I have written that into the checklist rather than asked people to remember it.
Ten. An apology you owe somebody who works for you. Written down, because the people who saw it need to see the correction too.
Hi Ruth,
I overruled you in front of the client on Thursday, and I was wrong about the substance as well as about doing it there.
Your read on the timeline was right, and I have told Bellweather that in writing this morning so the correction is on the record where the mistake was.
If it would help to talk about how those calls run, I would like to.
Across the ten, three things repeat. Whose fault it was arrives inside the first two sentences. Each one spares the reader the job of making the writer feel better. And every one of them names something specific that happens next.
The phrases that undo it
Each of these gets written by somebody trying to sound more apologetic, and each one costs the message something. The two worst, “I’m sorry if” and “I’m sorry you feel”, are in the section above. They survive most edits, so check for them last.
“We apologize for any inconvenience caused.” The most quietly insulting sentence in business writing. It reads as a form letter, it downgrades whatever happened to an inconvenience, and “any” says you’re still guessing at what it was. If you know what it cost, name it. If you’re guessing, go and find out before you write.
“We take this extremely seriously.” A claim about your own state of mind, made at the moment your state of mind is in question. The behavior in the message is the evidence anybody can actually use, so put the evidence in and cut the claim.
“As I’m sure you can appreciate.” This asks the injured party to agree with your side of it before you’ve finished apologizing. So does “in fairness”, and so does “to be honest”.
“Please accept my sincerest apologies.” Formality reading as distance. This is written language only, and the more elaborate the apology grammar becomes, the more it sounds like something a department sent.
Apologizing twice in one email. Once at the top and once at the bottom is the standard shape, and it’s one too many. The second one turns your mistake into a thing the reader has to manage, and it invites the reply where they reassure you, which is work you’ve handed to the person you just cost a morning.
“Unfortunately” doing the whole job. An apology built around “unfortunately” tends to leave out what happened, who did it, and what comes next. It sounds regretful and leaves the reader where they started.
Asking for something in the same message. An apology that ends by asking for the signed copy, or the payment, or a call, is a transaction. Send the apology, and let the ask travel separately, even if that’s a second email an hour later.
“Hopefully this won’t affect our working relationship.” It might, and that’s theirs to decide. Asking about it puts the job of reassuring you on somebody who’s still holding the damage.
The long explanation. Past two sentences, a reason has become a case, and a case reads as a plea to be found innocent. What the reader wanted was the sentence you skipped, which is what happens next.
Does saying sorry admit fault?
This question stops more apologies than any other, and it usually stops the wrong ones. Start with the reassuring part. For ordinary professional mistakes, silence carries the larger risk, and the caution people are carrying belongs to a narrower situation than they think. Two rules are worth actually knowing, because they’re the ones doing the work.
The first is the one that makes your email evidence. Under Federal Rule of Evidence 801(d)(2), a statement “offered against an opposing party” that “was made by the party in an individual or representative capacity” is not hearsay. The rule extends the same treatment to a statement “made by the party’s agent or employee on a matter within the scope of that relationship and while it existed”. In plain terms: what you wrote, and what your staff wrote, can be put in front of a court against you. That’s the default, and it holds whether or not the word “sorry” appears anywhere in it.
The second is the protection people assume they have. It’s real, and it’s narrow. Federal Rule of Evidence 408 makes “conduct or a statement made during compromise negotiations about the claim” inadmissible “either to prove or disprove the validity or amount of a disputed claim or to impeach by a prior inconsistent statement or a contradiction”. Read the conditions rather than the headline. There has to be a claim, it has to be disputed, and the statement has to be made in negotiating over it. So Rule 408 covers the settlement conversation. An apology you send on a Tuesday because you got a number wrong, before anybody has claimed anything, sits outside it. The rule also carries its own exceptions at 408(b), where a court “may admit this evidence for another purpose”.
What follows from those two is a drafting habit rather than silence. Write facts, and leave the legal conclusions to the lawyers. “The figure on page four was wrong and I sent it” is a fact you’d concede anyway. “We were negligent”, “this was a breach of our engagement” and “we failed to meet our obligations” are characterizations. They’re the other side’s job rather than yours, and the reader came for something else. Describe what happened, own it in ordinary words, commit to the fix. Where the exposure is real, meaning somebody has lost money at a scale that matters, or has started using the language of claims, read your professional liability policy before the email is written. Many of them want to hear from you at the point where something could become a claim, rather than after you’ve corresponded about it.
One more thing catches small firms out. Where the mistake exposed customer data, the apology to the person affected and the notification you owe a regulator are two separate obligations, and sending the first leaves the second still open. The FTC Safeguards Rule covers tax preparation firms, collection agencies, credit counselors and several other categories. Since May 13, 2024 the amended rule has required you to notify the FTC of a notification event. That’s defined as “an acquisition of unencrypted customer information without the authorization of the individual to which the information pertains”, involving at least 500 consumers. The timing is “as soon as possible” and “no later than 30 days after discovery” (checked September 6, 2026). State breach notification law sits on top of that and varies. The one-off email sent to the wrong contact, which is the case in the templates above, sits outside all of this. All of it applies the moment the number of affected people passes one.
When it should not be an email
Five cases where the conversation belongs somewhere other than a carefully written message, and one where people hold back and should just write.
It cost real money and you know the number. Say it out loud first. The other person will have a question the moment they read it, and a message that leaves them holding that question for four hours makes the damage worse. Call, say it, then send the written version the same day as the record.
You need to hear how it lands. Some apologies are the beginning of a conversation about whether the relationship continues. A written reply comes back shorter and more polite than the truth, so you want to hear this one.
It’s about how you treated somebody. Tone, an interruption, something said in front of other people. Written apologies for interpersonal harm arrive colder than you intended, because the reader supplies a voice and rarely a generous one. That effect is measured, and the measurement is in the polite reminder email. Say it where they can hear you, then write the short version if the incident was public.
This is your third apology to the same person about the same thing. A third apology describes a pattern. What it needs is a conversation about the pattern, and probably a change to how the work runs. Both of those sit outside a message about the latest instance.
You’re still finding out what happened. Send the holding note today, and the apology once you can name the cause. An apology with a wrong cause in it has to be apologized for.
The case people get backwards is the small one. A missed reply, a minor slip, a wrong attachment: email is exactly what those are for, and the two-line version sent within the hour is the entire job. What turns a small apology into a large one is almost always the delay in front of it, while somebody works out how to do it properly.
The apologies you never had to write
Most of the apologies in a small business are about capacity rather than competence. Something gets agreed in the middle of a thread on a Tuesday, it goes unwritten, and three weeks later it surfaces as a missed date. The email you end up writing is the bill for that.
Point is an email client for the Gmail or Microsoft 365 mailbox you have now, and what it carries here is the keeping track.
A commitment buried in the middle of a paragraph turns up as a dated task on the list you already work from. What you agreed on Tuesday is held for you, whether or not you remember Tuesday. Something you passed to somebody else stays an open loop, and it comes back up while there’s still time. Importance and volume are weighed apart from each other, so the note from a client who’s about to be let down sits above the forty newsletters. That’s the whole prevention story, and it’s worth more than any wording.
When one does have to be written, the material that makes it specific is already in place. Every conversation carries a plain summary, so what was promised, and on what day, is there to read. You get the facts at the moment you’re least inclined to reconstruct them from memory. Say what you want the reply to do, and it comes back phrased the way you phrase things, sitting above the thread it answers. Standing preferences about how you sound are kept as sentences you can open and edit, so a rule about client mail gets set once and stays set.
Where that draft goes next is a setting rather than a guess. The autonomy dial is picked per action type, from suggest-only at one end to handling the thing outright at the other. Review is where every type starts, so an apology Point has drafted waits for you until you move that dial yourself. What each position means day to day is on the autonomy dial. Actions are logged in sequence and undo works back along that log, with one limit that matters more in this subject than in any other: mail already delivered to somebody else’s server is beyond recall. That limit is the reason this whole category of email exists. Everything else a mailbox picks up from this is listed under benefits.
Common questions
How do you write a professional apology email?
Say what happened and that it was yours, in the first two sentences and in plain words. Give one sentence of cause, where the cause makes the fix more credible rather than moving the blame. Say what you’re doing about it, with a date on it, and what stops it happening again. Then apologize, once, and stop. The research on apology structure puts acknowledgment of responsibility first and offer of repair second. Those are the two parts most emails skip in favor of a longer expression of regret, which the same research places well down the list.
Should I say “I’m sorry” or “I apologize”?
Either works, and what surrounds it matters far more than the choice. “I’m sorry” is what people say out loud, so it reads as a person. “I apologize” is a shade more formal and slightly more distant, which is occasionally what you want in a message that will be filed. The one to skip is the elaborate version. “Please accept my sincerest apologies” is written language only, and the more ceremonial the phrasing, the more it sounds like a form letter about somebody else’s mistake.
Does apologizing in writing admit legal fault?
Your email is admissible against you as a matter of course, under the federal rule that treats an opposing party’s own statement as not hearsay, and that holds with or without an apology in it. The protection people assume they have, for statements made in compromise negotiations, attaches once there’s a disputed claim and you’re negotiating over it. An ordinary same-day apology sits outside that. So the practical answer is to write facts rather than legal characterizations: what happened, that it was yours, what you’re doing. Where somebody has lost real money, read your professional liability policy before you write anything, because many of them want notice at the point something could become a claim.
How do I apologize for a late reply?
Usually by thanking them instead. “Sorry for the late reply” is a small announcement that you’re unreliable, attached to a message the reader had already moved past. Repeated often enough it spends the word, and the word is empty on the day you need it. “Thanks for your patience on this” does the same courtesy and leaves the self-report out. Where the delay genuinely cost them something, name the length of it in one clause, skip the explanation, and put the answer they’ve been waiting for immediately underneath.
What do I write when the mistake cost the client money?
Name the number. A specific figure tells the client you’ve worked out the size of it, which is the thing they’re least sure of when they open the message. Then say what you’re doing about that specific amount. Pay it directly rather than credit it where you can, so it’s settled and off their desk. Keep money out of it where the cost was time, because an offer invites the reader to price the relationship. And if the number is large, call first and let the email be the record rather than the delivery.
Should I apologize for something that was not my fault?
For the reader’s bad circumstance, yes, and the evidence is on your side. There is field evidence that apologizing for something outside your hands increases trust and liking, apparently because it shows you noticed what the other person is dealing with. Credibility about your work is a separate account: in the same set of studies, the effect stayed out of perceptions of competence. So “I’m sorry you got caught in the middle of that” is worth writing. “Sorry, I’m hopeless with dates” is a forecast about yourself that the reader will file and use.
How long should an apology email be?
Under 150 words for nearly everything, and shorter for small things. An apology has four working parts. What happened, that it was yours, what you’re doing with a date on it, and one line of regret. All four fit comfortably. Length in an apology reads the way length in a refusal reads, as a case being made, and a case invites the reader to judge it. If yours has run long, the extra words are almost always explanation, and explanation past two sentences has stopped doing work.
How soon should I send it?
The same day you know, and inside the hour for anything small. The gap between the mistake and the message is information the reader can measure exactly, and a well-written apology that took four days to arrive has already answered the question it was sent to address. The one reason to wait is that you’re still finding out what happened. Even then, send two lines today. Say what you know, say you’re checking, and say when you’ll come back. Then send the real message once you can name the cause.
The short version
An apology email is a forecast wearing the clothes of an apology. The person reading it is deciding how much of their own week they can still hang on you, and everything you write either firms that up or loosens it. Which is why the order that works runs against the habit. What happened, that it was yours, what you’re doing about it with a date on it. Then one line of regret at the end, where it comes last and holds up nothing.
Watch the grammar rather than the tone, because that’s where responsibility actually lives. “I sent the report with the wrong figures” and “the report went out with the wrong figures” carry the same information, and one of them has an author. Keep the reason to a sentence, and keep it where it makes the fix more credible instead of relocating the blame. Cut the second apology, the inconvenience formula, the claim that you take it seriously, and the closing hope about the relationship.
Then send it today. An adequate apology sent on Tuesday beats the strongest one written on Friday, because the delay is the part the reader can measure. And notice which of these you keep writing. An apology that recurs is a report on how the work is set up, rather than a writing problem.
What you’re apologizing for shapes the emphasis. An accounting practice apologizing for an error in filed work leads with the cause, because the client’s next question is whether anything else is wrong. A design studio that missed a print date owes the new date and the recovery plan more than it owes regret. A coaching practice apologizing for a missed session is apologizing for the thing the client bought, so the repair is simple and the excuse can go. And a consultancy whose subcontractor failed still owns the whole of it, because the client signed with you. The other trades this was built for sit somewhere among the four.