AI-Generated Marketing Email: Pre-Send Review Checklist

Do not approve an AI-generated marketing email because the draft looks finished. Approve it only after named owners pass ten checks against the exact content, audience, sender, and schedule that will go live.

AI can find defects; a named human owns the send decision. NIST identifies confabulation as confidently presented false content from generative AI and recommends reviewing sources and citations before deployment. Email adds more failure points: a valid claim can reach the wrong audience, a working template can break in a major inbox, and a clean test email can hide a failed personalization branch.

This checklist is an operational review method, not legal advice. Email rules depend on recipient location, sender, organization, list source, and message classification. Have a qualified privacy or legal owner define the rules for your program.

Ten pass-or-fail gates#

Every row needs a named owner and attached proof. "Looks good" is not evidence.

One failed, expired, or unassigned gate blocks send.

1. Check claims against source material#

Verify facts before polishing grammar. Ask the AI or writer for a list of every checkable statement, then verify each one against product data, approved offer terms, legal copy, or another current source.

The FTC says US advertising claims must be truthful, non-deceptive, and evidence-based. This checklist applies that same rule to AI-written copy. Higher-risk claims, including health, finance, safety, comparative performance, scarcity, and endorsements, need review from the owner who can assess their evidence and applicable rules.

Pass evidence should identify:

• claim as sent;
• source URL or internal record;
• source owner;
• date checked;
• reviewer decision.

Delete unsupported copy. Softer wording does not repair a false underlying fact.

2. Read subject, preview, and sender fields together#

Review inbox chrome as one promise: display name, From address, Reply-To, subject, and preview text. Confirm the sending brand owns the identity and monitors replies where replies are invited.

For US commercial email, the FTC CAN-SPAM guide says header and routing information must be accurate and subject lines must reflect message content. Other jurisdictions can add different duties. The campaign owner should record which rule set applies instead of treating one country's checklist as global policy.

Fail examples:

• subject starts with Re: when message is not a reply;
• display name implies a person or company that did not send it;
• preview text promises a discount missing from offer terms;
• Reply-To points to an unmonitored mailbox.

3. Prove audience eligibility before reviewing creative#

AI should not infer permission from an email address, job title, public profile, purchase, or prior conversation. Audience owner must verify list provenance and current eligibility for this specific message.

Record segment query or saved audience version, inclusion reason, exclusions, suppression timestamp, and applicable jurisdiction. The ICO's UK guidance shows why context matters: subscriber type, consent, soft opt-in conditions, message purpose, and use of personal information can change the rule. That guidance covers UK law, not a universal standard.

Pass only after qualified owner confirms campaign against your program's approved audience policy.

4. Test unsubscribe and required sender details#

Inspect message body and received headers. Do not approve a visible unsubscribe link without testing the request and resulting suppression state.

For US commercial messages, FTC guidance covers accurate sender identity, valid postal address, advertising identification, opt-out notice, and prompt handling of opt-out requests. Requirements depend on message classification. Separately, Google's Gmail sender guidelines and Yahoo's sender requirements publish authentication and unsubscribe conditions for mail sent to their users.

RFC 8058 defines one-click signaling through List-Unsubscribe and List-Unsubscribe-Post headers. Sending owner should verify actual received headers, not assume email-builder settings produced them.

5. Use WCAG checks as baseline, then test email output#

WCAG 2.2 provides practical checks for text alternatives, color use, and contrast. For normal text, its Level AA minimum is 4.5:1; large text uses 3:1. Informative non-text content needs an equivalent text alternative, while decorative content should be ignorable by assistive technology.

Apply those checks to final email, including CTA text, legal copy, image-based offers, and dark-mode variants. Then test with accessibility tooling and assistive technologies appropriate to audience.

Passing these selected checks does not prove full WCAG conformance or legal compliance. Email-client support varies, so record tested clients and known limits.

6. Render where recipients read#

Browser preview proves little about inbox rendering. Mailchimp documents that email programs display HTML differently. Build target matrix from audience client data when available, then cover important mobile and desktop environments.

Inspect:

• structure and reading order;
• type size and line breaks;
• CTA visibility and tap area;
• image cropping, missing images, and alternative text;
• light and dark modes;
• long content and narrow screens;
• plain-text version.

Attach screenshots or test output for each required client. A generated preview is evidence only for environment that produced it.

7. Open every destination#

Automated link checks help, but they do not close gate. Mailchimp notes its checker cannot validate some links containing merge tags, anchors, or mailto: destinations. Other platforms have different limits.

Click final tracked URLs from received test message. Confirm destination loads without authentication surprises, matches CTA promise, preserves required parameters, and shows same price, date, product, and disclosure as email. Check linked logos and images too.

8. Test personalization with real branch cases#

Generic test sends can give false confidence. Mailchimp documents that contact-specific merge tags and dynamic content may not populate in a normal test email; it recommends live-profile preview or a small controlled test segment for those cases.

Choose profiles that exercise branches:

• all fields present;
• first name or company missing;
• unusually long values;
• non-Latin characters;
• each conditional segment;
• excluded or suppressed profile;
• expired or unavailable offer.

Fail on blank greetings, raw variables, wrong language, sensitive inferred traits, broken URLs, or copy that exposes segment logic.

9. Separate sender compliance from inbox predictions#

Content review cannot validate DNS or reputation. Deliverability owner should inspect authentication results and current requirements for receiving providers represented in audience.

Google and Yahoo document requirements for SPF, DKIM, DMARC in qualifying cases, DNS, message format, complaint rates, and unsubscribe behavior. Check current pages at review time because requirements change.

Do not approve claims such as "guaranteed inbox placement." Meeting published requirements addresses known provider conditions; it does not control every filtering decision.

10. Test received message, then freeze approval#

Send through final campaign path to controlled test recipients. Inspect actual received message, source headers, sender identity, subject, preview, images, links, personalization, footer, and unsubscribe behavior. If platform's test-send path skips audience data, use documented live-profile preview or controlled live test segment without exposing unapproved recipients.

Approval record should bind to exact version:

campaign_version: "immutable ID or content hash"
audience_version: "saved segment or query ID"
sender: "display name <address@example.com>"
scheduled_at: "2026-08-12T14:00:00Z"
gate_results: "link to signed checklist"
approved_by: "named human"
approved_at: "ISO-8601 timestamp"

Any change to content, audience, sender, offer, destination, or schedule should invalidate affected gates. Re-run those checks before send. Approval stays pending until a named human signs the exact version.

For ownership and permissions before this review stage, use AI email workflow from brief to send. For brand-specific review, use brand consistency rubric.