River
Y CombinatorBacked by Y Combinator

Free template

Marketing Editorial Calendar Template

A quarterly editorial calendar with owners, stages and review dates, plus sheets that size it to your team's real capacity and flag slipping pieces.

Free download · No account needed

What you get

Pack of 8 files: 4 documents, 4 spreadsheets

Marketing Editorial Calendar Template
  • Capacity MethodDocument
  • Workflow DefinitionDocument
  • Editorial PolicyDocument
  • Slip ReviewDocument
  • Capacity PlanSpreadsheet
  • CalendarSpreadsheet
  • Pipeline by StageSpreadsheet
  • Published RegisterSpreadsheet
RiverMarketing Editorial Calendar Template

Capacity Plan, Q1

Why the quarter was impossible in week one

Two writers, one editor, a designer at a fifth of a week. A fictional instruments manufacturer, Havelock.

StageOwnerTouch hours per pieceHours available per weekCapacity per week
BriefEditor3124.0
DraftTwo writers16402.5
EditEditor691.5
DesignDesigner, 0.2 FTE47.51.9 on 60% of pieces
ScheduleEditor0.5510.0

Nine hours. That is what was left of a full-time editor's thirty-five hour week after twelve hours of brief writing, five of scheduling, three of calendar admin and six of standing meetings. Six hours per piece against nine available is one and a half pieces a week, and it was the lowest number in the pipeline, so it was the pipeline.

Thirteen weeks at 1.5 is 19.5. The plan committed 24, drafts arrived at 2.5 a week, and the queue grew by one piece a week until March. Delivered 17, eleven of them on the promised date.

Page 1 of 1170 words

How to create an editorial calendar

An editorial calendar is the schedule of every piece your team has committed to publish, with each piece's topic, publish date, owner and current stage. To create one, list the stages a piece goes through and who owns each. Work out how many pieces your slowest stage can finish in a quarter, and fill only that many slots. Then date every request to people outside the team, such as legal, and review the calendar weekly.

Sizing decides whether the calendar holds: your slowest stage, not the empty cells in the grid, sets how many pieces a quarter can carry.

Two people planning at a glass wall covered in yellow sticky notes grouped under quarter labels
Plan the quarter around what your team can finish, not the wall space. Photo: airfocus on Unsplash

List the stages and who owns each

Start with the steps a piece goes through on your team, from brief to published. Give each step one named owner, a person rather than a team, and a test for when a piece is done with it. Make it a fact someone can check, like these:

  • Brief: the writer can start without asking a question.
  • Draft: complete, including the sections nobody enjoys writing.
  • Edit: the editor would publish it as it stands.
  • Outside review: written approval, or the specific changes the reviewer asked for.
  • Schedule: the post is set to publish in your publishing system, with a date.

Count each time a piece goes back a step. Drafts that keep bouncing back from edit often point to a thin brief, which a content brief template helps fix before anyone starts writing.

Measure what your team can publish

Work from what last quarter actually took, not from how long things should take. Social psychologist Roger Buehler, who studies the planning fallacy, explains that people underestimate how long a task will take even when they know similar tasks took them much longer1. The first fix he lists is the outside view: forecast from how long similar work took.

For each stage, divide the hours its owner really has for it each week, after meetings and other duties, by the hands-on hours one piece needs there. That gives pieces per week. Ask each owner for hands-on hours, and keep them apart from days elapsed: a draft that sits for 6 days may hold 16 hours of writing.

ExampleSizing a quarter for a small teamAn illustrative example written for this guide. The team is made up.

Drafting: two writers share 40 drafting hours a week, and a draft takes 16 hours. That is 2.5 drafts a week.

Editing: after briefs, meetings and admin, the editor has 9 hours a week to edit, and an edit takes 6 hours. That is 1.5 pieces a week.

The quarter: 1.5 a week for 13 weeks is 19.5 pieces. The old calendar promised 24, so finished drafts piled up at the editor all quarter.

  • The slowest stage sets the pace. Extra drafts don't become extra posts. They wait in the editor's queue, and every date behind them slips.
  • The bottleneck moves. Moving briefs to the writers frees editing hours. Drafting becomes the slowest stage, so the next hire is a writer.

