Content brief templates: 14 fields, four variants

Content brief templates are specs, not intake forms: a working one names the target query, the reader's job, the single promise, an outline with a word budget per section, the exact URLs that may be cited, the internal links to place, and the checks the draft has to pass before it ships. Fourteen fields cover that. Below is the field-by-field anatomy with fill times, four variants for four different jobs, a 100-point completeness score, and a JSON version a validator can read.

What each field has to decide

A field earns its place only if you can name the sentence in the draft that would be different without it. That test kills most of what accumulates in a brief template over a year: the persona paragraph, the brand-values reminder, the competitor list nobody opens, the "tone: professional yet approachable" line that would change no word of any draft ever written from it.

Here is the set that survives the test. The fill times are the budget I work to — they are a target for the person filling the brief, not a measurement of your team.

Cannibalisation, since the word does real work in field 13: two of your own URLs answering the same query, splitting the signals a single stronger page would hold. It is cheap to check while briefing and expensive to unwind after both pages are indexed.

The 22-minute budget

Those fill times sum to exactly 22 minutes, and two fields take a third of it. The outline is four minutes, the answer paragraph three — 7 of 22, or 32 per cent. That is the right shape, because those two fields *are* the article. A brief that spends more time on background than on the outline is a memo with a keyword attached.

Twenty-two minutes across twelve articles a month is 4.4 hours. A forty-five-minute brief at the same cadence is nine. The budget is not about speed. It is about finishing: a brief nobody can complete in one sitting gets completed badly, or gets completed after the draft, which is worse.

The 90-second payback rule

Adding a field to your template is a recurring cost, so price it that way. Ninety seconds to fill, twelve articles a month, is 18 minutes a month and 54 minutes a quarter — every quarter, for as long as the field exists.

The rule: keep the field if you can name the rework it removes and that rework costs more than 54 minutes a quarter. Drop it if you cannot name the rework at all. Most template bloat is fields added once to prevent a specific mistake and kept for years after the mistake stopped happening — the fossil record of old incidents, filled in by people who were not there.

Four templates, because there are four jobs

One template for every article is the most reliable way to teach writers that briefs are paperwork. The 14 fields stay; what changes is which ones carry the decision and which get one line.

The new-article brief

The full 22 minutes, all 14 fields, and the one field people skip under time pressure is number 11. Skipping it is how you get a competent page that has no reason to outrank the pages it was assembled from. Decide the original value before the outline, because the outline usually has to make room for it — a table needs its own section, a decision rule needs the section that sets up the decision.

The refresh brief

Fields 1 and 13 are already answered: the query and the competing URL are the page itself. What the refresh brief needs instead is a diff. Three columns — keep, cut, add — against the live outline, plus a re-verification pass on every external link the page already carries. A refresh brief that reads like a new-article brief produces a rewrite, and a rewrite throws away whatever the page had already earned.

The comparison brief

Criteria before options, always — with one exception worth naming: if the reader is choosing between exactly two known options, lead with the fork. Otherwise the brief specifies the criteria, the weights, and the trade-off each option carries, and the writer fills the grid. Fields 9 and 12 do the heavy lifting here, because comparison pages are where unsourced superlatives get written. Put the rule in the brief in plain words: state who each option fits and what it costs them, do not rank.

The source-led brief

When you supply the material — a transcript, a study, an internal report, a set of approved references — the brief's job flips. Field 9 stops being a permission list and becomes the entire corpus, and field 6 usually inherits the source's structure. The failure mode here is subtle and I have watched it happen: the corpus is attached but never actually loaded into the drafting step, so the writer produces confident prose with zero citations from material that was sitting right there. Make "every claim traces to a supplied source" a line in field 14, and check it before the draft, not after.

The brief as a contract a validator can read

Here is the part the downloadable-template roundups leave out. If your brief lives in prose, only a human can enforce it. If it lives in fields with types, a gate can — a gate being an automated check that holds a draft out of the publishing queue until it passes.

Nine keys are enough:

```json { "query": "content brief templates", "locale": "en", "promise": "A 14-field template a writer can build from and a validator can check.", "answer_paragraph": { "min_words": 30, "max_words": 120, "must_contain": ["content brief templates"] }, "outline": [ { "h2": "What each field has to decide", "words": 550, "h3": ["The 22-minute budget", "The 90-second payback rule"] } ], "sources": ["https://asana.com/resources/how-write-creative-brief-examples-template"], "internal_links": ["https://www.seoautopilot.cloud/en/blog/editorial-workflow-software-evaluate-choose-implement"], "forbidden_claims": ["superlatives", "unsourced pricing", "quantified outcomes"], "done_when": ["answer paragraph within bounds", "sources >= 2 distinct domains", "internal_links >= 1", "every outline h2 present in draft"] } ```

The same structure works as Notion properties or Airtable columns. What matters is that fields 5, 6, 9, 10 and 14 are addressable without a human copying them out of a paragraph.

What a machine can check

• The answer paragraph is between 30 and 120 words and contains the target query.
• The draft cites at least two distinct external domains.
• Every internal link matches a URL that exists in your own page inventory.
• Every H2 in the outline appears in the draft, and no unplanned H2 was added.
• No phrase from the forbidden list appears in the body.
• Section word counts land within a tolerance of the budget — I use ±25 per cent before it is worth a look.

