Newsletter Editorial Process Template
Three documents and three sheets that fill a newsletter's idea bank from your archive and reporting pipeline, ranked by what readers already opened.
Free download · No account needed
Every guide to newsletter sustainability gives the same advice: keep a running idea bank instead of starting from a blank page each week. None of them says where the bank comes from, so it becomes one more list an editor has to remember to update, and it goes empty in exactly the week that matters. This pack fills the bank from two sweeps instead of a memory: the archive for what a published story left behind, and the pipeline for what is already reported but too small to run alone.
The Halstead Ledger's Friday newsletter needs five items an issue across thirteen issues, sixty-five slots for the quarter. Sweeping a quarter's 168 published stories found 143 leftover angles, and the story pipeline held 24 more items that needed no new reporting. After removing 41 duplicates and stale entries, 126 usable candidates remained against 65 slots, a 1.94x bank depth. Ranked against what readers had actually opened before, the reader-mailbag and development-watch tags, the two best-performing, alone covered 47 of the 65 slots.
Open the pack in River and the agent reads your archive and pipeline before asking for a single new idea, or download the blank sheets and docs and run the sweep yourself. Either way, the Idea Bank holds every candidate with its source and its rank, the Issue Register tracks what filled each slot, and the Production Checklist gates the send date on bank depth instead of on how the week feels.
What's in the pack
Idea Bank, populated by two sweeps
One row per candidate, tagged by source: an archive sweep for what a published story left behind, and a pipeline sweep for what is already reported but too small to stand alone. On the worked quarter the two sweeps produced 126 usable candidates against 65 slots.
Performance by Issue
Open and click rate logged per issue and tagged the same way the bank tags candidates, so a tag's rank comes from what this newsletter's own readers have actually opened, not from a guess about what sounds interesting.
Format Template
The section order and the word count band for each one, so a reader can skim the same shape every week. Fixes the lead, the short items, the reader mailbag and the sign-off, and nothing else.
Editorial Standard
The line an archive-sourced item carries naming the original story, the rule against running the same leftover angle twice, and what happens to a newsletter item when the story behind it is later corrected.
Production Checklist, gated on bank depth
A Tuesday check of available candidates against the next two issues' slots, before the send date gets promised. Below 2x triggers a fresh sweep instead of a Thursday night scramble.
Issue Register
Which Idea Bank row filled which slot, logged the day the draft is set. This is what lets the next bank-depth check work from real numbers instead of a feeling that the well is running dry.
A space rule every prompt reads first
The idea bank is a sweep, not a brainstorm: read the archive and the pipeline before asking anyone to think of anything new, and never let a reused fact skip its disclosure line.
How to use it
- 1
Open it in River, or download it
Open the pack and let the agent read your archive and pipeline before it asks for a single new idea, or download the blank sheets and docs. The template library holds the rest of the desk's packs.
- 2
Send the archive and the pipeline, not just topics
Your published stories for the lookback period, whatever tracks beat notes and reporting in progress, and send history with open and click data if this newsletter has run before.
- 3
Sweep before anyone brainstorms
Every story checked for a cut quote, a smaller fact, or an unanswered reader question. Every pipeline item checked for whether it is confirmed and newsletter-sized rather than a story still being reported.
- 4
Rank the bank, then check its depth before the next send date
Tag every candidate and rank by what this audience has actually opened. Below 2x the next two issues' slots, sweep again before drafting anything.
Frequently asked questions
Is this template free?
Yes. Download the whole pack as Word documents and CSV sheets, no signup and no credit card. "Edit with AI" is a separate, optional path for anyone who wants the agent to read your archive and pipeline and build the ranked bank. Nothing happens until you send it something to sweep.
How is this different from just keeping a running list of ideas?
A running list only holds what somebody remembered to type into it, which is why it goes empty in exactly the week that matters. This sweeps the published archive and the reporting pipeline systematically, so the bank starts from what the newsroom has already done rather than what an editor recalled at 5pm on a Thursday.
What if we have never sent this newsletter before, so there is no send history to rank against?
The archive and pipeline sweeps still work; a new title just starts every tag at an even rank until a few issues have actually sent. Performance by Issue fills in from the first send onward, and the ranking gets sharper with every issue rather than staying a guess.
Why does the bank need the published archive and not just a topic brainstorm?
Because a leftover angle costs zero additional reporting: it already survived an editor and, on most desks, a fact check. A brainstormed topic still has to be reported and checked before it can run, which is a different amount of work than the newsletter's schedule usually has room for.
Does a fact reused from an old story need to be re-verified?
It needs its disclosure line naming the source story, and if that story is later corrected, the newsletter item drawing on it needs the same correction, independent of whatever ran on the original piece. The correction and accountability pack tracks that chain on the story side; the Editorial Standard doc here tracks it on the newsletter side.
How do you decide what to schedule first when two tags both have candidates available?
By what this audience has actually opened, not by launch order. Open and click rates vary widely by newsletter topic, which is why beehiiv's own 2025 State of Email Newsletters reports a platform average near 38 percent that individual categories run well above or below. Rank your own tags against your own sends, and schedule the scarce, high-performing one first.
Where does this sit in the rest of the desk's work?
It runs on its own weekly rhythm, separate from the editorial calendar that schedules features. A reader's name and location get handled the way the source pack already handles a source's identifying details, and the newsletter's voice can flex further than the desk's style guide without a lower bar on facts.
Fill the bank before you need it
Download the blank Idea Bank, Issue Register and Performance by Issue as Word and CSV files, or open this pack in River and let the agent sweep your own archive and pipeline.
Edit with AI