Evergreen

Recognition messages

Thanking Someone for Catching an Error: 10 Messages

Name the check that found the error and the next step it made possible. Keep blame out of the thank-you.

Reward the check that worked

“Thank you for checking the recipient list before sending. We corrected it before the message left the team.” That message identifies a repeatable practice and an observed result. The examples below are fictional and should not supply facts for a real incident.

When a colleague catches your own error, resist the urge to explain how busy you were. A short acknowledgement makes it easier for them to raise the next concern. If the error needs formal reporting, complete that process separately.

Keep the recognition proportionate

A wrong link and a stopped payment carry different consequences, but both can deserve a thank-you. You do not need to invent a financial saving to make careful work count. Describe what the person checked and what happened next.

For a broader pattern of careful work, use attention-to-detail messages. This page covers an identifiable error and the contribution of the person who found it.

10 messages you can send

  • Thank you for checking the date range before the report went out. We corrected the comparison while there was still time to explain it properly.

    On a reporting error

    Credits the check and its timing.

  • You noticed the account number didn’t match the approved record and stopped the payment. Thank you for following the check even when the request looked familiar.

    Private finance recognition

    Recognises a control without exposing payment details.

  • Thanks for questioning the total in my draft. I had included one row twice, and your note made it easy to find.

    Owning your own error

    Takes responsibility without turning the correction into a contest.

  • Your test caught the missing permission before release. Thank you for trying the flow with a new account as well as an admin account.

    On a software check

    Names the test condition that mattered.

  • I appreciate you flagging the wrong attachment immediately. We could correct the message and follow the reporting process promptly.

    On quick disclosure

    Thanks the response without minimising a possible information incident.

  • Thanks for noticing that the units had changed in the supplier sheet. That explained why the order looked unusually large.

    On a purchasing check

    Makes the observation concrete.

  • You asked us to verify the recipient list before sending. Thank you for making that pause feel like part of the job.

    On a prevention habit

    Recognises a repeatable check rather than a heroic rescue.

  • Thank you for catching the broken link in the instructions. New starters would have reached a page they couldn’t open.

    On a small but useful correction

    Shows why an ordinary error was worth reporting.

  • Your second count found the mismatch, and you recorded it clearly enough for us to investigate. Thanks for staying with the check.

    On an inventory discrepancy

    Credits evidence gathering without guessing the cause.

  • Thanks for telling me directly and kindly. We fixed the mistake without making the conversation harder than it needed to be.

    On respectful correction

    Acknowledges how the error was raised.

What makes one land

  • Describe the check rather than identifying who made the mistake.

  • Avoid hypothetical savings unless someone has verified the calculation.

  • Use a private note if the error involves personal, security or financial information.

  • If the same error recurs, recognise the person who improves the process as well as the person who catches it.

Questions people ask

How do I thank someone for correcting my mistake?

Acknowledge the correction and say what it helped you do. “Thanks for checking the date range; I corrected the comparison before sending” accepts responsibility and gives the other person useful credit.

Should the thank-you mention who made the error?

Usually the check is the useful part to recognise. If it was your own mistake, you can own it plainly. Avoid naming another person publicly or using praise for the reviewer to embarrass the author.

Can I say they prevented a costly incident?

Only if you have evidence for that claim. Otherwise describe the actual result: the payment was paused, the document was corrected, or the release waited for a fix. A precise modest statement is enough.

The values behind it

Where it fits

Other occasions

Only pay for active users who use Evergreen

Lots of support, with a help center and direct email options

Cancel at any time, so why not give us a try

Start feeling good about work

For only $3.99 per active user a month. In the 14 day free trial we don’t plant real trees, but you can skip the trial if you like.

No credit card needed • No setup costs