Email and Lifecycle Content

Newsletter Issue Planner

Select a coherent newsletter theme, audience value, evidence, sections, links, editorial balance, disclosures, primary action, and production schedule.

Free editable Markdown · Newsletter editors, content marketers, and community teams · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Issue foundation

Issue ID and send date: [Enter]
Subscriber relationship and segment: [Enter]
Consent/message class: [Enter]
Theme and one-sentence promise: [Enter]
Why this issue now: [Evidence]
Frequency expectation: [Enter]
Primary reader outcome: [Enter]
Editor and approver: [Names]

Section card

Duplicate for each section.

Section job: [Lead / Explain / Curate / Resource / Community / Product]
Headline: [Draft]
Source and destination: [Enter]
Accurate summary: [Write]
Why it fits the theme: [Explain]
Evidence cutoff: [Date]
Commercial or editorial relationship: [Enter]
Required disclosure or limitation: [Write]

Issue structure

Opening: [Orient to theme]
Section order and reason: [Enter]
Primary action and destination: [Enter]
Secondary utility links: [List]
Subject and preview: [Draft]
Sender and reply path: [Enter]
Preferences and unsubscribe: [Enter]
Source cutoff and production dates: [Enter]

QA and retrospective

Primary outcome and guardrails: [Enter]
Reader replies or feedback: [Enter]
Editorial lesson: [Enter]
Next review owner: [Enter]

Every summary matches its opened destination.
Links, tracking, rights, credits, and disclosures are correct.
Images, alternatives, headings, plain text, dark mode, and mobile were checked.
Subject, preview, sender, and issue body set consistent expectations.

How to use this template

Define subscriber relationship, segment, issue promise, theme, frequency, and consent basis.
Select sections and sources whose distinct jobs support that promise.
Verify summaries, links, rights, disclosures, balance, and primary action.
Assign production gates and test accessible responsive email and preference behavior.
Send the approved version and record audience outcomes and editorial lessons.

Define why this issue deserves the inbox

State the subscriber segment, relationship, frequency expectation, and question or outcome this issue serves. Choose one theme broad enough to support useful variety but narrow enough for a clear opening and action. An issue can curate several resources when the editor adds context about why they matter together. Do not send merely because the calendar date arrived; use a shorter edition, a service notice through the proper channel, or no issue when there is no relevant value. Separate editorial newsletters from transactional and promotional messages under applicable consent.

Give each section a distinct editorial job

Map opening, lead item, supporting items, practical resource, community or product note, and closing only as needed. For every link, open the current destination, summarize it accurately, and record source, date, author, relationship, and limitation. Avoid writing a headline broader than the linked evidence. Balance owned, external, commercial, and community material according to the newsletter's stated purpose. Sponsored or affiliate content should be unmistakable and should not borrow the editor's independent authority without disclosure.

Plan production, rendering, and learning

Assign source cutoff, draft, fact-check, rights, accessibility, approval, build, test, and send responsibilities. Verify subject and preview, sender, reply path, links, tracking, image alternatives, dark mode, mobile, plain text, localization, preferences, and unsubscribe behavior. Use a primary action only when it follows the theme; essential utility links remain available. Evaluate replies, useful clicks, complaints, unsubscribes, delivery, and qualitative feedback alongside opens. Record what the team learned for the next issue without rewriting editorial purpose around one noisy metric.

See the fields in context

Fictional example: evidence-first editing issue

The issue, sources, and community below are invented and do not report real newsletter performance.

Promise: Help fictional editors improve one evidence workflow this week.
Lead: A made-up interview on claim mapping, summarized without inventing results.
Resource: A fictional downloadable fact-check log with its limitations stated.
Balance: One owned guide and one external methods article; no undisclosed commercial item.
Action: Complete one claim row, not buy an unrelated upgrade.

Frequently asked questions

How many items should a newsletter contain?

Use the number needed to fulfill the issue promise without diluting attention or creating filler.

Can old content be included?

Yes when it remains accurate and timely for the theme. Recheck facts, links, dates, and product behavior.

Should every issue have one CTA?

One primary action can help focus, while editorial and preference links remain useful. Do not force an unrelated action.

How should newsletter success be reviewed?

Use reader outcomes, replies, useful clicks, delivery, complaints, and unsubscribes with editorial judgment and context.