Starting pieces faster than your slowest stage can finish them doesn't ship them sooner; they queue. Little's Law, proved by operations researcher John Little in 1961, links throughput, work in process and cycle time2. On a calendar, pieces in progress divided by pieces finished per week gives the average weeks each piece takes. Fourteen in progress at 1.5 a week is about 9 weeks each, whatever the plan says.

To size the quarter, multiply the slowest stage's weekly pace by the weeks in it. Then hold back slots for unplanned work, sized by the share of last quarter's pieces that weren't in the plan, and allow for finishing pieces already in progress. What's left is your commitment.

What to include in an editorial calendar

Fill only as many rows as your capacity number allows. Take topics from your keyword research, one target query per piece, and check that no page of yours already covers that query. A keyword clustering template and a content audit make both checks quick.

The columns an editorial calendar needs

ColumnWhat goes in itWhy it matters
Promised dateThe date you've told the businessMoves only at the weekly review, with a reason
Target dateA few days before the promised dateLeaves room for scheduling and a slow edit
Topic and queryA working title and the one search it targetsStops two pieces chasing the same search
FormatGuide, case study or short news pieceShows which stages it needs, like design
Owner and stageOne named person, and where the piece is nowMakes a stalled piece easy to spot
DependencyWhat you need from outside the team, from whom, and the date to askStarts the reviewer's clock in time
Status in your CMSWhat your publishing system says: draft, scheduled or publishedCatches rows that only look scheduled

Leave a few rows empty and label them held. They're for news and requests nobody could foresee, so don't fill them in the planning meeting. When a rush job arrives after they're gone, name the planned piece it pushes out and give that piece a new date.

Date every outside request

Anything that needs someone outside your team runs on their clock: a legal review, a customer quote, an interview with an expert. The Content Marketing Institute surveyed 980 B2B marketers for its 2025 benchmark report. In it, 33% named managing workflow and content approvals as a challenge3, and 33% named access to subject matter experts.

So give every outside dependency a request-by date. Start from the date you need it back by, subtract that person's usual turnaround, and write the result on the row. Send the request on that date, whatever state the draft is in. If legal usually needs 10 days and you need its answer by June 20, ask by June 10.

A legal reviewer mostly checks claims, customer names and figures, which rarely change in the final edit. Ask whether they'll start on a draft that's about 60% done, so their review runs alongside your edit instead of after it.

Review the calendar every week

Each week, check how long every piece has sat in its current stage, not just how close its date is. The Kanban Guide, created by John Coleman and Daniel Vacanti, counts work item age, the time since an item started4, among four required measures. It judges that age against a forecast built from how long past items took.

Apply that stage by stage. From last quarter's dates, find each stage's typical time (the median) and slow time (the 90th percentile, which only one piece in 10 exceeded). A piece past its stage's slow time is in trouble, even with weeks to go. That's when you can still act: unblock it, swap it with a ready piece, move it to a held slot or cut it.

Check the calendar against your publishing system too. WordPress, for example, gives a post set to go live later its own status, future5, separate from draft and pending. A row your sheet calls scheduled won't go live if the post still sits in draft.

A scheduled post publishes itself

If a post is scheduled before its review is done, it goes live on time without that review. Keep it unscheduled until approval is in writing.

Before you commit the quarter

  • Every stage has one named owner and a test for done
  • The number of pieces matches what your slowest stage can finish
  • Held slots are labeled and empty
  • Each piece targets one query that no existing page covers
  • Every outside dependency has a request-by date
  • Target dates sit a few days before promised dates

The template on this page has these columns ready, with a sample quarter filled in. Open it with Edit with AI, send River your last two quarters, and it works out how many pieces the next one can hold. Once a slot has its brief, River's SEO blog post writer or LinkedIn article writer turns it into a first draft.

How to use this template

