Skip to main content
Run this on a cadence to keep the content calendar accurate enough to produce against. It covers the planning session that fills the calendar and the weekly pass that keeps it true. The two halves have different actors. The planning session is people deciding what to say and when. The preparation for it, and the weekly pass, are a builder’s: a person or an AI agent working in the same calendar, briefs, and reporting.
This process uses the content calendar standard, the organic social post brief, the article brief, messaging, and the approval process.

What you’ll end up with

  • A calendar filled to your planning horizon, every row with an owner, a status, and a message pillar.
  • Every row that belongs to a campaign linked to it, with its place in the sequence if it is part of a set.
  • A brief for every row that has reached production.

Before you start

The planning session

1

1. Close out the last period first

Before adding anything, walk the rows that have passed. Fill in published URLs, move anything that did not ship to Dropped with a reason or forward with a new date, and note which posts did unusually well or badly against the channel reporting source named in Before you start.This step, and the next, are preparation a builder can finish before the session starts, so the people in the room spend the session planning rather than bookkeeping. Planning on top of an inaccurate calendar produces a plan nobody trusts by week two.
2

2. Lay in the fixed points

Start with what is already committed and cannot move: campaign flights from the campaign briefs, product releases from the release plan, events, reports, and anything seasonal.Everything added in the next step is timed around one of these, or is deliberately standalone.
3

3. Add supporting content around each fixed point

For each fixed point, decide what content it needs and in what order. Fill in the campaign and sequence columns as you go, not afterwards.A campaign flight usually wants a set rather than a single post. See the sequencing table below.
4

4. Fill the remaining slots, or leave them empty

Work to the target volume in your calendar standard, and stop when the ideas stop. A row that cannot say what it is for is a slot being filled, not a post being planned.
5

5. Assign an owner and a status to every row

One name per row. A row with no owner is a row that gets discussed again next month in exactly the same state.
6

6. Check the mix

Read the period as a whole: are the message pillars balanced, or has one taken over? Is one format doing all the work because it is the fastest to make? Both drift without anyone deciding. The counts are a builder’s to compute; whether the mix is right is the room’s call.

Sequencing content around a campaign

Organic content supporting a paid flight is a set with an order. Decide what each piece is doing before deciding what each piece is. Record each row’s position in the sequence column and link the campaign. That tells whoever picks up production which post has to be ready first.
Publishing a sequenced set out of order is worse than publishing one post. The pieces are written to build on each other, so a closing post that lands before the warming post reads as a non sequitur, and the set costs more than it returns.

The weekly pass

Short, and the thing that keeps the calendar worth reading. Run it as a scheduled pass: every bullet is a register query, so a builder runs the five and posts an exceptions list, rows missing a brief, an owner, a URL, or an approval, for the owner to clear. A clean week is a one-line result.
  • Every row publishing in the next two weeks has a brief and an owner.
  • Every row in production has cleared, or is queued for, whatever approval it needs.
  • Every row that published last week has its URL filled in.
  • Anything slipping has been moved, with its sequence moved with it.
  • Anything urgent that published without a row has one now.

When an anchor moves

A campaign flight or release that moves drags its supporting set with it. The move is mechanical and a builder can execute it; the confirmation is the owner’s:
  1. Filter the calendar to rows linked to the anchor.
  2. Shift the set, keeping the intervals between sequence positions.
  3. Check for collisions with other rows and flag any.
  4. Notify each affected row’s owner through the channel your team names here: E.g. Slack, #marketing.
The owner confirms the new dates before production continues; a sequenced set shifted without its owners knowing publishes out of order anyway.

Exceptions

  • A reactive or urgent post. It publishes first and gets its row the same day. The row is not optional; it is what keeps the channel report and the retrospective complete.
  • A recurring series with a fixed slot. One row per instance still, because each one needs its own URL and status, but they can share a brief per the post brief.
  • A channel someone else owns. If another team publishes on a channel you report on, the calendar still needs the rows, even if it does not own the production. Agree who adds them.
Type: process
Domains: content, social, campaign
Provides: process:content-calendar
Uses: approval-route, article-brief, campaign-brief, content-calendar, messaging, reporting-cadence, social-brief
Hands off to: process:organic-social, process:article, process:approval
Triggers: “Plan next month’s content” · “Fill in our content calendar” · “What should we post around the launch?” · “Run the weekly calendar check” · “Our campaign moved, shift the content”Asks, in order:
  1. Which period are we planning? Options: your answer. Skip when: calendar standard sets the planning horizon.
  2. Any fixed points I should plan around beyond the campaign briefs and release plan? Options: your answer. Skip when: never skip; quick confirm.
  3. For each campaign flight, which sequence positions do you want content for? Options: sequence-position. Skip when: default to all three.
  4. Who owns each row? Options: your answer. Skip when: single-person team.
Output: Calendar rows (owner, status, pillar, campaign, sequence) written to the user’s content calendar; closed-out last period; mix summary (pillar/format counts) for the owner; for the weekly pass, an exceptions list.

Get the complete Marketing OS

Subscribe to Snow Doughnut, our free weekly newsletter, and get the Notion workspace where you do the work: tasks, a marketing calendar, name generators, briefs, and more.

Have us run it for you

We implement this system, use it to help you grow and scale, then hand it all off to you when you’re ready.
Last modified on November 2, 2026