How to apologize to a client for a mistake: name it, fix it, then say what changes

Google autocomplete, checked on 22 October 2026, finishes "how to apologize to a client for a mistake" with "professionally" and "in email".

So people want the wording. You will get a sample near the end.

But the wording is the easy part.

Here is the complication. Most agency apologies fail before anyone types a word. They fail in the gap between the moment someone on your side spots the mistake and the moment the client hears about it.

That gap is where you decide whether this is a mistake you report, or a mistake they discover.

Those are two very different conversations.

Step 1: Tell them before they find it

If the mistake touches their work, their money or their audience, they hear it from you.

A wrong caption on a live post. An invoice with the wrong amount. A deliverable sent to the wrong person. A clip that went up with a typo in the hook.

The instinct is to fix it quietly and hope. Sometimes that works. But when it does not, the client now holds two problems: the mistake, and the question of what else you have fixed quietly.

The second problem is the one that ends retainers.

So the rule I run on is simple. If I would be uncomfortable with them finding it, I tell them.

Step 2: Start the fix before you send the apology

An apology with no fix attached is a confession. It hands the client the job of deciding what happens next.

So before the message goes out, the correction should already be moving. The post is edited or pulled. The corrected invoice is drafted. The right file is on its way to the right person.

Then the apology can say "here is what I have already done" instead of "let me know how you want to handle this".

That one sentence changes the tone of the whole exchange.

You are reporting, and you are in control of it.

Step 3: Name the mistake in one plain sentence

This is where most apologies go soft.

"There seems to have been an issue with some of the recent deliverables" is not an apology. It is fog.

Write the sentence a client would write if they were describing it to their own boss. "The Tuesday post went out with the wrong price in the caption." "We sent the draft to the wrong address."

One line, first line, no adjectives.

And own it as the business. "We sent it", not "our editor sent it". Your team member made the mistake, but the client hired you, and naming a person reads as passing the blame down the line.

Deal with the person separately and privately.

Step 4: Skip the long explanation

Explaining why it happened feels like accountability. To the client it usually reads as excuses arriving in a queue.

If they ask why, tell them, briefly and honestly. If they do not ask, one clause is enough. "A file was mislabelled on our side" covers most of it.

The worst version is the paragraph about how busy the week was.

They do not need your week. They need to know it is handled.

Step 5: Name the one change that stops a repeat

This is the part that keeps the client.

Not "this will never happen again". You cannot promise that, and they know you cannot. Every business makes mistakes; the question is whether it learns from them.

Promise the process change instead, because that part you control. A second check before anything with a price goes live. A naming rule for files. A sign-off step before a deliverable leaves the building.

I write these down the same day. If the change only lives in the apology email, it did not happen.

This is the same habit I use for corrections on the VALORAE blogs: the fix goes in, the date moves, and the note says what changed. A client apology is the private version of that.

When to offer something back

Short answer: offer to redo before you offer money.

If the work can be redone, redo it, at your cost, and say so. That is the fair trade for most mistakes.

VALORAE Arc, the group's short-form clipping agency, puts this on the record for its own work: a wrong name burned into a caption is not something the client pays to fix.

Money is the right offer when the mistake cost them money, or when the work cannot be redone. A post that ran with the wrong offer during a sale. A deadline missed that cannot be recovered.

A discount offered by reflex is the wrong move.

It puts a price on the relationship, and it tells the client that the next mistake comes with a coupon. I wrote about protecting the rate in the post on discount requests; the same logic applies here. Give something specific that matches the damage, or give nothing extra and let the fix speak.

The sample email

Here is the shape I use. Swap the brackets.

Hi [name],

I want to flag a mistake on our side before you come across it.

[One sentence naming exactly what went wrong.]

I have already [what you did to fix it], and [the corrected version or link] is ready now.

To stop this happening again, we are [the one process change], starting with your next [deliverable].

I am sorry for the trouble it caused. Happy to get on a short call if you want to talk it through.

[your name]

Notice what is not in it.

No "sorry for any inconvenience". No "sorry if this caused confusion". No name of the person who slipped. And one apology, not three.

The apology sits near the end on purpose. By the time they reach it, they already know the problem is handled, so it lands as courtesy rather than panic.

What happens after

Most clients reply with some version of "thanks for letting me know".

Some will be annoyed, and they are entitled to be. Let them say it. Do not argue the size of the mistake, and do not apologize a second time to fill the silence.

Then do the boring part. Make the process change. Mention it once, casually, when it catches something later.

That is the moment the apology pays off, weeks after you sent it, when the client sees the check you promised doing its job.

If the client leaves anyway

It happens.

Sometimes the mistake was the last straw on a relationship that was already tired. Sometimes it was simply too big.

Hand everything back cleanly, keep the reply short, and do not relitigate it. I covered that exit in the post on how to respond when a client fires you, and the same rule holds: how you leave is the reference they give about you later.

The short version

• Tell the client before they find it, if it touches their work, money or audience.
• Start the fix before you send the apology.
• Name the mistake in one plain sentence, first line, and own it as the business.
• Skip the long explanation unless they ask.
• Promise a process change, never "it will never happen again".
• Offer to redo before you offer money, and never discount by reflex.
• Write the process change down the same day, or it did not happen.

If you hire editors to do the work, agree up front what counts as a revision and what counts as a redo; the eight lines in a video editor contract start with revision rounds and what one round is.

More notes like this live at tgsidd.com.