Campaign Preflight Checks Before You Press Send
A send-readiness card for email campaigns: the fresh test-send rule, seven preflight checks from merge fields to segment size, what preflight cannot catch, and how to keep the card alive.
Most email campaign failures are not creative failures. They are preflight failures: the merge field that rendered as a blank first name, the link that pointed to staging, the list segment that included last year’s unsubscribes, the send that went out with last month’s footer address. Every one was catchable in the fifteen minutes before the send. A preflight checklist is not bureaucracy; it is the cheapest insurance in email marketing, and this one is built for small teams that send without a separate QA person.
The Rule Of The Fresh Test Send
Everything on the checklist happens against a real test send to a real inbox — not the platform’s preview pane. Preview panes lie about line breaks, dark mode, and image loading. Send the campaign to at least two addresses on different providers, open both on phone and desktop, and only then start checking. The ten minutes this takes is the single highest-value step on the list, which is why it comes first and gates everything after it.
Campaign Preflight Checks Send-Readiness Card
Work top to bottom. Each check names what to verify and what “done” looks like; do not tick a box on intention.
| Check | What to verify | Done means |
|---|---|---|
| Subject and preview text | Spelling, length under roughly 60 characters, no placeholder tokens | Read aloud once; renders fully in a phone inbox list |
| Merge fields | Every personalization token has a fallback and renders in the test send | A record with an empty first name shows the fallback, not a blank |
| Links and UTMs | Every link clicks through to production, tracking parameters correct | Clicked all links from the test send; staging URLs absent |
| Unsubscribe and address | Unsubscribe link works and is one click; physical mailing address current | Test unsubscribe flow completes; footer address matches this month |
| Segment and size | Segment matches intent; recipient count plausible vs expectation | Count is within 10% of what you expected; spot-check five recipients |
| Images and alt text | Images load; every image has alt text; total weight sane | Test send renders with images blocked and still makes sense |
| Send time and from-name | Scheduled time in the audience’s timezone; from-name recognizable | A colleague recognizes the sender at a glance in the inbox |
The segment row deserves extra respect, because segment mistakes are the most damaging and the least visible. A misfired merge field embarrasses you to one person at a time; a wrong segment embarrasses you to the whole list, and the recipients who get an irrelevant or repeated campaign do not complain — they disengage quietly. If the count surprises you, stop and explain the number before sending; a count you cannot explain is a segment you have not checked. For the list-health side of the same discipline, the list hygiene routine on this site covers the monthly version of that verification, and the newsletter preflight checklist is the sibling version of this card for recurring sends.
What The Preflight Cannot Catch
Honesty about limits makes the checklist stronger, not weaker. Preflight will not catch a strategically wrong campaign — the right message to the wrong audience at the wrong time sends perfectly and fails anyway. It will not catch deliverability problems that built up over months: a damaged sender reputation shows up as soft bounces and spam-folder placement that no preflight row detects, which is why bounce and placement monitoring belongs to a weekly habit, not a send-day habit. And it will not catch the typo in the third paragraph that five people missed; for that, keep the draft finalization at least one business day before the send whenever the schedule allows — distance catches what freshness cannot.
For the authentication layer that underpins whether campaigns reach the inbox at all, the plain-language SPF, DKIM, and DMARC guide on this site covers the records that send-day checks assume are working. Run that audit quarterly; a preflight card cannot fix what the domain has not authenticated. For the authentication records themselves, the DMARC.org overview explains how SPF, DKIM, and DMARC fit together in vendor-neutral terms.
Timing The Preflight
Run the card at a fixed point in the campaign calendar: content final at least one business day before send, preflight itself fifteen minutes before the scheduled time, and the actual send scheduled with a buffer rather than by hand. Teams that press send manually at “whenever it’s ready” skip the card exactly on the busy days when it matters most. Scheduling the send — and treating the scheduled time as a real deadline for the card — removes the willpower from the habit. If a last-minute content change comes in after preflight, the rule is simple and non-negotiable: the card reruns, or the send moves.
For campaigns with legal or regulated content — promotions with terms, healthcare or finance-adjacent messaging, anything with geographic restrictions — add one more row: a named human reviewer who approves the final test send. The card catches mechanical failures; it cannot judge whether a claim is compliant. That judgment needs a person, and naming them in advance beats scrambling at send time.
Making The Card Stick
Checklists die when they are long, vague, or owned by nobody. Keep this card printed or pinned next to whoever presses send, reduce it to the seven rows above — not forty — and assign the card itself an owner who updates it when a mistake slips through. Every real-world failure should end with the same two questions: which row would have caught this, and is that row clear enough? The card earns its keep the first time a test send reveals a staging link on a Friday afternoon, and it will.