Key Points
Email campaign QA (quality assurance) is the structured process for confirming that a campaign meets quality, compliance, and deliverability standards before it reaches the audience
QA and the pre-send check are complementary but distinct: QA is the ongoing process of maintaining standards throughout campaign production; the pre-send check is the final gate immediately before the campaign launches
A complete pre-send check has seven mandatory items that must all pass before the campaign proceeds — missing any one of them produces a predictable failure mode
Most B2B email campaign failures — personalisation errors, broken links, missing compliance elements, deliverability damage — are preventable through the pre-send check and are the direct consequence of skipping it under time pressure
Analyze this article with
Email campaign QA is the quality management practice that is most consistently skipped in B2B email teams under time pressure. The team has invested significant effort in content production, data sourcing, and platform configuration — the campaign is ready to send and the send date has arrived. The pre-send check is the final step before launch. Under time pressure, it is the step most frequently curtailed or skipped entirely.
The consequence is predictable: a campaign that was 95 percent ready reaches the audience at 95 percent quality — and the 5 percent that was not checked produces the broken unsubscribe link, the wrong personalisation token, the missing physical address, or the list that was not checked against the suppression file. These failures are not catastrophic individually, but they are visible to the audience, they damage the programme's credibility, and in compliance terms they are avoidable legal exposures.
Building QA and the pre-send check into the campaign workflow as non-negotiable steps — with the same discipline and the same ownership assignment as content production and platform configuration — is what converts the pre-send check from a best intention into an operational reality.
The Seven-Item Pre-Send Checklist
Item One — Physical Address in the Footer
Confirm that the sending organisation's valid physical postal address appears in the email footer. This is the CAN-SPAM requirement most commonly missing in first-time programme setups and most commonly assumed to be present in established programmes where the template has not been recently reviewed.
Check: open the test send in both desktop and mobile email clients and confirm the physical address is visible in the footer in both views. A footer that is visible on desktop but cut off in mobile rendering may not satisfy the CAN-SPAM physical address requirement in the mobile context.
Item Two — Unsubscribe Link Functional
Confirm that the unsubscribe link in the email is functional — it renders correctly, routes to the correct opt-out page, and records the opt-out in the programme's suppression file. A broken unsubscribe link is simultaneously a CAN-SPAM compliance failure, a GDPR violation (right to object not honoured), and a recipient experience failure.
Check: click the unsubscribe link in the test send and confirm the opt-out page loads correctly and the unsubscribe action is processed. Confirm in the platform that the test contact's unsubscribe is recorded.
Item Three — Personalisation Tokens Correct
Confirm that all personalisation tokens render correctly for five to ten contacts from the actual send list — not just for the test seed addresses. Personalisation token failures most commonly occur when: the CRM field the token references is empty for some contacts (producing a blank where a name or role should appear), the field mapping was configured incorrectly (a role field appearing where a company name is expected), or the test contacts have complete data while production contacts have incomplete data.
Check: run a preview send to five to ten contacts randomly selected from the actual send list and confirm all personalisation tokens render correctly.
Item Four — Database Providers Suppression Match Confirmed
Confirm that the most recent export delivery documentation from Database Providers confirms that the campaign's contact list was matched against the current suppression file before delivery. For campaigns using the Database Providers multi-unit account structure, this confirmation is included in the standard delivery documentation.
For campaigns sourced from other providers or from internal data, confirm that the current unified suppression file was applied to the contact list before it was imported into the sending platform.
tem Five — Domain Reputation Confirmed at Medium or High
Check the sending domain's reputation score in Google Postmaster Tools before any campaign send. A domain reputation at Low means a significant proportion of emails will route to spam regardless of list quality — the campaign should be delayed until the reputation is restored. A domain reputation at Medium requires heightened monitoring of the first batch's bounce rate. A domain reputation at High confirms standard deliverability expectations.
Item Six — CRM Attribution Active
Confirm that the CRM connection to the sending platform is active and will attribute opens, clicks, and replies from this campaign to the correct campaign record. An attribution configuration error discovered after the campaign sends cannot be retroactively corrected — the pipeline contribution from the campaign will be unattributable.
Item Seven — Send Schedule Correct
Confirm the send date, send time, and time zone in the platform configuration. A campaign configured to send at 9:00 am GMT that is intended to send at 9:00 am EST will reach the EST audience at 2:00 pm — below the optimal morning window. A campaign configured to send on Wednesday that was intended for Tuesday has missed the optimal day and the planned send window.
The email marketing guide from Database Providers covers the full pre-send checklist in the context of the campaign workflow. For the suppression match documentation that covers item four of the checklist, Database Providers provides email data list providers contacts and buy email address database segments with delivery documentation that directly satisfies the suppression match confirmation requirement.
How to Make the Pre-Send Check Non-Negotiable
The pre-send check becomes non-negotiable when it is built into the workflow as a blocking step — the campaign cannot proceed to the send configuration stage without a completed pre-send checklist attached to the campaign record. This is the institutional safeguard described in earlier blogs: not a reminder to complete the checklist, but a workflow dependency that prevents proceeding without it.
Implementation: add a checklist completion field to the campaign brief template. Before the send is approved in the platform, the checklist must be marked complete in the campaign tracking document. If it is not marked complete, the send is not approved.
FAQ's
The marketing operations team member responsible for platform configuration — not the campaign manager who produced the content. The pre-send check is a technical and compliance review, not a content review. Assigning it to a different team member from the content producer provides a second perspective and prevents the content producer from self-certifying their own work.
Fifteen to twenty minutes for an experienced operator familiar with the checklist items. The first time the checklist is used, it may take 30 to 45 minutes as the operator builds familiarity with where to find each confirmation. After the first five to ten campaigns, the 15-minute target is consistently achievable.
The campaign send is delayed until the failing item is resolved. The time pressure of the send date is not a justification for proceeding with a failing checklist item. A delayed send is always preferable to a sent campaign with a compliance failure, a broken unsubscribe link, or incorrect personalisation.
The seven core items apply to both campaign types. Promotional campaigns should add a commercial compliance review (honest subject line, no deceptive claims in the body). Informational campaigns should add a content quality gate (does this edition meet the editorial standard?). The campaign-type-specific additions sit on top of the seven universal items.
The pre-send checklist is the operational completion of the approval process — it confirms that the approved campaign has been correctly configured and is ready to send. The approval process confirms the campaign's strategic and content quality. The pre-send checklist confirms the campaign's operational and compliance readiness. Both are required; neither substitutes for the other.
