A status is a commitment, not a label.
An editorial calendar tells you what you planned. It rarely tells you the truth. The Editorial Pipeline shows the live state instead — where each asset actually is, who has it, and what breaks if it slips. Run it yourself, or with an AI watching the board while the commitments stay yours.
The workspace: one row per asset, eight status gates, and a protocol for when things stall.
Eight stages. Each one has to be earned.
Every status has an entry condition that must be true before you set it — a gate, not a label. Walk one asset through the pipeline:
In the product, every stage's full entry and exit conditions live in the Status Guide — and an agent evaluates them before recommending a move.
A slip is not a failure. An unidentified slip is.
Three named conditions, each with a governed response — caught before the due date passes, not after.
Due date passed
The date passed and the asset hasn't reached Approved for Publish. Extend with a reason, reassign, or cancel — and record the decision.
No owner
An active asset with no confirmed owner. Reassign, confirm the due date, and record it.
Stuck in review
In Review longer than the review window without advancing. Decide if the review is still live, reassign, or set a new target.
The agent watches the board. You make the commitments.
Approved for Publish, Published, and Cancelled are promises to people outside the system. The agent surfaces and recommends; a human sets them. That line is written into the fields, not left to discipline.
The agent may
- Report pipeline state across all active assets
- Surface slipped assets per the Slip Protocol
- Run the Pre-Publish Checklist and report results
- Flag assets within 14 days of their review date
- Update non-governed statuses after confirmed events
You confirm — always
- Approved for Publish — you run the checklist and set it. Never the agent.
- Published — you set the status and the publish date.
- Cancelled — you set it, with the reason recorded.
- Slipped — the agent surfaces; you confirm and respond.
A live operation, not a calendar.
Editorial Pipeline database
One row per asset, tracked by status, owner, and date. Eight prebuilt views, including a Board and a Calendar.
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 runs it the same way.
Pre-Publish Checklist
The binary gate before Approved for Publish, run against the brief — interactive checker embedded.
Worked Example
One asset tracked the full length of the pipeline, so you can see it run before you run it.
Field Guide + Running This With AI
Every field defined, plus the full permission map marking the governed statuses.
What changes.
Before
A 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. A 30-day review on every published asset, so the loop closes instead of leaking.
Fair questions.
Do 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.
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 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, 30 days out by default. At review, the asset is re-evaluated against its goal. One that's underperforming becomes a new audit finding, carrying its IDs back with it.
Do I need a paid Notion plan?
No. You duplicate the template into your own workspace and it runs on any plan, free included. It's yours to keep.
What does one purchase cover?
You and your own team, in your own workspace — duplicate it once, keep it for good. Deploying these systems for clients as an agency, consultant, or freelancer needs the Agency License ($179, unlimited client workspaces), sold separately in the Fully Inhabit shop.
See what's actually happening.
Add your first asset, set its status honestly, and stop discovering slips after the deadline. The pipeline runs what the other two jobs decide and spec — The Fully Inhabit Suite has all three on one thread.