The Email QA Checklist to Run Before Every Send

Before you hit send, run the checklist. Every broken link, misfired merge tag, or missing unsubscribe footer that reaches a subscriber's inbox is a trust event — and not a positive one.

An email QA checklist is a structured pre-send review that catches copy errors, rendering failures, deliverability risks, and compliance gaps before they become live problems. Teams that skip it ship broken campaigns. Teams that run it consistently ship with confidence — and protect the sender reputation and subscriber trust they have spent months building.

This article gives you the complete checklist, organized by category, so you can run it as a repeatable system before every send.

Why Email QA Is a Non-Negotiable System Step

A single bad send can do real damage. A broken personalization tag that addresses every subscriber as "Hi {first_name}," erodes trust immediately. A malformed link in a promotional campaign means lost conversions that cannot be recovered after the fact. A missing unsubscribe footer in a commercial email creates compliance exposure under CAN-SPAM.

The good news: all of these failures are preventable with a structured pre-send review.

Mailchimp's email automation resources and HubSpot's email marketing platform documentation both treat pre-send testing as a core operational step — not an optional last mile. The Customer.io blog on behavioral email operations makes the same point from the lifecycle side: the integrity of your sends is foundational to the data quality that drives automation decisions downstream.

"A checklist does not slow down your email program. It is the system that keeps a fast-moving program from shipping errors at scale."

If you are publishing on a regular cadence — a weekly newsletter, a nurture sequence, or a recurring promotional calendar — the checklist should be documented and assigned, not ad hoc. For teams running a high-frequency newsletter, the 90-Day Newsletter Operating System covers how to build the operational scaffolding that makes running a checklist sustainable week after week.

Section 1 — Subject Line and Preview Text

The subject line and preview text are the first impression of every email. They also carry their own failure modes beyond just persuasion.

[ ] Subject line is finalized and reviewed — not a draft placeholder
[ ] Subject line length is appropriate for mobile (under 50 characters is a safe target for most ESPs)
[ ] No all-caps, excessive punctuation, or spam-trigger language in the subject line
[ ] Preview text is set manually — not left blank or defaulted to the first line of body copy
[ ] Preview text complements the subject line rather than repeating it
[ ] Personalization tokens in the subject line (if used) have fallback values set — "Hi there" not "Hi {first_name}"
[ ] A/B test variant (if running) is configured and the winning condition is defined

For a deeper reference on what makes subject lines work, our guide to subject lines that get opened covers the tested frameworks — including what to do for cold and re-engagement sends where the stakes are especially high.

Want a faster path to better conversions? Get a free Conversion Infrastructure Audit and we will review your site, score your conversion path, and walk through the highest-leverage fixes on a live call.

Section 2 — Content and Copy

[ ] All body copy has been proofread — spelling, grammar, and sentence structure
[ ] No placeholder copy remains ("TBD," "INSERT STAT HERE," "Lorem ipsum")
[ ] All personalization and merge tags are rendering correctly in the preview (first name, company name, custom fields)
[ ] Fallback values are set for every dynamic field
[ ] Dates, times, and offers referenced in the email are accurate and still valid
[ ] Any pricing, promotion terms, or deadlines mentioned match what is live on the corresponding landing page or offer
[ ] Images have descriptive alt text — both for accessibility and for rendering in email clients that block images by default
[ ] Image file sizes are optimized — large image files increase load time and can trigger spam filters
[ ] The email renders acceptably in plain-text view (some clients and corporate filters display plain text only)

Section 3 — Links and CTAs

Broken links are the most common and most avoidable email error. Every link in the email should be clicked and verified before send.

[ ] Every link in the email body has been clicked and confirmed to load the correct destination
[ ] CTA buttons link to the correct destination — not an old version of the page or a staging URL
[ ] UTM parameters are present on all links if you use campaign attribution tracking
[ ] UTM parameters are consistent in naming (campaign, source, medium) — check for typos in parameter strings
[ ] No links point to localhost, staging environments, or internal preview URLs
[ ] Unsubscribe link is present and functional — test it in a preview to confirm it fires correctly
[ ] If linking to a time-sensitive resource (webinar registration, flash sale), confirm the destination page is live and not behind an error or redirect
[ ] Social sharing links (if included) point to the correct profiles or URLs

Section 4 — Rendering and Design

Email clients render HTML differently. What looks perfect in your ESP's preview may break in Outlook, Apple Mail, or Gmail depending on the CSS used.

