Before You Send: An Email Quality Checklist

A polished preview can still hide a wrong destination, an unresolved name or a message that changes after personalization. A pre-send email checklist helps your team catch these ordinary mistakes before the communication reaches customers.

Review the final message as a small release. Content, design and sending behavior have different owners, but they meet in the recipient’s inbox. The goal is a repeatable handoff with clear evidence, rather than a last-minute glance at the editor.

Confirm the message and its variable data

Read the subject, preheader and body together. They should describe the same announcement and make the next action understandable. Check product names, dates, eligibility and any offer against an approved source. A convincing sentence still needs a factual basis.

Then test personalization with representative fictional records. Include a long name, missing optional information and a value containing an apostrophe or accent. Confirm what happens when required information is unavailable: fix it, use an approved fallback or stop that send according to your application’s policy.

For example, review a webinar invitation with a first-name greeting and localized date. Try a reader without a first name and another in a different timezone. The resulting message should remain grammatical and communicate an unambiguous event time. Checking the literal placeholder in the editor does not establish that these rendered values are correct.

Open every meaningful destination

Inspect the main button, image links, footer links and any supporting resource. Open the destinations from the final test message, since a sending service may transform URLs after export. Verify that each page matches the promise of its label and works for the intended reader.

For a link into your application, test the expected authentication state. A signed-in colleague opening an administrator-only page does not prove that an ordinary recipient can use it. The right behavior may involve a login screen followed by a return to the intended destination.

Review image addresses separately. They should be public where required, stable for the intended retention period and free of accidental private identifiers. Load them outside your existing authenticated browser session. Do not rely on a preview that can display a local file or an image available only to your own account.

Check the message as a reading experience

Use the narrow preview and inspect the actual reading order. Long headings, multi-column sections and wide illustrations deserve particular attention. A button should remain understandable when adjacent decoration is removed, and important instructions should be present as text.

Review alternative text according to the image’s job. W3C’s image tutorial distinguishes informative, functional and decorative imagery. Describe useful information or the link’s purpose where appropriate; decorative images can use an empty alternative.

Also check heading hierarchy. W3C’s heading guidance explains its navigational role. Choose headings for structure before adjusting their appearance. Inspect the plain-text output as another way to notice missing words, confusing order or destinations that disappeared during export.

Send through the real delivery path

Use the same personalization, link handling and delivery configuration intended for the actual send. A browser preview tests the editing experience; a delivered message tests what the recipient receives. Keep both checks because neither replaces the other.

Send to a small set of representative inboxes and devices. Inspect the subject and preview text, image loading, layout and links. If dark mode or blocked images matter to your audience, include those states. Record the clients used so the team understands the coverage rather than assuming universal compatibility.

Ask the sending owner to confirm authentication and applicable subscription behavior. Gmail’s sender guidelines include requirements outside the HTML body, including relevant one-click unsubscribe headers. A visible footer link alone does not confirm that the sending system supplied them.

Approve an identifiable final version

Keep a concise review record: template or document revision, sample records used, destinations checked, inboxes inspected and the person approving the communication. This is especially useful when someone requests a late copy change. The team can see what changed and which checks need repeating.

Run a final exercise before handoff: reopen the approved document, export again and compare the final action and key facts with the test message. If personalization or sending settings changed afterwards, repeat the affected checks. A small deliberate review is more useful than assuming approval transfers automatically between versions.

Use this checklist for your next customer email and adjust it when a real issue reveals a gap. Explore Weavour for visual email creation within your application’s own delivery workflow.