GOOD SEND. / Field guide 01
Enterprise email campaign brief.
An enterprise email campaign brief tells CRM, creative, and campaign operations which subscribers to reach, what to send, who approves it, and how to judge the result. Use this checklist before a campaign goes into production.
Jump to the checklist01 / Audience
Decide who gets the send.
Start with subscribers eligible for the planned message in each market. Define the segments by what you know about their relationship with your brand and what each group needs from the send.
- Segment criteria
- Record the first-party signals you will use, such as recent purchases, product interests, or email clicks. Define the lookback window and how you will handle missing data.
- Overlap and priority
- Deduplicate subscribers who qualify for multiple segments. Set a priority rule so each subscriber receives the appropriate version.
- Exclusions
- Apply opt-outs, bounce and complaint suppressions, and market exclusions. Account for completed actions, frequency limits, and overlap with scheduled lifecycle sends.
02 / Message
Carry one promise across channels.
Write one sentence that states what subscribers should understand and one action they should take. Use that sentence to check the subject line, body, and call to action. Confirm that the landing page delivers the same promise and makes the next step easy to find.
If paid media supports the campaign, share the approved claim, offer, destination, and dates with that team. Use audiences approved for each channel and separate tracking links so reporting can distinguish email and paid traffic.
03 / Approvals
Give each decision an owner.
- CRM lead
- Approves segment definitions, exclusions, send priority, and the final go or hold decision.
- Brand and product
- Approve voice, creative, and evidence for campaign claims. Route claims through the company’s review process where required.
- Campaign operations
- Builds the approved versions in the email platform, reconciles segment counts, and runs test sends.
- Web and analytics
- Confirm the destination, offer details, tracking, and the event the campaign should drive. Set the reporting date before the send.
Approve audience and claims first, then creative, then the built send. Check sender identity, personalization fallbacks, mobile and dark mode rendering, accessible links, unsubscribe, tracking, and the destination. Hold the send when audience counts differ from the approved range, tracking fails, or the destination is unavailable.
04 / Measurement
Test one variable.
If you test two versions, pick one variable and randomly assign subscribers within each eligible segment. For a subject line test, keep the sender, preheader, body, landing page, and send timing consistent between versions.
Define the primary outcome, its denominator, and the reporting window before launch. Use clicks to diagnose engagement and watch unsubscribe and complaint rates as guardrails. Set the minimum effect worth acting on and the sample you need to measure it. An A/B test compares versions. Use a randomized no-send group when you need to estimate the lift from sending the campaign.
05 / One-page brief
The planning checklist.
Record these decisions in the brief your teams approve.
- Objective
- Name the subscriber action and business outcome the campaign should support.
- Audience
- List the segment rules, eligibility, exclusions, frequency limits, and send priority.
- Message and CTA
- Write the promise, supporting proof, call to action, and destination.
- Channel handoff
- Confirm who owns the landing page, paid coordination, and tracking setup.
- Test and reporting
- Specify the test variable, assignment, primary outcome, guardrails, and reporting window.
- Go or hold
- Identify approvers, checks that must pass, and who can pause or release the send.