The Editorial Engine.
One fixed day a week, and the slot decides what you write.
The Editorial Engine is Phil Henderson's four-slot newsletter calendar that repeats every month. Each week carries a different format in a fixed order, on the same weekday, so busy owners keep publishing without deciding from scratch what to write.
Last updated October 2026
What's the easiest way to keep a newsletter going every week?
Pick one weekday and stick to it, then rotate four formats in a fixed order: a flagship essay, a practical guide, a curated roundup and a field report. The slot decides what you write that week, so there's no blank page, and a heavy week is always followed by a lighter one.
It's worth trying if your newsletter keeps stalling because every week starts with a blank page, since the slot makes that decision for you. It's less use if you already publish every week without fail, or if you only ever want to send the occasional big essay. You can run it yourself, and it's the method behind every issue I write.
What goes on the newsletter
calendar each week?
| Week | Slot | Effort | What it delivers |
|---|---|---|---|
| 1 | Flagship essay | Highest | The signature piece, and the first impression for new readers |
| 2 | Practical guide | Lower | One usable skill in 800 to 1,200 words |
| 3 | Curated roundup | Lowest | 5 to 10 useful links, each with a line of context |
| 4 | Field report | Medium | One real situation, details changed, and what you'd do differently |
After week 4 it's a flagship again, so you always know what you're writing next.
Why does reliable
beat brilliant?
Because a reader can't remember a newsletter that never arrives. After studying the growth of thousands of publications, Substack's data team recommends one post a week as a benchmark. The Engine fixes the day and rotates the format, so readers get something familiar every week without getting the same thing twice. Long gaps carry a technical cost as well: Mailchimp warns that long gaps between sends can trigger spam filters.
How does a week run,
working back from send day?
Pick one weekday and hold it for 90 days. Here's the rhythm I use, with a Tuesday send.
| When | On your own | When I run it for you |
|---|---|---|
| Monday to Thursday | Capture ideas in a running note | You send voice notes or a quick message when something happens |
| Friday | Commit to the topic | I confirm the topic with you |
| Sunday | Draft the issue, in three hours at most | I send the draft over for you to read |
| Tuesday, 9am | The issue goes out | It goes out from your account |
What should I expect
while the habit forms?
| Phase | What it feels like | What to do |
|---|---|---|
| Friction, weeks 1 to 4 | The slot still feels like a chore | Send on the day, even when the issue feels thin |
| Forming | Work deadlines start colliding with the slot | Protect the three-hour cap, because most skipped weeks happen here |
| Autopilot | The slot runs itself | Keep going before you add anything new |
If you'd rather I ran it for you, start with a free sample article on your topic.
Questions about
the Engine.
How often should you send a newsletter?
Weekly, if you can hold it. Substack's data team recommends one post a week as a benchmark. If weekly is too much, pick a rhythm you can keep, and send on the same day every time.
What should I write about each week?
Let the slot decide: a flagship essay, a practical guide, a curated roundup, then a field report. After week four it's a flagship again.
See the Engine
in your own voice.
Get a free sample article on your topic. What you send stays between us.
Get your free sample article