You notice an error in a file that has already been sent. A date is wrong, but you do not yet know who used that version or whether it changed anyone’s next step. Waiting until you can explain the whole situation may feel safer. But the people who can help check its reach may need to know that there could be an issue.
You can send a useful first update without guessing at the consequences. Separate what you have confirmed from what still needs checking, and ask what to do next.
Check whether a formal reporting route applies
Before sending a routine message, consider what the error could involve. If it may affect someone’s safety, personal or customer information, money, access, a regulated record, or another formal process, use the reporting route your organization requires. That may be a designated team or incident channel rather than your direct manager. Do not delay a required report while trying to work out the full impact on your own.
For an ordinary work error without a special process, contact the manager or person responsible for the work. If you are unsure who owns the next step, say so and ask who should be involved.
Write down the confirmed facts
Make a short note before you reach out. Include:
- the specific file, message, decision, or task that may be wrong;
- when you noticed it and which version is involved;
- what you know about who received or used it;
- what you still do not know; and
- any action you have already taken that was safe and within your role.
Keep facts separate from guesses. “The date in the schedule I sent this morning is incorrect” is different from “No one will rely on it” or “The whole schedule is unusable.” If you have not confirmed the cause, do not present a possible explanation as fact.
Send a clear first update
Use the channel your workplace expects for this issue. A message might say:
“I need to flag a possible error in the schedule I sent this morning. The date in row 12 is incorrect. I’m checking which version was shared and whether anyone has relied on it, so I don’t know the full impact yet. I have not changed the shared file because I’m not sure which correction is authorized. Who should help confirm the scope? I’ll update you by 2 p.m., even if the check is still in progress.”
Adapt every detail to what actually happened. If you already made an authorized correction, say what you changed. If you did not, do not imply that you did. Promise a follow-up only when you can keep it; otherwise, ask when the person needs an update and set a reminder.
The first message does not need to explain why the error happened or propose a complete fix. It needs to help the right people understand what is known and decide on the next check.
Avoid a private fix that could make the record less clear
You may be able to correct a small error safely within your role. If other people may already have used the information, or if the correction affects a shared record, ask before replacing or deleting anything. Keep the relevant history intact and use the normal correction process. Quietly changing a file or retracting a message can make it harder to tell what was sent and who may need an update.
If the issue is still spreading, follow the required process promptly. You do not need to conduct an investigation beyond your role before raising it. You can say, “I’m not sure what is safe to change yet, so I have paused further distribution and am asking who should review it”—only if you have actually paused distribution.
Answer follow-up questions without filling gaps
Your manager may ask when the error happened, who received the material, or what you have checked so far. Answer directly when you know. If you need to verify something, say, “I don’t know yet. I can check the version history and report back.” That is more useful than a confident guess that later needs correcting.
If your action caused a problem, a brief apology may fit: “I’m sorry I sent the incorrect version. I’m checking who received it and will share the correction through the agreed process.” Then return to the facts and next action. Calling yourself careless does not clarify what needs to happen.
Close the loop when you know more
When the scope becomes clearer, send a short update: what was affected, what was corrected, who has been informed, and what remains open. Use any required record or approval process. If the issue is larger than you first thought, update the appropriate people as soon as you can rather than waiting for a perfect summary.
After the practical issue is handled, you can review one prevention step that matches what you have actually learned: a clearer version name, an added check, or instructions that were missing. Do not assign yourself a cause before it is established. If the incident leaves you stuck in harsh self-judgment, our separate guide to what to do after a mistake without beating yourself up covers that emotional step.
You do not need a complete explanation before you speak up. Name the error, mark what is still unknown, and agree on how the right people will check it.
Selected for this topic
Useful next reads
Four editorially reviewed guides chosen for relevance, not at random.
Self-worth & confidenceHow to Stop Taking Feedback Personally at Work
Self-worth & confidenceNervous Before a Job Interview? A Practical Plan for What to Do
Self-worth & confidenceDon’t Know an Answer in a Meeting? How to Respond Clearly
Understanding emotionsWhat to Do After a Mistake Without Beating Yourself Up