Use the files as they are, or open them in River with Edit with AI. River asks what you published over the last two quarters and who owns each stage. It also asks how much of their week each stage really gets, and what needs someone outside the team, like a legal review.

From that, River fills in the Published Register, finds the stage that limits your team and works out how many pieces next quarter can hold. It leaves the dates for later and suggests one change that would raise the number.

  1. Download it or open it in River

    Download four Word documents and four CSV sheets with no signup, or choose Edit with AI to work in River.

  2. Send your publishing history

    Share what went out over the last two quarters, with promised and actual dates, plus who owns each stage.

  3. Get your real capacity

    River names your slowest stage and tells you how many pieces next quarter can hold, before any dates go in.

  4. Fill the calendar and review weekly

    Fill the slots yourself or ask River to, then check each piece's time in its stage once a week.

What's in the template

The number, the quarter it buys, and the week that delivers itThe constraint moving after one change to who does what, the calendar with every dependency carrying a request-by date, and the weekly risk view read off stage age.
Marketing Editorial Calendar Template
RiverCapacity

Capacity Plan

Same three people. One task moved off the constrained person, and the constraint moved with it.

StageQ1 hours per weekQ1 capacityQ2 hours per weekQ2 capacity
Brief12, editor4.03, editor reviews onlyfolded into draft
Draft40, two writers2.540, two writers2.0
Edit9, editor1.518, editor3.0
Design7.51.9 on 60%7.51.9 on 60%
Schedule510.0510.0
Pipelineconstraint: Edit1.5 per weekconstraint: Draft2.0 per week
Quartercommitted 24capacity 19.5committed 21capacity 26

Relieving a constraint moves it, and that is the useful part. Writers self-briefing costs them four hours a piece, so drafting falls from 2.5 to 2.0 and becomes the new lowest number. Which makes the next hiring conversation one line long: a writer, not a second editor.

Commitment is capacity minus a reserve minus ramp. The reserve is the 12% of last quarter that arrived unplanned, measured rather than the round 20% every article recommends. Ramp is the fourteen pieces already in flight at the boundary.

RiverCalendar

Calendar

Every dependency carries a lead time and a request-by date back-computed from the target date.

SlotPromisedStageDependencyLeadRequest bySentCMSAgrees
Q2-0221 AprPublishedLegal review5d8 Apr7 AprpublishYes
Q2-0328 AprPublishedCustomer quote10d14 Apr13 AprpublishYes
Q2-0619 MayScheduleDesign7d7 May7 MayfutureYes
Q2-0726 MayEditLegal review5d14 May13 MayfutureNo
Q2-099 JunDraftCustomer quote10d25 May22 MaydraftYes
Q2-1016 JunBriefLegal review5d4 Junnot yetnoneYes
Q2-H229 MayPublishedLegal review5d21 May19 MaypublishYes
Q2-X1cut 11 MayCutExpert interview21d19 MaynevernoneYes

Row four is the one worth having. The post is already in a scheduled state and will publish itself on 26 May, and the piece is still in edit with legal outstanding. It was going to go live unreviewed, exactly on time, and nothing in a status column would have shown it.

The last row was cut in a weekly review rather than missed at the end of June. A 21 day interview lead time against a target of 4 June made the date impossible the moment it was written down.

RiverThis Week

Pipeline by Stage

Risk is days in stage against that stage's own distribution from the register. Not the publish date.

PieceStageDays inMedianP90RiskDays to dateDecision
Q2-06 Cost of ownershipSchedule112On pace1Publishes tomorrow
Q2-07 Method validationEdit425Watch8Chase legal. Unschedule the post today
Q2-08 Column careDraft12712At risk15Swap with Q2-11 or take a held slot
Q2-09 Titration automationDraft8712Watch22Quote is the critical path. Confirm this week
Q2-10 Qualification packBrief525At risk29Unblock, or the 4 Jun legal request slips with it
Q2-13 Pipette calibrationOutside review20519Blocked-7Escalate today or cut and take the slot back
Q2-14 FTIR against RamanDesign1349At risk8Ship without the diagram or move to 9 Jun
Q2-11 BalancesBrief125On pace36Nothing needed

