A pre-send email checklist catches the mistakes that, when wrong, reach your whole list at once: the subject line and preheader, every link, personalization tokens, the unsubscribe link, mobile and desktop rendering, the send segment, and the from name. Run the same checklist on every send, send yourself a test, and never schedule while rushed. Most email mistakes come from skipping a routine check under time pressure.
Key Takeaways
- Email is unforgiving because a single error reaches everyone simultaneously. There's no quiet fix after send.
- A written checklist beats memory every time, especially when you're rushed, which is exactly when mistakes happen.
- A test send to yourself and one colleague catches what re-reading the draft never will.
- The highest-risk items are the ones that touch the whole list: wrong segment, wrong from name, broken links.
- AI can run a fast mechanical first pass so your human review focuses on judgment and tone.
What should be on a pre-send email checklist?
These eight items cover the mistakes that hurt most, because each one reaches your entire list the moment you hit send.
- Subject line and preheader. Read them together as they'll appear in the inbox. Check for typos, truncation, and tokens that didn't render.
- Every link. Click each one. A broken or wrong link in your main call to action quietly kills the whole send's purpose.
- Personalization tokens. Confirm they populate. A "Hi {FirstName}" that ships literally is the classic trust-eroding mistake.
- The unsubscribe link. It must be present and working. This is a compliance issue, not a nicety.
- Rendering on mobile and desktop. Most opens are mobile. Check both before you assume it looks fine.
- The send segment. Confirm you're mailing the list you intend, not the whole database by accident.
- The from name and reply address. A wrong sender name confuses recipients and tanks opens.
- Images and alt text. Make sure images load and carry alt text for anyone who blocks them.
Print this, pin it, or paste it into your sending tool's notes. The value isn't the cleverness of the list. It's that you run the same one every single time, so nothing depends on you happening to remember it on a busy afternoon.
How do you prevent email sending mistakes in practice?
Three habits prevent almost all of them. First, use a written checklist on every send, no exceptions, including the "quick" one you're sure is fine. Second, send a test to yourself and one colleague, then read it in the inbox the way a subscriber would, not in the editor. Third, never schedule a send while rushed. Time pressure is the single most reliable cause of email mistakes.
From what I've seen, the team that ships a broken send almost never lacks knowledge of what to check. They knew the checklist. They just skipped it because they were behind, and the one time they skipped is the time the wrong link went out. A checklist removes the reliance on memory, and a test send catches what reading the draft misses, because your eyes skim what you wrote and gloss over the error you're closest to.
What's the difference between proofreading and QA?
These are two separate passes, and conflating them is where sends go wrong.
| Pass | What it checks | How to do it | | --- | --- | --- | | Proofreading | Words, tone, clarity, the argument | Read the draft in the editor | | QA | Mechanics: links, tokens, segment, rendering, from name | Run the checklist on a test send |
Proofreading asks whether the email is good. QA asks whether it will actually work when it lands. A beautifully written email sent to the wrong segment, with a broken main link, fails completely no matter how clean the copy is. Both passes matter, and the QA pass is the one founders skip because it feels mechanical and boring. That's precisely why it deserves a fixed checklist rather than a glance.
Can AI help with email QA?
Yes, as a fast first pass before your human review. AI can verify that links resolve, flag personalization tokens that didn't populate, check for voice and tone issues against your profile, and confirm that structural elements like the unsubscribe link are present. It's well suited to the mechanical, repetitive checks that are easy for a tired human to skim past at speed.
The split that works, from my experience, is letting AI catch the mechanical errors so your final human check can focus on judgment and tone. AI won't decide whether the offer lands or whether the joke works, but it will reliably notice that link three goes nowhere. Used that way, it tightens the QA pass without replacing the human read that protects your voice and your relationship with the list.
One caution: don't let an AI pass become a reason to skip the human one. The failure mode I've seen is a team that trusts the automated check so completely they stop sending themselves a test, and then a rendering issue or a wrong-segment error slips through because no human ever looked at the email as a subscriber would. AI is a strong first pass, not the last word. Keep both, and keep them in order, with the machine catching the obvious mechanical faults and the human confirming the send is actually right before it goes out to everyone at once.
Frequently Asked Questions
What should be on a pre-send email checklist?
Check the subject line and preheader, every link, personalization tokens, the unsubscribe link, rendering on mobile and desktop, the send segment, and the from name. These are the items that, when wrong, reach your entire list at once. A standard checklist catches them before they become a public mistake.
How do you prevent email sending mistakes?
Use a written checklist every send, send a test to yourself and one colleague, and never schedule a send while rushed. Most email mistakes come from skipping a routine check under time pressure. A checklist removes reliance on memory, and a test send catches what reading the draft misses.
Can AI help with email QA?
Yes. AI can verify links resolve, flag broken personalization tokens, check for voice and tone issues, and confirm structural elements are present. It runs as a fast first pass before your human review. AI catches the mechanical errors so your final check can focus on judgment and tone.
Read Next
- Email QA Checklist Before Send
- The AI Content Review Workflow That Catches What QA Misses
- Complete Guide to Email Ops and AI Workflows
If your sends still rely on remembering to check the right things, that's a process gap worth closing before it costs you a list. Get a free audit and we'll review your email ops for the gaps that quietly damage trust.