Owner, trigger and scope
The email marketer owns the procedure, runs the after-send steps and the monthly pass, and decides on re-permission messages. Marketing operations owns the suppression listA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints., the integrations that sync unsubscribesShare of delivered emails that led the recipient to opt out. and suppressions between systems, and the consent records. Both sign off the monthly report.
There are two triggers. After every send, bounces, complaints and unsubscribes are processed so that nobody who has asked to stop is emailed again; the email campaign send SOP passes them here as its last step. Once a month, the full pass runs: inactive segments, re-permission, removal and the consent check.
The scope is marketing email lists in the email platform and any system that feeds them. Transactional email, such as receipts and password resets, follows its own rules and is out of scope, though its bounces should still feed the suppression list. How lists are built and consent is collected is covered in the list building and consent guide; this SOP maintains what that process creates.
Before you start: inputs and access
| Input | Owner | Notes |
|---|---|---|
| Send reports | Email platform | Bounces, complaints, unsubscribes by send |
| Suppression list | Marketing operations | Global list, synced to every sending system |
| Inactivity definition | Email marketer | What "inactive" means for this list, agreed in advance |
| Re-permission template | Email marketer | Approved through creative approval |
| Consent records | Marketing operations | Source, date and wording of consent per contact |
| List health report template | Email marketer | Same format every month |
You need admin access to the email platform and read access to the CRM or wherever contacts originate. The deliverability guide explains why each step matters; keep it to hand when a number in the report moves unexpectedly.
The procedure
Export bounces and complaints
After each send, export hard bouncesAn email rejected permanently by the receiving server, usually because the address does not exist or the domain cannot receive mail., soft bounces, spam complaints and unsubscribes from the send report. Most platforms suppress hard bounces and complaints automatically, but confirm it has happened and that the change has synced to every other system that can send email. Repeated soft bounces from the same address are treated as hard bounces under the rule your team has agreed.
Update suppression
Add every unsubscribe, complaint and hard bounce to the global suppression list, with the date and the reason. Check that the list syncs to the CRM and any other sending tools, so an address removed in one place is not emailed from another. Suppression is permanent unless the person actively opts back in; the ICO's direct marketing guidance and the FTC's CAN-SPAM guide both describe honouring opt-outs promptly.
Flag inactive contacts
Once a month, build a segment of contacts who have not opened or clicked within the agreed inactivity window. Treat opens with caution, since some mail clients report them unreliably, and use clicks, site visits or purchases where available. The segmentation guide explains how to build engagement segments. Move flagged contacts out of regular sends into a holding segment.
Run re-permission
Send the holding segment a short, approved re-permission message asking whether they still want to hear from you, with a single clear action to stay subscribed. Send it once, with at most one reminder, and do not dress it up as a promotion. Contacts who click to stay return to regular sends; everyone else stays in the holding segment for the next step.
Remove non-responders
After the response window closes, move non-responders out of all marketing sends. Most teams keep them in a dormant state, suppressed from marketing but retained for records, rather than deleting them. Check the removal does not hit recent customers whose engagement shows elsewhere, such as purchases, since those contacts often have high LTVTotal value a customer brings over time. and may simply read without clicking.
Check consent records
Sample contacts added since the last pass and confirm each has a recorded consent source, date and wording, or another documented basis the organisation relies on. Check that imports from events, partners or new forms carried consent data across. Contacts without a record are suppressed until it is found. This is general direction drawn from the ICO guidance and the GDPR, not legal advice.
Report list health
Complete the monthly list health report: list size, new contacts by source, unsubscribes, complaints, bounces, contacts flagged inactive, re-permission responses and removals, compared with last month. Note any send with unusually high complaints or bounces and its likely cause. Track the list's KPIA metric tied directly to an objective. trends over months rather than reacting to one figure.
A dormant segment cleared before a seasonal peak
Willowmere Teas, an invented tea retailer with 48,000 subscribers, runs its monthly pass in October before the Christmas campaign. The inactive segment holds 9,600 contacts with no click or purchase in 12 months. The re-permission email brings 1,150 back; 8,450 are moved to dormant. A consent check finds 300 contacts imported from a trade fair without a consent record, and they are suppressed. Over the following 6 sends, complaints fall by about half, inbox placement improves on the largest mailbox provider, and the campaign's click-to-purchase CVRShare of visits or clicks that convert. rises because fewer emails reach people who never buy.
QA checks
Use a seeded test address that has unsubscribed to prove suppression works end to end, rather than trusting the platform's settings page.
Before the monthly report is signed off, the email marketer and marketing operations confirm:
- Every bounce, complaint and unsubscribe from the month is on the suppression list.
- Suppression syncs to every sending system and a test address confirms it.
- Inactive segment uses the agreed definition and excludes recent customers engaging elsewhere.
- Re-permission message was approved and sent only to the holding segment.
- Non-responders are suppressed from marketing sends, not deleted.
- Consent sample checked, with any contact lacking a record suppressed.
- List health report completed in the standard format and compared with last month.
Hand-offs and records
The list health report goes to whoever owns the email programme and feeds the monthly reporting pack. Any send that caused a spike in complaints is handed back to the lifecycle email programme owner with the evidence, since the cause is usually targeting or frequency rather than hygiene. Consent gaps found in imports go to marketing operations to fix at the source, for example by changing an event form.
The suppression list, the consent records and the monthly reports are the lasting records. Keep the suppression list indefinitely so opted-out contacts can never be re-added by a later import, and keep consent records for as long as the contact is emailed, plus whatever period your data protection lead sets. Both records have to travel when the programme changes platform, and the tutorial on migrating to a new email platform loads the suppression list before any contact is imported.
When the after-send export shows bounces climbing rather than holding steady, the email bounce rate diagnosis separates list-quality bounces from refusals caused by the sender's own identity or reputation.
Common mistakes
Each of these erodes either deliverability or the consent position, and both take far longer to repair than to protect.
- Deleting unsubscribes. The record that prevents re-adding them disappears. Suppress instead.
- Suppression that does not sync. An address removed in one tool is emailed from another.
- Relying only on opens. Some clients report opens unreliably. Use clicks and purchases too.
- Re-permission dressed as a promotion. It confuses the ask. Keep it short and plain.
- Removing quiet customers. Some buyers never click. Check purchase data before removal.
- Importing without consent data. Event and partner lists often arrive without records. Check before sending.
- Cleaning only before big sends. Occasional purges cause sudden list swings. Run the pass every month.
