Content Calendar Rules

A content calendar is a scheduling tool for a strategy that already exists, not a substitute for one — filling empty date slots with "what should I post today" produces a stream of disconnected posts no matter how consistently it runs.

Pillars before posts

• Define 3–5 content pillars (recurring themes tied to the audience's actual interests and the brand's actual expertise) before scheduling a single post — every post on the calendar should trace back to one pillar, or it's filler.
• Write one sentence per pillar stating what it's for and who it's for ("behind-the-scenes: builds trust with prospects evaluating us") — a pillar without a stated purpose degrades into "things we post sometimes."
• Revisit pillars quarterly, not weekly — pillars should be stable enough to plan against; if they're changing every few weeks, the calendar underneath them can't build any compounding recognition.

Sustainable cadence

• Set a posting frequency the team can sustain for a full quarter at the current quality bar, not the frequency that looks best in a growth-hacking article — a cadence that collapses into inconsistency after three weeks is worse than a lower cadence held steady, because inconsistency itself reads as abandonment to an audience.
• Match cadence to format cost: a daily cadence is realistic for a quick text post, not for a produced video — set different cadences per format/platform rather than one blanket number across everything.
• Build in slack for real life (illness, launches, holidays) by planning at ~80% of theoretical capacity — a calendar with zero margin turns every disruption into a missed post instead of an absorbed one.

Batching

• Produce content in batches by type (write all captions for the week in one sitting, shoot all video for the month in one day) rather than one platform-to-publish cycle per post — context-switching between ideation, creation, and publishing is the main hidden cost that makes calendars fall apart.
• Batch far enough ahead to buffer against a bad week, but not so far that timely content goes stale before it posts — a good target is 1–2 weeks of buffer for evergreen-heavy calendars, less for anything timely-heavy.
• Separate the batching session from the scheduling session: create content in bulk, then place it on the calendar as a distinct second pass — merging the two makes both worse.

Repurposing matrix

• For every piece of pillar content, plan its full format spread up front: a long video becomes clips, a blog post becomes a thread and several single posts, a podcast becomes quote graphics and captions — one asset, many calendar slots, produced once.
• Build a standing matrix (source format → derivative formats, per platform) once, and apply it to every new piece of source content rather than re-deciding the spread each time — the matrix is what turns one recording session into two weeks of calendar coverage.
• Stagger repurposed pieces across days/weeks instead of posting all derivatives at once — spacing gets more total reach out of the same source material than a same-day dump does.

Slotting timely vs. evergreen

• Split the calendar into two lanes: evergreen pillar content on a fixed, pre-planned cadence, and a smaller reserved set of open slots for timely/trending content decided closer to the date — a fully pre-planned calendar can't react, and a fully reactive one has no backbone.
• Reserve evergreen slots as the default and let timely content bump them only when it's genuinely timely — a bump that happens every week just means the evergreen cadence was never real.
• Flag date-sensitive evergreen content (seasonal, tied to a specific event) with its valid window right on the calendar, so it doesn't get scheduled outside the window by mistake during a batch reshuffle.

Review loop

• Review calendar performance on a fixed cycle (weekly for fast-moving channels, monthly for slower ones): which pillars are earning engagement, which formats are underperforming, what's due for retirement.
• Feed review findings back into the pillar and format mix explicitly — a review that doesn't change next month's calendar is a report, not a loop.
• Keep a running list of ideas that came up during review or batching but didn't fit this cycle, so they seed the next planning session instead of getting lost between calendars.