Newsroom Editorial Calendar Template
The stage chain behind every publication date, worked backwards, so the stories that cannot make their slot are named today rather than in the slot week.
Free download · No account needed
An editorial calendar template is a grid of publication dates: story, writer, section, publish-on, status. It reports every story as on schedule right up to the week that story was meant to run, and then reports a miss. A date sitting on its own has nothing behind it that anything can test. So this pack builds the stage chain between assignment and publication first, gives every stage an elapsed duration and an owner, and produces dates last.
Then it works backwards. It walks each chain in reverse, from the slot date to the stage the story sits in now, and returns the last day that stage could start and still make the slot. It ships filled in for The Halstead Ledger, an invented regional daily reading its Q2 schedule on Monday 6 April 2026: 41 features, 48 slots, 12 weeks. The date view showed four stories visibly behind. The backwards pass showed 15 past the point of no return, 11 of them invisible on the grid.
The second join decides what to do about it. Five of the eight stages belong to a shared desk with a fixed number of hours a week, so the pack sums what each desk is owed per week against what it has. The checking desk was owed 243.2 hours for the quarter against 264 available, a comfortable 0.92x, while five of its twelve weeks were over capacity and week one ran at 1.83x. Ten slot moves brought every week inside capacity, and one story had no week left in the quarter.
What's in the pack
Workflow Note, with two numbers on every stage
Elapsed working days and owner hours, recorded separately, because they are different numbers. A fact-check that takes three days on the calendar can book three hours of one checker's week or ten and a half.
Assignment Register, carrying the backwards pass
Draft due, developmental edit due, fact-check due with its hours, copyedit due, legal read due, lock. Then the latest day the stage the story is in now could have started, and the slack against today.
The already-impossible count
Stories whose latest start has passed, so no amount of effort makes the slot. It is arithmetic rather than a judgement, and it is available on the morning you read the calendar.
Slack ranking, which is the actual work queue
Sorted by days remaining until the point of no return. It does not run in publication order: a week two story in revision can have more room than a week seven story still reporting.
Capacity View, one row per desk per week
Hours owed against hours available, with the ratio and that week's queue listed by story id. The quarter total sits beside the weekly peak, so a quarter that fits while five weeks do not is visible on one line.
Calendar, with the slot count asked three ways
Aggregate, by week, and by week and section. Forty-one stories against 48 slots fits with seven spare, and six of them still had no slot in their own week. A Sunday long read is one slot whatever the weekly total says.
Assignment Brief Format, so the chain has inputs
The estimated assertion count, the reply window, whether counsel has to read it. Each one is a stage somebody outside the desk owns, each is knowable at commission, and each is normally discovered in the slot week. On commissioned work the chain starts in the freelance brief.
Schedule Recovery Note and one space rule
The moves, roomiest stories first, with the original slot kept on every row. Plus the rule every prompt reads: work backwards, never quote a quarter total without the weekly series, and no stage gets dropped without a name against it. A one-off project like a CMS migration needs its own slot here too, not an assumption that the desk absorbs it for free.
How to use it
- 1
Open it in River, or download it
Open the pack and let the agent build the chain and run both passes, or download the blank sheets and docs and do it by hand. The template library has the rest of the desk's packs.
- 2
Send the stages, not just the dates
Your pipeline with whatever slot dates exist, then what actually happens to a piece between commission and publication, with an elapsed duration and an owner on every stage.
- 3
Then the number nobody has written down
How many hours a week each shared desk can give features, net of the work already theirs. A copy desk mostly producing the daily paper is not available for 37 hours of feature copy.
- 4
Read the impossible list before the calendar
Work the slack ranking from the top and give every impossible story a named decision rather than a new date. Then move the roomiest stories out of the weeks that break.
Frequently asked questions
Is this template free?
Yes. Download the whole pack as Word documents and CSV sheets, with no signup and no credit card. "Edit with AI" is a separate, optional path for anyone who wants the agent to build the stage chain and run the two passes over a real pipeline. Nothing happens until you send it one.
How is this different from an editorial calendar template?
A calendar template stores publication dates, so it can only tell you a story is late once the date has gone. This models the stages behind each date and walks them backwards, which turns lateness into arithmetic you can read today. The output is a count, not a colour.
What if we do not track which stage each story is in?
Then start there, because the backwards pass has nothing to walk back to. It is one column on the pipeline and it is the cheapest change on this page. Without it, every verdict in the register is somebody's guess about a story dressed up as a date.
Why price the fact-check per assertion rather than per story?
Because it is the widest-varying stage in the chain, and the weeks that break usually break because two large checks landed together. The worked desk timed its own last 20 stories at 0.11 hours per checkable assertion, so its widest piece cost 10.6 hours and its narrowest 3.2.
Is a right of reply really a scheduling problem?
It is elapsed days owned by somebody who does not work for you, which is the definition of one. The BBC's fairness guidelines treat a right of reply as the norm where output alleges wrongdoing against an identifiable party. Reaching that party is contact work the source pack tracks.
Why does the legal read get its own stage?
Because counsel is a shared resource with a few hours a week for the whole title, so it queues like any other desk. The Reporters Committee's guide to pre-publication review notes that including the subject's response, even a no comment, helps the defence, and a response has to be sought in time to include.
Where does this sit in the rest of the desk's work?
It schedules the stages the other packs perform. The fact-check pass is one stage on the chain and copyedit and style is another. A recurring newsletter runs on its own weekly rhythm, which the newsletter pack schedules separately. Reporting that waits on records has no estimable start date at all until the request lands, which the FOIA pack clocks.
Find out what is already impossible
Download the blank Calendar, Assignment Register and Capacity View as Word and CSV files, or open this pack in River and let the agent run the backwards pass over your own pipeline.
Edit with AI