You have thirty ideas in a document. Some are good. You need a quarter's plan by Friday.
The usual move is to open a calendar and start assigning dates. It feels like progress and it produces something that looks like a plan. Then week three slips, every date after it is wrong, nobody wants to re-key twenty-six rows, and by week six the plan is a document people have stopped opening.
The fix isn't better dates. It's not using dates as the organising principle at all.
Sequence by dependency, not by date
Some of your ideas depend on other ones. The teardown needs the explainer to exist first, or half of it is spent explaining. The customer story needs the customer interview. The comparison piece needs the thing it compares against to have shipped.
Those dependencies are real and stable. Dates are neither.
So order the plan by what has to exist before what else, and put the calendar week in as a target, not a commitment. When something slips, the order still holds: everything downstream shifts by a week and the plan survives intact. That's the entire difference between a plan that gets used in month three and one that gets quietly abandoned.
Step 1: Sort the pile into three heaps
Before sequencing anything, triage. Every idea goes into exactly one heap.
Committed. You're doing this. There's a reason, and you can say it in a sentence.
Candidate. Plausible, but nothing has been established. It needs a reason before it's allowed in.
Parked. Not this quarter.
Most people skip the third heap, and it's the one that saves the most time. In week six somebody will suggest one of the parked ideas again, and "we decided not to, because X" ends that conversation in ten seconds. Without a written parked list you re-litigate the same three ideas all quarter.
Step 2: Make everything earn its place
For every item in the committed heap, write one sentence: why this, why now.
Not "it'll do well". Something specific and traceable:
- "This format is a gap in the cohort and the one competitor making it beats their median by 3×" (from competitor research).
- "Three of our five outliers were this structure and none of our worst five were."
- "Sales asks for this on every call and we have nothing to send."
That last one is a perfectly good reason, and it doesn't come from data at all. The point isn't that every item needs analytical justification. It's that every item needs a stated reason, so that when the quarter gets crowded you can compare the reasons rather than the enthusiasm.
If the "why now" cell is empty, it's an idea, not a plan item. Move it to candidate.
Step 3: Size it against real capacity
This is the step that decides whether the plan is real, and it belongs before sequencing, not after.
Work out honestly:
- Shoot days available per month
- Edit days available per month: usually the actual bottleneck, and usually the one nobody counts
- Pieces you can publish per week sustainably, not in your best week
- Review rounds you can absorb per piece
- Weeks genuinely available this quarter: thirteen minus holidays, minus the launch, minus the week everything goes wrong
Multiply pieces-per-week by weeks-available. That's your ceiling.
If your committed heap has more items than the ceiling, you don't have a plan, you have a wish. Cut now, deliberately, while you can choose what goes. Cutting in week eight means whatever happens to be last gets cut, which is rarely what you'd have chosen.
Step 4: Build the chain
Now sequence. For each item, ask one question: what has to exist before this?
Three kinds of dependency turn up:
Content dependency. The audience needs to know A before B lands.
Production dependency. Both pieces are shot on the same day, so they move together whether you like it or not. Batching is where most of the efficiency in a content plan actually lives. It's usually worth reordering the publish sequence to keep a shoot day intact.
Evidence dependency. You want to know how A performed before committing to B. This one is genuinely valuable and almost always omitted, because it requires admitting you don't know yet.
Then lay the chain across the weeks, respecting your ceiling.
Step 5: Leave gaps on purpose
A plan with every slot filled has no capacity to respond to anything.
Leave roughly one slot in five open. Not as slack for overruns (although it will absorb those) but as room to react: to a competitor breaking out, to a comment thread that reveals a question you hadn't thought of, to something in your category actually happening.
A plan that can't respond to the month it's living in is a publishing schedule, not a strategy.
What a good plan looks like when it's under pressure
The test isn't week one. It's week seven, when something has gone wrong.
A date-first plan under pressure: every row is red, nobody has re-planned it because re-planning means re-keying, and people have started working from a side conversation instead.
A dependency-first plan under pressure: item 9 slipped, items 10 and 12 depended on it and moved with it, item 11 didn't and got pulled forward. Ten minutes of work, and the plan is still the plan.
The columns that make it survive
Whatever tool you use, these earn their place:
| Column | Why it's there |
|---|---|
| Working title | Not the final title. Naming it makes it discussable. |
| Why now | The reason it's in the plan. Empty = not a plan item. |
| Depends on | The whole point. |
| Target week | 1–13, not a date. |
| Owner | One name. Not a team. |
| Status | idea → briefed → in production → in review → scheduled → published |
| Brief link | Where the actual instructions live |
Everything else is optional and most of it is decoration.
Where Acumin fits
The Content Calendar is where a sequenced plan becomes scheduled work, with a cadence read showing what you actually published against what you planned, which is usually the most uncomfortable and most useful comparison available. The Content Planner holds the sequence itself, and briefs generated from your signals attach to plan items so the "why now" and the instructions live together.
The calendar is two-sided: brand dates and creator dates on the same surface, so a shoot day and the piece it produces aren't tracked in two places by two people.
How to use this tomorrow
Take your idea list and do only step 1: three heaps, ten minutes, no sequencing.
The parked heap will be bigger than you expect, and writing down why each one is parked is the part that pays for itself in week six.
Related: How to write a creative brief is what a plan item becomes when it's ready to make. Outliers, not virality is where the "why now" for most items should come from.