The typo in the company-wide email. The client's name spelled wrong. The "please find attached" with nothing attached. Everyone has a story, and almost every story was preventable with one structured minute before sending. Here's that minute, itemized.
The mechanical five (20 seconds)
These are the failures with the highest embarrassment-per-character ratio. Check them in order, every time:
- Recipient fields. Right person, right company? Autocomplete has ended careers. Check especially when two contacts share a first name, and check reply-all versus reply.
- Names and titles. The recipient's name, spelled as they spell it. Getting this wrong in an otherwise flawless email undoes all of it.
- The attachment. If the text says "attached," verify the paperclip. (Writing the email first and attaching before writing the send-off is the durable habit fix.)
- Numbers and dates. Reread every figure against its source. "June 15" vs "June 25" and "$1,500" vs "$15,000" are one keystroke apart and pass every spellcheck.
- Links. Click each one. Does it go where it claims, and is it the shareable version rather than your private draft?
The reading pass (30 seconds)
Now read the message once, aloud if circumstances allow, watching for:
- Skipped and doubled words — "the the," "I will not be able attend" — invisible to a silent skim, obvious out loud.
- The autocorrect specials — real words in wrong places: "now" for "not" (which reverses meaning), "public" missing its L, "manger" for "manager." Spellcheck approves all of these.
- One-read comprehension. Any sentence you had to read twice, the recipient will read three times or not at all. Split it.
- Tone spot-check. Last line and first line: do they sound like a person you'd want to receive email from?
The stakes multiplier
Scale the ritual to the blast radius. A chat message to a teammate merits a glance; anything mass-distributed, external, or permanent merits the full treatment — and for genuinely high-stakes pieces, two additions:
- Change the rendering. Preview the document as the reader will see it — export to PDF, print preview, or at minimum a different window. Fresh visual context surfaces errors your eyes have stopped seeing in the editor. It also catches formatting breakage that the editing view hides.
- Borrow eyes or tools. A colleague's thirty-second read catches what familiarity blinds you to. When no colleague is handy, a rewriting tool like Wrivio serves as a decent proxy: run the text through it and scan the proposed diff — the places it wants to change are frequently the places something is genuinely off, even when you keep your own wording.
Make it automatic
A checklist you have to remember is a checklist you'll skip under deadline — which is precisely when errors happen. Pin it: a sticky note on the monitor, a text expander snippet, or for teams, a shared pre-send checklist for recurring high-stakes sends (newsletters, client deliverables) tracked somewhere visible like MyTeamTask so the ritual survives personnel changes.
Sixty seconds. It's the cheapest insurance in professional life.