[ ] Email has been tested in a rendering preview tool (Litmus, Email on Acid, or your ESP's built-in inbox preview) across major clients: Gmail, Apple Mail, Outlook, and mobile browsers
[ ] Mobile layout renders correctly — single-column stacking, legible font sizes, tappable CTA buttons
[ ] Desktop layout renders correctly — no broken table structures, misaligned columns, or oversized images
[ ] Dark mode rendering has been reviewed — logos and images with transparent backgrounds can appear broken in dark mode
[ ] Fonts fall back gracefully in clients that do not support custom web fonts
[ ] Email width is appropriate for the template — typically 600px is the standard for desktop
[ ] Header image or hero image loads correctly and is not blocked or broken
[ ] Footer is complete: company name, physical mailing address, unsubscribe link, and any required legal disclosures

Section 5 — List Targeting and Segmentation

Sending to the wrong segment is one of the most consequential errors in email operations — and one of the hardest to undo.

[ ] The correct list or segment is selected — double-check the segment name against the campaign brief
[ ] Segment logic is reviewed: confirm filters are set to "and" vs. "or" correctly and the audience count looks reasonable
[ ] Suppression lists are active: unsubscribes, hard bounces, and spam complainers are excluded
[ ] If this is a resend to non-openers, confirm the original send recipients are excluded from the new segment
[ ] If this is a promotional email, confirm the audience has opted in to promotional content — not just transactional or newsletter opt-ins
[ ] Audience count is validated against expectations — a dramatically lower or higher number than expected is a signal to recheck the segment logic before sending
[ ] If this email is part of an automation sequence, confirm entry conditions are set correctly and contacts will not receive duplicate sends

Section 6 — Deliverability and Technical Setup

[ ] Sending domain has valid SPF, DKIM, and DMARC records configured
[ ] From name and from address are consistent with your established sender identity — do not change these arbitrarily, as consistency builds domain reputation
[ ] Reply-to address is set and monitored — replies should go to a real inbox, not a no-reply address that auto-discards
[ ] List-Unsubscribe header is present (this is required by Google and Yahoo for bulk senders)
[ ] Sending volume for this campaign is within normal range for your domain — large spikes in volume from a low-sending domain trigger deliverability flags
[ ] If using a new template for the first time, send a small test batch before full deployment to check inbox placement
[ ] Campaign has been run through a spam scoring tool (many ESPs include this, or use Mail-Tester) — resolve any high-severity flags before send

Section 7 — Legal and Compliance

[ ] CAN-SPAM requirements are met: physical mailing address is present, unsubscribe mechanism is functional, from address is not deceptive
[ ] If sending to contacts in the EU or UK, GDPR consent requirements are satisfied — contacts were acquired via explicit opt-in and consent is documented
[ ] If sending to contacts in Canada, CASL express or implied consent applies for commercial emails
[ ] Any claims in the email (results, testimonials, statistics) are accurate and substantiated
[ ] Promotional language complying with FTC guidelines if endorsements or affiliate content is included
[ ] Mandatory disclosures (affiliate disclosure, sponsored content labeling) are present if applicable

The Complete Pre-Send Checklist at a Glance

Use this condensed version as the quick-reference you run before every send. Work through the full sections above when onboarding new team members or reviewing a new campaign type.

Subject line and preview text:

[ ] Finalized subject line with fallback values for personalization tokens
[ ] Preview text set manually and complementing the subject line

Content and copy:

[ ] Proofread, no placeholders, all merge tags tested with fallbacks

Links and CTAs:

[ ] Every link clicked and verified, UTM parameters present, no staging URLs

Rendering and design:

[ ] Tested in major email clients, mobile layout confirmed, footer complete

List targeting:

[ ] Correct segment selected, suppression lists active, audience count validated

Deliverability:

[ ] SPF/DKIM/DMARC confirmed, List-Unsubscribe header present, spam score reviewed

Legal and compliance:

[ ] Unsubscribe functional, physical address present, consent requirements satisfied

Frequently Asked Questions

How long does an email QA checklist take to run?

For a trained team member working from a documented checklist, a thorough pre-send review typically takes 15 to 30 minutes for a standard campaign. The first few times are slower. Once it becomes a routine, the process speeds up significantly — and the time investment is always less than the time required to manage errors after a bad send goes out.

Should every email go through the full checklist?

Yes for campaigns (newsletters, promotions, announcements). For individual transactional emails or automated sequences that have already been reviewed and approved, a lighter spot-check focused on link validity, merge tag functionality, and list targeting is appropriate. Any time a template is modified, run the full checklist again.

What is the most common email QA mistake teams make?

Skipping the link check. It is the step most likely to be cut under deadline pressure, and it is the step that catches broken CTAs, expired URLs, and staging environment links. Make clicking every link non-negotiable, regardless of time pressure.

Do ESPs have built-in QA tools?

Most major platforms — including Mailchimp and HubSpot — include inbox preview, spam scoring, and link checking as native features. They are useful but not comprehensive. Rendering tools like Litmus or Email on Acid provide broader client coverage. Your checklist should include both your ESP's built-in tools and any supplemental tools your team uses.

How do I get a team to consistently use the checklist?

Ownership and documentation. Assign the QA step to a specific role in your production workflow — not "anyone who has time." Document the checklist in your project management tool as a required task before any send is approved. Platforms that support campaign approvals can gate sends behind a completed QA task, which enforces the process structurally rather than relying on individual discipline.

Want Help Applying This?

If your team is sending campaigns without a documented QA process — or if past sends have shipped with errors that affected deliverability or subscriber trust — the place to start is understanding where your current email operation has gaps.

Request a free email audit and we will review your sending setup, list health, and campaign workflow to identify the highest-risk areas and give you a prioritized action plan at no cost.