Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Checklists

Email Campaign QA Checklist

A pre-send QA checklist for email campaigns: audience and suppression, subject and preheader, links and tracking, rendering and dark mode, and accessibility.
Checklistbeginner7 min readUpdated

When to run this checklist

Run it before every scheduled campaign send, with no exception for small sends or urgent ones; the urgent sends are the ones that go out to the wrong list. For automated flows, run it when the flow is created and again after any change to its template, its trigger or its audience, because a flow sends for months after anyone last looked at it. Run it with particular care on the first send from a new domain or a new sending platform, when authentication and reputation are untested and a mistake costs more than a bad campaign. It is also the right list after a platform migration, where fields are renamed, suppression lists do not carry across, and the footer address is still the old one. Where a campaign's click-through rate (CTR) collapses on one send with no change in the offer, the list run afterwards usually finds the link or rendering line that would have caught it beforehand.

Before you start

  • The brief: the segment, the offer, the send time and the person who signs off, so that each line is checked against an intention rather than against whatever the draft happens to contain.
  • The final version, not the working draft. QA on a version that is still being edited is QA on something that will not be sent.
  • The link list with the UTM parameters each link should carry, following the naming convention the reporting depends on.
  • Seed addresses on real devices: at least one phone, one desktop client and one webmail account, with dark mode available on one of them.
  • A second reader who did not write the email and has not seen it, with time to read the test send properly.
  • The suppression lists and consent records, so the audience lines are checked against the list of people who should not receive the email as well as the list of people who should. The list building and consent guide sets out what a usable consent record looks like.

The checklist

The groups are ordered by cost of failure. An email to the wrong audience cannot be undone and may breach consent; a broken link can at least be redirected; a rendering fault in one client is embarrassing rather than harmful. Work in that order and treat the send settings group as the final gate: nothing in it is ticked until every line above it is. For automated flows, "the segment" means the trigger condition and "the send time" means the delay, and every line still applies.

0/30

Audience

Content

Rendering

Accessibility

Compliance

Send settings

If an item fails

Stop the schedule, fix the line, and run the group again rather than only the line that failed, because the fix usually touches neighbours: a corrected link means a new test send, and a new test send means the rendering group is checked again. Audience failures are the only ones that should escalate beyond the team on the day. A segment that includes people without consent, or that misses a suppression list, is a compliance question before it is a marketing one, and the send waits until someone with the authority to decide has decided. Deliverability failures, authentication and unsubscribe headers in particular, are rarely fixable in the hour before a send; the deliverability guide explains what the mailbox providers require and why the fix sits with whoever manages the domain. Everything else is a question of time: a rendering fault in a minor client can ship with a note, a wrong price cannot. A preheader left as the template default is a content fix of a minute, so it never needs to ship.

Group that failedWhere the fix is explained
Audience, complianceList building and consent, and the Gmail sender guidelines in the sources list
Content, rendering, accessibilityNewsletter design and copy, which covers the template, dark mode and the writing
Links and trackingNaming conventions and UTMs and the landing page checklist for the destination
Send settings, deliverabilityEmail deliverability

A failed personalisation line often points to a field that should not be in the template at all, which the guide to personalising email content helps decide, along with fallbacks for the fields that stay.

Illustrative example — not a real result

A garden centre's spring sale send

A garden centre prepares a spring sale email to its full list of 42,000 subscribers. The audience group fails twice: the segment includes 1,800 addresses that bounced in the previous two sends, and nobody has suppressed the 3,400 customers who bought the featured greenhouse range in the last month, who would receive a discount on something they just paid full price for. The links group fails once, since the "shop the sale" button points to the staging site. The rendering group fails in dark mode, where the green-on-transparent logo disappears. The fixes take an afternoon: the bounces and recent buyers are suppressed, bringing the send to 36,800, the link is corrected and a new test is read on three devices. The send goes out a day late with a conversion rate of 1.9% on clicks, and the recent buyers, who would have complained, receive a separate thank-you email instead.

When a mistake gets past the list and the email has already gone, the tutorial on fixing a mistake in a sent email stops the send, decides whether a correction is needed and adds the missing line here.

Common mistakes

  • Running QA on the draft. The reader approves a version that is edited again afterwards, and the edited version is the one that ships unchecked.
  • Testing only in the builder's preview. The preview is a rendering, not a client; the fault appears in the one client the preview does not imitate.
  • Checking links by hovering. The URL looks right and the redirect behind it goes to a page that was retired last week.
  • Signing off the count, then applying suppressions. The suppressions change the count and nobody reconciles the two, so a segment that lost a quarter of its size goes out without question.
  • Treating the plain-text version as automatic. The generator leaves merge-field labels, image names and the footer's layout table in the text recipients with images off will read.
  • Skipping QA for automated flows. The flow that sends every day was last checked the day it was built, and the template it uses has changed twice since.
  • No record of approval. When the wrong price goes out, nobody can say which version was approved or by whom, and the same mistake happens again.

The campaign launch QA checklist is the matching list for paid campaigns, and the checklists library holds the rest.

Terms used on this page

Where this page is used

Also related

Sources

  1. Email sender guidelines — Google Workspace Admin Help
  2. Web Content Accessibility Guidelines (WCAG) — W3C

Related