---
name: content-calendar
description: Use when asked to build or maintain a content calendar — a scheduled plan of what content gets published on which channel and when, with an owner and status per item — distinct from a [[press-release]] or any single piece of content, which is one entry that might sit on the calendar rather than the schedule itself.
---

# Content Calendar

A content calendar is a forward-looking schedule of what gets
published where and when. It's a planning and coordination tool, not
the content itself — each row or card points at a piece of content
(a blog post, a social update, an email, a launch announcement) and
tracks when it goes out, who owns it, and whether it's actually ready.

## Key components

- **Channel** — which platform or format the item runs on (blog,
  newsletter, a specific social network, paid, PR), since the same
  topic often needs different treatment on different channels.
- **Publish date** — when the item goes live, the backbone the
  calendar is organized around.
- **Topic or title** — enough detail to identify the piece without
  opening a separate doc, plus a link to the actual draft or brief.
- **Owner** — the specific person accountable for getting the item
  from idea to published, not a team name.
- **Status** — where the item actually is (idea, drafting, in review,
  scheduled, published), kept current so the calendar reflects reality
  rather than intent.

## Why plan ahead instead of publishing reactively

A calendar built a few weeks or a quarter out gives a team room to do
things reactive, day-of publishing can't: keep a consistent cadence
instead of bursts followed by silence, schedule content around known
launches, campaigns, or seasonal moments instead of scrambling after
the fact, and spot gaps (a channel gone quiet) or duplication (two
teams both planning a post on the same topic the same week) while
there's still time to fix it. None of that rules out reactive or
timely content — see below — it just means the planned content isn't
what's competing for that room.

## Leaving room for timely content

A calendar filled solid weeks out looks organized but can quietly
break the team's ability to respond to anything unplanned — a news
hook, a trending topic, a customer question worth answering fast.
Deliberately under-book some slots, or mark specific slots as flexible
holds, so timely content has somewhere to land without bumping
something else that was already committed.

## Common pitfalls

- **Dates filled in with no real owner** — a slot on the calendar
  isn't the same as someone accountable for it; without a named owner,
  items quietly slip and nobody notices until the date has passed.
- **Every slot booked weeks out** — leaves no room for timely or
  reactive content, and forces a choice between ignoring a real
  opportunity or bumping something already promised.
- **Status never updated** — a calendar that still shows "drafting"
  for an item that published last week (or shows nothing at all) stops
  being trustworthy, and the team falls back to asking in chat instead
  of checking it.
- **Calendar as wish list, not a plan** — listing every idea anyone has
  had with no realistic capacity to produce it all sets the team up to
  either miss dates constantly or quietly abandon items with no record
  of the decision.
- **No visibility across teams** — separate calendars per team or
  channel recreate the exact duplication and gap problems a shared
  calendar exists to prevent.

## Learn more

- [[press-release]] for one specific kind of item that might appear on
  the calendar around a launch or milestone.
- [[content-calendar]]'s natural companion, [[customer-journey-map]],
  for thinking about which stage of the journey each piece of content
  is meant to serve.
- [[marketing-manager]] for the broader role usually accountable for
  keeping the calendar coherent across channels.
- [[branding]] for the voice and identity a calendar's content should
  stay consistent with across every channel.