A closer look
Define the audience, offer and first launch
Start with one named campaign owner, one audience segment and one outcome you want the campaign to create. For example: start relevant conversations with operations leaders at businesses expanding into a new region. This is more useful than a brief that only says send more emails.
Write down what the recipient will receive or discuss, why this audience is relevant and how the next step will be fulfilled. Check that brief against the subject, message and any linked page. Resolve an unclear offer or audience before choosing the sending schedule.
List the domains, mailboxes and sending tool you plan to use, who controls them and what still needs preparation. The checklist applies whether your team manages the setup or uses a provider. Record which checks remain open so the launch decision reflects the actual campaign.
| Decision | What to record |
|---|---|
| Audience | Who qualifies, why this offer is relevant and which records are excluded. |
| Offer | What the reader can receive or discuss, including any conditions. |
| Next step | The exact request in the email and who will fulfil it. |
| First launch scope | The reviewed audience, prepared sending accounts, campaign owner and remaining checks. |
The essentials
Connect the right identity to the right workspace
Write down the sender name, sending address, domain, reply destination and sending-tool workspace. Check these against the identity the recipient will actually see. A connection labelled successful is only one part of that review.
Keep the setup owner and campaign owner visible in the record. The person managing infrastructure should know which routes are in use; the campaign owner should know where replies arrive and who handles them.
- Confirm each sending account belongs to the intended business or client workspace.
- Check that the person named in the message is authorised to represent the sender.
- Confirm the reply destination is monitored, including when a reply-to address differs from the sending address.
- Record who reconnects an account if access expires or the integration stops working.
The essentials
Review the audience and prove exclusions work
Inspect a sample of the actual contact file. Can the campaign owner explain why these people fit the offer? Check company, role, source, the date of the last contact check and any uncertain records. Remove duplicates and resolve missing personalisation before import.
An address check does not establish permission, relevance or inbox placement. Confirm the intended contact follows your organisation’s audience policy and the requirements of the services involved. Keep uncertain records out until reviewed.
Treat opt-outs and exclusions as an operational test. Microsoft’s guidance for external senders to Microsoft 365 requires an unsubscribe mechanism that is easy to find and use. Your team also needs to know how that preference reaches active and future campaigns.
- 01
Identify the exclusion source: opt-outs, known invalid contacts and people your team has decided not to contact.
- 02
Apply exclusions before scheduling and check how new exclusions reach queued follow-ups.
- 03
Use a controlled test contact to exercise the intended opt-out process. Confirm it is excluded from later sends.
- 04
Record the result, the scope tested and the person responsible for keeping exclusions current.
References [2]
Put it into practice
Test the message that will actually be sent
Send a controlled message to a mailbox your team owns or is authorised to use for testing. Use the intended sender, route and message settings. If a preview bypasses normal campaign processing, arrange a controlled test that exercises the real path before scheduling contacts.
For personal Gmail recipients, Google requires sender authentication, valid forward and reverse DNS, and TLS. Requirements differ by sender category. Ask the setup owner to check the applicable requirements and record the actual received authentication results; a DNS screenshot alone is incomplete evidence.
References [1]
The essentials
Separate target volume from confirmed starting capacity
Your monthly ambition is a planning input. The volume authorised for the first sending period is a separate decision. Include follow-ups and other scheduled traffic when checking what the selected accounts will actually send.
Record sending days, time zone, initial daily allocation, account limits and the person who approved the schedule. Do not turn unused capacity into an end-of-month burst. Google advises consistent sending, monitoring responses and reducing volume when bounces or deferrals appear.
Agree how any increase will be reviewed. The date on the calendar is not sufficient evidence to expand. Use the agreed service capacity, observed responses and the setup owner’s assessment together.
- Target: the monthly message volume you want the plan to support.
- Starting allocation: the actual schedule approved for this launch.
- Review: when the team will inspect results before changing the allocation.
References [1]
Put it into practice
Complete one launch-readiness worksheet
Copy this record into your team’s working document. Each readiness row needs a responsible person, evidence, a last-checked date and a state. Use Ready, Blocked or Needs review. An untested assumption belongs in Needs review, even when the launch date is close.
Your launch-readiness record
Copy this worksheet into your own document, then fill it in with your details.
CAMPAIGN Name / business or client: Campaign owner / backup: Audience segment and reason for contact: Sending infrastructure / remaining preparation: Sending tool / workspace: Approved sender identities / reply destination: Monthly target / sending days / time zone: Confirmed starting allocation / approved by / date: READINESS ROWS For every row record: responsible person | evidence reference | last checked | state Identity and workspace: Audience quality and exclusions: Opt-out and suppression test: Actual message and authentication test: Reply handling and follow-up stop test: Starting allocation and schedule: Monitoring access and pause authority: OPEN ITEMS Blocker | responsible person | next action | due date: DECISION Ready to schedule / blocked / needs review: Decision owner / date: First monitoring review / responsible person: Conditions requiring a pause: Next capacity review:
The checklist is a local planning aid. Ticking boxes does not verify infrastructure, certify compliance or authorise a send. Keep the supporting evidence in your team’s record.
A closer look
Decide when to pause before you press send
Agree responses to problems while the team can think clearly. Record the affected campaign or route, preserve the error or example, assign the fix and retest before resuming. Use the response itself to distinguish a temporary deferral from a permanent failure.
Microsoft says not to retransmit the same message to a recipient after a permanent SMTP rejection. Do not keep retrying simply to complete the planned volume.
| Finding | Immediate decision | Review owner |
|---|---|---|
| Incorrect identity, broken variables or misleading content | Pause the affected campaign; correct and review the actual message. | Campaign owner |
| An opt-out remains queued | Pause affected follow-ups; fix the exclusion process and repeat the test. | Campaign and tool owners |
| Authentication failure or unexpected delivery errors | Pause or reduce affected traffic as appropriate; inspect the specific response and retest. | Infrastructure owner |
| Replies are not reaching the responsible team | Pause new activity until the reply path and ownership are restored. | Campaign owner |
References [2]
The essentials
Hand over the first review, not just the launch date
Before scheduling, send the finished record to the people who own the launch. Confirm who is available for the first review and who covers absence. A named backup prevents an unresolved issue from sitting inside an unmonitored inbox.
At the review, compare scheduled activity with actual sends, inspect delivery responses, check that exclusions worked and read the replies. Separate infrastructure faults from audience or message feedback so the right person can act.
Finish with a recorded decision: continue within the agreed allocation, correct and retest, or pause. Update the worksheet when the audience, identity, route or schedule changes. Readiness is maintained through the campaign; it is not a document you complete once and forget.
A CLEAR START, WITH OWNERSHIP
Give every launch check a person, a piece of evidence and a decision. Start within the agreed allocation, keep the reply path covered and make the next review part of the launch itself.
A LITTLE MORE CLARITY
Your questions, answered.
What should an email launch checklist cover?+
The audience, sender identity, tool connection, message, authentication evidence, opt-out and exclusion process, reply handling, starting capacity and monitoring owners. Record a responsible person, evidence, last-checked date and state for each area.
Can I skip launch checks if the infrastructure is already set up?+
No. A prepared sending setup still needs to be checked with your actual audience, message, reply path, exclusions and starting schedule. Ask whoever manages the infrastructure what has been verified and what remains open before scheduling.
How many emails should I send on the first day?+
Use the initial allocation agreed for your infrastructure and campaign, including follow-ups and other scheduled traffic. This checklist does not establish a universal starting volume. Confirm the schedule with the setup owner and review actual responses before changing it.
Does a successful test email prove the campaign will reach inboxes?+
It proves only the observed test result. Use it to check the intended identity, message, authentication and reply path. Continue monitoring after launch because other recipients, traffic patterns and later configuration changes can produce different results.