Brief to draft content assembly with human approval (L2)

AI drafts, humans approve. The brief, the source material, and the draft live in one place so the writer edits rather than starts from blank. Notion or Google Docs plus Claude or ChatGPT is enough.

WORKFLOW1Standardize the briefNotion2Ground the draft in your …wn materialClaude3Two-pass human editGoogle Docs4Measure edit distance, no… volumeManual
4 steps, in order, with the tool that owns each one.
Adoption ladderSix levels from Starter to Rebuilt. This item sits at level 2.L1 StarterOne tool, no workflow changeL2 AssistedAI drafts, humans approveL3 IntegratedWired into CRM and SlackL4 OrchestratedMulti-step, owned, measuredL5 AutonomousAgent runs, human auditsL6 RebuiltThe process itself changes
This playbook belongs at L2 Assisted. Running it above your level is how pilots stall.
Measures of successTime from brief to publish; Share of draft surviving edit; Organic sessions per published piecePROVE IT WORKEDTime from brief to publishShare of draft surviving editOrganic sessions per published piece

The steps

  1. 01

    Standardize the brief

    Tool: Notion

    One template: audience, buyer question the piece must answer, three required sources, the claim you will not make, and the call to action. Owner: content lead. Pitfall: briefs that only list a keyword. The draft comes back generic every time. DoD: every content task uses the template and no draft starts without one.

  2. 02

    Ground the draft in your own material

    Tool: Claude

    Paste customer interview notes, call transcripts, and product docs into the prompt. Ban outside claims unless the source is named in the brief. Owner: writer. Pitfall: letting the model supply statistics. Unsourced numbers are the fastest route to a correction. DoD: every factual claim in the draft maps to a source listed in the brief.

  3. 03

    Two-pass human edit

    Tool: Google Docs

    First pass for accuracy, second for voice. Track changes stay on so you can see how much rewriting the draft needed. Owner: editor. DoD: the doc shows a named editor and resolved comments before publish.

  4. 04

    Measure edit distance, not volume

    Tool: Manual

    Log roughly how much of each draft survived. Rising survival means the prompt and source pack are improving. Falling survival means the workflow is costing time, not saving it. Owner: content lead. DoD: a monthly number exists and is reviewed.

Tools in this playbook

Next playbooks

Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.

Share this playbook

Posting to Instagram or TikTok? Copy the link, it carries the title, summary and share image.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.