Marketing · Content calendar

A content calendar that maintains itself between meetings

The calendar stops rotting the moment somebody other than you is responsible for updating it every week.

What the worker does

A content calendar in Polaris is a workstream with a lane per stage and one task per planned piece, each with an owner and a date. An AI worker with the Google Calendar and Notion connections keeps it current: it opens tasks for upcoming slots, flags weeks with nothing planned, and posts a gap list every Friday as a comment. A person approves what actually gets scheduled.

Connections
Google Calendar · Notion · Slack
Lives in
A workstream, list and board share lanes
Cadence
Weekly recurring task

Why calendars die

A content calendar is accurate on the day it is built and wrong two weeks later. Not because anyone is careless, but because updating it is nobody's actual job. The person who made the spreadsheet moved on to writing, and the spreadsheet quietly became a record of what you once intended to publish.

The fix is not a better template. It is making the maintenance a task that somebody holds, with a date on it, every week. That somebody can be an AI worker.

Setting it up

About fifteen minutes, once.

  1. 1

    Create the workstream

    Call it Content. Add lanes for the stages you really use: Ideas, Briefed, Drafting, In review, Scheduled. List view and board view share these lanes, so you organise once.

  2. 2

    Hire the worker

    Tell your Chief of Staff the calendar keeps going stale. It runs a short interview: a name, the role, what the worker should be great at, which tools it needs. Pick Google Calendar and Notion. The answers become an editable SKILL.md.

  3. 3

    Write the maintenance brief into the skill file

    Your publishing cadence, the lead time each format needs, which lane a piece should be in by which day, and who owns each format by default.

  4. 4

    Assign the recurring task

    One task, due every Friday: review the next four weeks, open a task per unfilled slot, and report gaps. Put it in the Focus lane so it never scrolls away.

  5. 5

    Approve the first delivery

    The worker posts its review as a comment on the task, with the proposed new tasks listed. You read it, close the task and rate it. Nothing was created behind your back.

What comes back every week

  • The gap list

    Weeks in the next month with no piece in Briefed or later, named by format and audience rather than left as an empty cell.

  • Slipped pieces

    Anything still in Drafting past its lead time, with how many days it has been there and who owns it.

  • Proposed tasks

    A task per gap, prefilled with bucket, lane, format and a suggested owner, waiting for one click.

  • Calendar collisions

    Two pieces landing the same morning, or a publish date on a company holiday it read off Google Calendar.

Questions people ask

+Does the worker create tasks automatically?

It proposes them. Prefilled task suggestions arrive in the Inbox with bucket, lane, labels and owner already set, and a person accepts them with one click. Polaris never adds a task to your board without approval.

+Can it read our existing calendar in Notion?

Yes, if you connect Notion. Connections are authorised once for the whole organisation and stored server-side, so the worker reads the space while your team keeps editing it as usual.

+What happens to the calendar when the worker is not running?

It is a normal workstream of tasks, so people use it exactly as they would any board in Polaris. The worker maintains it; it does not own it.

+How is a weekly calendar review billed?

By the human-equivalent hours the delivery represents, at about $2 an hour, itemised on the worker's work log. A short weekly review is a short line on the bill, and you can challenge any line from the log itself.

Your next hire takes 60 seconds.

The software is free — unlimited people, tasks, workstreams and docs. You pay only for work an AI worker actually delivers, itemised by the hour.

Get started free

Last checked .