The reality of email marketing checklists
Most people treat a checklist like a formality. They copy-paste one they found online, tick the boxes, and hit send. That approach works until it doesn't. I watched a client blast an email with a broken UTM parameter in the subject line preview text and lose nearly forty percent of their open rate on a campaign that had been budgeted for a major product launch. The issue wasn't the content. It was that nobody ran the final pre-send verification properly because the checklist they were using stopped at "proofread the copy." This isn't a generic list you'll find on a marketing blog. It's the ten items I actually verify before every send, and it's organized around what breaks when you skip steps, not what looks nice in a presentation. 1. Authentication records are valid and current. SPF, DKIM, and DMARC need to be checked against what your sending domain is actually configured to do. I had a client who migrated from SendGrid to a new ESP and forgot to update the DMARC policy. Their DMARC was set to reject mode but the SPF record still referenced the old service. Every email bounced or went to spam. The fix took twenty minutes but cost them three days of back-and-forth with their provider.
2. List hygiene is documented for this specific send. Hard bounces should be removed before the send, not after. Suppression lists need to match across your CRM and your ESP. If you're merging two audiences, run a dedup check first. I once saw a newsletter where the same person received two emails within four hours because the suppression export was stale by six weeks. It doesn't look great for deliverability or for your reputation with subscribers. 3. The from address and from name are consistent with past sends. Sudden changes trigger spam filters more often than people realize. If you normally send from noreply@ and suddenly switch to hello@ on a high-volume day, expect a deliverability dip. I've seen a twelve percent drop in inbox placement from nothing more than a from-name change without warning the infrastructure team. 4. Link tracking is verified end-to-end. Click all your links before sending. Check that UTM parameters are attached correctly. Check that redirect links resolve. I built a simple script that opens each link in a headless browser and logs the final destination URL. It catches tracking issues that manual clicking misses, especially when third-party cookies or ad-blockers interfere with analytics pixels.
5. Mobile rendering is tested on actual devices, not just browser simulators. Browser dev tools show you roughly what an email looks like on a phone. They don't show you how Gmail's mobile renderer actually handles certain CSS properties. I test on an iPhone and an Android device running the current Gmail app. The difference between a simulated preview and the real thing matters more than most people think. Buttons get cut off. Images misalign. Text overflows containers in ways that no desktop preview ever warns you about. 6. Alt text is written for every image. This isn't just about accessibility. It's about deliverability and engagement. Many email clients block images by default. The alt text is what the recipient actually sees. I use a standard format: image description plus a text version of the CTA. So instead of alt="btn", it reads "Download the report". Simple change, noticeable difference in click-through when images are blocked. 7. The unsubscribe link is functional and compliant. CAN-SPAM requires a working unsubscribe mechanism. The GDPR requires it too if you're dealing with EU addresses. The link should remove the subscriber within five seconds of clicking. I've audited campaigns where the unsubscribe button linked to a homepage instead of a preference center. That's a compliance issue and it damages trust. Make sure the opt-out is frictionless and immediate.
Get the Full Details
8. Send time aligns with the audience's actual behavior, not industry averages. Tuesday at 10 AM works for some B2B audiences and completely fails for others. I look at the send performance data for the specific list segment before picking a time. If your historical data shows a Wednesday 7 PM peak for your particular audience, don't send on Tuesday morning because a blog told you to. One client had a D2C brand whose subscribers were predominantly parents. Their best sending window was Thursday evening between 8 and 9 PM, when kids were finally asleep. Sending at the "standard" Tuesday noon slot cut their open rate by twenty-two percent. 9. The subject line passes a spam score check and a plain-language read-through. SpamAssassin scores are useful but incomplete. Most modern filters use machine learning models that don't publish their criteria. Run your subject line through a spam checker, then read it aloud. If it sounds like something a person would actually want to open, you're in better shape than if it just scores low on keywords. I've seen emails flagged as spam because the subject contained a string of exclamation marks that looked algorithmically suspicious, even though the content was perfectly legitimate. 10. A small test send is routed to human reviewers on different providers. Send to your own email at Gmail, Outlook, Yahoo, and Apple Mail. Check how it renders in each. Look at the spam folder placement. Verify that links work in each client. This step catches the problems that automated checks miss. I learned this the hard way after an email rendered perfectly in every testing tool but displayed a broken layout in Outlook because of a CSS property Outlook ignores. The fix was adding a table-based layout wrapper around the affected section.
Where this approach falls apart
This checklist assumes you have control over your ESP configuration and access to testing accounts across major providers. If you're sending through a platform that restricts your access to authentication settings or blocks headless browser testing, you'll need to work around those limitations. Some smaller ESPs don't let you customize DMARC policies at all, which means you're dependent on the platform's defaults. In those cases, the authentication step becomes less of a verification and more of a trust exercise. The checklist also doesn't account for seasonal deliverability fluctuations. Email congestion around Black Friday and holiday seasons changes how aggressively providers filter messages. A send that clears the spam folder in March might land in promotions or spam in November with identical content and infrastructure. There's no checklist item for that except monitoring your deliverability metrics week over week and adjusting send volume accordingly. If you're looking for a downloadable version, most ESPs include a pre-send checklist in their sending workflow. You can map these ten items onto your platform's native checklist and run it as part of your standard operating procedure. The value isn't in having a PDF. It's in treating each item as a verification gate that must be passed before the send button is clicked.
