Quality checks to run on suppression, claims and rollback before an email release

This email marketing software quality checklist is a release gate, not a score. An unchecked mandatory item pauses the send until an authorised owner supplies evidence or accepts a documented exception within their remit.

The non-ranked checklist was compiled on 5 September 2026 for email work operated from England. It covers production readiness and excludes product rankings, deliverability promises, legal certification and invented pass rates. No supplier funded it, and no product was tested.

What to take away

Treat the checklist as a release gate, not a score, so an unchecked mandatory item pauses the send.
Suppression records should preserve objections rather than simply delete them, per ICO preference guidance.
Each objective claim needs current documentary evidence, a named owner and visible qualifications.
Accessibility testing must name the clients, devices and assistive technologies actually covered.
The release owner confirms every approval covers the same version before recording go, pause or reject.

Scope and identity

The record names one purpose, message classification, recipient population, geography and accountable owner.
The sender identity, reply route, subject line, copy, destinations and release window match the reviewed version.
Requested or service information has not acquired promotional material without a fresh classification decision.

Audience and suppression

The data source, collection context, notice or permission evidence where relevant, query and snapshot are recorded.
Inclusion, exclusion, deduplication and subscriber-category rules are reproducible.
Known suppressed fixtures stay excluded after imports, joins and restores.
Late objections have a route into the final population before release.

The ICO's preference guidance supports suppression rather than simple deletion when an organisation needs to remember an objection. Qualified privacy review must set retention and access for the actual record.

Tracking and data use

Every pixel, redirect, identifier and linked-page technology appears in the inventory.
The configured state matches the approved decision and the test evidence.
Exports, logs and integrations expose only the data needed by authorised roles.

The ICO's storage and access guidance requires analysis of the specific technology and purpose. A preview that loads does not settle that assessment.

Claims and recognition

Each objective claim points to current documentary evidence and an owner.
Qualifications remain visible where a recipient will encounter the claim.
Commercial relationships, incentives or affiliate interests are disclosed in context.
A recipient can recognise the message as marketing where the rules require it.

CAP publishes separate material on substantiation and recognition of marketing communications. These sources support the checks; they do not clear a particular message.

Accessibility

Reading order, headings, link purpose, colour reliance, zoom and plain text have been examined.
Personalised and fallback variants have the same accessibility review.
The test record names email clients, devices, keyboard use and assistive technologies actually covered.
Unrepresented environments remain limitations rather than assumed passes.

The Great Britain service-provider disability guide explains anticipatory reasonable-adjustment duties. Legal and accessibility specialists must judge the service and evidence; a software feature cannot certify it.

Configuration, security and recovery

Sender domains, SPF, DKIM and DMARC evidence match the intended route.
Publishing, audience export and administrator access follow least privilege.
A restore or rollback route has an owner, current baseline and tested instruction.
Logs can identify who changed the audience, content or configuration.

NCSC's email-security guidance supports staged authentication controls. It makes no promise about inbox placement or marketing permission.

Final decision

The release owner verifies that every approval covers the same version. Record go, pause or reject, the decision time, remaining exposure and restart evidence. After release, reconcile recipient selection, complaints, suppression events and defects. Close the job only after retention or deletion actions and post-launch owners are assigned.

Before you act

Name the purpose, classification, population, geography and accountable owner.
Confirm suppressed fixtures stay excluded after imports, joins and restores.
Inventory every pixel, redirect, identifier and linked-page technology.
Point each objective claim to current evidence and an owner.
Check reading order, headings, link purpose, colour reliance and zoom.
Verify SPF, DKIM and DMARC evidence match the intended route.

Common questions

What happens if a mandatory checklist item is unchecked?

The send pauses until an authorised owner supplies evidence or accepts a documented exception within their remit. The checklist is a release gate, not a score, so an unchecked mandatory item blocks release rather than merely reducing a rating.

Why does the article favour suppression over deletion?

The ICO preference guidance supports suppression rather than simple deletion when an organisation needs to remember an objection. Qualified privacy review must then set retention and access for the actual record, so the objection remains effective.

Does a working email preview settle the storage and access assessment?

No. The ICO storage and access guidance requires analysis of the specific technology and purpose, and a preview that loads does not settle that assessment. The configured state must also match the approved decision and test evidence.