An email campaign pre-send checklist that fits the decision

Confirm who receives what

Review the audience, exclusions, channel permissions, language versions, and personalization fallbacks. Sample relevant customer records rather than trusting a segment name. Check whether active automations create overlap for the same people.

In Sendvio, inspect the configured schedule and time zone. Confirm whether the action will save a draft, schedule a campaign, or activate a journey. Those are different decisions and should not be hidden inside a generic “looks good.”

Use a short checklist backed by completed tests

The final reviewer should be able to answer each item using the actual campaign and the relevant preparation evidence. If an answer is unknown, mark it unresolved rather than checking the box because the campaign is due. The deeper work belongs in preparation; this list confirms that it was completed for the release in front of you.

• Audience: the intended people qualify, exclusions and channel permissions are respected, and overlapping journeys have been considered.
• Promise: product facts, offer terms, stock, and deadline match the approved brief and the destination.
• Message: sender, subject, preview, language versions, and long or missing personalization values have been reviewed in the final layout.
• Route: primary links, relevant discount cases, mobile destination, and the supported unsubscribe or opt-out process work.
• Action: the exact campaign or journey, final version, schedule, time zone, and intended activation state are confirmed.
• Ownership: approval is recorded, post-launch monitoring has an owner, and the response to a material failure is understood.

Verify the promise and route

Check product facts, prices, eligibility, expiry, and availability. Follow the main links and test relevant discount paths. Ensure the destination agrees with the email or SMS and is usable on a phone.

Review the rendered message with long and missing data values. Check the sender, subject, preview, main action, and unsubscribe experience. A visual screenshot alone cannot verify every link or audience rule.

Keep the evidence close to the decision

Attach or reference the controlled test outcomes, final preview, and factual brief in the team's normal workflow. The reviewer should not have to search through several conversations to determine which price was approved. Keep private customer data and access links out of broadly shared evidence.

Distinguish a release-blocking failure from an optional refinement. A broken primary destination or wrong audience needs correction before the affected send. A preference between two accurate headings may not. This makes the checklist useful under time pressure without turning it into a reason to ignore important problems.

If the final version changes, reopen the affected items. A revised button label may alter meaning or wrap poorly; a new audience condition changes eligibility; a moved schedule can cross an offer deadline. Approval should follow the consequences of the edit rather than the apparent size of the change.

Name the owner of the next step

Record the approved version and who will monitor the first results. Decide how unexpected delivery problems, incorrect offers, or customer complaints will be handled. Keep a practical way to pause or correct the relevant work.

If a material change happens after approval, revisit the affected checks. The checklist should create clarity, not a ceremonial signature. A concise review works when everyone knows what was verified and what action that verification authorizes.

After launch, note any issue the checklist missed and decide whether it reveals a missing check or a failure to perform an existing one. Add only the information that would change a future decision. A concise checklist stays effective when its items remain specific, consequential, and supported by real verification.