Rules
Part of What an Email Marketing Template Actually Needs
Send-day checklist for email marketing templates
An email marketing templates checklist for send day: inbox view, rendering, authentication, one-click unsubscribe, links, seeds, and release records.
What to take away
- Check the rendered message and the production sending path. A clean design-tool preview does not prove authentication, delivery, or suppression behavior.
- Work in send-day orderinbox view, rendering, sending path, unsubscribe, then links, seeds, and counts.
- Mark each check pass, fail, not applicable with reason, or assigned with owner and due date, and stop release for unresolved material defects.
- Repeat the checks after material changes to provider, domain, authentication, code, client, accessibility, data, or audience.
Start with the inbox view
Open a seed copy and read the inbox view as a stranger would. The From name, address, reply-to, subject, and preheader must identify the sender and describe the message without deception. Promotional content must not pose as a receipt, service alert, or personal reply.
The FTC's CAN-SPAM compliance guide says the "From," "To," "Reply-To," and routing information must be accurate and identify the person or business who initiated the message.
Canada has its own regime: CASL requires businesses and organizations to obtain consent before sending commercial electronic messages. US CAN-SPAM and CASL are not interchangeable global approvals, so get qualified local review for each market. Record the message class and purpose in the campaign brief so reviewers know which rules apply.
Render and accessibility checks
Render the message in the clients your readers use, then repeat the check with images blocked and in dark mode. The design-tool preview shows what the template intends; only the rendered copy shows what arrives.
Accessibility and Code Checks
- Reading order, headings, alt text, contrast
- Meaning available with images blocked
- Responsive stacking, zoom, dark mode tested
- HTML uses supported structures and fallbacks
- Every meaningful image carries alt text; decorative images use an empty alt attribute.
- Heading order runs h1, h2, h3 with no skipped level, and each heading describes the block below it.
- Body text keeps a contrast ratio of at least 4.5:1, large text 3:1, confirmed in a contrast checker.
- Lists and headings use real markup so screen readers announce them in order.
- Calls to action use descriptive link text and never rely on color alone.
- Render checks cover Gmail, Outlook on Windows, Apple Mail, and Yahoo Mail.
Litmus and Email on Acid give rendering screenshots and crawl every link, but a screenshot tool is not a screen reader. Check heading order and alt text in the code itself.
Authentication and the sending path
Confirm the stream, domain, authentication, transport, and headers on a real seed copy, not on the provider's settings page. The settings show what was intended. The raw headers show what was sent.
Yahoo Sender Hub's sender requirements require authentication and low complaint rates for every sender to Yahoo domains, and add SPF, DKIM, DMARC alignment, easy unsubscribe, body links, processing, DNS, and message-format duties for bulk senders. The page says requirements can change, so verify the current text for the real stream.
| Check | Where to look | Pass looks like |
|---|---|---|
| Authentication | Raw headers of a seed copy | SPF and DKIM pass, DMARC aligned with the From domain |
| Stream and domain | Provider settings and headers | The intended sender, not a test account |
| Suppression | The audience query and sync log | Suppressed addresses are absent |
| Schedule | Send time and time zone | Matches the approved plan |
A template whose fields enforce decisions, as in marketing plan templates, can make the sender domain and stream required fields.
One-click unsubscribe
RFC 8058 says a sender that wishes to enable one-click unsubscription places one List-Unsubscribe header field and one List-Unsubscribe-Post header field in the message. The message must also carry a valid DKIM signature that covers at least those two headers.
The standard does not replace a visible body link, local law, preference handling, or mailbox-provider requirements. Test it from a seed copy: use the mailbox client's own unsubscribe control, then confirm the address reaches suppression before the next send.
Links, seeds, and counts
Last come the checks that depend on the live send. Each one needs evidence from the production path, because a staging copy can pass while the real stream fails.
- Every link, redirect, landing page, reply, preference route, unsubscribe path, and automation exit works signed out and on a phone.
- Production-path seeds cover representative records and every branch.
- Final counts reconcile with approved source queries.
- Approvers, version, evidence, monitoring, rollback, correction, incident contacts, expiry, replacement, and archive are recorded.
Audience source, consent or other permitted basis, and notice version are settled upstream, as the marketing plan template checklist shows. Record the final counts too, because the report template checklist starts from numbers that reconcile.
Inherited templates need an audit
Audit any inherited template before you reuse it. Free email templates can carry another sender's footer, tracking pixel, and unsubscribe address. Replace the footer identity, postal address, reply-to, and tracking domains with the current sender's, then re-test the production path.
Vetting a free file follows the same logic in every template family, as free marketing plan templates show. The campaign brief checklist makes the same demands before anything is built.
Common questions
Does a clean preview mean the message is ready?
No. The preview does not exercise authentication, suppression, or the real sending stream. Check the rendered copy and its headers.
What if a mailbox provider changes its requirements?
Verify the current text for the real stream, record the date checked, and repeat the sending-path checks. Do not rely on a remembered version.
Who performs the final live check?
A named publisher should inspect production-path seeds, the actual sender and headers, message variants, links, replies, preferences, unsubscribe, authentication, monitoring, and rollback.
