Most apologies at work fail in one of two ways. They’re too vague to be about anything, or they’re really a request for the other person to make you feel better.
“Sorry if that came across badly.” “Apologies for any confusion.” “I’m sorry you feel that way.” Each one sounds like an apology and does the opposite. It tells the other person you still don’t see what happened, or that you think the problem is their reaction.
What does an apology that lands actually contain?
Researchers have taken apologies apart to see which pieces people value. Roy Lewicki and colleagues worked with six components:
- Expression of regret
- Explanation of what went wrong
- Acknowledgement of responsibility
- Declaration of repentance, which in plain terms means saying it won’t happen again
- Offer of repair
- Request for forgiveness
Across two studies, one with 333 working adults online and one with 422 business students, apologies containing more of the components were rated as more effective than those containing fewer. Acknowledging responsibility came out on top in the first study. Offering repair and committing not to repeat it came out on top in the second. Asking for forgiveness came last in both.
Those were ratings of written apologies in a scenario, not real colleagues. They tell you what people say they want rather than what changes how they treat you. The pattern is still worth using.
Which parts matter most at work?
Say what you did, plainly. “I told the client the figures were final before you’d signed them off.” Not “there was a miscommunication”. If the sentence has no “I” in it, it probably isn’t owning anything.
Say what it cost them. “You had to take the client’s call and explain something you hadn’t agreed to.” This is the part people are listening for, because it shows you’ve seen it from where they were standing. If you don’t know what it cost them, ask, and let them answer without finishing the sentence for them.
Explain only if it helps them. An explanation is useful when it tells them something they need, such as whether it’s likely to happen again. It turns into an excuse when its job is to shrink your share. A quick test: would you still say it if it made you look worse?
Offer something concrete. What will you put right, and what will you do differently? “I’ll call the client this afternoon and correct it, and from now on nothing goes out until you’ve signed it off.” Specific enough that they can check it.
Leave out the request for forgiveness. “Can we put this behind us?” asks them to do work on your timetable. It came last in both of Lewicki’s studies, and it’s easy to see why. Their confidence in you is theirs to give back when they’re ready. You can’t ask for it back, and you can’t demand it.
Why don’t words on their own hold?
Because an apology is a claim about the future, and the other person can only check it later.
Maurice Schweitzer and colleagues tested this in a repeated trust game with 262 participants. After someone had behaved untrustworthily, a consistent run of trustworthy behaviour restored trust. A promise helped at first but not in the long run. The apology on its own made no significant difference. Where the bad behaviour had involved deception, trust never fully came back, even with a promise, an apology and good behaviour afterwards. Young participants in a laboratory game, not a team at work, but the direction is hard to ignore. What restored trust was what people did next.
So the apology is the opening, not the repair. It earns you the chance to show something different. If the next three weeks look exactly like the last three, the apology becomes one more thing you said.
That’s why the commitment inside your apology should be small enough to keep. “It’ll never happen again” is a big promise that’s easy to break. “I’ll send you the draft by Wednesday so you can check it before it goes” is a small one you can keep this week. Keep it, and the apology starts to mean something.
An apology is a promise about your behaviour. They’ll believe it when they’ve seen the behaviour.
When should you apologise?
When you understand what you’re apologising for, and not before.
An apology rushed out in the first five minutes is often for the wrong thing, because you haven’t yet found out what the break meant to them. The repair page sets out that order: understand what broke, put right what you can, then give them evidence they can check.
Don’t wait so long that the silence says something of its own, though. Ask first, listen properly, then apologise for what you now know you did.
Does the kind of mistake change the apology?
Yes. If you couldn’t deliver, an apology plus a visible change in how you take on work usually goes a long way. If you weren’t straight with someone, the apology is still necessary but does less, because owning it confirms what they feared. Both Kim’s and Lewicki’s studies found apologies did better after competence breaches than after integrity ones. The difference between the two kinds of let-down changes where the rest of your effort needs to go.
What should you avoid saying?
- “Sorry if…” A conditional apology questions whether anything happened at all.
- “Sorry you feel that way.” This apologises for their reaction, not your action.
- “Sorry, but…” Whatever follows the “but” cancels what came before it.
- “I’ve said sorry, what more do you want?” The honest answer is: evidence.
When an apology isn’t the right tool
Not every problem needs one. If you made a decision you’d make again, apologising for it would be untrue. Acknowledge what it cost people, and explain why you made it. “Explain the reasoning behind decisions that impact others” is one of the twenty behaviours that strengthen trust for exactly this situation. Don’t pretend to regret what you don’t.
And if a formal process is running, or anyone’s safety is in question, follow the process. Nothing here is HR or legal advice.
The research below tells us which parts of an apology people value and that behaviour afterwards matters more than the words. It doesn’t test the Trust Leader approach, and no apology guarantees anyone’s confidence comes back. Reviewed 4 October 2026 by Scott Hunter.