The calendar is where everything you publish becomes visible in one grid. How campaign content appears there, what the chips and ghosts mean, and which surface to use for which job.
Jump to module
The calendar is the whole picture: everything you are publishing, from every source, in one grid you can scan by week.
That is a genuinely different question from the one a campaign page answers.
| Question | Surface |
|---|---|
| "Did this campaign work?" | The campaign page |
| "What is going out Thursday?" | The calendar |
| "Is next week too heavy?" | The calendar |
| "Are my three image posts still on plan?" | The campaign page |
| "Am I posting the same thing twice?" | The calendar |
| "Which angle earned the engagement?" | The campaign page |
A campaign shows one campaign's content in the order the plan unfolds — oldest first, deliberately, because it is a plan unfolding and not a feed. The calendar shows everything, in time order, including routine output, agent output and anything you wrote by hand.
Neither is a replacement for the other, and you will use both weekly.
Campaign content is not a separate layer on the calendar — it is ordinary content with a label.
The campaign chip. A post that belongs to a campaign carries a small chip naming it. The chip is deliberately neutral rather than brand-coloured: a campaign is a grouping label, so it should read at the same weight as the platform chips beside it, not compete with the status badge for your eye.
Two campaigns on one post. A post can legitimately belong to more than one campaign — an evergreen explainer can serve a spring launch and an autumn one. The card names the first and shows a count for the rest; hover to see the full list.
This is also why per-campaign numbers do not sum to a workspace total (Module 12). A post counted in two campaigns is one post.
Both ways in. A post reaches a campaign either because a campaign run produced it, or because a person attached it. The calendar shows both identically, because from the calendar's point of view they are the same thing: a post that belongs to a campaign.
Drafts awaiting review. Content that exists but has not been approved shows differently from content that is genuinely scheduled. Do not read an unapproved draft as a commitment — it will not go out until somebody decides on it.
Both surfaces can change the same content, and it is worth knowing which change belongs where.
Do in the calendar:
Do on the campaign:
The rule of thumb: the calendar edits a post; the campaign edits the plan. Moving one post in the calendar does not change the plan, and it does not change next week. If every week is landing wrong, fix the plan — or better, your workspace preferred schedule, which is where campaign times come from in the first place (Module 9).
Times a campaign proposes are real. A draft carries the prompt's time, and approving it keeps an existing future time rather than reallocating one. So if the calendar shows a campaign post at an hour you dislike, moving it there works — but the same hour will come back next week unless you fix the source.
A weekly rhythm that uses each surface for what it is good at:
Monday — the calendar. Look at the week ahead. Is it balanced? Is anything colliding? Is there a day with nothing? This is the five-minute pass that catches the problems no single campaign page could show you, because they are problems of combination.
Midweek — the Approve queue. Decide on drafts. The queue, not the calendar, is where deciding happens; the calendar is where you check the consequence.
Friday — the campaign pages. For each running campaign: is it still on plan, is the content still matching the angle, has anything failed. This is also where you notice a campaign that has quietly stopped generating.
At the end of a campaign — the campaign page. The outcome, the empty reason if there is one, and the decision about whether to duplicate.
Treating the calendar as the plan. It is a view, not a source. Deleting a post from the calendar removes that post; it does not change what the campaign will produce next week.
Approving from the calendar out of context. The queue exists so you decide on drafts as a batch, with the campaign's angle in mind. Approving one post at a time as you notice it on the grid is how a campaign ends up half-published and incoherent.
Judging a campaign by its calendar footprint. A campaign that looks busy on the grid may have published none of it. Only the campaign page counts published per account (Module 12); the calendar shows what exists, not what landed.