Start here

Use the relevant reporting process promptly and state what happened, what is known about the effect and what action has already been taken. Separate a proposed fix from confirmed facts. Preserve required records and obtain the right authority before making consequential changes.

You notice that a document went to the wrong recipient. A vague message saying something went wrong leaves others unable to respond appropriately.

Use the relevant reporting process promptly, particularly if private data or security is involved. State what you know, when it happened and who or what may be affected. Do not guess at an impact you have not checked.

Separate the facts from the proposed fix

Explain any action already taken and ask about the next step if it requires another person's authority. Preserve useful records according to the organisation's requirements. Avoid deleting evidence to make the mistake less visible.

For an ordinary, low-impact error, a clear correction and revised document may be sufficient. Follow through on what you agreed and confirm when it is done. Later, examine the step that allowed the mistake and make a proportionate change. The immediate message should help people deal with the situation, leaving room for a calmer review once the necessary response is underway.

Correcting an ordinary document version error

An illustrative example

Suppose you send an old, non-sensitive agenda to the intended meeting group. You check which version went out and send a correction through the same normal channel: "The agenda in my previous message was the earlier version. Please use this revised file; the discussion order has changed." You identify any immediate effect, such as someone preparing for the wrong item, and clarify the updated arrangement. You keep the relevant record rather than silently replacing the file and hoping everyone notices. Afterwards, you move old drafts into a clearly labelled location. If the error had involved a wrong recipient or sensitive material, you would use the organisation's reporting process before improvising a response.

Provide facts people can act on

Tick the steps as you work through them.

0 of 5 steps checked

When the impact is still unknown

Say what has been confirmed and which part is being checked. Avoid filling the uncertainty with a reassuring or alarming guess. Follow the relevant incident or correction process and preserve records as required. For an ordinary low-impact mistake, the next update can confirm the corrected version and whether any further action remains. Review the cause after the immediate response is underway. A proportionate change should address the step that allowed the error, with responsibility and timing made clear rather than an absolute promise that no mistake can recur.

A factual correction note

Your notes stay in this page. Copy them before leaving; they are not saved or sent to us.

Next useful stepHow to choose a private setting for a sensitive conversation →

Written by the Painless Success editorial team. Our upcoming book, Painless Success, brings these ideas together. Preview its contents or join the release waitlist.