Six checks, all mechanical, all cheap to run on every draft. This is the layer that turns a template into part of a content pipeline rather than a document.

What stays with a human

Whether the promise in field 3 is actually true. Whether the source in field 9 supports the specific sentence it was attached to, or merely sits near the topic. Whether the original value in field 11 is genuinely absent from the pages already ranking, or just phrased differently. No validator settles those, and a template that pretends otherwise is selling you a review process you do not have.

Score the template before you queue forty briefs

Score your current template out of 100 against the fields, not against how it looks:

Below 70 you have an intake form. The arithmetic is deliberate: outline, answer paragraph and original value are 38 points between them, so a template missing all three tops out at 62 — it cannot reach the floor even if everything else is perfect. That is the correct verdict, because those three fields are the only ones that determine what the article *is*.

There is a second reading worth doing. Drop only the source list and the claim rules and you score 78, a pass. That 78 is exactly the template that produces drafts which stall in review: complete, well-shaped, and full of assertions nobody scoped. If your review queue is growing while your briefs look fine, check fields 9 and 12 first.

When to change the template

Change it between cadences, not during one. Editing a brief template while forty briefs sit queued against the old version means re-briefing forty articles or shipping two standards side by side, and teams reliably pick the second.

One observation on timing, from the keyword sample this article was planned against (DataForSEO, pulled 7 September 2026, single keyword): searches for content brief templates ran 480 in September 2025, 320 in October, 260 in November, and 70 by July 2026 — October sits at 67 per cent of the September peak, and the summer floor is about a seventh of it. One keyword from one tool is not a market, so treat it as what it is: a hint that people go looking for brief templates when they are planning, and stop when they are executing. If your first-quarter calendar gets filled in November, the template edit has to land before it, in the weeks when the queue is short.

Where briefs break

1. The brief written after the draft. Retro-fitted to justify what was produced. Early symptom: the outline in the brief matches the draft's headings word for word, including the odd one.
2. The outline copied from the top result's headings. You have reproduced the consensus. Nothing in the page is quotable, and there is no reason for anyone to link it. Field 11 exists specifically to stop this.
3. The empty source field on a topic that needs sources. The writer fills the vacuum with plausible-sounding authorities. If you have a gate it blocks the draft; if you do not, the claim ships.
4. The field that changes nothing. Test it by swapping the value: if "tone: authoritative" instead of "tone: friendly" would alter no sentence, the field is decoration. It costs 90 seconds a brief anyway.
5. The brief edited mid-draft without a version bump. Two people then work from two specs and argue about the output. Version the brief or freeze it at handoff; either works, doing neither does not.
6. The forty-field template. Nobody completes it, so fields quietly become optional, then decorative, and within a quarter the whole document is advisory. Bloat does not kill briefs by being wrong. It kills them by being ignorable.

The pattern under all six: a brief is a decision record. The moment it becomes a description of intent rather than a set of decisions, it stops changing what gets written, and everything downstream — drafting, whether by a person or a model, review, publishing — absorbs the ambiguity instead.

Word, Docs, Notion, PDF: pick what your reviewers already open

Content Harmony's roundup collects nineteen downloadable briefs across Google Docs, Notion, Word and PDF, and MarketMuse's post gathers fifteen filled-in examples from different teams — useful for seeing how other people phrase fields before you write your own. Take the field list from one, the format from your own stack.

The decision rule is not about the tool's features. Choose the format your reviewers already have open, then ask one question of it: can a script read field 6 and field 9 without a human copying them? If not, your template can inform a writer but cannot feed a check — which is fine for a team of two, and the binding constraint the moment you are running a queue in dedicated editorial workflow software.

FAQ

Is there a content brief template for Word?

Yes, and Word is a reasonable choice when your reviewers work in track changes and briefs move by email. The trade-off is machine-readability: a .docx brief is prose plus tables, so the outline and source list can only leave the file if a person copies them. If you expect to automate any check later, keep the same 14 fields but hold them in a structure with named properties.

Where do free content brief templates and PDF downloads come from?

Mostly from content-marketing vendors and agencies publishing their internal templates as lead magnets — Content Harmony's collection covers Google Docs, Notion, Word and PDF, and MarketMuse's collects filled-in examples from a range of teams. Both are linked above. Download two or three, extract the field list, then discard the layout: the value is in which decisions the fields force, and a PDF is the one format you cannot edit into your own workflow.

What is the difference between a content brief and a creative brief?

A creative brief scopes a campaign or an asset. Asana's guide sets out ten elements including goals, audience, messaging and tone, deliverables, stakeholders, budget and timeline — the shape of a project, not of a page. A content brief scopes one piece of writing: target query, answer, outline, sources, links, checks. They overlap on audience and messaging and diverge everywhere else, which is why a creative brief template used for an article leaves fields 5, 6, 9 and 11 with nowhere to go.

What does a filled-in content brief example look like?

Concretely: field 1 is `content brief templates / en`, field 3 is one sentence naming what the reader leaves with, field 5 is 80 words of drafted opening, field 6 is six H2s with word counts attached, field 9 is three URLs the writer may cite and nothing else, field 11 says "22-minute field budget plus a 100-point score", and field 14 lists the four checks the draft has to pass. That is the whole artifact — roughly one screen, filled in 22 minutes, and specific enough that two different writers would produce recognisably the same article from it.