Most content planning lives in a different tool from publishing. A Notion table, a Google Sheet, an Airtable. The handover is where it drifts. The sheet says one thing, the scheduler says another, and nobody trusts either by week three.
Workbench is the planning workspace inside EziBreezy. Folders and pages, planning tables with custom columns, research notes for sources and briefs, series sections for ordered launches. Link a row to a real draft and that row's status, scheduled date, posted date, and assignees read straight from the post.
A planning workspace has to hold four different shapes of work without making you pick. Loose notes for the brain dump. Research with sources and media. A row-and-column table when you want to scan twenty topics at once. An ordered sequence for a launch week. Workbench stacks all four on the same page in any order.
A planning row can link to a real draft. Once linked, Status, Date Scheduled, Date Posted, and Assignees read straight from the post, so the planning table stops drifting away from the schedule. Captions still live on the post.
Drag-and-drop tree
Nest pages inside folders for clients, campaigns, months, or recurring content plans. Each page has a title, description, and a stack of sections.
Stack any combination
Notepads, research, planning tables, and series builders sit on the same page in the order the work needs.
Six default columns
Topic, Linked content, Status, Date Scheduled, Date Posted, Assignees. Add custom columns: text, select, multi-select, checkbox, date, person, linked draft.
One-way, draft to row
Link a row to a draft and Status, dates, and assignees read live from the post. Editing the row doesn't push back, so the schedule stays the source of truth.
Real colours on status
To do gray, Doing amber, Done emerald, Archived slate. Each note carries body, URLs, media, priority, due date, owners, pillars, formats, and an activity log.
Ordered children
A series container holds title, theme, and goal. Drag child posts into the order they ship. Useful for launch weeks, tutorial runs, and carousel rollouts.
Top-level pages or pages nested inside folders for clients, campaigns, months, launches, or recurring content plans.
Each page has a title, description, and a stack of section blocks. Auto-saves while you work.
Notepads, research, planning tables, and series builders sit on the same page in any order. One section type or all four.
Freeform rich text for hook ideas, campaign notes, and post angles that aren't ready for the composer.
Per item: title, body, URLs, media gallery, priority, due date, assignees, pillars, formats, campaign, labels, workflow status, activity log.
To do gray, Doing amber, Done emerald, Archived slate. Reorder within the active or archived group.
Six default columns: Topic, Linked content, Status, Date Scheduled, Date Posted, Assignees.
Add text, select, multi-select, checkbox, date, person, or linked-draft columns. Select options carry custom colours.
Bind a row to an active top-level draft in the same workspace. The cell shows a draft summary chip you can open.
Linked rows mirror Status, Date Scheduled, Date Posted, and Assignees from the post. One-way: draft to row, never row to draft.
Sort by any column. Filter by status or assignee. Reset to the default planning order when the working view gets too cropped.
Series container with title, theme, and goal. Ordered child posts hold platforms, formats, captions, priority, due date, assignees, labels, and pillars.
Pillar chip, format chip, priority chip, tags, assignees, due date, caption fields, and full activity history per item.
Click any planning row to open a side drawer with the full property panel and a rich-text body field that doesn't fit in a cell.
The Workbench plans the work. Once a row links to a draft, the same post also lives where the next job happens: scheduling on the calendar, approval on the Board, caption work in the composer, feed layout in the grid planner, and the client sign-off batch in client reviews. Same post, different shape.
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 EziBreezy'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. Open the linked draft from the row to write the caption and any per-platform overrides. The reasoning: a cell is the wrong shape for platform-specific caption work. Use the composer for the caption itself, the table for the columns around it.
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. If the team wants to push the other direction, that's the workaround: 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 colours 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 colours 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.
Define pillars, formats, audience, and cadence before the planning table starts filling up.
Use the free monthly calendar builder when you need a simple content plan before moving into a live workspace.
Pillars, formats, labels, and hashtag groups: the workspace taxonomy the Workbench property panel reads from.
Open the real draft from a linked planning row, then write platform-specific captions and previews.
Send a planned batch for token-link approval after the planned rows are drafted. Clients do not need an account.
Let an agent create research notes, fill planning rows, or prepare drafts from the same workspace context.