Content Calendar Template
A recurring structure organised around publish dates rather than a start and end date: idea, draft, review, scheduled, published, for teams that never really finish, only keep going.
No end date. Cards move left to right by publish date, and the calendar keeps going after this month's cards clear.
Why content calendars stop getting filled in
A content calendar is different from most boards in one important way: it never finishes. There's no launch day, no wrap-up, no closing sprint. That's exactly why it's so easy to let slide, and why the failure mode looks different from a project board's.
The idea column empties out and nobody notices for a month. Ideas get pitched in bursts, usually right after a planning meeting, and then the well runs dry quietly. Because there's no deadline forcing the issue, an empty idea column doesn't feel urgent until the draft column is empty too.
Publish dates live in a separate calendar app from the drafts themselves. The writing happens in one place and the schedule in another, so keeping them in sync becomes its own recurring task, one that gets skipped the first busy week and never quite recovers.
Review has no limit, so pieces stall there indefinitely. A draft is "in review" for three weeks not because it needs three weeks of review, but because nothing forces a decision, and it's easier to leave a card sitting than to make the call.
There's no ongoing signal that the calendar is healthy or thin. A project has a burn-down; a calendar just quietly has fewer cards in it than it did last month, and without something measuring that, the first sign of trouble is an empty scheduled column two weeks out.
A calendar is a different kind of thing to plan than a project, and it needs a different kind of structure: one built around a steady rhythm rather than a finish line, with its own signals for when that rhythm is slipping.
The structure, and why each part is there
The calendar tracks how many ideas are sitting in the first column, so a shrinking supply is visible weeks before it becomes an empty drafting column.
A WIP limit stops five pieces being half-written at once. Two or three finished drafts move the calendar forward faster than five started ones.
Capping how many pieces can be in review at once forces a decision on the oldest one before a new one enters, which does more than a due date ever does.
Cards in this column are the calendar itself, ordered by the date they go out, so the publishing plan for the next few weeks is one glance at the board, not a separate spreadsheet.
Finished pieces stay visible as a running archive of what's gone out, useful for spotting gaps: a topic or format that hasn't appeared in months.
A recurring task to pitch new ideas, set at a fixed interval, so the first column refills on a schedule instead of only after someone notices it's empty.
Not every idea is worth a full brief. A short triage step decides which ideas advance and which get parked, so drafting time isn't spent on pieces that were never going to run.
A running series, a monthly customer story, a quarterly roundup, gets its own wiki page tracking which subjects have already been covered, so the fifth instalment isn't accidentally the same as the second. Teams keeping this page current tend to notice the repeat before a reader has to point it out.
The plan for how many pieces move through drafting each week is set against how much writing time actually exists, leave included, rather than a target rate the team quietly can't sustain.
How to use it
- 01Start a workspace. It opens with a sample calendar already populated across all five columns, so the flow is visible immediately. Free for up to five people, permanently.
- 02Order the scheduled column by publish date, not by when the card was created. The column should read top to bottom as the plan for the coming weeks.
- 03Set a WIP limit on drafting before you set one anywhere else. It's the column most likely to silently fill up with unfinished pieces.
- 04Add a recurring task to pitch new ideas, weekly or biweekly, so the calendar doesn't rely on someone remembering to think of a topic.
- 05Review the published column monthly for gaps, not to grade output, but to notice a format or topic that's quietly stopped appearing.
- 06Count the ideas column, not just the scheduled one, at the start of every month. A thin ideas column is the earliest warning the calendar gives you, weeks before the scheduled column shows anything wrong.
- 07Give each recurring series its own wiki page from the start, even before there's much to put on it. It's much easier to keep a running log current than to reconstruct one after the tenth instalment.
Unlike a campaign or a launch, this board is never really "finished." The goal is a steady rate of cards crossing from idea to published, indefinitely. That's a different discipline from hitting a deadline, and the structure here is built for the former. A calendar that's judged only by the current month's scheduled column will always look fine right up until it isn't.
- A content calendar has no end date, so it needs a refill cadence, not a deadline, to stay healthy
- A capped review column forces decisions; an uncapped one accumulates stalled drafts
- The scheduled column, ordered by publish date, is the calendar; everything else feeds it
Common questions
This one is for longer-form pieces, articles, guides, case studies, organised by publish date with a slower cadence, often a handful of pieces a month. The social media calendar template is organised by channel instead of by stage, with a much higher cadence, often daily. They're built for different rhythms of work.
No, there's no publishing or scheduling integration. The scheduled column tells you what's meant to go out and when; the actual publishing still happens wherever your content normally goes live.
Free covers up to 5 users and 2 projects permanently, with every template included, this one among them. Team is ₹299 per user per month for larger teams, up to 40 users. See pricing for details.
Nothing automatic. The recurring pitch task is there specifically to prevent it, but if it still happens, the fix is a dedicated ideas session rather than pressuring the drafting column to move faster than it has material for. A calendar with three well-chosen ideas beats one with ten forced ones.
No, there's no publishing integration with any blog, CMS or content platform. The published column records that a piece has gone out and where, but the act of publishing still happens in whichever system your content actually lives on.
Related pages
See it on your own work.
A workspace your whole company will actually use is 60 seconds away. No card, no risk, nothing to install.
14-day full-access trial · sample project included · no card required