Your content calendar, true again every Monday morning
Every Monday at eight, every planned piece checked against the live blog, channel and newsletter archive, with statuses, URLs and actual dates updated and nothing else touched.
Content calendars rot in one direction. The plan gets updated at planning time and reality gets updated never. Three weeks in, five pieces read "scheduled": two shipped, one shipped under a different title, one slipped, one was abandoned without a word.
A companion checks every row against the published surfaces themselves and records the difference. It is allowed to edit exactly three fields. That scoping is what makes it safe to run against the calendar your whole team works from, and Notion is a native integration in Strawberry.
What is the exact prompt?
"Every Monday at 8am, reconcile the content calendar in [Notion database / sheet] against reality. Reality means: the blog's actual index page, the YouTube channel's uploads, the newsletter archive in [tool], and our social profiles in my session. For each calendar item dated in the last 30 days, mark it: Published (set status, paste the live URL, record the actual publish date; Retitled) same, but note the title change; Slipped (flag it and, if a new date is discoverable from drafts or the CMS, record it as 'proposed', not as the plan; Ghost) no trace anywhere, flag for the meeting. Then the reverse pass: anything published in the last 30 days that never appeared on the calendar, append at the bottom tagged 'untracked'. You may edit exactly three fields: status, URL, actual-date. Titles, owners, briefs and future rows are read-only. Post a five-line summary of what changed to [channel]."
The reverse pass finds the interesting problems. Untracked publishing is how brand voice drifts and how two teams ship the same post in one week.
Why only three editable fields?
The calendar is a shared workspace.
Scoping writes to status, URL and actual-date makes the worst possible failure a wrong status: visible, reversible, cheap. The "proposed, not the plan" rule for slipped dates keeps rescheduling a human conversation.
This is the general pattern for letting a companion write into team tools. Narrow the writable surface until a failure cannot hurt, then widen it once earned. You can see exactly which properties changed, and Ask Always mode in Settings → AI permissions puts a card in front of every write while trust builds.
What the Monday meeting looks like a month in
The archaeology is gone.
The board is true when the meeting starts, so the meeting is about the flags: two slips with proposed dates to accept or argue, one ghost that needs an owner, one untracked post that starts a conversation. Those are the actual content-ops decisions.
The summary line builds a second asset. A month of "3 published, 1 slipped" summaries is a velocity record nobody had to maintain. Teams pair this with the content repurposing playbook, where a Published mark triggers the derivative formats, and keep the system in the Notion integration.
Check the matches for the first two weeks
Retitled pieces are the hard case.
The calendar says "Q3 pricing deep-dive", the blog says "What our pricing actually costs you". Glance at every Retitled call for the first few weeks, because a wrong URL on a calendar row propagates into every report built on it.
Ghost calls deserve one manual check each: search the CMS drafts before declaring a piece untraceable, since "ghost" sometimes means "sitting in review with a different slug". After two clean weeks the spot-checks can stop, which is why this makes a good first routine for a marketing team new to agents.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents