Short answer: A professional apology names the specific thing you did, takes responsibility for it without excuses, and says what you'll do next - in that order. Skip "sorry you feel that way" and "sorry if"; both apologise for the other person's reaction instead of your action, which is why they backfire.
Everyone gets it wrong at work sometimes - a sharp message, a missed deadline, a claim that turned out to be false. What separates people who stay trusted from people who quietly lose standing isn't the number of mistakes. It's whether they know how to apologise in a way that actually repairs things.
Here's how to do it, and the exact wording for the situations that come up most.
Researchers who studied the components of an apology (Lewicki, Polin & Lount, 2016) found that of the six things people typically include, acknowledgement of responsibility is the one that most predicts whether the apology is accepted. An expression of regret alone - "I feel terrible about this" - is among the weakest.
In plain terms: saying you feel bad is not the same as taking responsibility. A professional apology has three parts, and only one of them is the word "sorry":
Before the examples, cut these. They feel like apologies but read as dodges:
Intent belongs nowhere in a repair. "I didn't mean it that way" explains you; it doesn't fix them. Say what you did, not what you meant.
Subject: My earlier message
Rereading my message from this morning - it came out sharper than I intended. I wasn't annoyed with you, I was frustrated with the deadline, and that shouldn't have landed on you. The question still stands, but the tone was mine and I'm sorry for it.
Why it works: names the action (the sharp message), takes responsibility ("the tone was mine"), and separates the trigger from the person.
Quick heads-up before you plan around it: the report won't be ready today as promised. That's on me - I underestimated the vendor export. Realistic date is Tuesday. If today is immovable, I can send the top-line numbers now and the full version Tuesday. Sorry for the short notice.
Why it works: no drawn-out self-flagellation, just the fact, a new commitment, and an option. The apology is one line because the useful information is the rest.
Correction on what I said Tuesday: I stated the migration wouldn't affect EU accounts. It does - about 400 of them. I was reading the staging config, not production. Apologies to anyone who planned around "no EU impact"; that's changed.
Why it works: it corrects the error at the same volume it was made, so the team isn't left planning against bad information - which is the actual harm.
I let you down on the handoff - I said I'd send the brief Friday and it slipped to Monday, which pushed your part back. That's mine, and I know it cost you the weekend buffer you'd planned. Going forward I'm blocking Thursday afternoons for handoffs so this doesn't repeat.
Why it works: it names the concrete cost to them (the weekend buffer) and ends with a mechanism, not a promise to "be better."
Two cases where you should not apologise:
If you remember nothing else: name what you did, own it plainly, say what's next. That's the whole thing. Most professional apologies fail not because they're too short, but because they spend their words on feelings and excuses instead of those three moves.
Be specific and brief. Weakness reads as vagueness and over-apologising ("so so sorry, I feel terrible"). Strength reads as naming exactly what you did, owning it in one line, and stating the fix. Confidence in an apology comes from precision, not from softening.
Match the channel to the stakes. A minor, factual slip (a late file, a wrong number) is fine in writing. Anything emotionally charged or about someone's standing is better in person or on a call - text strips tone and can make a sincere apology read as flat. If you do it live, follow up with one written line so the resolution is on record.
It's weak because it's generic and impersonal - it names no specific action and takes no real responsibility. Replace it with the actual thing: "Sorry the report was late" beats "sorry for any inconvenience caused."
Don't apologise again - a second apology asks them to manage your discomfort about not being forgiven. State once that you're available to talk, then let reliable behaviour do the rest. Trust after a mistake is rebuilt through kept commitments over time, not better wording.
Stop apologising and change the system. A pattern signals something structural, and words don't touch structure. Say what you've actually changed - a calendar block, a checklist, an automated reminder - and tell the other person what to do if it happens again.
Real situations, before/after examples, and a quiz. Chapter 1 is free.
Open the course