Accuracy Without the Applause: Correcting a Colleague Calmly

You are halfway through a shared document when a number jumps out at you. The figure in the summary does not match the figure in the table. It is not a disaster. It is a slip. But it is the kind of slip that could travel: into a deck, into a client email, into a meeting where someone repeats it with confidence.

So you have a choice. You can say something and risk making your colleague feel small. Or you can say nothing and risk the error going wider. Most of us wobble between the two, then send a message that starts with 'Just to flag...' and ends with an apology for existing.

There is a better way. Correction at work is not a performance. It is maintenance. The aim is not to prove you noticed. The aim is to keep the work accurate and the relationship intact.

First, ask whether it needs saying

Not every mistake needs a correction. Before you type, run three quick tests.

Is it material? A wrong figure in a client report matters. A stray comma in an internal note usually does not. If the error would change a decision, cost money, mislead someone outside the team, or embarrass the person later, it is worth raising. If it is a matter of style, let it go.

Is it timely? A correction that arrives before the document is sent is helpful. A correction that arrives three weeks after everyone has moved on is just archaeology. If the moment has passed and nothing is at stake, file it under 'not now'.

Is it yours to raise? If you own the document, the client relationship, or the piece of work, yes. If you are a bystander in someone else's project, you might still flag it — but quietly, to the person who can fix it, not to the whole thread.

If the answer to all three is no, the kindest and most professional move is often silence. Accuracy matters, but so does knowing which battles are actually yours.

The private correction: small, specific, and easy to act on

Most corrections should happen one-to-one. A direct message, a quick call, or a quiet word after the meeting. The goal is to make the fix easy, not to make the mistake memorable.

A useful shape is: flag, fix, forward. Name what you noticed, name the correct version, then point to the next step. Keep it short. Avoid 'actually'. Avoid 'just'. Avoid anything that sounds like a teacher's red pen.

Try:

• 'I might be reading this wrong — should the Q3 figure be £42k rather than £24k? Happy to be corrected.'
• 'Small flag on slide 4: I had the client as Fenwick & Co, not Fenwick Group. Thought you would want to know before it goes out.'
• 'Quick one — the deadline in the note says Thursday 12th, but I think it is Thursday 19th. Can you confirm?'

Notice what these do. They put the uncertainty on you, not on them. They name the specific thing. They do not ask the person to explain themselves. And they leave the door open for you to be wrong, which — let us be honest — you sometimes will be.

If the mistake is repeated or part of a pattern, do not pile it into the same message. Fix the immediate thing first. Then, if it matters, have a separate conversation about the process: 'I have noticed a few date slips in the shared tracker. Is there a version-control thing we should tighten up?' That is a different chat, and it should happen later.

The public moment: protect the person, fix the fact

Sometimes the correction has to happen in the room. A client name is mispronounced in a meeting. A figure is quoted in a Teams call. A wrong date is agreed in front of six people.

In public, your job is to correct the fact without correcting the person. Do not say 'You mean...' Do not say 'Actually, it is...' Do not turn it into a mini-lesson. Use a question that gives the other person an easy way to land.

• 'Quick check — I had that as [correct name]. Is that right?'
• 'Can we confirm the figure? I have £42k in my notes.'
• 'Just so I am clear — the deadline is the 19th, yes?'

Then move on. Do not wait for a thank-you. Do not add 'I thought you should know' or 'I noticed earlier'. The moment has been fixed. Let it be fixed.

If the person doubles down on the wrong version, do not argue in public. Say, 'Let us check after this' and park it. A public debate about who is right is almost always more costly than the original error.

In email, the same principle applies. If you can, reply only to the sender. If the whole group needs the correction, keep it neutral and for the record: 'Small correction for the record: the deadline is Thursday 19th, not Thursday 12th. Apologies for any confusion.' If the error was yours, own it plainly. A boring, specific apology rebuilds trust faster than a long one.

When to let it go

Some corrections are not worth the relational cost. A harmless typo in a chat message. A slightly loose phrase in a brainstorm. A point of style that no one will remember by lunchtime. Let those go.

Also let go of the urge to correct the same person in front of others more than once. If you have flagged something privately and it is fixed, you are done. Bringing it up again in a meeting does not make you thorough. It makes you the person who keeps score.

And if you are the one being corrected? Try to hear the fix, not the fanfare. A short 'Thanks — good spot' is enough. You do not need to explain how the mistake happened unless someone asks. The work is better. That is the point.

A thirty-second routine

Next time you spot a colleague's slip, run this:

1. Pause. Name the stake: does this change a decision, a cost, or an external message?
2. Choose the smallest channel. Direct message or quick call beats a group thread.
3. Lead with a question or a flag. Give the other person room to be right.
4. Name the fix, not the fault. Say what the correct version is.
5. Move on. Close the loop with a simple 'Thanks — updated' and leave it there.

Accuracy is a team habit, not a trophy. The best correctors at work are rarely the loudest. They are the ones who notice the small thing, fix it quietly, and make it easy for everyone to keep moving. That is not pedantry. That is good communication.