Pre-launch workflow planner

Plan a reviewable email testing path for your next release

Choose the release size, email types, and number of reviewers to generate a time budget and execution checklist. Planning results stay on this page.

Generate test plan

Allow 45 minutes

Basic regression

Create a dedicated temporary address for this round.
Verify code delivery, expiration, and error responses.
Save screenshots of the subject, sender identity, timestamp, and body.
Have a second team member review the key templates.

Execution cadence

Four gates turn “it seems to have arrived” into release-ready evidence

Each gate has a defined output. Without evidence, do not move on—and never use a personal inbox to store test materials.

Prepare

Define samples and addresses

List every trigger, template, language, and environment. Assign a dedicated address to each test batch so old messages do not affect your judgment.

Template checklist
Address assignment
Expected subject

Execute

Trigger and record

Trigger business actions in a fixed order, recording the UTC time, task ID, and receipt time. If something fails, preserve the initial state instead of retrying repeatedly.

Send evidence
Arrival time
Failure response

Review

Compare content layers

Check the subject, sender, HTML, and plain text together. For verification codes, confirm the length, validity period, error message, and repeated-use behavior.

Brand header
Plain-text fallback
Links and attachments

Release

Record decisions and open items

Record passed checks, blockers, and known limitations separately. A second team member must review high-risk templates before the release window.

Pass checklist
Blocking issues
Owner

Sample matrix

Cover normal, delayed, and error paths at a minimum

Sample	Trigger action	Primary assertion	Failure evidence
Login verification code	Request a one-time code	Six-digit code, validity period, single use	Error code and resend cooldown
Transactional notification	Complete a test order or task	Variables, amount, time zone, plain text	Task ID and template version
Security alert	Simulate a device or account event	Device, time, risk explanation	Event ID and sender identity
Multilingual version	Switch the user language	Subject and body use the same language without layout overflow	Locale and fallback rules

Role assignment

Give the triggerer and reviewer the same facts

The executor handles reliable reproduction and recording. The reviewer does not reinvent the steps, but checks the same address, time, and template version. The release owner accepts only evidence-backed conclusions.

Handoff package must include

Environment and version

Commit ID, template ID, language, and feature flags

Actions and timing

Trigger steps, UTC time, and task ID

Results and open items

Screenshots, response codes, blocker severity, and owner

Pre-launch checklist

Use the final ten minutes for deterministic checks only

Every expected template has been triggered in practice Sender, reply-to address, and subject match the environment HTML and plain text are both readable Verification-code expiration and resend logic have been verified Multilingual subjects and bodies are not mixed Every blocker has an owner and a decision

Start this test round

Create a clean address first, then verify each message against the checklist

A temporary inbox works well for a single release window. For cross-cycle monitoring, log in to create a dedicated public inbox.

Create a test address