PRE-SEND CHECKLIST
The pre-send cold email
checklist
What to check before launching any cold email campaign. Eight areas that cover every preventable failure mode — from DNS misconfiguration to broken merge tags.
10 min read01
Why pre-send checks matter
Most cold email deliverability problems are not caused by spam filters reacting to your copy. They are caused by infrastructure failures that were already present before the campaign launched — broken DNS records, un-warmed inboxes, unverified lists, broken merge tags.
Once a domain takes damage — a spike in bounces, a spam complaint rate above 0.1%, a blacklist listing — recovery takes weeks of reduced sending, active warmup, and monitoring. The inbox reputation that took months to build can be lost in a single bad send.
Pre-send checks do not guarantee a campaign performs well. They guarantee it does not fail for a preventable reason. That is the goal of this checklist: remove every variable that you can control before the first email leaves.
Campaigns should not launch until every critical risk on this list has been resolved. A blocked launch costs you an hour. A damaged domain costs you weeks.
FORGESEND
How this maps to ForgeSend
ForgeSend brings these pre-send checks into the campaign builder as launch-readiness guardrails. Before a sequence can be activated, the campaign builder surfaces DNS health, list quality, suppression coverage, variable resolution, schedule settings, and sending limits as a structured review. Critical risks are treated as blockers rather than passive warnings — a campaign should not go live until they are resolved.
The checklist sections below map directly to what that pre-send review covers. Where a check is best done with an external tool before you import into a campaign, the relevant free tools are linked inline throughout this guide.
02
DNS and authentication
DNS authentication is the foundation. Inbox providers check SPF, DKIM, and DMARC before deciding whether to deliver, quarantine, or reject your email. A missing or misconfigured record is a hard blocker — not an advisory warning.
dig TXT yourdomain.com or a DNS lookup tool.p=none policy is better than no DMARC at all. Gmail and Yahoo now require DMARC for bulk senders. Move to p=quarantine or p=reject once your authentication is stable.For a full walkthrough of each record, see the SPF, DKIM, and DMARC explained guide →
Use the free DNS Health Checker to verify SPF, DKIM, DMARC, and MX records across your sending domains, and the Blacklist Checker to scan your sending IP and domain before launch.
03
Inbox health and sender limits
Even with valid DNS records, a cold inbox — one that has not been warmed — will fail. Inbox providers use sending history and engagement patterns to assign a sender reputation score. Sending volume that outpaces warmup destroys that score quickly.
Warmup and campaign sending are not mutually exclusive
Warmup should continue running while campaigns are active. The goal is to maintain a baseline of warm engagement signals alongside your campaign sends. Stopping warmup the moment you start a campaign removes the engagement floor that protects your reputation.
Use the free Warmup Calculator to plan a safe sending ramp for new inboxes before your first campaign goes live.
04
List verification and risky contacts
Unverified lists are the most common cause of bounce rate spikes. Invalid addresses, deactivated inboxes, and role-based addresses all produce hard bounces that damage sender reputation. Verification should happen before the list enters any campaign, not during it.
info@, support@, and admin@ have high spam complaint rates and are checked by spam filters. Remove them unless you have a specific reason to target them.05
Suppression and unsubscribes
Sending to contacts who have previously opted out, bounced, or indicated they are not interested is both a compliance failure and a deliverability failure. A suppression list must be checked against every new campaign before launch.
06
Personalisation variables and fallbacks
Broken merge tags are one of the most visible campaign failures — and one of the easiest to prevent. An email that begins with "Hi {first_name}" or "I noticed {company_name} recently" goes directly into the trash. Every variable needs a fallback value, and every fallback needs to make grammatical sense.
first_name is empty, the fallback should be "there" or a neutral substitute, not a blank space or the literal tag. Configure fallbacks at the field level, not just in the template.{option1|option2} block is correctly closed and contains at least two non-empty options.Use the free Spintax Generator to build and validate variation blocks before importing them into your sequence steps.
07
Sequence timing and daily caps
Timing and volume controls prevent two distinct problems: sending at hours when recipients are not at their desks (which reduces reply rate), and sending more than your inboxes can safely handle (which raises bounce rate and flags your domain).
Use the free Send Time Optimiser to find the best send windows for your target audience's timezone before locking in your schedule.
08
Final review before you click send
Once the technical checks are done, a final human review catches the things automation cannot — copy that sounds wrong, CTAs that ask for too much, and structural issues that reduce reply rate.
Run your copy through the free Spam Checker and Subject Line Tester before finalising your sequence. If you need a starting structure for any step, the Email Template Generator can help.
QUICK REFERENCE
Full checklist summary
Print or bookmark this list. Work through it before every campaign launch.
DNS & Authentication
Inbox Health & Sender Limits
List Verification
Suppression & Compliance
Personalisation Variables
Timing & Caps
Final Review
Run these checks automatically before every launch
ForgeSend brings pre-send guardrails into the campaign builder so operators can review launch risks before a campaign goes live. DNS, list quality, suppression, variables, schedule settings, and sending limits are treated as launch-readiness checks rather than after-the-fact reports.
Start free trial →