Teams treat briefs like admin. Something to fill in after the keyword is picked. That is backwards. The brief is where you decide whether the piece should exist, who it is for, and what it must accomplish. A writer working from a one-line Slack message will guess on all three. Some guesses will be wrong. You will pay for those guesses in revision rounds.
The job of a brief is to remove ambiguity
Ambiguity is expensive. When a brief says write about project management software without naming the reader, the writer defaults to a generic overview. When it says target finance directors evaluating tools for a 200-person team, the piece gets specific examples, tighter vocabulary, and a structure that matches how that buyer reads.
A brief should answer questions a writer will ask in the first hour of work. Who is this for? What do they already believe? What should they do or understand after reading? What must we not say? What proof do we have? If those answers live in someone's head, they are not in the brief, and the draft will reflect that gap.
Start with intent, not the keyword
Keywords belong in briefs, but they should not lead them. Start with search intent: what the searcher wants to accomplish, and what format the SERP rewards. A query that ranks list posts should not get a 2,000-word essay because someone prefers long form. Read the SERP before you brief. We wrote a full walkthrough on reading a SERP for intent; the brief should capture your conclusion from that exercise.
Include the primary keyword, secondary terms that appear in ranking pages, and the page type you are producing: guide, comparison, how-to, glossary, or opinion. Note cannibalization risk if another URL on your site already targets the same intent. The brief is the right place to say publish on this URL or create a new one.
Angle is the difference between useful and redundant
Ranking pages overlap. If your brief only says cover the topic, the draft will repeat what already ranks. The brief needs a stated angle: the specific lens, audience, or gap you are filling. Examples: compliance risks for mid-market HR teams, not project management in general; implementation timelines for teams migrating off a named incumbent, not a feature tour.
Angle also sets boundaries. A brief for SEO content writing should say what the piece will not try to be: not a product page, not a sales deck, not a glossary of every term in the category. Boundaries keep writers from padding and keep editors from rejecting whole sections.
What to include in every brief
| Section | What it contains | Why it matters |
|---|---|---|
| Audience | Role, context, knowledge level, objections | Sets vocabulary, examples, and depth |
| Intent and goal | SERP read, primary keyword, desired action | Prevents format mismatches |
| Angle | Specific lens and explicit exclusions | Avoids redundant drafts |
| Outline | H2s with one-line purpose each | Aligns structure before writing |
| Sources | Approved links, SMEs, internal data | Reduces unsupported claims |
| Voice rules | Tone, terms to use or avoid, reading level | Keeps brand consistency |
| Acceptance criteria | Word range, links, meta, fact-check notes | Defines done clearly |
Not every brief needs a novel-length background doc. A tight brief with those sections beats a ten-page brand deck that never mentions the outline. For recurring programmes, maintain a voice guide and link to it rather than pasting the same paragraphs every time.
Sources and claims need explicit rules
Writers fill gaps. If the brief does not list approved sources, they will search and cite whatever ranks, including competitors and outdated stats. Specify what may be linked, what requires internal approval, and which claims are off limits. If you have SME input, say so and attach notes or interview transcripts.
- Name primary and secondary sources the writer should use.
- Flag statistics that need a dated citation or legal review.
- List competitor pages that may be referenced but not copied.
- Note product claims that require documentation from product marketing.
For technical topics, point the writer to an internal expert or schedule an interview. Our guide on interviewing subject matter experts covers how to turn a 30-minute call into brief-ready material.
Acceptance criteria prevent endless revision
Done is a defined state. Acceptance criteria belong in the brief: target word range, number of internal links, meta title and description requirements, image needs, and revision round limits. When criteria are vague, every stakeholder treats the draft as a brainstorming doc.
Include internal link targets where you already know them. Suggest anchor text only when it matters for navigation or SEO; otherwise let the writer choose natural phrasing. If the piece supports a programme, note where it sits in the calendar and what older posts it should link to or update.
What a brief should not do
A brief is not a draft. Long pasted paragraphs from ChatGPT do not replace an outline; they constrain the writer to bad prose. A brief is not a substitute for voice documentation. Repeating we are friendly every time wastes space unless friendly is defined with examples.
Avoid briefing by committee without a decider. Ten comments on a shared doc before the outline is approved guarantees conflicting direction. One owner approves the brief. Others comment once. Then the brief is locked and the writer starts. Changes after lock are scope changes, not free revisions.
If you hand off to an external writer, pair the brief with context on how to brief a writer who does not know your product. The document does the heavy lifting; the handoff call confirms assumptions.
Review the brief like an editor, not a approver
Before a writer starts, an editor or strategist should read the brief cold and ask whether a stranger could draft from it. If you need ten Slack messages to explain the angle, the brief is incomplete. Fix it there, not in draft one.
Strong programmes store briefs in a shared library with tags for cluster, intent, and outcome. When a URL refreshes six months later, the old brief is the baseline for what changed in the SERP. That history beats searching email for the original keyword note.