← All posts

Email QA checklist for agencies: 25 checks before send

A 25-point email QA checklist for agencies: brief, brand, links, images, rendering, deliverability and client sign-off checks before a campaign goes live.

An email QA checklist is a fixed list of checks that a second person runs on every campaign before it is scheduled. For agencies, it should cover the brief, the client's brand rules, links and tracking, images, rendering, deliverability and written client sign-off. The 25-point checklist below is built for teams that ship campaigns for many clients at once.

A single brand can sometimes get away with an informal final look before sending. An agency cannot. Every client has different brand rules, different tracking conventions, different approvers and different email platform settings, and the person who built the email is the one least able to spot what is wrong with it. A written checklist turns QA from a personal habit into a step the whole team runs the same way.

Why agencies need a written QA process

Three things make QA harder for agencies than for in-house teams.

  • Volume across clients. More campaigns a week means more chances for one small mistake, and the mistake is public the moment the email is sent.
  • Different rules per client. One client writes "free shipping" in the headline; another never mentions it above the fold. A checker who relies on memory will mix them up.
  • The client relationship. A broken link in an agency-built email is not just a lost click. It is a conversation with the client about whether they can trust the next campaign.

A shared checklist, a named checker and a record of who approved what solve most of this.

The 25-point email QA checklist

Run these checks in order. Each one has a suggested owner: the person who built the email (Builder), a second team member (Checker), or the account manager (AM).

Brief and content

# Check Owner
1 The email matches the brief: goal, audience, offer, dates and primary action. Checker
2 The subject line and preview text are final and read well together. Checker
3 Every date, day and time zone is correct, including the year. Checker
4 Personalization fields have fallbacks, so no reader sees an empty greeting. Builder
5 Spelling, grammar and the client's product and brand names are correct. Checker
6 Required legal lines, offer terms and exclusions are present and current. AM

Brand

# Check Owner
7 Logo, colors and fonts match the client's current brand guidelines. Checker
8 The tone matches the client's voice, not the last client the team worked on. AM
9 Product names, prices and images match what is live in the store today. Checker

Links and tracking

# Check Owner
10 Every link and button has been clicked, not just looked at. Checker
11 Tracking parameters follow the client's naming convention. Builder
12 Product links land on the right product, in stock, at the right price. Checker
13 Discount codes work at checkout and are spelled exactly as created. Checker
14 The unsubscribe and preference links work. Checker

Images and layout

# Check Owner
15 Every meaningful image has descriptive alt text; decorative images have empty alt text. Builder
16 Images are compressed, so the email loads quickly on mobile data. Builder
17 The offer, the deadline and the button are live text, not part of an image. Checker

Rendering

# Check Owner
18 The email works on a phone first, then on desktop. Checker
19 It renders correctly in Gmail, Outlook and Apple Mail. Checker
20 Dark mode does not hide the logo, invert buttons or make text unreadable. Checker

Audience and deliverability

# Check Owner
21 The right segment is selected and suppression lists are applied. AM
22 The sending domain is authenticated and the email supports one-click unsubscribe. Builder
23 The send time is set in the client's intended time zone. AM

Sign-off

# Check Owner
24 A final test has gone to a seed list that includes the client contact. Builder
25 The client's approval is recorded in writing, with the date and the version approved. AM

Who runs which checks

The builder fixes what they own before handing over: fallbacks, tracking, alt text, image weight, authentication and the test send. The checker runs everything that benefits from fresh eyes, especially content, links, brand and rendering. The account manager owns the checks that depend on the client relationship: legal lines, tone, audience, send time and approval.

The one rule worth enforcing: the builder never signs off their own email. Even a two-minute review by someone else catches mistakes the builder will read straight past.

Deliverability checks that protect every client

Deliverability problems are easy to miss in QA because the email looks perfect. Gmail's sender guidelines set clear rules for anyone sending more than 5,000 messages a day to Gmail accounts: authenticate the sending domain with SPF, DKIM and DMARC, support one-click unsubscribe with a visible unsubscribe link in the message, and keep the spam rate reported in Postmaster Tools below 0.30%, with Google recommending a target below 0.10%.

For an agency, the practical step is to check authentication and one-click unsubscribe once per client during onboarding, record the result, and re-check whenever a client changes email platform or sending domain. Check 22 in the list then becomes a quick confirmation rather than an investigation.

Keep the spam-rate check in the monthly client report rather than in the per-campaign checklist. Spam rates move over weeks of sending, so a single campaign rarely tells you much, but a rising trend is an early warning worth raising with the client.

Build QA into production, not after it

The fastest QA is the QA you do not have to repeat. Components that have already passed review, such as a footer with the legal lines, a product grid and a button style, do not need to be checked from scratch every week. Build each client's library once, and most of the checklist becomes a confirmation.

Production tools can take on part of the work. Nexmail's SmartSlicing step, for example, slices each section of a design, attaches the destination URLs, writes alt text, optimizes image sizes, uploads into the client's email platform and prepares the email for QA. Its editor keeps a component library and version history, which makes check 25 easier to record. Agencies using Nexmail for retention and Klaviyo agencies still run a checklist, but they spend their checker's time on the brief, the offer and the audience instead of on slicing and link-pasting.

If you want to see that workflow on one of your clients, you can book a demo or get your first 2 campaigns free, no card needed.

Keep a simple QA log

A QA log does not need special software. A shared sheet with one row per campaign is enough:

  • Client and campaign name
  • Builder and checker
  • Date checked
  • Issues found and fixed
  • Client approver, approval date and version approved

Over a few months, the "issues found" column becomes your most useful training material. If the same mistake appears three times, it deserves a permanent fix in the template, not another reminder.

Share the log with clients when they ask for it. Most never will, but when an error does reach subscribers, being able to show who checked the campaign, what was found and which version the client approved turns a difficult conversation into a short one.

How long should email QA take?

Aim for a checklist the checker can finish in about fifteen minutes for a standard campaign. If it routinely takes longer, the problem is usually upstream: briefs that change after design, templates that break in Outlook, or links built by hand. Fix those, and QA gets faster without getting weaker. For more on reducing production time across clients, read how agencies scale email production without hiring more designers.

FAQ

What should an email QA checklist include?

Checks for the brief and content, brand rules, links and tracking, images, rendering in the main inboxes and dark mode, audience and deliverability, and written sign-off. The 25 checks above cover each area.

Who should do email QA at an agency?

Someone other than the person who built the email. The builder fixes their own technical items first, a second team member runs the content, link and rendering checks, and the account manager confirms the audience, timing and client approval.

Which inboxes should we test in?

At a minimum, check the email on a phone, then in Gmail, Outlook and Apple Mail, and in dark mode. Each one renders email differently, and most layout problems show up in one of them.

How do Gmail's sender rules affect agency QA?

For senders above 5,000 messages a day to Gmail accounts, Gmail requires SPF, DKIM and DMARC authentication, one-click unsubscribe and a spam rate below 0.30% in Postmaster Tools. Confirm these once per client and re-check whenever the sending setup changes.

Can QA be automated?

Parts of it can. Slicing, link attachment, alt text and image optimization can be handled in production, and reusable components reduce repeat checks. Judgment checks, such as whether the email matches the brief and the client's voice, still need a person.

Ship more client campaigns with fewer surprises

Nexmail has generated more than 10,000 emails for production use, and it is built so agencies can produce on-brand campaigns for many clients without adding designers. See how it fits your workflow with Klaviyo email design that exports production-ready HTML: book a demo or get your first 2 campaigns free.