Operations
Part of Running email software with a durable record for every campaign
Six steps that take an email campaign from open job to recorded closure
Move an email campaign through six steps: intake, audience freeze, evidence hand-off, tests, approval and closure, with PECR, DMARC and ICO breach checks.
An email marketing software operating workflow needs an evidence packet, named hand-offs and reversible state changes. A calendar entry labelled "send" is not a process.
What to take away
- An email campaign needs an evidence packet, named hand-offs and reversible state changes, not just a calendar entry.
- Subscriber status and collection circumstances matter to PECR, so intake must point to evidence, not a consent label.
- Suppression lists and screening must reach the send population, or the job pauses and the route is corrected.
- Authentication passes belong in technical evidence and do not answer the PECR question or promise delivery.
- Closure reconciles logs, assigns retention actions and records what must change, with every open action owned.
Step 1: open the job
The requestor records the purpose, message type, intended recipients, acquisition route, geography, deadline and team roles for service ownership. Attach the proposed claims and any supplier dependency. If the request mixes a receipt, requested information and promotion, split the content or ask for a specific classification decision.
Intake record fields
- Purpose and message type
- Intended recipients and acquisition route
- Geography and deadline
- Service owner
- Proposed claims and supplier dependency
- Evidence pointer, not copied consent label
Subscriber status decides which PECR rule applies. The ICO's electronic mail marketing guidance treats sole traders and some partnerships as individuals, who can be emailed only with specific consent or under the soft opt-in. The intake record must therefore point to evidence, not a copied consent label.
Step 2: build and freeze the audience
The data owner writes the inclusion query and exclusion rules, using the quality checks as the test list. Preserve the query version, source snapshot, duplicate treatment, suppressions and reconciliation count. Test a deliberately suppressed fixture and a record whose status changed after extraction.
Audience freeze and suppression test
- Write inclusion query and exclusion rules
- Preserve query version and source snapshot
- Record duplicate treatment and suppressions
- Reconcile counts
- Test suppressed fixture and changed-status record
- If objection failspause, stop automation, correct, rerun
People have an absolute right to object to or opt out of direct marketing at any time. Good practice is to keep a do-not-email list of businesses that object or opt out and screen any new marketing lists against it.
If an objection fails to reach the send population, move the job to paused, stop downstream automation, correct the route and rerun the test.
Step 3: hand approved evidence to production
The content owner supplies a numbered copy version, subject line, sender identity, destination pages, claims file and expiry dates. The privacy and PECR decisions identify their factual scope. The accessibility reviewer states the clients, zoom, keyboard and assistive-technology checks performed, along with any gap.
The operator receives signed inputs rather than interpreting them. Record the exact audience snapshot, template, tracking state, personalisation fallback, sending domain, reply route and schedule in a configuration sheet. The operations and delivery guide shows how to keep that record durable.
Step 4: test the configured release
Use synthetic records and authorised test inboxes. For each test, write the expected result before execution, then store the observed result, environment, tester, timestamp and evidence. Cover exclusions, links, fallback text, plain text, layout, tracking state, authentication, logging and rollback.
The NCSC's email anti-spoofing guidance describes SPF as publishing the IP addresses trusted for your domain, DKIM as signing your mail, and DMARC as setting the policy for mail that fails both. They are separate controls. An authentication pass belongs in the technical evidence column. It does not answer the PECR question or promise delivery.
Step 5: approve or return
The release owner compares the same content, audience, settings and test versions reviewed by specialists. Privacy, PECR, claims, accessibility, security, commercial and finance gates each have their own decision. One failed gate returns the job to the relevant owner; it cannot be offset by another approval.
Record "approved", "paused" or "rejected", plus the reason and the restart evidence. The ninety day plan shows how that evidence file builds up over a quarter. A change to copy, selection logic, tracking or sending infrastructure reopens the affected checks.
Step 6: release, monitor and close
The operator confirms the immutable release version and watches errors, replies, complaints, suppression events and supplier notices. Escalate against pre-agreed definitions, not an invented industry threshold.
Where an event may involve personal data, assess the likely risk to people's rights and freedoms. If a risk is likely, you must notify the ICO as soon as possible and, where feasible, within 72 hours.
Closure reconciles the audience and release logs, captures exceptions, assigns retention or deletion actions and records what must change. Review again after a complaint pattern, failed test, supplier change or unclear hand-off. The workflow is complete only when every open action has an owner and a condition for safe restart.
Before you act
- Record purpose, message type, recipients, acquisition route, geography, deadline and service owner.
- Preserve query version, source snapshot, duplicate treatment, suppressions and reconciliation count.
- Obtain signed inputs for copy, sender identity, claims file and expiry dates.
- Test exclusions, links, fallback text, plain text, layout and tracking state.
- Compare content, audience, settings and test versions reviewed by specialists before approval.
- Reconcile audience and release logs, capture exceptions and assign retention actions.
Common questions
What should happen if an objection fails to reach the send population?
Move the job to paused, stop downstream automation, correct the route and rerun the test. Do this before any further sending occurs.
Does an authentication pass answer the PECR question or promise delivery?
No. An authentication pass belongs in the technical evidence column. SPF, DKIM and DMARC are separate controls, and none of them shows that the recipient agreed to receive the message.
When is the workflow complete?
The workflow is complete only when every open action has an owner and a condition for safe restart. Closure reconciles audience and release logs, captures exceptions, assigns retention or deletion actions and records what must change.
