The Brief-to-Draft Ratio That Separates Good Content Ops from Bad
Most content operations run on underwritten briefs and overwritten drafts. A Google Doc with the target keyword, a vague audience description, three bullet points of 'what to cover,' and an unrealistic deadline gets sent to a writer who produces a draft that mostly misses. An editor rewrites 40% of it. The client asks for revisions. Two weeks later a piece ships that nobody is proud of.
The fix isn't hiring better writers. It's writing better briefs. This piece covers the brief quality bar we hold at It's Not Techy across every client engagement, and why front-loading brief work is the single highest-leverage change most content teams can make.
The brief is the work — not the prelude to the work
A great brief makes the first draft 80% right on arrival. A bad brief forces writers to guess about audience, scope, and structure, which leads editors to rewrite, which leads clients to revise, which leads to drafts that drift further from the original intent with each round. The cumulative cost is massive: we've measured it across dozens of engagements, and a well-briefed piece costs roughly 40% of the total hours a poorly-briefed piece of equivalent quality consumes.
The mental reframe that helps: the brief is the work. It's where you decide who the reader is, what question you're answering, what sources you're pulling from, what the opening paragraph should accomplish, and what a successful outcome looks like. If those decisions aren't made in the brief, they get made reactively during drafting — badly, and with less context than the brief stage offers.
What a real content brief contains
Our brief template has eight required fields. One: the target reader in one sentence, specific enough to exclude people ('mid-market ecommerce marketing directors evaluating agency partnerships' not 'marketers'). Two: the one question the piece answers — articulated in the reader's voice, not ours. Three: the three proof points the piece must include — specific claims, data, or examples that give the piece credibility. Four: the format structure — headline working hypothesis, H2 outline, approximate word count per section.
Five: internal link targets, chosen from the site's existing content, with anchor text suggestions. Six: external link targets for credibility, usually 2–4 authoritative sources. Seven: the SME (subject-matter expert) to interview, with pre-written interview questions. Eight: the piece's success metric — what would tell us six months from now that this piece worked (organic traffic threshold, backlinks, sales-cycle references, etc.). Without all eight, we don't ship the brief to a writer.
The 20-minute SME interview that separates our content from everyone else's
Before any piece on a specialty topic, we interview a subject-matter expert for 20–45 minutes. The interview is the raw material. Without it, you're producing paraphrased summaries of other people's content — which is what 90% of the content on the internet already is, and which has no chance of earning AI citations or durable rankings.
The interview format we use: recorded on Riverside for quality, seven prepared questions, permission to follow threads. Questions aren't 'what is X' — they're 'what's the most common mistake you see teams make with X,' 'what did you used to believe about X that you've changed your mind on,' 'what's a specific case where the textbook answer was wrong.' These questions surface pattern-matching that's never been written down. That's the moat.
The transcript becomes the source document. The writer's job is to structure and tighten the SME's thinking, not to generate new claims. Every paragraph should pass a 'would the SME actually say this' test. If not, cut it or rewrite from the transcript.
The time budgets that reveal whether you're briefing well
Our standard time budget for a 1,500-word piece: 2 hours brief, 45 minutes SME interview, 4 hours draft, 1 hour edit, 30 minutes final review. Total: about 8 hours of skilled time. If your equivalent piece takes 15+ hours end to end, the leakage is almost always in drafting (too much guessing) and editing (too much rewriting) — both symptoms of a thin brief.
The diagnostic question: in your current workflow, how often does the first draft require structural rewriting (not just line edits)? If more than 30% of drafts do, your brief quality is the bottleneck, not your writer's skill. Most teams keep hiring better writers trying to solve a briefing problem. It doesn't work.
Key takeaways
- A thin brief costs more than it saves. Well-briefed pieces ship in 40% of the hours a poorly-briefed equivalent takes.
- Every brief needs eight components: reader, question, proof points, structure, links, SME, and success metric.
- Interview subject-matter experts before writing. The transcript is the moat — without it you're paraphrasing other people's content.
- If first drafts regularly need structural rewrites, the problem is briefing, not writing. Hiring better writers won't fix it.