How to correct someone's mistake politely
To correct someone's mistake politely, do it privately, assume good faith, and be specific about what's wrong and what right looks like - leaving room that you might be the one missing context.
Correcting someone's mistake politely is about fixing the work while protecting the person. Do it privately, assume good faith, and be specific about what's wrong and what right looks like. Leaving room that you might be the one missing context - 'unless I'm misreading this?' - costs nothing and saves you when you are.
9 polite ways to correct someone's mistake
Ordered from most gentle to most direct.
- 1.“Quick thing I spotted in [document] - I think [item] should be [correct version]. Easy fix!”
- 2.“Small flag: the [figure/date/name] in [place] doesn't match [source]. Worth a double-check?”
- 3.“I might be missing context here, but should [item] be [correct version]? Happy to be wrong.”
- 4.“Before this goes wider - one correction needed in [section]: [what and why].”
- 5.“I noticed [error] in the version that went out. Not a big deal, but let's fix it before [next milestone].”
- 6.“Heads-up: [item] is based on the old [data/spec] - it changed on [date]. Here's the current version.”
- 7.“There's an error in [deliverable] that we should correct today: [specifics]. Can you take it or should I?”
- 8.“I want to flag this directly because it's now affecting [downstream impact]: [error]. Let's fix it and check where else it landed.”
- 9.“This same error has come up a few times now, so let's solve it properly - can we walk through the process together and find where it keeps slipping in?”