When to run this checklist
Run it before any automated email flow goes live: a Welcome SeriesThe automated sequence of emails sent to a new subscriber in the days after sign-up., an abandoned cart or browse reminder, a post-purchase sequence, a win-back flow, or a Lead NurturingKeeping in useful contact with leads who are not yet ready to buy until they are. sequence for business buyers. Run it again whenever the trigger, the entry rules or the branches change, and whenever a new flow is added that could reach the same contacts, because a new flow changes the frequency every contact in the old ones experiences.
The person who built the flow runs the trigger and logic groups, ideally with a colleague who did not build it walking test contacts through every branch. The frequency and consent group needs whoever owns the overall email calendar, since no single flow can see the others. Per-email checks, such as rendering, links, the subject line and the footer, belong to the email campaign QA checklist, run on each email in the flow. This list does not repeat them.
Before you start
- A map of the flow: trigger, entry rules, each step, each delay, each branch condition and each exit, drawn or written so it can be checked against what the platform actually does.
- Test contacts that meet each branch condition, created with addresses the team can read.
- A list of every other live flow and the regular campaign calendar, so overlaps can be spotted.
- The offer terms: codes, expiry dates and any limits, from the people who own them.
- The UTMURL tags identifying traffic source. convention the reporting depends on, so flow and step names can be built into the links.
- The consent fields the platform uses, and the rule for which contacts may receive marketing email.
The checklist
The groups follow the life of a contact in the flow: how they get in, how they move through and get out, what they read, how often they hear from the brand overall, and how the flow will be judged later. The trigger and consent lines are the hard gates: a flow that reaches the wrong people sends to them every day until someone notices.
Trigger and entry
Logic
Content
Frequency and consent
Measurement and ownership
Where each check is explained
The widget keeps each line short enough to tick; the reasoning sits in the guides. Each check links to the page that explains it.
| Check | Explained in |
|---|---|
| Confirm the trigger fires for the right contacts and only those | Building a welcome series |
| Set entry rules so contacts cannot enter the flow twice by mistake | Automation governance |
| Keep contacts out of competing flows that would message them at the same time | Automation governance |
| Set exit rules so a purchase or reply removes the contact | Building abandoned cart flows |
| Check delays and send windows against the contact's time zone | Nurture sequences |
| Test every branch with a contact that meets its condition | Nurture sequences |
| Check personalisation fields have fallbacks in every step | Newsletter design and copy |
| Confirm offers and codes stay valid for as long as the flow runs | Building abandoned cart flows |
| Cap total messages per contact across flows and campaigns | E-commerce email and SMS flows |
| Confirm every contact entering has consent for marketing email | List building and consent |
| Tag links with parameters that name the flow and the step | UTM and naming conventions for analytics |
| Keep a holdout group where the flow's value needs proving | Email metrics and testing |
| Name an owner and a review date for the flow | Automation governance |
If an item fails
Trigger, exit and consent failures keep the flow switched off. A trigger that also catches existing customers sends a welcome discount to people who have bought for years; an exit rule that does not see purchases sends cart reminders to people who have already paid. Both erode trust faster than the flow earns revenue. A contact entering without marketing consent is a compliance question rather than a judgement call, and the flow waits until the entry condition checks consent directly. Fix the rule, then walk every test contact through again, since a change to entry or exit logic alters which branches contacts reach.
Content failures are fixed in the email, then the email goes back through the email campaign QA checklist. An offer that expires before the flow does is easy to miss because the flow will run correctly on launch day; the failure arrives weeks later, when a contact clicks a code that no longer works. Either give the code no expiry, or set a review date on the flow that falls before it.
Measurement lines can ship with a plan if the flow is urgent, but not without one. A flow switched on with no Holdout GroupA randomly chosen part of an audience kept from exposure to measure what exposure caused. can never show what it added beyond what those contacts would have done anyway, which matters most for flows that will later be credited with revenue, such as cart reminders whose results are read against the shop's Cart Abandonment RateShare of shopping carts created that did not become an order..
A kitchenware shop's cart reminder
Kestrelby Kitchenware, an online cookware shop, builds a three-email abandoned cart flow with a discount code in the third email. Walking test contacts through the branches shows two failures. The exit rule checks for a purchase only before the first email, so a test contact who buys after the second still receives the discount a day later. And the code was created with a thirty-day expiry, while the flow is meant to run all year. The exit rule is moved to before every step, the code is reissued without an expiry, and a tenth of eligible contacts are held out. After a quarter, the flow's recovered orders are compared with the holdout's own purchases, and the shop finds that about half the orders it would have credited to the flow came from customers who returned on their own.
A flow that passed this checklist and later went quiet is diagnosed stage by stage in why an automated email flow stops sending, from a renamed trigger event to refused mail. One that sends too much instead, with contacts receiving the same message twice, is traced in subscribers receiving duplicate emails, from flow re-entry to two systems sending.
Common mistakes
- Testing only the main path. The branch for contacts without a first name, or the one for repeat customers, is the one that breaks.
- Exit rules that check once. The purchase is checked at entry and never again, and paying customers keep receiving reminders.
- Flows that cannot see each other. A new contact enters the welcome series, the browse reminder and the weekly newsletter on the same day.
- Offers with a shelf life. The code expires, the flow keeps sending, and customers meet an error at checkout.
- No holdout. The flow is credited with every order its recipients place, including the ones they would have placed anyway.
- No owner. The flow outlives the person who built it and runs unchanged long after the products and prices it mentions have changed.
The email campaign QA checklist covers each email inside the flow, and the checklists library holds the rest.
