Content Brief Template That Writers Actually Follow

The content brief is where article quality is actually decided — before a word gets drafted — and most briefs fail their one job: writers don't follow them, because they're either keyword-dump spreadsheets nobody can write from or ten-page documents nobody reads. The brief that works fits on one page, answers the questions writers actually have, and makes the wrong article impossible to write. Here's that template, field by field, with the process that keeps briefs honest.

The template (one page, nine fields)

1. The assignment sentence: "Write [format] for [reader] searching [primary query], so they can [outcome]." One line that makes drift visible — every later disagreement resolves against it.
2. Keyword-group: primary plus the variants and subquestions from the map — presented as topics to cover, not densities to hit (the brief's framing here decides whether you get coverage or stuffing).
3. The SERP verdict, pre-read: intent and format per the 30-second read, done by the briefer — "the SERP rewards listicles with pros/cons" is a brief line; making writers deduce it is how format misses happen.
4. The angle: what this piece does that positions 1–3 don't — the field most templates omit and the process calls non-negotiable: "same but by us" briefs produce "same but later" articles.
5. Coverage skeleton: the must-include H2s (from SERP gaps and outline research) — a skeleton, explicitly not the finished outline: writers own the structure inside the coverage floor, which is the autonomy that makes briefs followable.
6. Evidence and sources: the data points, internal research assets and approved sources to draw on — plus the quote sourcing where planned.
7. Internal links, both directions: the money page this routes to and the siblings to reference — the architecture as a brief field, because links briefed get placed and links assumed don't.
8. Specs in one line: length range (a range — the completeness rule, not a quota), tone reference, deadline, and the template if one applies.
9. The don'ts, kept short: the three to five known failure modes for this topic (claims we can't make, competitors we don't name, the standards most violated) — a short list gets read; the policy manual gets linked.

The process around the template

Brief time is research time: the twenty minutes of SERP-and-map work per brief (the brief-tool class compresses it usefully — with the tool's output as input, the judgment fields still human); the writer reads it back: a two-line "here's my planned angle and structure" reply before drafting — the cheapest revision-prevention step in content operations; and the brief is the review standard: edits per the checklist cite brief fields, not fresh opinions — which is what trains writers that briefs are contracts, and briefers that fields left vague get filled by someone else's guess.

Frequently asked questions

How long should writing a brief take?

Thirty to forty-five minutes with the research included — against the hours it saves in revisions and the misses it prevents. Briefs taking five minutes are keyword dumps; briefs taking three hours are the briefer writing the article resentfully.

Do experienced writers still need briefs?

They need different briefs — the assignment sentence, angle, links and evidence still transfer knowledge the writer can't deduce (your map, your assets, your architecture); the coverage skeleton lightens as trust grows. The brief shrinks with seniority; it never disappears, per the team operations reality.

What's the most commonly missing field in failed briefs?

The angle — its absence produces competent redundancy, the content graveyard's largest section — with internal links second (the routing that never got briefed never got built). Both cost one line to include, which is the whole template's argument: one page, every decision that matters, made once — and the article then competes on the pair no brief supplies: execution and authority (briefed and delivered, us).