Owner, trigger and scope
The email marketer runs the procedure from brief to record. The approver signs off the content and the audience on the final test; for anything carrying a claim or an offer, the approver works within the creative approval SOP. Marketing operations issues the tagged links and owns the Suppression ListA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints., the integrations that keep it in step and the consent records behind it.
The trigger is a one-off campaign email or a newsletter issue falling due in the email marketing calendar, or a brief that asks for one. Every such send runs the procedure, however routine; the routine ones are where shortcuts build up.
The scope is broadcast marketing email. Neighbouring jobs have their own pages:
| Situation | Where it is handled |
|---|---|
| Automated journeys and flows | Lifecycle email programme playbook |
| Planning a sequence of emails for a sale or launch | Sale and launch emails |
| Bounces, complaints, inactives and re-permission after the send | Email list hygiene SOP |
| An email that has already gone out wrong | Fixing a mistake in a sent email |
| Receipts, password resets and other service messages | Promotional and transactional email compared |
If the same error also appears in a live ad or page, the live ad and page error response SOP handles those copies. The SOP library routes the other recurring jobs.
Before you start: inputs and access
| Input | Owner | Notes |
|---|---|---|
| The brief or calendar entry | Email marketer, with the requester | The job of the send, the audience and the date |
| Approved copy, images and offer terms | Requester and approver | Offer terms in writing, not from memory |
| Segment definitions and the suppression list | Email marketer and marketing operations | As the segmentation guide defines tiers and preferences |
| Tagged links | Marketing operations | Issued through the UTM link request SOP and held in the link register |
| The seed list and test addresses | Email marketer | A test address on each main mail client the list uses |
The email marketer needs build and send rights in the email platform; the approver needs to receive tests. If the sending domain or platform is new, its set-up comes first and is not part of a routine send.
The procedure
Confirm the brief, the date and the frequency promised to subscribers
Read the brief and write the job of the send in a sentence: what the email should make people do, and how you will know. Check the date against the calendar. Then count what the people in the audience will receive that week, including the newsletter and any automated flows they are in, and compare it with the frequency promised at sign-up. The sale and launch emails tutorial does this for a promotion and gives the options when the total runs over: cut, narrow or tell subscribers in advance. For a newsletter, the guide to choosing a newsletter format covers the promise made at sign-up and the cadence that keeps it.
Build the segment and apply the suppressions
Build the audience the brief names, using the definitions in the segmentation guide: lifecycle stage, behaviour, engagement tierEmail subscribers grouped by how recently and often they interacted with mail, such as active, warm, cooling or inactive, with windows set by cadence. and preferences. SegmentationDividing a market or customer list into groups that need different offers or messages. decides who should receive the email; suppression decides who must not. Apply the suppression list after the segment is built, not before, so that unsubscribes, bounces and complaints from other sends are removed even if they arrived since the segment was defined. Suppress the inactive tier the hygiene routine has set aside, and anyone who already did what the email asks. The list itself only holds people with the right permission, which the list building and consent guide describes from the ICO's direct marketing guidance; a segment that pulls in addresses from outside it stops here.
Build the email from the template with tagged links
Build from the team's approved template, not from a copy of last month's email, so old links and old offers do not travel. The newsletter design and copy guide sets the structure: a subject line that makes a true promise about the lead item, Preheader TextThe short line of text an inbox shows after or below an email's subject line, taken from the start of the message. written deliberately, scannable copy and one main call to action. Every link is a tagged link from the register, carrying UTMURL tags identifying traffic source. parameters issued through the link request routine, so results can be read later. Keep honest sender and subject details: the sale and launch tutorial notes that the FTC's CAN-SPAM guide expects subject lines not to mislead recipients. This is general direction, not legal advice.
Run the campaign QA checklist
Run the email campaign QA checklist on the built email: audience and suppression, content, links and tracking, rendering, accessibility, compliance and send settings. Run it in full every time; its compliance lines carry the visible unsubscribe link, the one-click unsubscribe headers and passing authentication that Google's sender guidelines document for bulk marketing mail, as the deliverability guide explains them. Fix each failed line at source and run that group again. Do not tick a line that was checked on a previous send.
Send tests and get approval of content and audience
Send tests to the seed list and the test addresses, and send the final test to the approver with the segment definition and its count. The approver signs off two things: the email as it will arrive, and the audience it will reach. Approval of an earlier draft does not count; anything changed after approval goes back for another look. Which further reviews that look reopens depends on what changed, as the guide to handling changes after approval explains. Where the email carries a claim, a price or an offer, it follows the creative approval SOP, including its claims and compliance check. Record who approved, which version and when.
Schedule the send and pause anything that would collide with it
Schedule the send at the time the calendar sets, in the audience's time zone. Then look at what else will reach the same people: other broadcasts that day, automated flows that would send an offer the same morning, a reminder from another team. The calendar template's flows-in-play column records which flows reach the same people and whether they pause. For a large send, or one from a new domain, the deliverability guide explains why sudden spikes in volume are a risk, and the segmentation guide names the most engaged subscribers as the right audience for the first batch.
Watch delivery, complaints, unsubscribes and links after the send
After the send, watch what the platform and the mailbox providers report: bounces, deferrals, complaints and unsubscribes, and the clicks on each link. The deliverability guide explains how the spam rateShare of delivered emails that recipients marked as spam. and DeliverabilityWhether sent email reaches the inbox rather than spam or rejection, decided by sender reputation. signals are read, and points to the providers' own tools and documented thresholds rather than repeating them. If unsubscribes jump against the sends around it, the unsubscribe rate spike diagnosis locates the cause. If a link is broken or the email is wrong, stop and switch to fixing a mistake in a sent email.
Record the results and hand list problems to hygiene
Read the result against the job in the brief. The email metrics and testing guide reads clicks and the outcome the brief named, measured where it happens, and treats opens as a weak signal within one list. The CTR calculator for email campaigns works out unique clicks over delivered emails. Write the row in the send log, then pass bounces, complaints and unsubscribes to the email list hygiene SOP so nobody who asked to stop is emailed again.
A theatre's season newsletter (illustrative)
The season announcement and the segment built too early
Zantuvo Playhouse, an invented small theatre, sends its season newsletter to past bookers and newsletter subscribers. The brief's job is ticket bookings for the first 4 productions, and the calendar sets a Thursday send.
The frequency check finds that 1,200 past bookers are also in a post-show feedback flow that sends on Thursdays; the flow is paused for the day. The segment was built on Monday: 9,400 subscribers and past bookers, plus a lapsed-member segment of 2,100. At the suppression step on Wednesday, the email marketer sees that the lapsed-member segment was built before the last unsubscribes synced from the box office system. Rebuilding it and applying the suppression list removes 86 people who had unsubscribed that week.
The QA checklist catches a booking link without campaign parameters, reissued through the link request routine. The approver signs off the final test and the segment count. After the send, 3 hard bounces and 1 complaint go to the hygiene routine.
The open rate looks high, but the record reads the send by its job: 640 unique clickers and 212 bookings tracked from the email's tagged links in the following fortnight.
QA checks
Before the send is closed, the email marketer checks the record against this list. A failed check is fixed and noted in the send log, so the next send starts from a corrected process.
- The audience matches the brief and the suppression list was applied after the segment was built.
- Every link is a tagged, tested link from the register.
- Unsubscribe and sender details are present and work.
- The approver signed off the final test, not an earlier draft.
- Results are recorded against the brief's job, not only opens.
Hand-offs and records
The procedure hands on three things. Marketing operations receives the bounces, complaints and unsubscribes through the list hygiene routine, which keeps the suppression list current for the next send. The requester receives the result read against the job in the brief, with any caveat on how conversions were attributed. The calendar owner receives anything the send taught about timing or collisions, so the next entry in the calendar accounts for it.
The lasting record is a row in the send log: date, segment and size, suppressions applied, subject line, approver, links issued, and the results read against the brief, with any list problems passed to the hygiene routine.
Common mistakes
Most of them come from treating a routine send as too small for the procedure.
- Copying last month's email. Old links, old offers and old dates travel with it. Build from the template.
- Suppressing before segmenting. Apply suppressions last, so recent unsubscribes are removed.
- Ignoring the flows. A broadcast and an automated offer on the same morning break the frequency promised.
- Approving the draft. The approver signs off the final test and the audience, not an earlier version.
- Untagged links. A link without campaign parameters leaves the result unreadable later.
- Ticking the checklist from memory. Each send gets its own QA pass.
- Judging by opens. Read clicks and the outcome the brief named.
- Leaving bounces and complaints in the platform. Pass them to the hygiene routine after every send.
