Plan a Newsletter Issue
Plan one newsletter from reader promise to send-ready outline.
A strong newsletter issue starts with one useful promise. This Cookbook helps you name the reader, choose an angle, outline sections, package the subject and preview text, and finish with a send checklist. Every step works only from the facts you enter and the artifacts you approve.
- Made for
- Newsletter writers planning one useful issue at a time
- You leave with
- reader promise, issue angle, section outline, subject options, opening, CTA plan, preview blurb, and send checklist
- Time
- about 35 minutes
- Steps
- 8 guided steps
- Requires
- any AI you already use (a free chat account is usually enough); sample answers included where available
- Completed runs
- 221 (demo metric)
- Average rating
- 4.7 / 5 (demo metric)
Also in Start Here Selected by SousMeow Recently Added Deep Workflows
Have an account? Sign in.
Stages
3 stages in sequence-
12 steps
Reader
Name the reader promise and the issue angle.
-
23 steps
Draft bones
Outline sections, subject options, and the opening.
-
33 steps
Package
Plan links, preview copy, and the send checklist.
Workflow steps
8 steps · completed in orderStage 1: Reader
-
1
Name the reader promise
Turn the issue facts into one clear promise for the reader.
A newsletter issue becomes easier to plan when every section must earn its place under one reader promise.
- Promise is reader-centered The payoff says what the reader can do or decide.
- Facts stay supplied No audience research, links, or offers were invented.
- Success is observable The signal is an action or decision, not a vague feeling.
-
2
Pick the issue angle
Choose the practical angle the issue will hold from opening to CTA.
A tight angle keeps the issue from becoming a loose pile of useful but disconnected notes.
- Angle is singular The issue has one center, not three competing themes.
- Fit is explained The angle connects to the approved promise.
- Boundaries are clear Unsupported topics are explicitly kept out.
Stage 2: Draft bones
-
3
Outline the sections
Build a scan-friendly issue spine from opening through CTA.
A section outline lets you see whether every part supports the promise before drafting full copy.
- Outline has a full arc It moves from opening to CTA.
- Each section supports the promise The flow explanation ties back to the reader payoff.
- Unknowns are not filled in Missing facts are named instead of invented.
-
4
Write subject options
Draft subject lines that promise the issue without overclaiming.
The subject line should tell the right reader why this issue is worth opening.
- Three options exist There are exactly three subject lines to compare.
- Recommendation is explicit One subject is chosen for drafting.
- No unsupported urgency The fit explanation does not add deadlines or promotions.
-
5
Draft the opening
Write the first lines that set up the promise and lead into the outline.
A useful opening earns attention quickly and tells the reader what the issue will help them do.
- Opening names the topic The first paragraph clearly matches the issue.
- Hook serves the reader The hook ties to the reader promise.
- Bridge points forward The reader knows what comes next.
Stage 3: Package
-
6
Plan links and CTA
Place the call to action and name any missing link facts.
A good issue can lose momentum if the next step is vague or unsupported by real link details.
- CTA is single The issue asks for one next action.
- Placement is planned The CTA has a home in the issue.
- Missing links stay missing Unknown URLs are not invented.
-
7
Write preview blurb
Package the issue promise into inbox preview and sharing copy.
Preview copy should support the subject line and make the issue easy to recognize at a glance.
- Preview is concise The preview line is short enough for an inbox.
- Blurb matches the issue The sharing copy reflects the approved topic.
- Open reason is grounded The reason points to the reader promise.
-
8
Pack the send checklist
Assemble the approved parts into a send-ready outline and checklist.
The final package catches mismatches before the issue moves into drafting or scheduling.
- Package includes key parts Subject, preview, outline, and CTA are present.
- Checklist catches risky gaps The checklist includes facts, links, and promise alignment.
- Unknowns remain visible Missing facts are not silently resolved.
Your information
6 details, answered once- Newsletter name Use the exact name readers see.
- Issue topic Name the issue in plain words.
- Reader promise What will a reader be able to do, decide, or understand after reading?
- Must include Facts, links, sections, or reminders that must appear. Known facts only.
- Call to action The one action this issue should invite.
- Send day The planned send day if known.
Finished files
What you export when every step is approved
One Markdown file per approved step, plus kit.html (opens in any browser, offline)
and a README of what you approved.
kit.htmlOffline HTML reader for every approved step01-name-the-reader-promise.mdName the reader promise02-pick-issue-angle.mdPick the issue angle03-outline-sections.mdOutline the sections04-write-subject-options.mdWrite subject options05-draft-opening.mdDraft the opening06-plan-links-and-cta.mdPlan links and CTA07-write-preview-blurb.mdWrite preview blurb08-pack-send-checklist.mdPack the send checklistREADME.mdManifest of what you approved