Every asset tracked by status, owner, and date from brief receipt to post-publish review. Most editorial calendars record what you hoped would happen. This one shows what's happening, who has it, and what breaks if it slips.An editorial calendar tells you what you planned. It rarely tells you the truth. Dates pass, owners change, drafts sit in review, and the calendar keeps showing the version of the schedule everyone agreed to weeks ago. The Editorial Pipeline is built to show the live state instead — where each asset actually is, who actually has it, and what breaks if it slips.It's for solo operators, small content teams, and content strategists running real production — anyone who needs to move work from brief to published without losing track of it. Every asset is a record with a status, an owner, and a date. Status isn't a label; it's a commitment about where the work is. Each status has an entry condition that must be true before you set it, so the pipeline can't quietly tell everyone downstream something that isn't so.What changes is that slips become visible before the due date, not after. The Slip Protocol defines three specific slip conditions — due date passed, no owner, stuck in review — each with a governed response. A slip stops being a vague feeling that something's behind and becomes a named condition you can act on. Nothing falls off the edge of the schedule unnoticed.The pipeline runs without AI. Connect Notion AI or an MCP agent and it manages the operational layer: tracking status across every active asset, surfacing slipped items, running the Pre-Publish Checklist, and flagging assets approaching their review date. What stays with you are the commitments. Approved for Publish, Published, and Cancelled represent promises to people outside the system — the agent surfaces and recommends, but a human sets them. An agent that advances these has made a commitment on your behalf, and that's not what the system is for.That's the difference. This isn't a calendar that records intentions. It's a live operation with governed status gates and a defined slip protocol — so what you're looking at is what's actually happening, not what you hoped would.What's included The Editorial Pipeline — a full Notion workspace, ready to duplicate Editorial Pipeline database — one row per asset, tracked by status, owner, and date, with cross-system reference keys; eight prebuilt views (Active, In Review, Approved for Publish, Slipped, Post-Publish, Full Pipeline, a Board grouped by status, and a Calendar by due date) How This Works — the eight stages from Brief Received to Archived, each with entry and exit conditions Status Guide — every status defined: what it means, what triggers it, and what must be true before you set it Slip Protocol — three slip conditions and their governed responses, structured so a human or an agent can run it Pre-Publish Checklist — the binary gate before every move to Approved for Publish, run against the brief, with an interactive checker embedded in the page Field Guide — every database field defined: what it captures, valid input, and what breaks downstream if it's skipped Worked Example — one asset tracked the full length of the pipeline, so you can see it run before you run it Running This With AI — how to connect Notion AI or an MCP agent, with a full field permission map marking governed statuses Who this is for Solo operators moving their own content from draft to published Small content teams that need one honest view of who has what Content strategists managing a production schedule they have to report on Anyone whose editorial calendar shows the plan instead of the truth Operators who want an agent watching for slips so they don't have to ask What this solves Calendars that show the plan, not the live state Slips no one catches until the due date has already passed Statuses that lie to everyone downstream Published work that ages with no review and quietly becomes the next problem AI that commits to publish dates on your behalf How it worksAn asset moves through eight stages, each with a defined status and conditions: Brief Received. An approved brief arrives. You create a record, link the brief, copy in the Brief ID, and set the status. In Progress. The writer has the brief and is producing the content. This is the longest status in most pipelines. In Review. A complete draft is with the reviewer. The Pre-Publish Checklist must run before the asset can advance. Revision Required. The review found issues. The draft returns to the writer with specific direction — used for substantive revisions, not minor edits. Approved for Publish. The checklist passed and a human confirmed the asset is ready. A governed status. The agent must not set it. Published. The content is live. The human sets the status, records the Publish Date, and sets the Review Date (default 30 days out). Post-Publish Review. The review date arrives and the asset is re-evaluated against its goal. This is the loop back to the audit — an underperforming asset becomes a new finding. Archived. The asset is retired or superseded. Records aren't deleted; they're archived for the trail. Running alongside: the Slip Protocol catches assets that stall, and the Pre-Publish Checklist gates every move to Approved for Publish.Why it worksThe system treats status as a fact about the work, not a label on it. Every status has an entry condition that must be true before it's set, so a status change is a verifiable claim rather than an optimistic one — which is exactly what lets an agent evaluate whether a transition is valid. The Slip Protocol turns "something's behind" into three named conditions with defined responses, so slips get caught early and handled the same way every time. The governed statuses draw the line at commitments: anything that represents a promise to someone outside the system requires a human to set it. And the Review Date is the mechanism that closes the loop — published work doesn't age unwatched; it comes back for review.Before and afterBefore: An editorial calendar that shows the agreed plan, not the live state. Slips discovered after the due date. Statuses that don't match reality. Published content that ages with no review until it becomes the thing an audit has to flag.After: One database showing where every asset actually is, who has it, and what's due. Slips surfaced as named conditions before they pass their date. Governed status gates that hold the line on real commitments. A 30-day review on every published asset, so the loop closes instead of leaking.FAQDo I need AI to use this?No. The pipeline runs fully by hand. AI manages the operational layer — tracking, surfacing, checking — but every governed decision stays with you.What does the AI actually do?With an MCP agent connected, it reports pipeline state across all active assets, surfaces slipped items per the Slip Protocol, runs the Pre-Publish Checklist, flags assets within 14 days of their review date, and updates non-governed statuses after confirmed events.Which statuses can't the agent set?Approved for Publish, Published, and Cancelled — plus confirming a Slip. These represent commitments to people outside the system. The agent surfaces and recommends; a human sets them.What's the Slip Protocol?Three defined slip conditions — due date passed, no owner, stuck in review — each with a governed response. It's how a slip becomes a named, actionable condition instead of a vague sense that something's behind.What's the Pre-Publish Checklist?A binary gate run against the brief before any move to Approved for Publish. Each item passes or fails; one fail returns the asset to In Review. It checks the content against the brief, not against a general standard.How does the loop back to the audit work?Every published asset gets a Review Date (default 30 days out). At review, the asset is re-evaluated against its goal. One that's underperforming becomes a new audit finding, carrying its Pipeline ID and Audit Reference back with it.Does this require the other two tools?No. The Editorial Pipeline is complete on its own. If you also run The Content Brief, assets arrive with a Brief ID; if you run The Content Audit, the review loop feeds new findings back to it.Will it work in my existing Notion workspace?Yes. You duplicate it in and start adding assets. It's self-contained.Do I need a paid Notion plan?No. You duplicate the template into your own workspace and it runs on any plan, free included.Get The Editorial Pipeline. Add your first asset, set its status, and start seeing what's actually happening.The pipeline runs what the other two jobs decide and spec. The Fully Inhabit Suite has all three — audit, brief, and pipeline, on one thread from finding to published and back.