All people, messages, amounts and replies in these examples are fictional. Adapt the wording to your situation; no script guarantees a response.

Before you begin

Speed matters when other people may act on incorrect information. Do not wait for a perfect fix before flagging a problem that needs attention. If there is a safety, security or data incident, use the required incident channel promptly; a polished message should not delay it.

Write four notes: the error, known impact, immediate action and help needed. Avoid filling gaps with reassuring guesses. In the fictional example below, Jules sent a client a report containing last month’s figures.

What to say: example wording

Flag the error

“I need to flag a mistake: I sent the client report with last month’s figures in the summary table. I spotted it at 10:20. It went to three people, and I don’t know yet whether anyone has used it.”

This opening names a concrete problem and separates known distribution from unknown downstream impact.

Propose the next action

“I’ve made a corrected version and checked the summary against the source sheet. Can you look at it before I send the correction? I’ll update you by 11 either way.”

Ask for the help that matters. Do not promise an outcome controlled by someone else; promise a status update you can deliver.

Send a short recap

“Quick recap: I sent the corrected report at 11:05 and marked the earlier file as out of date. I’m checking the export template and will suggest a validation step tomorrow. Sorry I missed the old table.”

The correction, apology and prevention step have separate jobs. State only actions that have actually happened.

What not to say, and why

  • “It’s probably fine.” That is speculation if you have not checked the impact.
  • “The spreadsheet did it.” A tool problem can be relevant, but explain your own action and investigate the cause without prematurely assigning blame.
  • “I’m terrible at this job.” Your manager needs facts and a response plan; self-condemnation makes them manage your distress as well.

How the other person might react

These are invented possibilities to prepare for, not predictions.

They are frustrated

“I understand why you’re concerned. The immediate correction is ready. After that, I’ll walk through how this happened.” Acknowledge the impact without arguing that you meant well.

They ask a question you cannot answer

“I don’t know yet. I’m checking whether the figures were used in the meeting and will include that in the 11 o’clock update.” Do not guess to fill the silence.

They want a prevention plan now

“My current hypothesis is that the summary tab was not refreshed. I’ll verify that before proposing the fix.” An untested explanation is not a root cause.

Close the loop after the correction

A useful follow-up says what changed and what remains open. If the issue is resolved, confirm the resolution with the people who need it. If it is not, keep the promised update time and explain the next dependency.

Make the prevention step proportionate: a source check, a clearer owner or a review before sending. Avoid promising that no mistake will ever happen again. You can commit to a specific check that addresses this failure.

Rehearse it first

Practice a concise first report and an honest “I don’t know yet.” The aim is to make the facts easier to say, not to make the mistake sound smaller.

Pretake on iPhone lets you practice messages with AI and rewind to try different words. It is AI practice, not the real person; a simulated reply cannot tell you what they will think or say. Practice messages are never sent to them.

Try Pretake on iPhone

18+ · Free to start · In-app purchases · Prices and limits

Prefer a worksheet? Use the free conversation planner. Read how imported chat text is processed before bringing private context.