Introduction
A page matched the keyword, missed the SERP intent, and never ranked. The writer did nothing wrong. The brief failed.
A content brief is where a page wins or loses, and it's written before the draft starts. This is the operating manual for building briefs that decide whether a page ranks before a single paragraph exists. A field-tested system, not another template dump.
Key Takeaways
- A content brief is a spec sheet, not a form. Under-specify it and you pay in revisions; over-specify it and you get on-brief copy that ranks for nothing.
- A 2026 brief has two readers: Google's ranking systems and the AI engines that decide what to cite. They reward different things, and the brief must name both.
- The five fields that do most of the work are the single job, the SERP teardown, the question cluster, the proof and sources, and the definition of done. Most templates skip the first and the last.
- Briefs fail in predictable ways: underspecified intent, SERP mismatch, stale competitor picks, and E-E-A-T treated as a footer problem. Each failure has a specific fix.
- The brief is where you scale. A repeatable brief system is what lets one strategist run content across multiple writers and clients without becoming the bottleneck.
The client's page matched the keyword perfectly and sat on page four for six months; I switched from handing writers a keyword list to writing the brief as the contract between strategy and execution, lost the speed of a one-line brief, and gained pages that actually ranked. That switch is why I now treat the brief as the control system, not the paperwork.
A 2026 brief has two readers. Google's ranking systems reward a page that answers the query better than the pages already ranking. The AI engines that decide what to cite reward something else: extractable passages, clear claims, named sources. Name both readers in the brief, or the page gets written for neither.
Five fields do most of the work. The single job states what the reader can do after reading. The SERP teardown reads the top pages through content type, format, and angle. The question cluster lists the follow-up questions the page must answer.
Then the proof and sources field names the evidence the page will cite, and the definition of done is the editor checklist before the page ships. Most templates skip the first and the last. That is exactly where pages fail.
Before the fields, the definition. A content brief is the contract between strategy and execution. The next section separates it from the documents people confuse it with.
What a Content Brief Actually Is (and What It Is Not)
That promise only holds if the tool is defined tightly enough to use. A content brief is the contract between strategy and execution. It tells a writer what to win, who already won, and what done looks like before a single paragraph ships.
Most briefs I see are keyword lists wearing a title. Last spring a client sent over a three-page document with a primary keyword, five related terms, and a list of competitor URLs. Every field was filled. The writer still had to guess the audience, guess the angle, guess what done meant. The draft came back generic, the editor rewrote the scope twice, and the page shipped two weeks late. The document had the shape of a brief and none of its function: it killed zero guesswork. A real brief names the page's single job, the audience, and the definition of done before drafting starts. That is the whole difference.
The brief is the smallest viable spec for a page. It is not a research dump or a style guide; every field exists to kill a specific kind of guesswork. A field that removes no guess the writer would otherwise make does not belong in the brief.
In 2026, one brief governs human writers and AI generation runs from the same document. It pairs search intent with answer intent, and it carries an entity map, a heading skeleton, mandated proof sources, and E-E-A-T quality gates.
Brief vs Outline
These two documents solve different problems, and they do not have to live in separate files. The brief gives context and requirements. The outline organizes the page itself. A heading on its own is a guess dressed up as structure. The brief supplies the intent notes that make the outline load-bearing, so the content brief versus an outline split is really a split of responsibility, not of files.
Brief vs Strategy
The brief sits inside a larger content stack. Strategy decides what to create and why, across a portfolio. The brief specs one page, one query, one job. A common failure is writing briefs with no strategy behind them, which produces pages that are individually competent and collectively pointless. The strategy versus a brief question comes down to sequence: strategy first, brief second.
Brief vs Creative Brief vs SEO Brief
Terminology blurs here, and the blur costs real time. A creative brief specs a campaign or brand asset. An SEO brief is a content brief with ranking requirements added: keywords, SERP context, internal links, schema. A content brief is the broader document; an SEO brief is the version built for search. Some teams use the terms interchangeably. The distinction still matters, because the ranking requirements change what the writer needs on day one.
| Document | Primary purpose | Typical owner | Key outputs |
|---|---|---|---|
| Content brief | Define the page's single job, audience, and definition of done | Content strategist or content ops lead | Single job statement, audience notes, definition of done, proof requirements |
| SEO brief | Add ranking requirements to the content brief | SEO strategist | Keyword targets, SERP teardown, internal link map, schema notes |
| Creative brief | Spec a campaign or brand asset | Brand or campaign manager | Campaign message, audience insight, tone direction, asset specs |
| Content outline | Organize the page itself into a heading structure | Writer or editor | Heading skeleton, section flow, content placement |
A brief that meets this definition should be hard to get wrong. The next section shows why it is not.
Why Most Content Briefs Fail
The definition is set. Now the failure modes, because a brief that ships a keyword and three links leaves every hard decision to the writer, and the writer guesses wrong.
Most briefs specify the keyword but never the reader's intent. The writer sees "best standing desk" and produces a generic overview of standing desks. The query wanted a comparison of the top five models under $500. The page matches no query, so it ranks nowhere.
Missing proof requirements do something worse. Ask a writer to make claims without a list of acceptable sources and they will invent them or pad the draft with fluff. Editors then strip those sections in revision loops, and the publish date slips.
What does a bad brief actually cost? Across the cases I have seen, the answer is the same number every time: weeks. A brief that lists a keyword and three links and stops there produces a draft, then a rewrite, then a second rewrite. Every gap in the brief becomes a decision the writer makes alone and the editor unmakes later. The brief is where the page wins or loses, written before the draft starts. A blank field is a revision cycle waiting to happen.
Underspecified format and angle leave the writer guessing at structure. The draft comes back needing a full rewrite instead of line edits, because the writer chose a listicle when the SERP rewards a how-to.
Every failure mode traces to a field left blank, and none of them trace to writer skill. The brief is the control point. Whether a content operation ships clean drafts or burns weeks in revision loops is decided by this single artifact, before anyone writes a word.
The next section walks through the fields that earn their place, each one built to kill a specific kind of guesswork.
The Anatomy of a Working Brief: The Fields That Earn Their Place
Every failure in the previous section traced back to a missing field. Here are the fields that earn their place, and the specific guesswork each one kills.
The eight-field template functions as a control system. Every field exists to eliminate one failure mode before the writer opens a document. Remove a field and you reintroduce the guesswork it was designed to kill.
The first two fields do most of the work. Page basics locks scope before any research starts: the URL, the target keyword, the audience, the funnel stage.
The single job locks the definition of success in one sentence: what the reader can do after reading. Eight fields on the template, and the single job field was the one I saw writers fill in first: with it done, the outline stopped drifting. Together they kill the two biggest guesses a writer makes.
Each middle field kills a distinct guesswork. A SERP teardown kills format and angle guesswork by reading the top pages through content type, format, and angle. The question cluster kills coverage guesswork by listing the questions the page must answer. Proof and sources kills evidence guesswork by specifying what substantiates the claims.
Outline with intent notes kills structure guesswork by annotating why each section exists. On-page spec kills optimization guesswork by fixing title, meta, headings, internal links, and schema before drafting.
Definition of done is the load-bearing field. It turns the brief from a wishlist into acceptance criteria an editor can enforce: the editor checklist before the page ships. Leave it out and "good enough" becomes whatever the writer felt like submitting.
Here is the full field list as a control system:
| Field | What it specifies | The guesswork it kills |
|---|---|---|
| Page basics | URL, target keyword, audience, funnel stage | Scope: what page this is and who it serves |
| The single job | One sentence stating what the reader can do after reading | Success: what "done" means for the reader |
| SERP teardown | Content type, format, and angle of top ranking pages | Format and angle: what shape the page should take |
| Question cluster | The questions the page must answer | Coverage: what the reader expects to find |
| Proof and sources | Evidence, data, and sources the writer can cite | Evidence: what substantiates the claims |
| Outline with intent notes | Section structure with intent annotations | Structure: how the page flows |
| On-page spec | Title, meta, headings, internal links, schema | Optimization: how the page gets found |
| Definition of done | Editor checklist before the page ships | Acceptance: what "ready" means |
Field lists scale. Templates with fourteen mandatory fields, readability targets, schema, E-E-A-T proof slots, and GEO notes show the structure can grow. But each added field must still map to a guesswork it eliminates. Add a field that specifies nothing and you have created a new form to fill out, not a new control.
The field list is the spec. The next section turns that spec into a repeatable build process, step by step, from query to shipped brief.
How to Build a Brief: The Step-by-Step Workflow
The field list tells you what belongs in a brief. The workflow tells you what order to fill those fields, and order is where most teams lose the plot. A brief assembled out of sequence looks complete in the template and does nothing in the SERP.
Ten minutes flat, the AI handed me back a finished brief. Heading skeleton, question list, a proof section, all of it. It was also wrong in three places I only caught by opening the actual search results. That was the day the setting finally clicked: AI can take brief creation from 30 minutes down to 10 when it generates outlines and spots gaps, but only if the 10-minute output gets validated against SERP data before anything ships. The validation gate was the missing piece, not speed. Now every AI-generated outline runs through a quick SERP check before it touches the template, and the ten minutes hold up.
The sequence below follows the eight-field structure from Perkins Growth Systems and folds in the entity map and proof gates from Digital Applied's 2026 template, so every field has a specific job.
The build sequence, end to end:
- Single job → what the reader can do after reading
- SERP teardown → the pattern the top pages reward
- Question cluster → every question the page must resolve
- Proof and sources → the evidence behind each claim
- Outline with intent notes → locked headings and section jobs
- On-page spec → meta, title, slug, internal links
- Definition of done → the pre-ship checklist
Each output feeds the next. Skip the teardown or the question cluster and you get a brief that looks complete and ranks nowhere.
Step 1: Define the Single Job
A brief with three competing goals is a brief with none. The single job is one sentence: what the reader should be able to do after reading. Write it before anything else, because every later field either serves it or gets cut.
Bad: "Educate readers about content briefs and establish thought leadership while driving conversions."
Good: "After reading, the reader can run a seven-step brief workflow on their next page."
The first has three jobs and does none of them. The second is testable: hand the page to someone who has not read it, ask them to run the workflow, and see if they can. That test is the definition of done in embryo.
Step 2: Run the SERP Teardown
Open the top three to five ranking pages and read them through three Cs: content type (guide, list, tool, comparison), content format (long-form article, video-led, interactive), and content angle (the specific promise each page makes).
The teardown names the pattern the SERP rewards. Then the brief states where this page goes further. Beat the baseline, never copy it. The teardown tells you what Google is already rewarding; your page has to offer something the top five do not. That is the whole line between ethical competitor research and plagiarism, and the next section goes deep on it.
Step 3: Map the Question Cluster
The question cluster marks the difference between mentioning a topic and resolving it. Pull real questions from People Also Ask, related searches, and forum threads, then tag each one: must-answer in the body, or FAQ-only.
Questions tagged must-answer get a predictable H2 or H3 location. That predictability is what improves scannability for readers and extraction for AI engines deciding what to cite. A question buried in a 400-word paragraph is an unanswered question to both.
Step 4: Assemble Proof and Sources
Trust is the most important component of E-E-A-T, so the brief cannot stop at "add citations." It points the writer at real evidence. List each specific claim that needs a source and where that source lives: which study, which dataset, which primary document.
For YMYL pages, the brief names the reviewer and the disclaimer requirements outright. "Reviewed by a licensed financial advisor" is a field in the brief, not a hope. "Add citations" is a vague instruction that produces vague pages; "cite the primary dataset in the proof section" is a spec.
Step 5: Lock the Outline with Intent Notes
Headings are promises the outline makes to the reader. Lock the mandatory H2s in order, list optional H3s beneath them, and write one line under each heading stating what that section must accomplish. That line is the intent note.
It prevents the "brilliant but off-structure" draft: a writer who nails the prose but buries the single job three sections deep. The note says "this section answers question cluster items four through seven and ends on the proof," so the writer cannot drift.
Step 6: Spec the On-Page Elements
The on-page spec covers meta description direction, title tag, slug, and internal links by URL, not by vague instruction. "Link to the pricing guide" is a guess; "link to /pricing from the proof section" is a spec.
It also connects the brief to the site's internal linking architecture. The pillar page is the hub those links point to, so every brief names which URLs point in and which URLs the page points out. Skip this and you ship a page that is structurally invisible to the site it lives on.
Step 7: Write the Definition of Done
The definition of done is a short checklist the editor runs before the page ships. It is the last field in the brief and the one that catches everything the first six missed.
A working checklist:
- The single job is answered in the first 200 words.
- Every question from the cluster is addressed, in body or FAQ as tagged.
- Every claim has a source, and YMYL pages name their reviewer and disclaimers.
- Internal links are in place by URL.
- Meta description and title tag match the on-page spec.
If any line fails, the page does not ship. The definition of done turns the brief from a planning document into a control system.
THE DESK REFERENCE
Brief Build
Checklist.
Keep the seven steps beside you while you build your next content brief. One page, ready to print.
Download the checklistmuhammadmahad.com
- Single jobWhat the reader can do after reading.
- SERP teardownThe pattern the top pages reward.
- Question clusterEvery question the page must resolve.
- Proof and sourcesThe evidence behind each claim.
- Outline with intent notesLocked headings and section jobs.
- On-page specTitle, meta, slug and internal links.
- Definition of doneThe checks to run before publishing.
The step that carries the most weight in this workflow is the SERP teardown, which gets its own deep dive next.
The SERP Teardown and Ethical Competitor Research
Step 2 of the workflow deserves a closer look, because the teardown does the most work of any step. It turns a live SERP into a spec before anyone writes a word. Screenshot the target locale and device profile, record every feature above the fold, and note where mobile and desktop diverge.
During the Q3 planning sprint for a home-services client, I watched a content manager run a teardown that skipped mobile entirely. She captured one desktop SERP, noted the top three titles, and called it done. The brief she wrote matched the number-one page's angle almost word for word. When the draft shipped, it ranked nowhere. The mobile SERP for that query showed a local pack, three People Also Ask boxes, and a featured snippet pulled from a page with a comparison table. None of that made it into her brief because none of it was visible on the desktop screenshot she had taken. Her brief mapped search intent but never touched answer intent, the pairing the 2026 template requires. That mistake cost a full rewrite cycle.
Then map the reward system. Across the top three to five pages, identify content type, format, and angle. Note which answer formats the SERP surfaces: featured snippets, AI Overviews, People Also Ask. This is where you learn what the answer intent actually looks like on the live SERP, not what a tool guesses it might be.
Keep the ethical line explicit. The teardown tells you what the SERP rewards, not what to copy. The angle that beats the baseline must be original.
A teardown that skips mobile, or one that stops at listing URLs, produces a brief that guesses. One done properly produces a spec.
Who Should Create Your Briefs: In-House vs Outsourced
The teardown is done. You know what the SERP rewards and where your angle beats the baseline. Now someone has to turn that into a spec. Which option fits the team you actually have depends on four factors: cost, speed, depth, and control. The build-versus-buy decision for outsourcing content briefs scores each factor in full.
Cost is the easiest place to start, and the easiest place to fool yourself. In-house means a salary, benefits, and a strategist who spends part of every week on briefs instead of strategy. Outsourced means per-word or per-project billing. White-label brief writers cluster from $0.05 to $0.30 per word, with most charging $0.08 to $0.15 for bulk agency work.
Agencies routinely resell that output at two to five times the purchase price. The margin exists because the agency sells something the white-label writer does not: the brief itself, the spec that carries SERP context and brand voice. "You're paying them eight cents a word and charging me how much?" a client asked, and that line is the pattern I have seen repeat across every white-label engagement: the brief is the actual product, not the prose.
Speed and scalability favor outsourcing, but only if the spec is tight. A white-label provider can turn around ten briefs in the time an in-house strategist drafts two. The catch is brand knowledge.
An outsourced writer has never sat in your client's kickoff call or read the support tickets, and they have not absorbed the voice guide. Everything they know about the brand is what you put in the brief.
That is the entire point of a spec: the brief carries what the writer cannot know.
SEO depth is where in-house strategists hold a real edge. They carry the SERP context and keyword history in their heads. They know why the last page on this topic underperformed, which internal link moved rankings, and which angle the client's audience rejected. An outsourced writer needs all of that written down. If the brief does not carry it, the writer guesses, and the guess is usually the median result.
Control and consistency follow the same line. In-house briefs align with brand voice and E-E-A-T signals because the person writing the brief is accountable for the page that ships. Outsourced briefs drift unless the definition of done is enforced at the editor level. Drift is a spec problem.
| Factor | In-house | Outsourced |
|---|---|---|
| Cost | Salary plus benefits, fixed monthly | $0.05–$0.30/word, most $0.08–$0.15 bulk |
| Speed | Slower, limited by headcount | Faster, parallel throughput |
| Brand knowledge | Deep, absorbed over time | Only what the brief carries |
| SEO expertise | Holds SERP history and keyword context | Needs the brief to supply context |
| Scalability | Linear, hire to scale | Near-instant, volume-based |
| Control | Direct, aligned with voice and E-E-A-T | Requires enforced definition of done |
| Best for | High-stakes pages, complex SERPs | High-volume, templated, lower-risk pages |
Once the who is decided, the next challenge is scaling across many writers and clients without the strategist becoming the bottleneck.
Scaling Briefs Across Writers and Clients
A decision on who writes briefs only matters if that person can scale. One strategist feeding ten writers across eight clients fails the moment every assignment demands a custom document.
The fix is a single template with a fixed field list. Entity map, heading skeleton, mandated proof sources, E-E-A-T quality gates. Same order, same names, every time. One definition of done so every writer ships against the same bar. That's what separates a content operation that ships clean drafts from one that burns weeks in revision loops.
I spent a quarter writing bespoke briefs for each client. Different field order, different labels, different definition of done. A new writer joined mid-quarter and her first week was pure back-and-forth: which fields mattered for this client, what counted as done for that one. That lost week was the price of my flexibility. The fix was one template with the fixed field list, then a short guardrail block appended per client. Onboarding dropped to a single read-through, and I stopped being the only person who could explain the spec.
Client-specific guardrails layer on top of the standard template. Brand voice, compliance requirements, tone preferences. These live in a short appended section, not a rewritten document. A financial services client gets a compliance block. A lifestyle brand gets voice notes. The core spec never changes.
New writers also need a handoff checklist so they never start cold. The checklist details live in the guide to managing briefs across multiple writers, but the principle is simple: no writer opens a brief without knowing the single job, the SERP context, and the definition of done.
That standardization is what makes quality control possible. A brief system needs a quality gate, not just a template.
Auditing Brief Quality: The Quality Gate
Scaling a brief system without a quality gate is where most content operations quietly break. You standardize the template, you train the writers, and drafts still drift into revision loops because the brief itself was broken from the start. The gate catches bad briefs before a writer touches them.
It runs in five minutes. Four yes/no questions, each mapped to one failure mode:
- Does the brief name a single job? No single job means scope creep. The writer tries to cover everything and ranks for nothing.
- Does the SERP teardown state an angle? No angle means a generic page that reads like every other result on page one.
- Does the question cluster resolve the query? An unresolved query means answer mismatch. The reader lands, doesn't get what they came for, and leaves.
- Does a definition of done exist? No definition of done means endless edits. The editor has no concrete bar for shipping, so revisions pile up.
The 2026 SEO content brief template from Digital Applied makes this concrete by pairing search intent with answer intent and building in E-E-A-T quality gates alongside mandated proof sources. The audit checks that those gates are present and functional, not just that fields got filled in. A brief with an empty "author credentials" field and no mandated proof sources fails the gate even if every box has text in it.
The cursor blinked on a brief I'd written for a commercial flooring client last spring, and I caught myself staring at the SERP teardown field. It listed three competitor URLs and nothing else. No angle. No content type call. I ran the four questions and hit "no angle" inside ninety seconds. That brief would have produced a generic comparison page and burned a week in revisions. I sent it back to myself, added one line, "angle: cost-per-square-foot across five material types for facility managers," and the draft came back clean on the first pass. The whole audit took under three minutes. If yours takes longer, the brief is too complex, not the gate.
Brief Quality Scorecard
| Single job stated in one sentence |
|
Scope creep |
|---|---|---|
| SERP teardown names an angle |
|
Generic page |
| Question cluster resolves the query |
|
Answer mismatch |
| Definition of done exists |
|
Endless edits |
Send-back threshold: 3 or fewer passes. No writer sees the brief until it scores 4/4.
Teams that want a deeper grade can run an audit of a content brief against a full 13-field framework. The four-question gate is the fast version. Use it on every brief, every time.
With the gate in place, the last piece is writing briefs for the two readers covered earlier: Google's ranking systems and the AI engines that decide what to cite.
Briefs for Two Readers: Google and AI Engines
A brief that passes the quality gate still has a job left undone: it has to satisfy two readers with different appetites. Google's ranking systems reward original information, demonstrated experience, and trust. AI engines reward clear, extractable, citable passages. Your brief has to name both outcomes explicitly, or one reader gets served by accident.
For Google, the steering mechanism is the Who, How, and Why test. The brief's E-E-A-T fields should require visible authorship, a stated production process, and concrete trust signals.
Trust sits at the center of E-E-A-T: without it, experience, expertise, and authority carry little weight. A brief that says "cover E-E-A-T" is useless.
A brief that says "name the author, link to their bio, state how the data was collected, and cite two primary sources" gives the writer something to build against.
For AI engines, the steering mechanism is structure. The brief should specify predictable H2 and H3 locations, direct answers to PAA questions, and passages that stand alone. An AI engine citing your page is not reading for nuance. It is reading for a clean, self-contained answer it can extract verbatim. If your brief does not mandate where those answers live, the writer will bury them inside a paragraph and the engine will skip you.
A client's pillar page on retirement tax thresholds started getting cited in AI answers the week after I rebuilt the brief to include a standalone H3 answering "At what income does Social Security become taxable?" with a direct numeric sentence. The previous version had the same information buried in the fourth paragraph of a longer section. Same writer, same facts. The only change was the brief requiring an extractable passage at a predictable heading location.
The practical move is to add two fields to every brief template. One field names the E-E-A-T requirements: who authored it, how it was produced, why the reader should trust it. The other names the citation targets: which questions get direct standalone answers, and which headings hold them. A brief with both fields stops guessing at what the page is trying to become.
With both readers in mind, the final body section consolidates the failure modes and the fixes that trace back to the brief.
Common Mistakes and How to Fix Them
When a draft comes back wrong, the instinct is to fix the draft. The better move is to trace the failure to the brief field that was missing or vague and fix it at the source. In a high-volume operation, revision loops almost always trace back to an underspecified brief, not writer incompetence. The content brief is the single artifact that decides whether the operation ships clean drafts or burns weeks in revision loops.
| Failure mode | What it looks like | The fix |
|---|---|---|
| Underspecified intent | Draft covers the topic but never states what the reader should do after reading | Add a single-job statement: one sentence naming the reader's next action |
| SERP mismatch | Draft is a listicle when the top five results are how-to guides | Run a SERP teardown and lock content type, format, and angle in the brief |
| Stale competitor picks | Brief references pages that dropped out of the top ten months ago | Re-run the SERP teardown at briefing time, not at strategy time |
| E-E-A-T as footer problem | Author bio and trust signals bolted on after the draft, not designed into the page | Specify the Who, How, Why evidence in the brief before drafting starts |
| Over-specified brief | Writer follows a 40-field template and produces a page with no point of view | Cut the brief to the smallest viable spec: single job, SERP context, definition of done |
| Keyword density targets | Writer stuffs the keyword to hit a percentage and the prose reads like a robot | Replace density targets with a definition of done: natural use, no forced placement |
The third revision request landed in my inbox at 4:50 on a Friday. Same draft, same writer, same complaint: the page didn't say what it was for. I pulled the brief and found the problem in thirty seconds. No single-job statement. The keyword was there, the headings were there, the internal links were there. But nothing told the writer what the reader should be able to do after reading. Three rounds of edits, and the fix was one sentence added to the next brief: "After reading, the reader can choose a project management tool for a team under ten people." The next assignment came back clean on the first pass. The upside nobody puts in the marketing: the single-job statement doesn't just guide the writer, it kills the revision loop before it starts. I've seen the same pattern across a half-dozen clients. The brief field that looks like philosophy is actually the cheapest quality control lever in the operation.
Each fix in the table is a definition of done the writer can verify before drafting begins. If the single-job statement is missing, the writer stops and asks for it. If the SERP context is stale, the strategist re-runs the teardown. The mistakes are catalogued; the FAQ answers the most common questions.
Conclusion
So which fields actually earn their place? The single job and the definition of done changed my drafts; most of the other 13 fields were guardrails I could trim when a deadline bit. That is the whole argument: a brief that kills guesswork gets drafts back right first time, because the writer never had to wonder what the page was for.
The document matters less than the system behind it. Run the same 13-field audit on every page, hold every draft to the same definition of done, and quality stops depending on which writer picked up the assignment. The brief becomes repeatable, auditable, scalable.
Three things carry forward: the audit for coverage, the single job for focus, the definition of done for shipping. Start with one. Download the Brief Build Checklist, run the audit on your next page, or write the single job before you touch a keyword.
The brief is where a page wins or loses. You have the spec now. Ship the next draft clean.
Trust & Sourcing
-
For topics touching money, health, safety, or minors, the brief itself specifies the E-E-A-T requirements: reviewers, citations, and disclaimers are assigned before drafting starts, not after legal flags the draft.
-
This article specifies the exact sources, author credentials, and review steps a brief must name for performance, financial, or health claims, so no brief ships with a vague 'add citations' instruction.
-
The AI-citation requirements in this section trace to Google's Who, How, and Why test and the 2026 Digital Applied template, which pairs search intent with answer intent and mandates visible proof sources.
Frequently Asked Questions
1) Is a brief just a detailed outline?
2) What should a brief include?
3) How long should it be?
4) Who writes it, and does strategy come first?
5) How do I brief a writer new to the brand?
