Scope: what this audit covers and what it does not
The scorecard covers everything that makes an email programme work over months rather than a single send: how subscribers join and what they agree to, how the list is kept clean, whether sending domains are authenticated and mail reaches the inbox, how the audience is segmented, which automated lifecycle flows exist and how well they perform, the quality of content and design, the testing habit and how results are reported. It applies to retail newsletters, subscription businesses and business-to-business nurture programmes alike.
Individual campaigns are out of scope; they are checked before sending with the email campaign QA checklist. The mechanics of inbox placement are taught in the email deliverability guide, and the routine of pruning and suppressing addresses sits in the email list hygiene procedure. Setting up a new sending domain or platform before its first campaign is the job of the email sending domain setup checklist. The audit gives general direction on consent rules but is not legal advice. Analytics attribution for email visits belongs to the analytics scorecard in the audit library.
Before you score: access and evidence
You need admin access to the email platform, read access to the sending domain's DNS records, and a contact on the team who knows how sign-up forms and data imports work. Agree a fixed window that covers a full sending cycle, including seasonal campaigns if they matter, and keep it for every rescore.
Collect the sign-up sources and the wording shown at each one, the record of where imported contacts came from, and the unsubscribe and complaint handling. Look up the domain's authentication records and any reputation data the mailbox providers make available. Export list growthNet change in an email list over a period as a share of its size at the start., bounces, complaints and unsubscribes by month. List every automated flow with its trigger, its emails and its results. Gather the last few reports the team sent to leadership, because reporting is scored on what decision-makers actually see.
Criteria and scoring
Rate each row missing, partial or solid. Consent and authentication are gates.
| Criterion | What good looks like | Score guidance |
|---|---|---|
| Consent records (gate) | Every subscriber's source, date and agreement can be shown | Missing: unknown sources or bought lists / Partial: gaps for older contacts / Solid: complete records |
| Unsubscribe handling | Clear unsubscribe in every message; honoured promptly across all tools | Missing: hard to find or not synced / Partial: works with delays / Solid: easy and prompt |
| List hygiene | Bounces suppressed, long-term inactive contacts re-engaged or removed | Missing: never cleaned / Partial: occasional / Solid: scheduled routine |
| Authentication (gate) | Sending domain authenticated with the records providers expect, aligned with the from address | Missing: none / Partial: some records or misaligned / Solid: complete and aligned |
| Sender reputation | Complaints low, no blocklisting, reputation data healthy | Missing: blocklisted or high complaints / Partial: warning signs / Solid: healthy |
| Inbox placement | Mail lands in the inbox at the main providers; seed or panel checks done | Missing: known spam-folder issues / Partial: unchecked / Solid: checked and good |
| Segmentation | Sends targeted by behaviour, lifecycle stage or interest, not only to everyone | Missing: one list for everything / Partial: basic splits / Solid: meaningful segments |
| Welcome flow | New subscribers greeted promptly with a sequence that sets expectations | Missing: none / Partial: single email / Solid: designed sequence |
| Lifecycle flows | Key moments covered, such as abandonment, post-purchase, win-back or nurture | Missing: none / Partial: one or two / Solid: the moments that matter covered |
| Flow maintenance | Flows reviewed on a rhythm; content, offers and links current | Missing: set and forgotten / Partial: occasional checks / Solid: reviewed regularly |
| Content and design | Clear purpose per email, readable on mobile, accessible, on brand | Missing: cluttered or broken on mobile / Partial: inconsistent / Solid: clear and consistent |
| Frequency and fatigue | Sending cadence matched to engagement; pressure managed by segment | Missing: everyone gets everything / Partial: some rules / Solid: managed by segment |
| Testing practice | Tests planned, one variable at a time, results recorded | Missing: no tests / Partial: ad hoc / Solid: planned and logged |
| Reporting | Reports outcomes such as revenue or leads by send and flow, not opens alone | Missing: opens only / Partial: clicks with some outcomes / Solid: outcome-led |
For consent, use the UK ICO's direct marketing guidance or the US FTC's CAN-SPAM compliance guide as general direction for the markets you send to, and refer specific questions to a privacy adviser. For testing and reporting, the email metrics and testing guide explains which measures still mean something now that mail clients mask opens.
The open rate versus click rate comparison explains why a reporting pack built on opens scores as a weakness here.
How to score and prioritise
Score the gates first. A missing consent score is a legal and reputational exposure as well as a data problem: mail to people who never agreed to it drives complaints, and complaints damage delivery for everyone else on the list. A missing authentication score means a growing share of mail may never be seen. Either one pushes every other row down the list.
Then rank the remaining weaknesses by the revenue or relationship they touch. Missing lifecycle flows usually rank high, because flows reach people at the moments they are most likely to act and they keep working once built; their effect shows over time in LTVTotal value a customer brings over time. rather than in a single send. Hygiene and frequency problems rank high when reputation shows warning signs. Content polish ranks lower unless emails are broken on mobile. Reporting ranks high when budget or headcount decisions are being made on open ratesShare of delivered emails recorded as opened..
Reading the result: what to do with each band
Red means a gate scored missing. Stop sending to contacts with no consent record, put authentication in place, and pause large broadcasts until the sending domain is set up correctly. Rescore after a full sending cycle on the repaired set-up.
Amber means the gates hold but several rows are weak. Build or repair the missing flows first, starting with welcome and the flow closest to purchase, then fix segmentation and frequency, then reporting. Treat each flow change as a chance to run an A/B TestControlled comparison of two variants. on one element.
Green means the programme is sound. Keep a quarterly rescore, review flows on a fixed rhythm, and move effort to deeper personalisation and testing aimed at CVRShare of visits or clicks that convert. from email visits.
From audit to action plan
Each weak row becomes a plan line with the finding, the fix, the owner and the rescore date. Separate technical fixes (authentication, syncing unsubscribes) from content and flow work, because they sit with different people. Present the band, the gate findings and the top flows to build; keep the full table as the working document.
A homeware brand without flows
A homeware brand with 38,000 subscribers sends a weekly newsletter to everyone and nothing else. Consent records score partial: around 4,000 contacts were imported from a trade show with no record of agreement. Authentication scores solid. Lifecycle flows and segmentation both score missing, and reporting scores missing because the monthly report shows only opens. The band is red until the trade-show contacts are suppressed pending a re-permission email. The team then builds a three-email welcome flow and a basket-abandonment flow. Six months later, flows account for about 30% of email revenue from under a tenth of the sends.
Common mistakes
- Auditing the newsletter and calling it the programme. The broadcast is the visible part. Flows, consent and authentication decide most of the outcome.
- Scoring reports on open rates. Opens are distorted by mail-client privacy features. Score whether outcomes are reported.
- Keeping old contacts for the list size. Unengaged and unconsented addresses hurt delivery for everyone else. Clean them out.
- Building flows and never reviewing them. Offers expire and links break. Flow maintenance is a criterion for that reason.
- Treating the consent row as legal sign-off. The audit shows the gaps; a privacy adviser confirms the rules.
- Judging flows on a single send. A flow's value builds over months. Score its results across the whole evidence window, not its latest email.
