Every content professional I know has a graveyard.
It lives in Notion, usually. Sometimes Airtable. Occasionally a Google Sheet with colour-coded columns that made perfect sense in January. It's the editorial calendar you built with real intention — dates, topics, formats, assigned owners, status columns — and then watched slowly collapse into a monument to good planning that life refused to cooperate with.
By March, three rows are marked "published." The rest say "draft" or "in review" or, most honestly, nothing at all. By May you've stopped opening the tab.
If this has happened to you once, it's a planning problem. If it keeps happening — if you rebuild the calendar, get excited, and watch it fall apart again — it's a systems problem. And the solution isn't a better template.
The editorial calendar was never the problem
Let's start here, because most advice about editorial calendars is really just advice about different editorial calendars. Use this tool instead of that one. Try this column structure. Add a content pillar field. Colour-code by funnel stage.
None of that is wrong, exactly. But it's rearranging the furniture in a house with a broken foundation.
The editorial calendar is an output document. It's where your decisions land, not where they're made. When a calendar breaks, it's almost always because one of the decisions underneath it was shaky — or was never made at all. The dates were aspirational. The topics were picked without a clear brief. The person "assigned" didn't actually have capacity. The publishing frequency was based on what sounded good in a strategy meeting, not what the team could actually sustain.
The calendar looked fine. Everything underneath it didn't.
So before you open another Notion template or buy a new Airtable base, sit with an uncomfortable question: what decisions have you not actually made yet that your calendar is pretending you have?
The four things broken calendars are hiding
A collapsing editorial calendar is usually covering for one of four things. Sometimes more than one at once.
01
An unclear publishing purpose
Who is this content for, specifically? What do you want them to do after reading it? Where are they in their relationship with your brand? If you can't answer those three questions for every piece on your calendar, you don't have a content plan — you have a content wish list. Wish lists are easy to abandon when life gets busy, because nothing on them feels urgent. Content with a clear job to do feels different. It has stakes.
02
Frequency that was never realistic
Someone — maybe you, maybe a stakeholder — decided that publishing four times a week sounded ambitious and professional, without running the numbers on what four times a week actually requires. A well-researched, well-edited piece of content takes time. If you're a team of one or two, and you also have meetings and briefs and performance reports and stakeholder requests, four times a week is not a strategy. It's a setup. The calendar doesn't break because you're lazy. It breaks because the frequency was dishonest from the start.
03
No brief, no ownership
A content item that says "SEO blog post — keyword: content marketing tips — Due: March 14 — Owner: Sarah" is not a brief. Sarah doesn't know the angle, the target reader, the word count, the competing pieces she should be aware of, or what success looks like. She'll either write something generic or she'll stall. Either way, the calendar suffers. A title and a due date is an intention. A brief is a commitment. If your calendar doesn't have briefs attached to it — or a clear process for generating them — you're expecting your team to read minds on a deadline.
04
No decision-making process for what gets cut
Things always come up. A product launch. A campaign that wasn't in the plan. A piece that takes twice as long as expected. An SEO insight that makes the originally planned topic feel irrelevant. Every content team faces these moments, but most editorial calendars are built as if they won't. When there's no documented process for what happens when capacity drops or priorities shift, the default is avoidance. The piece gets pushed. And pushed again. And then it's awkward to acknowledge how behind things are, so nobody does. And the calendar becomes a fiction everyone quietly agrees to ignore.
What to build instead
You still need something that maps out your content over time. I'm not telling you to abandon planning. I'm telling you to stop building plans that require everything to go right and start building systems that can absorb when things don't.
Build a content operating system, not a publishing schedule
A publishing schedule tells you what goes out and when. A content operating system tells you how content gets made — the full sequence from insight to idea to brief to draft to edit to publish to distribution to measurement. When your publishing schedule breaks, and it will, a content operating system tells you exactly where in the chain the break happened and what to do about it.
The difference sounds abstract until you're in a scramble. With just a calendar, a missed deadline is chaos. With an operating system, a missed deadline is a data point: was it the brief? The review process? Capacity? You can fix what you can diagnose.
Separate your strategy layer from your execution layer
Most editorial calendars collapse these two things into one document, and that's part of the problem. Strategy tells you why you're making content, who it's for, and what business outcome it serves. Execution tells you what specific piece is being made, by whom, by when, and in what format.
When both live in the same row of a Notion database, they get confused. You end up making tactical decisions (what should we write this week?) without the strategic anchor (what are we trying to accomplish this quarter?). That's how you end up with a full calendar and a content programme that isn't actually moving anything.
The fix
Keep a separate, stable strategy document that governs your content choices. Review it quarterly. Let it change only when the business changes — not when someone has a new idea on a Tuesday. Then use your calendar only for execution, and let it be lighter and more flexible than you've been making it.
Drop the frequency. Build a bank instead.
Here's a counterintuitive move that works: publish less frequently and build a content bank.
Pick a publishing frequency you can genuinely sustain with buffer. If one polished, well-distributed piece per week is realistic for your team, that's your frequency. Not three. Not five. One. Then use any capacity above that to build a bank of completed, edited, approved pieces ready to publish.
A content bank changes your relationship with the calendar entirely. You stop operating in perpetual emergency mode — where a sick day or a slow week means a publishing gap — and start operating from surplus. When something comes up, you pull from the bank. When the bank gets low, that's your signal to create.
Most teams never get here because they're always publishing at 100% of capacity. If you're always at full stretch, you have no buffer. Build the buffer first. It will feel slow. It is, in fact, the only thing that makes you fast when it counts.
Create a brief template and make it non-negotiable
Every piece of content that enters your production process should have a brief. Every single one. Even if the brief is short. Even if you wrote it yourself in ten minutes. The brief should answer: who is reading this, what do they need to believe or understand or feel by the end, what is the single most important thing this piece needs to say, and what does success look like?
A brief does two things that a calendar entry cannot. First, it forces a decision before production begins — which surfaces problems early, when they're cheap to fix. Second, it gives anyone reviewing or editing the piece a benchmark. You're not editing against taste. You're editing against intent.
If you manage writers — staff or freelance — a mandatory brief process also reduces revision cycles dramatically. Briefs are annoying to write. Revision spirals are more annoying. Brief templates take the friction out of writing them.
Build a kill decision into the system
Finally: decide in advance what conditions trigger a piece being cut, delayed, or deprioritised, and write it down.
Example kill decision rule
If a piece misses its draft deadline by more than one week and we have bank content available, it moves to next cycle. If we have no bank content, the deadline extends by three days maximum and the assignee flags blockers to the lead.
This feels overly formal until the moment you actually need it. Then it's the thing that stops a missed deadline from becoming a team morale spiral or a passive-aggressive Slack thread or a pile of content everyone pretends doesn't exist.
Systems aren't bureaucracy. Systems are what you use so that human beings don't have to improvise their way through every problem from scratch.
The calendar is a symptom, not a strategy
If your editorial calendar keeps breaking, you don't have a calendar problem. You have a decision-making problem — and the calendar is just where the unresolved decisions are showing up.
The fix is not a new tool. It's not a better template or a fancier database or a project management software with a Gantt view. The fix is making the decisions your calendar has been assuming you already made.
Who is the content for. What it needs to do. What you can honestly produce. Who owns what. What happens when things go wrong.
Make those decisions explicitly, document them somewhere stable, and let your calendar be what it was always meant to be: a simple, flexible, honest map of what you plan to make next.
Not a monument to ambition. A working document.
She Leads Content is a platform and community for women stepping into senior content roles. If you found this useful, there's more where it came from.