Every red row still has time on it. That is the entire reason the view reads stage age: overdue is a result, and a piece past the ninetieth percentile with fifteen days left is a decision somebody can still make.

Across the quarter, eight pieces crossed a ninetieth percentile and each was flagged a median of eleven days early. Five recovered, two swapped with ready pieces, one was cut. None was discovered at its date.

  • Capacity MethodSeven steps from your team's real hours to the number of pieces a quarter can hold.
  • Workflow DefinitionEach stage from brief to published, with one owner, a test for done and request-by dates.
  • Editorial PolicyStanding decisions on what earns a slot, cadence, the two dates, approvals and rush requests.
  • Slip ReviewA made-up team's missed quarter, worked through: three fixes, and on-time delivery rising from 46% to 90%.
  • Capacity Plan sheetHours and pieces per week at each stage, the slowest stage named, and the quarter's commitment.
  • Calendar sheetEvery committed and held slot, with promised and target dates, dependencies, request-by dates and CMS status.
  • Pipeline by Stage sheetPieces in progress, with days in stage against typical and slow times, a risk level and this week's action.
  • Published Register sheetOne row per piece: promised and actual dates, days in each stage, returns and the cause of any slip.

Common questions

What should an editorial calendar include?

An editorial calendar should list each piece's working title, target query, format, owner, current stage and publish date. Strong ones add a target date a few days earlier and a request-by date for anything needed from outside the team. They also show each post's status as your publishing system reports it, and keep a few slots empty for unplanned work.

What's the difference between an editorial calendar and a content calendar?

Many teams use the two names for the same thing. Where they differ, an editorial calendar tracks how each piece gets made, with stages, owners and deadlines from brief to publish. A content calendar shows what goes out where and when, often including social posts. This template is an editorial calendar for a team that writes its own pieces.

How many pieces should we publish a week?

Publish as many as your slowest stage can finish each week, and no more. To find it, divide the hours each stage gets a week by the hours one piece needs there. The lowest result is your pace. An editor with 12 hours for editing and 4-hour edits can handle 3 pieces a week, however many writers you add.

How far ahead should you plan an editorial calendar?

Commit specific pieces one quarter at a time. A quarter is long enough to book reviews and interviews, and short enough that your capacity numbers still describe the same team. Keep later ideas in an undated backlog, and measure capacity again whenever someone joins, leaves or changes what they do.

Why does our editorial calendar keep slipping?

Usually because it promised more pieces than the slowest stage can finish, so drafts queue and every later date moves. Two habits make it worse: asking outside reviewers only once a draft is final, and letting rush jobs replace planned pieces without saying so. Size the quarter from last quarter's real dates, and review stage times weekly.

Is this editorial calendar template free?

Yes. Download the four Word documents and four CSV sheets without signing up. The sheets come filled in with a made-up team's quarter, so you can see how they connect before you clear them. Edit with AI opens the same files in a free River workspace instead.

What does Edit with AI do?

It opens this template in a free River workspace. River asks for your last two quarters of published pieces, who owns each stage and what needs outside review. It then measures each stage, names the one that limits your team and works out how many pieces next quarter can hold. Calendar dates come after that.

Sources

  1. Society for Personality and Social Psychology. “The Planning Fallacy: An Inside View.” spsp.org (opens in a new tab)

  2. Project Production Institute. “Reprint: Little’s Law as Viewed on Its 50th Anniversary.” projectproduction.org (opens in a new tab)

  3. Content Marketing Institute. “B2B Content Marketing Benchmarks, Budgets, and Trends: Outlook for 2025.” contentmarketinginstitute.com (opens in a new tab)

  4. Kanban Guides. “The Kanban Guide.” kanbanguides.org (opens in a new tab)

  5. WordPress.org. “Post Status.” wordpress.org (opens in a new tab)

Written by

Chandler Supple

Co-founder & CEO, River

Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.

Reviewed by

Brian Joseff, Co-founder, River