Email Campaign Testing Checklist: Pre-Send Quality Assurance for Deliverability

A systematic pre-send testing process catches the deliverability and quality problems that would otherwise manifest as campaign performance problems after full deployment — when they are expensive to fix and costly in reputation damage. Authentication failures, broken links, spam-triggering content, and broken rendering in dark mode are all issues that a 20-minute pre-send checklist catches before the campaign reaches the full list. This checklist documents the specific checks that commercial email programmes should run on every campaign before deployment.

Authentication Verification Checks

Authentication verification is the highest-priority pre-send check — an authentication failure on a full campaign deployment causes every email to either fail DMARC or produce misaligned authentication signals that can damage reputation. The authentication check should be run on a test send from the actual campaign sending configuration (not from a test account with different authentication settings).

Content and Spam Filter Testing

Content testing identifies spam filter triggers in the email content before full deployment. Even well-authenticated senders face content score penalties for specific patterns that can tip borderline-reputation campaigns into spam folder placement:

Rendering Testing Across Clients

Email rendering varies significantly across clients — what looks perfect in Klaviyo's preview may render broken in Outlook on Windows or in dark mode on Apple Mail. A minimum rendering test matrix before any major campaign:

Commercial rendering test tools (Litmus, Email on Acid) provide all of these views in a single test run, without needing actual access to each device and client. A rendering test run takes 5-10 minutes and costs the per-test price of the subscription — significantly cheaper than deploying a broken template to the full list.

List Quality Pre-Send Checks

Link and Tracking Verification

Broken links and misconfigured tracking are among the most embarrassing and commercially costly campaign failures. A campaign where the primary CTA link 404s wastes the entire send. A campaign where tracking is broken provides no performance data for optimisation. The link verification checklist:

Timing and Scheduling Checks

Seed Send Before Full Deployment

For major campaigns (volume above 100,000 or high commercial importance), run a 2-5% seed send before the full deployment. The seed send uses the actual campaign configuration to send to a representative sample of the full audience — catching any list-specific delivery problems before they affect the entire list:

• Hard bounce rate on seed send: must be below 0.5%. Above this: pause full deployment, investigate the list segment.
• Complaint rate on seed send: must be below 0.05%. Above this: pause and investigate content or segment targeting.
• Time to delivery at major ISPs (Gmail, Yahoo, Microsoft): all major ISPs should show delivery within 60 minutes of send. Extended queue times at specific ISPs indicate rate limiting — check the accounting log for 4xx deferral counts at those ISPs.

Post-Send Monitoring Checklist

The campaign testing does not end at send — post-send monitoring in the first 4 hours confirms the campaign is delivering as expected:

• Hard bounce rate within 1 hour: Check the campaign's reported hard bounce count. Any unexpected spike (above 2%) requires immediate investigation and potential send pause.
• Complaint rate at 2 hours: Any FBL complaint notifications received in the first 2 hours. Above 0.05% on initial sends: investigate before continuing the send (if using batched sending).
• Postmaster Tools spam rate: Check next-day Postmaster Tools spam rate data for the campaign day. Above 0.08%: investigate root cause before the next campaign deployment.
• Click rate at 4 hours: An unexpectedly low click rate relative to recent comparable campaigns may indicate inbox placement problems (emails going to spam generate no clicks even if they were technically "delivered").

The pre-send testing checklist turns campaign deployment from a high-stakes single event into a systematic quality assurance process where problems are caught before they reach the full audience. The 20 minutes invested in running the checklist before every major campaign is repaid many times over in the problems it prevents — preventing a single broken-link incident, a single authentication failure, or a single spam folder placement from degrading the commercial performance and reputation of a campaign that represents weeks of content and strategy investment.

Checklist Frequency and Documentation

How often to run the full checklist: run the complete checklist before every campaign above 10,000 recipients, and before any campaign to a new or recently imported list segment regardless of size. For recurring campaigns (weekly newsletters, daily digest emails) that use the same template and sending configuration, a streamlined version of the checklist (authentication spot-check, link verification, list check) is appropriate rather than the full checklist on every send -- the full checklist was completed when the template and configuration were initially set up. Significant template changes or ESP configuration changes should trigger a full checklist run regardless of campaign frequency.

Document the checklist results: create a simple checklist record for major campaigns noting which checks were run, who ran them, and the result. This documentation creates accountability (the person who ran the checklist takes responsibility for the verification), provides a reference if post-send problems need to be investigated against the pre-send state, and builds institutional knowledge about common failure modes in the programme's specific sending configuration. After three months of documented checklist runs, the most common failure modes become apparent -- and can be addressed systemically rather than reactively caught in each pre-send check.

The pre-send checklist is the operational discipline that separates professional email programmes from amateur ones. Professionals check their work before committing it to 100,000 subscribers. Amateurs discover the broken link from subscriber replies. The 20-minute investment in systematic quality assurance is the single easiest operational improvement available to any email programme that does not yet have a documented testing process.

Make the checklist a team ritual, not a solo task. Pair the content creator with the deliverability manager for pre-send review -- two people checking the checklist catch more issues than one. The content creator reviews for accuracy and relevance; the deliverability manager reviews for authentication, spam filter signals, and list quality. This paired review transforms the checklist from a compliance exercise into a genuine quality gate that improves every campaign it touches.

Every major deliverability failure that occurs in a well-established email programme — authentication breakage, broken links reaching the full list, rendering failures in dark mode — is a pre-send testing failure as much as it is a technical failure. The problem existed; the testing process that should have caught it either did not exist or was not followed. Build the testing process; enforce it consistently; and the pre-send checklist becomes the operational standard that prevents the preventable problems that are otherwise discovered the hard way, after the campaign has reached its full audience.