Email Newsletter Production

You produce a newsletter people look forward to: each issue keeps the promise subscribers signed up for, gives them one thing worth their time, and asks for one action. Every issue goes out tested, tagged and compliant, and is judged on clicks, replies and outcomes rather than opens. Nothing is sent or scheduled without the owner's go-ahead.

When to use

• "Write this week's newsletter."
• "Set up a monthly customer newsletter."
• "Our newsletter gets no clicks. Fix it."
• "Send an announcement email to the list."
• Relaunching a newsletter after a gap.

What you need

• Access to the email tool: a connected app (Mailchimp, HubSpot) or the owner's signed-in browser for other platforms. If neither, deliver the HTML and plain text as files.
• The newsletter's promise: who it is for, what they get, how often. If none is written, draft one in step 1 and confirm it with the owner.
• Content inputs: recent articles, product news, events, customer stories, the editorial calendar (see also editorial-calendar-planning).
• Brand voice guide and design template, if they exist.
• List and segment details: size, segments, consent basis, past performance (clicks, unsubscribes, complaints per issue).
• Legal requirements for the owner's country: a visible unsubscribe link, sender identity and, in some countries, a postal address (for example CAN-SPAM in the US). Confirm with web_search and cite.

Method

1. Fix the promise and the format. One sentence: "Every [frequency], [audience] get [specific value] in [time to read]." Pick a format and keep it stable: a single main story with short extras, a curated digest, or a letter from a person. Readers return to a predictable shape.
2. Choose the issue's one job. The single action you want (read the guide, register for the webinar, reply with a question, try a feature). Everything else is secondary. One primary CTA, repeated at most once lower down.
3. Outline the issue.
   • Opening: 1 to 3 sentences that say why this issue matters to the reader now.
   • Main story: the value, written to be useful in the email itself, not only a teaser.
   • Primary CTA: a button with a verb and the outcome ("Get the checklist").
   • Two to four short extras with one link each, if the format has them.
   • Sign-off from a real person, and a reason to reply.
4. Write subject line and preview text together. Subject: specific, honest, ideally under about 50 characters so it shows on mobile; front-load the key words. Preview text: continues the subject, does not repeat it, about 40 to 90 characters. Write 3 to 5 options and, if the list is large enough, test two (see also ab-test-design). Never write misleading subjects ("Re:", "Your order", fake urgency).
5. Build for every inbox. Single column, about 600 px wide; live text, not text inside images; body text at least 14 to 16 px; colour contrast that passes WCAG AA; descriptive alt text on every meaningful image; buttons built in HTML, not images; a plain-text version; dark mode checked. Keep the HTML under about 100 KB so Gmail does not clip it.
6. Tag every link. Add UTM parameters: utm_source=newsletter&utm_medium=email&utm_campaign=[issue-date-or-name]&utm_content=[link-position]. Use the same naming every issue so results compare.
7. Segment and personalise only where it helps. Exclude people who would find the issue irrelevant (for example customers from a prospect-only offer). Personalisation tokens need a fallback ("Hi there" when the first name is empty).
8. Run the pre-send QA in references/newsletter-kit.md: links, tokens, images, rendering in the main clients (test sends to Gmail, Outlook and Apple Mail accounts you control), unsubscribe link, sender name and reply-to, spelling, facts and dates, legal footer.
9. Get approval, then schedule. Send the owner a test email and the planned send time and segment. Schedule only after an explicit go-ahead. Choose send time from the list's own history; if there is none, start mid-morning on a weekday in the audience's time zone and test from there.
10. Report at 48 hours and 7 days. Primary: click rate (unique clicks / delivered), clicks on the primary CTA, conversions from UTMs in Google Analytics, replies. Health: unsubscribe rate, spam complaints, bounces. Opens are inflated by Apple Mail Privacy Protection and are useful only as a rough trend. Compare with the last 6 issues, not with industry averages.
11. Feed back. Note which topics and formats got clicks in memory, and adjust the next issue.

Output

• The issue: subject options, preview text, HTML (or the draft in the email tool), plain-text version.
• Send plan: segment, exclusions, send time, test plan, UTM campaign name.
• QA checklist with every item ticked.
• After sending: a short report (template in references/newsletter-kit.md) on a show_card.

Checks before you finish

• One primary CTA, clear in the first screen on mobile.
• Subject and preview text are honest and work together.
• Every link works and carries UTMs; tokens have fallbacks.
• Unsubscribe link, sender identity and any required postal address present.
• Accessible: live text, alt text, contrast, plain-text part.
• Test sends checked in at least Gmail and Outlook.
• Owner approved the final test and the send time.

Pitfalls

• Everything newsletter. Ten equal links means no clicks. Choose the one job.
• Teaser-only content. If the email has no value without clicking, readers stop opening. Give value in the email, and a reason to click for more.
• Judging by opens. Privacy features inflate opens. Optimise for clicks, replies and conversions.
• Image-only emails. They break when images are blocked and fail screen readers.
• Mailing everyone always. Long-inactive subscribers hurt deliverability. Suppress or re-permission them (see also email-deliverability-check).
• Sending without approval. A send cannot be recalled. Wait for the explicit go-ahead.