Every brief begins with a request and ends with an approval, and nothing in between is optional. A Notion system that runs by hand or with an AI agent drafting the brief while you keep the approval.A vague brief is a meeting you're about to have. The writer reads it, fills the gaps with assumptions, and those assumptions come back as revision cycles. The cost shows up later, in the rework — but it was decided earlier, in the brief that left incomplete. The Content Brief is built so that doesn't happen: no brief leaves the system until every required field is accounted for.It's for solo operators, small content teams, and content strategists — anyone who hands work to a writer, including themselves, and wants the brief to be the most precise thing in the room. Every brief begins with a documented request, moves through a structured draft, passes a completeness check, and is approved before it reaches a writer. The Brief Body tells the writer everything they need and nothing they don't: context, key messages, required inclusions, and things to avoid.What changes is that the brief carries its own weight. The Completeness Checklist is binary — each item passes or fails, one fail returns the brief to draft. That removes the judgment call about whether a brief is "good enough." It either passes every item or it doesn't move. By the time a brief is approved, the writer's job is unambiguous.The system runs without AI. Connect Notion AI or an MCP agent and the drafting changes hands: the agent reads the audit finding, populates the brief fields, drafts the Brief Body, and runs the Completeness Checklist before you ever open the record. What doesn't change is the gate. The Approval field is governed — the agent never sets it. A brief the human hasn't read is not a brief.That's the difference. This isn't a brief template you fill in and hope is complete. It's a brief system with a binary completeness gate and a governed approval, so the thing that reaches your writer is finished — not a starting point for questions.What's included The Content Brief — a full Notion workspace, ready to duplicate Content Brief Database — one record per brief, with every required field, approval status, and cross-system reference keys; five prebuilt views (Ready for Approval, Approved, In Pipeline, From Audit, and a Board grouped by status) How This Works — how a brief moves through Request, Draft, Review, and Approved, with entry and exit conditions for each stage Completeness Checklist — the binary gate run before every approval, structured so a human or an agent can execute it item by item, with an interactive checker embedded in the page Field Guide — every database field defined: what goes in it, what valid input looks like, and what breaks if it's skipped Worked Example — one brief filled in completely, so you can see the standard before you meet it Running This With AI — how to connect Notion AI or an MCP agent, with a full field permission map marking what the agent drafts and what stays your call Who this is for Solo operators writing their own briefs and then writing the content Small content teams handing work between a briefer and a writer Content strategists who need every brief to meet the same bar Anyone tired of revision cycles that trace back to a thin brief Operators who want an agent to draft briefs from audit findings while they keep the approval What this solves Briefs that leave incomplete and come back as questions Revision cycles caused by assumptions the brief should have closed "Good enough" briefs that vary by who wrote them Work that reaches a writer before anyone confirmed it was ready AI that approves briefs instead of preparing them How it worksA brief moves through four stages, each with a defined entry and exit condition: Request. Every brief begins with a documented request — what was asked, by whom, and why. If it follows a Content Audit finding, the Finding ID goes in the Audit Reference field and stays there. Draft. Open a record and fill every required field. The Brief Body is the core deliverable. If you're running an agent, this is where it works — populating fields from the finding and drafting the body. You review the output. Review. Run the Completeness Checklist. Every item is binary. One fail returns the brief to Draft. The checklist is the gate, not a suggestion. Approved. The human reviewer sets Approval to Approved. The brief is complete and moves on. It doesn't change after approval — if the writer has questions, they come back to the reviewer, not the brief. Why it worksThe system makes "complete" a fact instead of a judgment. The Completeness Checklist is binary — twelve items, each pass or fail, no partial credit — so a brief either clears every gate or returns to draft. That structure is what lets an AI agent run the check programmatically and lets a human trust the result. The Approval field is governed and set only by a person, which means no brief reaches a writer without someone reading it. And the Brief Body is specified down to what it must cover — context, key messages, required inclusions, things to avoid — so the field the whole system exists to fill correctly gets filled correctly.Before and afterBefore: Briefs that vary in quality, leave with gaps, and generate questions the moment a writer opens them. Revision cycles that trace back to something the brief never said. No shared bar for what "ready" means.After: Every brief clears the same binary checklist before it's approved. The Brief Body answers the writer's questions before they're asked. Approval means a person read it and signed off. Briefs that come from an audit carry their Finding ID, so the work stays connected to the decision that started it.FAQDo I need AI to use this?No. The brief system runs fully by hand. AI changes who drafts and checks, not how the system works.What does the AI actually do?With Notion AI or an MCP agent connected, it reads the audit finding, populates the brief fields, drafts the Brief Body, and runs the Completeness Checklist — all before you open the record. You review and approve.Can the agent approve a brief?No. The Approval field is governed and set only by a human. An agent that sets Approval has bypassed the system, not used it. The point of the brief is to make the writer's job unambiguous, and a brief no one read can't do that.What's the Completeness Checklist?A binary, twelve-item gate run before every approval. Each item passes or fails. One fail returns the brief to Draft with a note on what failed. It's built so a human or an agent can run it the same way.What's the Audit Reference field?It's where the Finding ID from a Content Audit decision goes (format AUD-[id]). It connects the brief to the audit finding that originated it, so the work can be traced back. Required when a brief comes from an audit.Does this require the other two tools?No. The Content Brief is complete on its own. If you also run The Content Audit, briefs receive findings from it; if you run The Editorial Pipeline, approved briefs hand off to it with a Brief ID.What if a brief isn't from an audit?That's fine. The Audit Reference field is conditional — required only when a brief originates from a Content Audit finding. New briefs start from a documented request.Will it work in my existing Notion workspace?Yes. You duplicate it in and start creating brief records. 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 Content Brief. Fill one record completely, run the checklist, and hand a writer something finished.A brief sits between a decision and a published page. The Fully Inhabit Suite covers both sides — the audit that feeds it, the pipeline that ships it, all three tools on one thread.