The content planner

The planner is a board that carries a post from idea to review to ready, with calendar and list views over the same data, and it never publishes anything. It has four lanes over three statuses, where Overdue is derived from a past scheduled date rather than stored — so a past-due card sits in Overdue whatever its status, and moving it between lanes settles its date in the same action.

Prefer the long version? How to use the content planner to run a week of posts walks through it in depth.

What it is

One board with three views. Board shows cards in lanes, Calendar places them by date, and List is the dense view for bulk tidying. All three read one dataset loaded in a single request, which is why filtering and switching views are instant.

A card holds a post type, an audience, the text, an optional image prompt, and a scheduled date.

The planner plans and never posts. There is no publishing integration for it to use. Marking a card Posted records that you published it yourself, somewhere else.

Statuses and lanes

Three stored statuses — idea, review, ready — plus posted. But the board shows four lanes, and the extra one is not a status:

LaneWhat it holds
OverdueAny dated, unposted card whose date has passed — derived, not stored
Needs reviewUndated drafts waiting on a human
ScheduledReviewed, dated, waiting for its day
PostedThe archive

Overdue wins. The review and scheduled lanes exclude overdue cards, so a past-due card is pinned to Overdue regardless of what its status says.

The consequence that surprises people: setting an overdue card's status to "review" does not move it. The status changes, the save succeeds, and the card stays where it was — because it is still past due.

How a lane move settles the date

Because of the above, moving a card between lanes adjusts its scheduled date in the same action:

Move toWhat happens to the date
Needs review, or ideaCleared — undated-in-review is a normal state
ScheduledRolled to today — "Scheduled, no date" is a contradiction
PostedUntouched — the archive matches on status alone
Any lane, from a card that was not overdueUntouched

When a move changes a date, the board tells you. It does not move it behind your back.

Overdue is compared by calendar day, not by timestamp — a post due at 09:00 does not turn red at 09:01.

Generating

Generate a post turns one line of intent into a caption with hashtags, written into a card. It does not publish and it does not schedule.

Image prompt produces a dense visual description you can paste into whichever image tool you use. It is a prompt, not a picture. It runs on its own model setting, and where that is left unset the extra pass is skipped rather than repeating an identical call.

Make longer or shorter resizes an existing card's text.

If a generated reply comes back unusable — models sometimes pad or wrap their output — the request fails cleanly rather than writing a junk row. Generate again.

The stat tiles

The tiles count the whole board, never the filtered slice.

That is deliberate. If they counted the filter, searching would make Overdue drop and read like progress, which is the opposite of what an overdue count is for.

Capacity

A board loads up to 500 rows in one request. Past that, archive what is already posted — the tiles and filters stay honest and the views stay instant.

Limits

  • No publishing, no queue, no scheduler that fires. Scheduled means "ready and dated".
  • No analytics. It does not fetch engagement figures; audience and post type are your own filtering fields.
  • Generation needs AI configured. If it is not, the two Generate buttons say so plainly and every other part of the board keeps working — you can still add, move, date and edit by hand.
  • The calendar's first day follows your week-start display preference.