How to run an email preflight check
Run an email preflight check for broken links, missing alt text, inconsistent offers, and sender settings that need review before a campaign goes out.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What an email preflight check is
An email preflight check is a review of the exact campaign draft you intend to send. Read it as a recipient, compare its claims with the approved offer, and check that each important action leads to the right place. Then verify what the sending platform adds when it builds the message. An email QA checklist is the record of those checks, the evidence behind each finding, and the fixes still needed. It should let another person pick up the draft and know which version to review.
Email campaign proofing covers several layers of the same message. The copy can be accurate while the primary button leads to an older offer. The HTML can read well while the plain-text version still has a previous deadline. Information such as a personalized greeting or an opt-out link may appear only after the sender processes the draft. A preflight review ties each finding to the layer where it can be verified and gives the responsible person a clear way to close it.
What it does for the business
- Protect the path from email to actionA destination check can catch a draft that sends readers to an old registration page or a mismatched offer. The campaign owner can correct the reference while there is still time to test the full route.
- Give readers the same essential informationA readable text version and useful image descriptions help people understand the email when images are blocked, unavailable, or read through assistive technology. Checking these details also surfaces deadlines and instructions that need to appear in the visible body.
- Make corrections easier to approveA finding that names the affected line, evidence, and proposed edit gives an editor a concrete decision. The campaign owner can review the revised language without reconstructing the conversation that led to the change.
- Keep launch issues with the right ownersA proofing report can distinguish a headline correction from a sender setting that requires access to the campaign platform. With clear owners, the copy can move through review while the operator confirms the configuration that affects the release.
How to build an email preflight check, step by step
Inventory the draft and campaign facts
Tie every finding to the campaign version the sender will use.
What to do
- Save the exact HTML, the available plain text, the subject, and the preview text, which is the short snippet that may appear next to the subject. Record the draft version and identify which pieces are missing.
- Gather the current offer, audience, deadlines, eligibility rules, and sender information. Compare these facts with the actual draft and identify who can confirm anything unresolved.
- Record each link and image reference with its location and purpose. List template placeholders and merge tags, which are fields the sender replaces with data such as a recipient's first name.
- Identify what the sending platform provides when it assembles the email. Record what you can confirm from the supplied draft and what requires the configured message or its preview.
Why
An exact inventory reduces the chance of correcting copy in a document while the sender uses a different version. It also makes it clear why a missing footer in the source is an open check until you know what the platform inserts.
Check destinations and readable alternatives
A working link should lead to the action described in the email.
What to do
- Compare the label and surrounding copy with the intended destination. Review the final page after a safe redirect, and check that the offer, audience, and next step still match. Record the evidence and whether the destination was observed, supplied, or unavailable.
- Identify action links and addresses with private recipient tokens before opening anything. Have the sending owner verify unsubscribe, confirmation, and preference actions through a controlled test account or an authorized platform preview.
- Read links on their own and replace labels such as 'Click here' with text that identifies the action. Check the surrounding content for key details that would disappear if images failed to load.
- Give meaningful images concise alt text that conveys their purpose. Use empty alt text for decorative images. When an image is the only content of a link, make sure its alternative identifies what the link does.
Why
A redirect may succeed while delivering the wrong page. A personal link may change a real subscriber's preferences when opened. Recording the role and the evidence for each link helps the next reviewer understand what was tested and which checks still belong in the sender's environment.
Check the offer, wording, and sender details
The subject line, body, and destination should describe the same offer.
What to do
- Read the subject and preview together. Verify that their promises have support in the campaign facts and that any urgency reflects an actual deadline. Compare dates, time zones, exclusions, and eligibility across the body and the destination.
- Check every call to action, the instruction that asks readers to take the next step. Confirm that the primary button and any repeated links describe a consistent action.
- Read the HTML and text versions side by side. Keep the important terms, links, and instructions equivalent even where the formatting changes. Read the greeting with complete, missing, and unexpected recipient values.
- Record sender identity, footer, and opt-out questions for the operator. For each finding, reference the affected line or setting and describe what would resolve it. Give issues that can materially mislead readers or block essential actions the highest priority.
Why
A subject that oversells the body may draw attention to a claim the team cannot support. Missing fallback language and conflicting instructions can undermine an otherwise accurate offer. Treat urgency and other spam-like wording as editorial signals and record the actual setup details that still require verification.
Correct the draft and verify the fixes
A correction is ready for review when its evidence and remaining dependencies are clear.
What to do
- Make corrections in a new version and keep the source intact. Remove unsupported claims, preserve verified offer terms, and change destinations only when you can confirm the replacement.
- Give unresolved placeholders visible labels in the review copy, and tell the sender which values to supply. Record the expected behavior for a missing field so the operator can configure a sensible fallback.
- Review each changed element against the original finding. Reread nearby copy, confirm corrected destinations, and verify that the revised text and HTML still carry the same essential information.
- Have the operator preview the final assembled message and run a test send to approved internal addresses. Check representative reading conditions, links, and sender details. Record any material issue that still blocks the send.
Why
Edits can introduce new mismatches, especially when a deadline or destination appears in several places. A second pass checks the changes together, and an assembled preview answers configuration questions the source draft leaves open. The send decision belongs with the person who controls the final campaign.
Common mistakes
- Testing only for a successful responseOpen safe destinations far enough to see whether the reader reaches the current offer and intended action.
- Opening real subscriber action linksUse authorized test records to verify links that change subscriber preferences or confirm an action.
- Leaving terms inside an imagePut the key dates, conditions, and actions in readable text so they remain accessible when the image is unavailable.
- Fixing only the HTML versionCompare the revised text and HTML to ensure every recipient receives the same essential terms and instructions.
- Marking unresolved settings as checkedRecord which sender or provider details still need confirmation and assign them to someone with access.
What a good result looks like
- The inventory identifies one current draft and the versions of all supplied components.
- Link findings include their source location, evidence type, and observed or unknown result.
- Meaningful images, link labels, and text alternatives communicate the necessary information.
- Both draft versions retain the verified offer and have clear markers for unresolved fields.
- The handoff names material blockers and identifies where each one can be verified.
And then what? Using the result
- Give the campaign owner the corrected copy with unresolved configuration items marked so they can update the working draft.
- Confirm sender details, merge fallbacks, and opt-out behavior in the sending platform with an authorized test record.
- Review the assembled email with an internal test audience and open the safe primary link from the received message.
- Save the final checklist alongside the sent version so the next campaign starts with known settings and a current record of recurring issues.
When to run it
- Before a campaign handoffRun the check when the draft is stable and the offer is approved. This gives the sending owner a specific list of configuration checks and copy changes.
- When a recurring template gets a new offerCheck repeated dates, destinations, and terms after replacing them. Review the carried-over text and fallback copy for references to the earlier offer.
- After a late editReview the changed elements and related references in both versions. A new link or deadline can affect the subject, text version, and landing page together.
Questions people ask
What is an email preflight check?
It is a review of the exact email draft, destinations, and available setup details before sending. Its output is a record of verified findings, corrections, and open checks for the sending owner.
How do you verify links without triggering subscriber actions?
Inspect the source and use an authorized test record or platform preview for links that can act on a subscriber account. For ordinary destinations, check where the link lands and record the evidence.
What should the plain-text version include?
Keep the offer, essential terms, primary action, and necessary sender and opt-out information. Read it on its own and ensure a reader can act without relying on images or the HTML layout.
What should you do when a merge tag has no value?
Configure a suitable fallback or write the sentence so it reads naturally without the field. Preview the rendered message with the field missing so you can verify the result.
Can a wording review predict inbox placement?
A wording review can flag misleading copy and spam-like language, but it cannot predict inbox placement. Configuration and actual sending behavior require checks in the sending environment.
What does a test send add to a static review?
A test send shows what an approved recipient receives after the platform assembles the message. It can reveal unexpected placeholder values, destination changes, or display problems in the clients you actually check.
More jobs in Marketing
Check an email before it goes out, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac