Professional
Professional Alternatives to “Sorry” (Without Sounding Cold)
Better ways to apologise or acknowledge a mistake at work, from genuine apologies to lighter acknowledgements, with tone notes and examples.
By Vocabaura Editorial · Published 6 August 2026 · 7 min read
Quick answer
Use “I apologise” or “I’m sorry for the delay” when you genuinely owe an apology, “thank you for your patience” when you want to acknowledge inconvenience without over-apologising, and “I should have caught that” when you want to own a mistake plainly. Save “sorry” itself for smaller, casual moments — repeating it too often dilutes it and can read as anxious rather than professional.
“Sorry” is one of the most overused words in professional writing. It gets attached to emails that don’t need an apology at all (“sorry to bother you”), to genuine mistakes that deserve a fuller acknowledgement, and to everything in between. The result is that “sorry” starts to sound like a verbal tic rather than a meaningful statement — and worse, over-apologising can make you sound less confident and less in control of a situation you’re actually handling well.
The fix isn’t to avoid apologising. It’s to match the words to the size of the situation: a real mistake needs a real apology, a minor inconvenience needs a lighter touch, and a request for someone’s time needs no apology at all — just courtesy.
Quick Answer
For genuine mistakes, use “I apologise” or “I’m sorry for the delay” and say plainly what went wrong. For minor inconveniences, replace “sorry” with an appreciation of the other person’s patience or flexibility. For requests that don’t need an apology at all, drop “sorry” entirely and just ask directly.
When You’ve Made a Real Mistake
I apologise for…
Formal, direct, and appropriate for client-facing or written communication. Example: “I apologise for the error in yesterday’s invoice — a corrected version is attached.”
That was my mistake
Plain, accountable, and good for internal team communication where owning the error matters more than formality. Example: “That was my mistake — I sent the old file by accident. Here’s the current one.”
I should have caught that
Useful when the error was preventable and you want to show you understand why it happened, not just that it happened. Example: “I should have caught that before it went to the client. I’ll double-check before sending next time.”
I regret the confusion this caused
Slightly more formal and distancing; useful in official or public statements where you’re representing a team or company rather than speaking purely for yourself. Example: “We regret the confusion this caused and have updated the schedule accordingly.”
When It’s a Minor Inconvenience
Thank you for your patience
Reframes a delay positively instead of apologising for it repeatedly. Example: “Thank you for your patience while we sorted out the access issue.”
Thanks for bearing with me
Warmer and slightly informal; good for colleagues you know well. Example: “Thanks for bearing with me — I was juggling two calls at once.”
Appreciate your flexibility
Best when someone has adjusted their schedule or plans for you. Example: “Appreciate your flexibility in moving the meeting to Thursday.”
When You Don’t Need to Apologise at All
Quick question
Replaces “sorry to bother you” when asking something reasonable. Example: “Quick question — do you have the latest version of the deck?”
Following up on…
Replaces “sorry for chasing” when you’re simply doing your job. Example: “Following up on the contract I sent last week — any updates?”
To confirm…
Replaces “sorry, just to check” when clarifying details that are genuinely worth clarifying. Example: “To confirm, the deadline is Friday at 5pm, correct?”
| Situation | Say instead of “sorry” | Why it works |
|---|---|---|
| A genuine error you caused | “I apologise for…” / “That was my mistake” | Shows accountability without excessive self-criticism |
| A short delay or wait | “Thank you for your patience” | Acknowledges the inconvenience while sounding composed |
| Asking a reasonable question | “Quick question…” | Removes an unneeded apology from a normal request |
| Following up on something owed to you | “Following up on…” | Asserts your right to a timely response |
What to Avoid
- Don’t stack apologies — “I’m so sorry, really sorry about this” reads as anxious rather than sincere.
- Don’t apologise for things outside your control, like someone else’s late reply or a system outage; acknowledge the impact instead of taking blame.
- Don’t use “sorry” as a placeholder for “excuse me” in every request — it weakens the word for moments that genuinely need it.
- Don’t over-explain a small mistake; a short, clear acknowledgement is more professional than a long justification.