Operations
Part of Running email software with a durable record for every campaign
Email marketing software launch gates before publication
An email marketing software launch gate framework for testing claims, accessibility, authentication, security and contract terms before publication.
What to take away
- This is a gate framework for an email marketing software launch, not a review of a named product; it authorises no launch.
- A valid review must name the reviewer, the legal supplier entity, the product and edition, scope, evidence cut-off and decision authority.
- Run Mailchimp, Klaviyo or Brevo through the same gates; supplier documentation supports a claim but never proves behaviour in your account.
- Record each gate as pass, fail, not tested or not applicable, and never average non-compensating gates into a score.
- A verdict returns only when the accountable owner and the specialist veto holders sign the same release version.
The named elements a valid launch review must record
A launch review is a signed file, not an article. It records six items before any verdict appears: reviewer name and role, supplier legal entity, exact product and edition, operating scope, evidence cut-off date, and decision authority.
Reviewer identity is part of the test. A verdict signed by someone who never opened the account is a summary of marketing pages, not a result.
If an item is missing, say so. Do not infer a feature from a supplier page, and do not fill a gap with a rival tool's performance.
A desk shortlist is only a starting point. Compare the email marketing software shortlist for England against each gate before treating any tool as tested.
How to appoint the decision authority
Record role titles and dates, because a title outlasts a person.
- The board or senior management team names one accountable owner, such as the Head of CRM or the Marketing Director.
- Name a deputy who can stop a release when the owner is unavailable.
- Appoint veto holders for data protection, accessibility and security; each can halt a release alone.
- File the appointment, its date and its scope with the review.
Without a named authority there is no go or no-go outcome, only an opinion.
Trace the data, permission and suppression path
Run one synthetic recipient through the whole path before any real send.
- Add the synthetic address at source and record the lawful basis and collection route.
- Post it to the audience and check the consent field, its timestamp and source label.
- Add the address to suppression, then send a campaign and confirm the send is blocked.
- Raise a late objection, restore a backup and disconnect one integration, then repeat the send.
- Export the record and list what leaves the system, and where it goes.
The ICO's electronic mail guidance explains why the subscriber's circumstances and collection route decide whether the message is lawful.
Challenge claims, accessibility and security
Objective claims need a document held before release. CAP's substantiation advice marks the advertising boundary but does not clear your wording. Pair it with your own checking an email advert for claims and permission.
| Gate | Test step | Fails when |
|---|---|---|
| Claims | Match each objective claim to a held document | The file holds only a supplier page |
| Accessibility | Test the final message, fallback and destination with stated clients, keyboards, zoom and assistive technology | No assistive technology was used |
| Authentication | Check SPF, DKIM and DMARC on the sending subdomain | DKIM alignment is missing |
| Security | Review privileged access, release logging, backup and incident suspension | Administrators share one credential |
| Contract | Read liability, renewal, exit and data return terms | No exit route or data return is defined |
Accessibility is anticipatory. The Great Britain disability guidance for service providers frames it as a duty to plan and adjust in advance, not a product conformance certificate.
Security evidence comes from the account, not the brochure. NCSC's guidance on using SaaS securely covers access control, logging and supplier contact routes. Ask for the audit log export and an incident contact name in writing.
Commercial terms sit beside the technical gates. Use the contract areas to check before signing so liability, renewal and exit are settled before launch, not afterwards.
Example: one filled gate row and its restart condition
Use this row shape when you record a failed gate.
Gate: authentication. Criterion: DKIM aligned to the sending subdomain. Product: Klaviyo, sending from mail.example.co.uk, an illustrative domain. Result: fail. Evidence: raw headers from a seed mailbox. Restart condition: re-publish the selector for the sending subdomain, re-run a signed test and attach the new headers.
The failed gate pauses the review, and no verdict is published while it stands. The sender, the deliverability specialist and the accountable owner sign the same recording before the gate reopens.
Common questions
Does this page review a named email marketing product?
No. It names Mailchimp, Klaviyo and Brevo only as platforms to pass through the gates. It publishes no reviewer, edition, test result or verdict, so treat it as the checklist a real review must satisfy.
What must a launch review name before publication?
The reviewer, the supplier legal entity, the product and edition, the operating scope, the evidence cut-off and the decision authority. Missing any one turns the review into an opinion.
Who can authorise a launch?
The accountable owner named by the board or senior management team, with data protection, accessibility and security veto holders able to stop a release alone.
What happens when a gate fails?
The review pauses. It restarts only when the missing evidence is attached and the named specialists sign the same release version. Outcomes are go, limited release, pause or reject.
