Most content briefs specify the things a competent writer would have worked out anyway — the keyword, a word count, "friendly but professional" — and omit the things only the commissioner can decide. The draft then comes back reasonable and wrong, and the disagreement gets discovered at review, where fixing it is expensive.
A brief is not a requirements list. It is a set of decisions taken before writing starts, so the writer spends their effort on execution rather than on guessing what was wanted.
The template
Copy this. It fits on one page deliberately.
CONTENT BRIEF
1. TARGET QUERY
Primary query: [exactly one, as people type it]
Intent: [informational | commercial | transactional | navigational]
Confirmed by: [what the current results actually show]
2. THE ANGLE ← the load-bearing field
In one sentence, what does this say that nobody else is saying?
[If this sentence is hard to write, stop. The piece is not ready.]
3. WHO IT IS FOR
Reader: [role, and what they already know]
They arrive: [what triggered the search]
They leave able to: [the specific thing they can now do]
4. DELIBERATE EXCLUSIONS ← prevents more rework than inclusions
Not covering: [topics adjacent but out of scope]
Because: [where those belong instead]
5. STRUCTURE
Type: [guide | comparison | checklist | template | insight]
Snippet target: [the question, and a one-paragraph answer]
Required sections: [only those that must exist]
Required format: [table | framework | steps — the extractable element]
6. CONNECTION
Supports: [the ONE commercial page this earns authority for]
Must link to: [specific internal URLs, in context]
Will receive links from: [where inbound links come from]
7. EVIDENCE
Must cite: [sources, data, or first-hand experience]
Must NOT claim: [anything unverifiable — no invented statistics]
8. FAILURE CONDITIONS
This piece has failed if:
- [specific, checkable outcome]
- [specific, checkable outcome]
9. PRACTICALS
Length: [a floor for usefulness, not a target]
Deadline:
Reviewer:
Why these fields and not others
Field 2 does most of the work. If the angle sentence will not come out cleanly, the piece has no argument — and no amount of research during drafting will supply one. Writing that sentence takes two minutes and prevents a fortnight of producing something that reads like everything already ranking.
Field 4 prevents more rework than any inclusion list. Writers expand into adjacent territory because it feels helpful. Naming the boundary, and where the excluded material actually belongs, is what keeps a page serving one intent.
Field 6 answers why the piece exists commercially. A resource that supports no money page can still be good and still be a poor use of the next two weeks. Naming the target page and the required links up front means the link graph is designed rather than discovered.
Field 8 makes review objective. "Make it better" is not actionable. "A practitioner reads this and learns nothing they did not know" is checkable, and both parties can agree in advance on what would constitute failure.
Deciding which pieces to commission at all — the query, the intent, and which commercial page each supports — happens before any of this, and is
the content strategy work that produces the brief.A filled example
The brief that produced the technical SEO checklist for Next.js sites on this site.
CONTENT BRIEF
1. TARGET QUERY
Primary query: next.js technical seo checklist
Intent: Informational — practitioner looking for specifics,
not a definition of technical SEO
Confirmed by: Current results are framework-agnostic checklists.
None address Next.js-specific failure modes.
2. THE ANGLE
The expensive Next.js SEO failures are silent: a config flag disables
redirects with no warning, page metadata wipes inherited Open Graph
tags, a trailing-slash mismatch turns every canonical into a redirect.
None of them produce an error.
3. WHO IT IS FOR
Reader: Developer or technical SEO on a Next.js site
They arrive: Rankings underperform and the cause is unclear
They leave able to: Run eight specific checks and find the fault
4. DELIBERATE EXCLUSIONS
Not covering: Keyword research, content strategy, link building,
general (non-Next.js) technical SEO
Because: The angle is framework specificity. Generic advice is
the thing this piece exists to not be.
5. STRUCTURE
Type: Checklist
Snippet target: "What is different about technical SEO on a Next.js
site?" — answered in one self-contained paragraph
Required: Ordered items, each with how to verify
Required format: A table of what `output: 'export'` silently disables
6. CONNECTION
Supports: /services/seo/technical-seo/
Must link to: /services/seo/technical-seo/ in context, not a footer
Inbound from: SEO pillar page, siblings in the cluster
7. EVIDENCE
Must cite: Only failures observed first-hand on production sites
Must NOT claim: No invented percentages, no "studies show", no
fabricated before/after numbers
8. FAILURE CONDITIONS
Failed if:
- A senior Next.js developer reads it and learns nothing
- Any item is true of every framework rather than this one
- It reads as a sales page for technical SEO services
9. PRACTICALS
Length: Whatever covers eight checks properly. No target.
Reviewer: [named]
Note field 8: two of the three failure conditions are about the piece being too generic, because that was the specific risk for that topic. Failure conditions should be written against the way this piece is most likely to go wrong, not copied between briefs.
How to use it in practice
Fill it in order. Fields 1 and 2 gate everything else — if the angle will not come, do not proceed to field 3 hoping it appears later.
Twenty minutes, maximum. A brief taking an hour has started drafting the article.
Give the writer the reasoning, not just the conclusions. A writer who understands why an exclusion exists will handle the edge cases you did not anticipate. One who receives it as a rule will follow it off a cliff.
Keep it with the draft. At review, the brief is what "done" is measured against. Reviewing against remembered intent is how scope quietly changes and nobody notices until publication.
Using this in practice?
The template is yours. If you want it applied across a real site, we can do that with you.