Email campaign QA process flowchart (build to post-send report)
Email campaign QA flowchart template: ESP build, rendering and link test, audience check, consent and unsubscribe compliance, test send and sign-off, A/B or full send, stop-send monitoring and report.
What the email campaign QA process flowchart (build to post-send report) process is
Email is unusual among marketing channels because a sent message cannot be recalled. A wrong link, wrong segment or missing unsubscribe goes to everyone at once, and the only remaining control is to stop whatever has not yet left. That one fact shapes this chart: it is built as a series of gates before the send, and an exception path after it.
The checks are deliberately separated by role. The Email producer builds and tests rendering, Marketing ops / deliverability checks the audience and watches delivery, the Compliance reviewer answers "Is the send compliant?" and the Campaign owner signs off. The compliance check covers consent basis, suppression lists and unsubscribe, and the rules behind it, such as CAN-SPAM in the United States or GDPR and ePrivacy rules in Europe, differ by country and by message type; the chart is a checklist, not legal advice, so check your jurisdiction and counsel. For the earlier stage, see /templates/content-approval-process and /templates/campaign-launch-process; for requests that arrive from other teams, see /templates/marketing-request-intake-process.
Three loops keep rework visible: "Do rendering and links pass?" returns to the build, "Does the segment match the brief?" returns to the audience, and "Does the campaign owner sign off?" returns changes to the producer. After the send, "Are bounces or complaints over the stop-send threshold?" is the hard stop. The threshold is a placeholder to set with your deliverability lead and your ESP's guidance.
What this flowchart covers
In this template
- Four swimlanes (Email producer, Marketing ops / deliverability, Compliance reviewer and Campaign owner) across five phases: build, test, compliance, send and report
- A technical gate, "Do rendering and links pass?", that returns to the build, and an audience gate, "Does the segment match the brief?", that returns to the segment
- A compliance gate, "Is the send compliant?", covering consent basis, suppression and unsubscribe, with a gap path that records the fault and sends it back to the build
- Test send and sign-off: "Does the campaign owner sign off?" with a changes-requested loop, then "Send as an A/B test or to the full list?"
- Delivery monitoring with "Are bounces or complaints over the stop-send threshold?" and an exception path, "Stop the send and pause the queue"
- A post-send report and review so learnings improve the checklist
When to use this template
- A campaign has gone to the wrong audience, or with a broken link, and you need checks that would have caught it
- Compliance asks how consent, suppression and unsubscribe are verified before each send, and the answer lives in people's heads
- You are scaling email across several producers and need one checklist and a named sign-off
- Deliverability dips or complaint spikes have occurred and you want a clear rule for who may stop a send
- You are introducing A/B sending and need the decision and the winner rule written down
How it works
Rename the lanes to your team
Replace Email producer, Marketing ops / deliverability, Compliance reviewer and Campaign owner with your roles. In a small team one person may hold more than one lane; keep the lanes so the checker is never the builder.
Write the build and render checklist
List the clients, devices and conditions you test, such as dark mode and images off, and what counts as a pass. Keep the list short enough that it is actually run.
Define the audience check
Say how the segment is compared with the brief, what recipient count is expected and which exclusions apply. An unexpected count should stop the process.
Turn the compliance check into a checklist
Set out what the reviewer confirms: consent basis, suppression lists applied, unsubscribe working and sender identity present. Ask your counsel which rules apply in each market; the chart does not replace that advice.
Set the stop-send threshold
Choose the bounce and complaint levels that trigger a stop, with your deliverability lead, and name who may pull the stop. The numbers on the chart are placeholders.
Decide the A/B rules
Write the test size, the winning metric and the wait time before the test starts. Choosing the winner after looking at results invites bias.
Run it on a recent send
Take a real campaign and trace it through. Note which gate would have caught any past mistake and adjust the checks.
Frequently asked questions
What should an email campaign QA checklist include?
Rendering across the clients you care about, every link clicked, the audience and recipient count, consent and suppression handling, a working unsubscribe, sender identity, a test send read as a recipient, and a named sign-off. The chart arranges those as gates in order.
Is this a legal compliance process?
No. It is a process map that makes a compliance check a visible step with an owner. The rules, including CAN-SPAM, GDPR and ePrivacy requirements, vary by country and by the kind of message, so check your jurisdiction and counsel for what the checklist must contain.
Why is there a stop-send step if everything is checked beforehand?
Because some problems only show after sending: bounces, complaints or a blocklisting. Since a sent email cannot be recalled, the useful control is stopping the rest of the send. The chart's exception path, "Stop the send and pause the queue", draws it.
How is this different from a content approval process?
Content approval decides whether the message is right to say. This chart checks whether the built email will render, reach the right people lawfully and be monitored once sent. The earlier stage is at /templates/content-approval-process.
Where this process fits
In most operations this process follows Campaign launch process flowchart (brief to post-campaign review).
It is one step in Campaign delivery.
Step 1: Marketing request intake process flowchart (form to backlog review)
Step 2: Campaign launch process flowchart (brief to post-campaign review)
Marketing campaign launch flowchart template: brief and sign-off, parallel creative and channel builds, pre-launch QA, go/no-go gate, first-week monitoring and a review that feeds the next brief.
Step 3: Email campaign QA process flowchart (build to post-send report) You are here
Email campaign QA flowchart template: ESP build, rendering and link test, audience check, consent and unsubscribe compliance, test send and sign-off, A/B or full send, stop-send monitoring and report.