Most content plans live in a different tool from publishing, and the handover is where they drift: the sheet says one thing, the scheduler says another, and by week three nobody trusts either. The Workbench is the planning workspace inside Maeve, so a planning row can link to a real draft, and its status, dates, and assignees read straight from the post. The plan cannot drift away from the schedule.
3 days free. Cancel anytime.
The planning table starts with Topic, Linked content, Status, Date Scheduled, Date Posted, and Assignees, and you can add your own text, select, checkbox, date, and person columns. Link a row to a draft and its status, dates, and assignees mirror the live post. The mirror runs one way, draft to row, so the schedule stays the source of truth. Captions stay on the post, one click away in the composer.
Research notes hold the links, media, and briefs behind the posts, each with a priority, a due date, owners, and a status that reads at a glance: To do, Doing, Done, Archived. The source material sits on the same page as the plan it feeds, instead of in a doc nobody can find later.
A series holds work that has to go out in order, a launch week or a tutorial run, built as ordered child posts that each carry their own platforms, formats, captions, and status. Drag them into the sequence they should ship. Notepads sit alongside for the looser thinking: hook ideas, campaign notes, and angles that are not ready for the composer yet.
Pages stack any combination of the four section types in any order, and everything auto-saves while you work. Nest pages inside folders for clients, campaigns, and months, write together in real time, and lock private pages to the people who need them. Every item keeps an activity log, so there is a paper trail when someone asks what happened.
Once a row links to a draft, that post also lives where the next job happens. Switching surfaces does not duplicate the post; it shows the same draft in the shape that fits the job.
For planning before the workspace: free, open to everyone, no account needed.
A social media content planner is the workspace where ideas, briefs, research, and campaign notes live before they reach the publishing calendar. It usually holds owners, due dates, status, and rough dates. Workbench is Maeve's version, kept in the same workspace as the drafts so the plan and the schedule don't disagree.
The Workbench is a planning workspace built from four section types: notepads for raw thinking, research notes for sources and media, planning tables for spreadsheet-style rows, and series builders for ordered launches. A page can stack any combination. Planning rows can link to a real draft and mirror its live status, dates, and assignees.
Notion and Google Sheets are fine for planning, but they don't publish. The handover is where things drift: the sheet says one thing, the scheduler says another. In Workbench, a planning row can bind to a real draft, so its Status, Date Scheduled, Date Posted, and Assignees read from the post itself.
It's the spreadsheet shape inside the workspace. Default columns are Topic, Linked content, Status, Date Scheduled, Date Posted, and Assignees. You can add custom text, select, multi-select, checkbox, date, person, and linked-draft columns. Sort, filter, and the linked rows keep mirroring the live posts.
Captions live on the post, not in the table. A table cell is the wrong shape for per-platform caption work, so the composer handles the caption and the table handles the columns around it. Open the linked draft from the row to write the caption and any per-platform overrides.
Use the row's Linked content column to bind it to an active top-level draft from the same workspace. Once linked, the row reads the draft's workflow status, scheduled date, posted date, and assignees. Create the draft in the composer first, then link it from the table.
Not yet. Mirror runs draft to row only. The schedule is the source of truth, so the calendar and Board are where status moves through Idea, In Progress, Review, Approved, Scheduled, and Published. The planning row reflects whatever the draft says; to change status, open the draft from the row.
A series is for ideas that need to ship in order: a launch week, a tutorial run, a carousel rollout, a recurring weekly slot. The container holds a title, theme, and goal. Inside, child posts carry platforms, formats, captions, priority, due date, assignees, labels, and pillars. Drag children into the order they should ship.
Research notes live in their own section and don't pretend to be posts. Each note can carry body text, URLs, a media gallery, priority, due date, assignees, pillars, formats, a campaign, labels, and an activity log. Status colors read To do gray, Doing amber, Done emerald, Archived slate, so a stuck note surfaces at a glance.
Add a select column for any of those. Select options carry custom colors so the table reads at a glance. Custom columns are row-only metadata used for sort and filter; the post itself reads pillars and formats from the workspace taxonomy when you open the draft.
Both. A solo creator runs the planning table as a personal content queue and skips the assignees and approval status columns. A team adds owners, due dates, and the Review/Approved status values, and the activity log gives each item a paper trail.
Workbench is the planning surface. Once a row links to a draft, that post also lives on the calendar (date-first), the Board (workflow-first), and the composer (caption-first). Switching surfaces doesn't duplicate the post; it shows the same draft in the shape that fits the job.
Not yet. Each series is built from scratch, and there's no clone-from-template or recurring series. The workaround for repeating formats is to keep a series container around as a planning shell and copy its child posts into a fresh draft when each round comes up.