An email preview can look finished while the wrong audience, old link or unfinished personalization remains selected. A pre-send check should cover both the message and its delivery settings. Check the exact version that will run, record any corrections and repeat the affected checks after an edit so approval does not refer to an earlier draft.
Confirm the campaign and intended audience
Record the campaign name, version, purpose and intended recipients. Inspect the actual audience selection in the sending tool, including exclusions and preference handling. Compare the count with what you expected and investigate an unexplained difference. A larger list is not automatically the correct list, and a familiar campaign name does not prove its settings are current.
Check whether the message overlaps an active automation or another scheduled send. Identify any test addresses or internal contacts that should be treated separately. If the audience depends on a rule, inspect representative controlled records to confirm the rule selects the intended people. Do not expose real customer details in a general QA document.
Read every part of the message
Review the sender name, sender address, reply address, subject and preview text alongside the body. Confirm dates, prices, conditions and service scope against approved information. Look for leftover template instructions and links to old promotions. Read image text too, because an outdated date in a graphic can contradict an otherwise correct message.
Test personalization with both populated and missing values using the tool’s supported test process. Check that the fallback reads naturally and does not reveal raw field syntax. A simple test send may not exercise every audience-specific substitution, so establish what your tool’s test mode actually covers before treating the result as proof.
Open every customer destination
Make a list of all links, including text links, buttons, images and footer controls. Open each from the received test when that is supported, and verify the final destination rather than only the URL shown in the editor. Check that the page offers what the email promised and works without your logged-in administrator session.
For forms, downloads or checkout routes, test the relevant controlled customer path to the extent appropriate for the campaign. Do not create real purchases or send live customer messages merely to test a link. Check subscription preferences and unsubscribe behavior with a designated test subscriber; document any test-mode limitation rather than clicking controls on a real customer’s record.
Illustrative test log entry
Campaign: fictional workshop preparation guide. Version: final copy, revision three. Main button: opens the correct public checklist on a phone. Reply: arrives in the monitored support inbox. Missing-name test: uses ‘Hello’ without an empty field. Audience: the approved guide-subscriber group, with suppression rules checked. Issue: footer still referenced an older business address; corrected and retested before approval.
Check the received email on a phone
Inspect the actual test message at a comfortable reading size. Look for horizontal scrolling, tiny conditions, awkward image crops and buttons that are difficult to tap. Confirm that the main action remains understandable if images do not load. Important instructions should not exist only inside a large promotional graphic.
Read the message in order and follow the main action once more. A layout that looks attractive in the editor may interrupt the reading sequence in the inbox. For a routine update, prioritize the change and required action over decorative elements. Use the customer environments relevant to your business; a single test is not proof of every email client’s rendering.
Approve settings separately from publication
Before the final send or scheduling action, confirm the exact campaign, audience, date, time and time zone. Record who approved it. If the message changes after that approval, identify which checks must be repeated. Do not let a corrected button or image bypass the final review because the previous version already had a checkmark.
After scheduling, reopen the campaign and verify the saved state. After the send, inspect the provider’s actual status and any reported errors. Scheduled is not sent, and sent does not establish that every recipient received or read the message. Keep the test record useful by describing observations precisely.
- Correct campaign version and audience.
- Facts and personalization checked.
- Every destination verified.
- Received mobile display reviewed.
- Time zone and approval recorded.
- Saved schedule or send status read back.
Your next step
Create a one-page test log for your next email. Record the exact version, test addresses, links checked, issues corrected and final approval before scheduling it.
