How to handle an email you sent by mistake
The one-sentence retract, when a follow-up email actually helps, and the surprisingly common cases where silence is the correct move
You've just sent it. The attachment was wrong, or the recipient was wrong, or the tone was wrong, or the whole thing was a draft you never meant to send at all. Your stomach does that small, cold thing. You are now going to make a decision in the next ninety seconds that will shape how much of tomorrow you spend thinking about this.
Most people make it worse. Not because they panic — because they over-explain. What follows is the shape of the thing, in the order it actually happens.
Stop moving for sixty seconds
Before you type anything, close the sent email and look away from your screen. I mean this literally. The instinct is to fire off a follow-up while the adrenaline is still doing its work, and that is exactly when people write three paragraphs when they needed one sentence.
Use that minute to answer two questions, in this order:
- Who actually saw this? One person? A distribution list? A client? Your skip-level? The answer determines everything about your response, and it is not always what you assumed in the first flush of panic. Check the To, Cc, and Bcc lines slowly.
- What is the actual damage? Not the imagined damage. The imagined damage is always worse. Wrong attachment to a colleague you trust is a shrug. Wrong attachment to a competitor is a phone call to your manager. There is a wide band between those, and you are probably in it.
The thing tutorials skip: most email mistakes are, in the recipient's inbox, one of forty items they will half-read on their phone between meetings. You are the only person watching this in slow motion. That doesn't excuse doing nothing — but it should lower the temperature of what you write next.
Also: forget the Recall function. In Outlook it works maybe 30% of the time and only within the same organization, and it sends a loud notification saying you tried. Gmail's Undo Send is only useful in the first 30 seconds, and if you're reading this, you're past that. Assume the email has arrived and stays arrived.
The single-sentence retract
For about 80% of email mistakes, the correct response is one sentence, sent within a few minutes, from the same thread. Not a new email. Reply to your own message so it sits directly underneath the error.
The template, which you can adapt:
Apologies — please ignore the previous message; wrong [attachment / recipient / thread]. Correct version below.
That's it. No "so sorry for the confusion," no explanation of how it happened, no self-deprecating aside about needing more coffee. The sentence does three things: it acknowledges the error, it tells the reader what to do (ignore it), and it points to the fix. Anything beyond that is you managing your own embarrassment at the reader's expense.
If you have a corrected version, attach or paste it in the same reply. If you don't have one yet, write: Correct version to follow shortly — and then actually follow shortly, meaning within the hour, not tomorrow.
The wrong-recipient case has a slightly different script. If you sent something to the wrong person entirely — Sarah instead of Sara, external instead of internal — reply to them (the wrong recipient), not to your intended one:
Sent this to you by mistake — please disregard and delete. Apologies for the clutter.
Then send the original, correctly, to the person who was supposed to get it. Do not mention the mistake in that second email. They don't need to know.
When a second email is actually warranted
Sometimes one sentence isn't enough. The rough test: a second, longer email is warranted when the mistake has caused someone to do something, or is about to.
Examples:
- You gave a client the wrong price and they've already forwarded it to their finance team.
- You cc'd someone confidential onto a thread and they've now been included in three replies.
- You said something in a message — a tone, a critique, a piece of information — that a person read and reacted to before you could pull it back.
In these cases, the retract still comes first, in one sentence, immediately. The second email — or more often, a phone call or a walk-over to someone's desk — comes after you've thought about it for at least fifteen minutes. Its job is not to apologize again. Its job is to fix the downstream thing: the wrong number in someone's spreadsheet, the meeting that got scheduled on false information, the person who is now in a thread they shouldn't be in.
Write it plainly. Say what went wrong, say what you're doing about it, say what you need from them, if anything. Do not perform contrition. Senior people, in my experience, respect a clean fix and get uneasy around excessive apology — it starts to feel like you're asking them to reassure you.
When to say nothing at all
This is the part nobody tells you.
If the mistake is: a typo, a slightly awkward phrasing, a missing word, a forgotten "thanks," a reply-all where the reply-all was mildly unnecessary but not harmful, a message sent five minutes later than you meant to — do nothing. Sending a follow-up to correct these draws attention to something the recipient almost certainly did not notice and would not have cared about if they had.
The heuristic I use: if the correction email would itself be embarrassing to send, don't send it. "Sorry, I meant their not there" is worse than the original error. So is "Just realized I didn't say hi at the top of that last one!"
The same goes for tone mistakes that only exist in your head. You reread the email an hour later and think it sounds curt. It probably doesn't. Curtness is the default register of work email and nobody notices it but you. Send a warmer message next time. Don't retroactively soften this one.
The hardest version of "say nothing" is when you've sent something mildly unprofessional — a venting message, a joke that landed weird — to someone who is going to remember it but not act on it. The instinct is to over-correct. Resist. A follow-up email calling attention to your own lapse doubles its footprint in the recipient's memory. Let it recede.
You will send a bad email this year. You will send a worse one within five years. Everyone at your company has, including the people you're most afraid of looking foolish in front of. The skill isn't avoiding the mistake — it's the ninety seconds after, and how small you can keep your response.
The smallest version of this practice, for this week: the next time you catch a minor error in a sent email — a typo, a missing "please" — do nothing. Just watch what happens. Which is, almost always, nothing.
Related
How to ask for a raise when your manager already thinks you are paid fairly
The three-part case—market comp, scope creep, forward risk—and the exact words to open the meeting
When to quit — the signs that mean it, and the ones that only feel like they do
The difference between quitting on a bad day and quitting for a reason that survives a calendar and a pay stub
"Follow your passion" is bad advice — here is what to do instead
Steve Jobs's 2005 line about passion sounds like a compass, but the research on skill capital points somewhere else