From Draft to Send: The Complete Checklist to Prevent Email Disasters

Why Checklists Beat Willpower

Atul Gawande's *Checklist Manifesto* made the point in surgery. Airline pilots have known it for decades. Software engineers know it as pre-commit hooks. The lesson generalizes: complex, high-stakes, repeatable activities are performed reliably not through willpower but through externalized checklists.

Email fits that description. It is complex (recipients, threads, attachments, tone, policy), high-stakes (deals, relationships, careers), and repeatable (40+ times per day for most professionals). Yet almost no one uses a checklist. The most common approach is "read it once and hope."

This piece is the 25-item checklist that professional writers, sales leaders, and support managers use — either manually or automated — to prevent the common failure modes. Print it, memorize it, or automate it with a tool like Presend. The specific method matters less than the discipline of running through the list.

Category 1: Recipients (5 items)

1. Every address is intentional. No autocomplete-selected wrong Sarah. Every recipient has a specific reason to be on the message.

2. To/CC/BCC split is correct. People in "To" are expected to act. People in "CC" are informed. People in "BCC" are informed *without* the other recipients knowing.

3. No unnecessary reply-all. If the message is meant for one person on a large thread, direct-reply instead.

4. External domains are appropriate. No external domain on a thread whose content is internal-only.

5. Sensitive addresses double-checked. For any message going to legal, HR, executive team, external counsel, or the press, the recipient list is verified visually before send.

Category 2: Subject Line (3 items)

6. Subject is present. No empty subject line.

7. Subject is specific. "Update" and "Question" are not subjects. "Q3 pricing update: 8% increase effective Aug 1" is.

8. Subject matches thread convention. If replying, the subject preserves the original thread's naming so filters and searches work.

Category 3: Attachments (4 items)

9. If body mentions an attachment, an attachment is present. The classic. Search the body for "attached," "enclosed," "see the file," "PFA," "the deck below" — verify against the attachment picker.

10. Attachment is the right file. Filename matches the version, the date, the deal, whatever the context requires. No stale drafts.

11. Confidential filenames are appropriate for the audience. Files with `internal only`, `draft`, `confidential` in the name are not going to external recipients.

12. Attachment size fits recipient limits. Under 25MB for Gmail, 20MB for Outlook. Larger files go through a link.

Category 4: Content (5 items)

13. First sentence carries the point. No ceremonial opener. The recipient can see what the email is about from the first line.

14. Numbers are specific, not vague. Not "significant improvement" but "cut latency from 480ms to 190ms."

15. Claims are defensible. No promises the sender cannot keep. No SLAs the team has not committed to. No feature dates the roadmap does not support.

16. Links resolve and are correct. Every URL in the body goes where the sender intends.

17. No secret data in the body. No API keys, passwords, tokens, SSNs, credit card numbers, or JWT strings inline.

Category 5: Tone and Voice (4 items)

18. Tone matches the thread. A casual reply to a serious escalation is a mistake. A formal reply to a colleague's off-hand question is also a mistake.

19. No AI slop tells. No "I hope this email finds you well." No triple tricolons. No metronomic paragraph lengths.

20. At least one contraction per 100 words. A durable signal of human voice.

21. Signoff is appropriate. First-name for peers, "Thanks" for most professional contexts, formal signoff only when genuinely needed.

Category 6: Structure (2 items)

22. Formatting supports readability. No wall of text. Paragraph breaks between ideas. Bullet lists when they add clarity, not when they add visual noise.

23. No leftover merge tags. No `{{first_name}}` or `[COMPANY]` sitting in the body because the template was not properly rendered.

Category 7: Policy and Compliance (2 items)

24. Required disclaimers present. For public companies, forward-looking statements language. For regulated industries, appropriate footers. For legal privileged communication, the header note.

25. Approvals are on the CC line. For pricing changes, comp discussions, or other content requiring an approver, the approver is on the message and has confirmed in writing.

How to Actually Use This

Twenty-five items is too many to run manually on every send. Two workable approaches:

Manual triage. For low-stakes internal email, skip the checklist. For medium-stakes (external contacts, decisions being communicated, first-touch outbound), run a fast subset — recipients, attachments, subject. For high-stakes (executive audience, sensitive content, first email to a new party), run the full checklist. This is what most senior professionals do implicitly.

Automated coverage. Install a tool (Presend is the reference implementation, but others exist) that runs the mechanical checks — attachments, recipients, secrets, merge tags, subject presence, tone match — automatically on every send. This gets you coverage on 18 of the 25 items without manual effort. The remaining 7 are the ones that require human judgment (specificity, defensibility, appropriateness).

The combination — automation for the mechanical, discipline for the judgmental — is what separates careful senders from apologetic ones.

The Two-Minute Rule for High-Stakes Sends

For emails you know are high-stakes — board updates, customer escalation replies, first outreach to a decision-maker, incident notifications — add a mandatory two-minute cooling period between "done drafting" and "send." Use those two minutes to:

• Walk through the checklist above.
• Read the message aloud.
• Verify every specific claim.
• Check the recipient list one more time.

Two minutes on a message that took twenty to write is a rounding error. Two minutes on the message that would have caused an incident is the best time you will spend all week.

What Not to Put on the Checklist

Some things get proposed and then removed because they add friction without preventing meaningful mistakes:

• "Does the message need to be sent at all?" Good question, but not one a checklist answers. If you are drafting, you have already decided.
• "Is the recipient going to like this?" Not the sender's job on most communication. Deliver the message clearly and honestly.
• "Is the timing right?" Sometimes yes, but for most email the answer is "send it when it is ready."

Keep the checklist to items that either (a) prevent factual mistakes or (b) reduce risk of misinterpretation. Everything else belongs in a different process.

The Checklist Is a Starting Point

The 25 items above are the baseline. Every team has its own high-stakes patterns worth adding:

• Support teams add "KB article linked when appropriate."
• Sales adds "pricing quote references the current price sheet version."
• Legal adds "privilege language present on privileged mail."
• Ops adds "runbook link in incident notifications."

Add the items that map to your team's recurring mistakes. Prune the items that never fire. Re-review annually.

Bottom Line

Careful email senders are not paranoid. They are systematized. The system can be an internalized habit, a printed card next to the monitor, or a tool that runs the checks invisibly. The specific implementation matters less than the fact that a system exists.

Twenty-five items. Two minutes on high-stakes sends. One tool for the mechanical checks. That is the difference between a sender who occasionally apologizes and one who does not.

Add Presend to Chrome — Free →