What is the purpose of an editorial brief?

It aligns writer, editor, and stakeholder on the reader, outcome, scope, evidence, deliverable, and review standard before drafting. A good brief removes consequential ambiguity without scripting every sentence. It makes disagreements visible while they are cheap to resolve, protects against topic duplication and unsupported claims, and gives the reviewer observable acceptance tests rather than a late request to make the article more engaging.

How detailed should a content brief be?

Detailed enough to define the reader question, required coverage, exclusions, evidence needs, examples, care line, format, and acceptance tests, but not so detailed that it prewrites transitions or forces research into an unsupported conclusion. High-risk, technical, commercial, or multi-format work needs more specification. A familiar low-risk essay may need less. Every field should prevent a plausible misunderstanding or support a real review decision.

What belongs in a content brief outline?

List the questions the article must answer in reader order and add one sentence describing each section's required outcome. A how-to needs prerequisites, steps, verification, failure handling, and next actions. A comparison needs criteria, verdict, evidence, tradeoffs, and audience fit. Keep headings provisional until research clarifies the material. The outline should define logical coverage, not serve as decorative furniture the evidence must squeeze around.

How do I specify tone without vague adjectives?

Translate tone into observable behaviors: define terms on first use, prefer concrete verbs, use second person in instructions, limit asides, state uncertainty, avoid hype, and never joke across identified care boundaries. Provide a short approved excerpt and explain what it does well when voice matching matters. “Friendly, expert, and engaging” alone does not tell a writer how sentences, evidence, humor, or reader address should work.

What acceptance criteria should an editorial brief include?

Use yes-or-no checks tied to the assignment: the opening answers the question, every required section delivers its outcome, time-sensitive claims are current and sourced, arithmetic reconciles, examples work, links resolve, metadata matches the body, care requirements are met, and files follow the delivery format. Add article-type tests such as doneness for recipes, runnable code for tutorials, or criteria and drawbacks for commercial comparisons.

Planning Tools

Write an Editorial Brief That Prevents Rewrites

The Draft Bench · Updated 2026-07-19 · 4 min read

Quick answerWrite an editorial brief as a decision record. Define the reader, the action or decision the article should enable, and the risk it should avoid. State the question, article type, target length, deliverables, deadline, owner, reviewer, format, and acceptance criteria. Add explicit includes and excludes, duplication boundaries, a question-led outline, voice behaviors, required examples, source and claim plans, internal-link targets, and the subject's care line. End with yes-or-no checks for promise, coverage, current evidence, reconciled numbers, valid links, aligned metadata, and correct files, plus open questions and named decision owners.

Contents

A brief is a decision record, not a wish
State the assignment facts
Define scope with includes and excludes
Convert tone words into behaviors
Build a question-led outline
Attach a source and claim plan
Specify examples and care lines
End with acceptance tests

A brief is a decision record, not a wish

An editorial brief should tell a writer which reader needs what outcome, within which boundaries, using what evidence, in which deliverable. “Write 1,500 words about project management and make it pop” tells us the topic, approximate furniture requirement, and nothing about who lives there.

Begin with one sentence:

After reading, [specific reader] should be able to [observable decision or action] without [important risk or confusion].

For example: “After reading, a first-time team lead should be able to choose a weekly status format without buying software or exposing private employee information.” That sentence shapes scope, examples, sources, and the care line.

State the assignment facts

Put these fields at the top:

working title and primary reader question;
audience knowledge and context;
article type and target length;
publication, category, voice, and delivery format;
deadline, owner, reviewer, and approval path;
success criteria and any fixed requirements.

A target length is a planning range, not permission to inflate three useful paragraphs into a ceremonial fog bank. Define acceptable tolerance. If the piece needs a table, calculator, code sample, recipe, image, quote, or downloadable file, say so now.

Record title constraints and metadata requirements separately from the body. A search query may inform the angle, but it does not replace the reader or make every exact phrase grammatical.

Browse planning tools for brief fields suited to different article types.

Define scope with includes and excludes

Write three to six things the article must cover and two to five things it will not cover. Exclusions prevent a useful article from becoming a tiny encyclopedia with one paragraph per continent.

For a guide to choosing a meeting format, scope might include participant count, decision type, preparation, accessibility, privacy, and follow-up. It might exclude a vendor roundup, employment-law advice, and instructions for a specific company's internal system.

Name adjacent published or queued topics that must not be duplicated. Link the current content inventory or list exact titles and slugs. “Avoid overlap” is not enough when nobody has been shown the other work.

Convert tone words into behaviors

“Friendly, expert, engaging” describes nearly every brief produced since the invention of adjectives. Translate voice into observable choices:

define specialist terms on first use;
use direct second person only in practical steps;
include one dry aside per major section at most;
never joke about harm, identity, grief, illness, or safety;
prefer concrete verbs and examples to hype;
state uncertainty and disagreement openly.

Add a short excerpt from an existing article when voice matching matters. Say what works in it. Otherwise, writers may imitate surface quirks and miss the publication's actual relationship with the reader.

Build a question-led outline

List the questions the body must answer in reader order. A how-to commonly moves through prerequisites, setup, steps, verification, failure modes, and next actions. A comparison needs a verdict, criteria, comparable evidence, tradeoffs, and who should choose each option.

Keep headings provisional until research clarifies the material. The brief should specify logical coverage, not force evidence into a decorative outline. Include one sentence describing what each section must deliver so two headings do not quietly answer the same question.

Attach a source and claim plan

Identify the claims that need current or primary support: laws, prices, specifications, health or safety guidance, dates, records, product features, named organizational policies, and statistics. List preferred source types and any mandatory official sources.

Do not prefill a persuasive statistic because the angle would enjoy one. Write the information need instead: “Find current official data on processing time, or generalize if unavailable.” Mark facts that must be recomputed, screenshots that need dates, and quotations that require exact attribution.

Separate source links from internal-link targets. An internal link must resolve and help the reader; it is not evidence for an external factual claim.

Specify examples and care lines

State which example the article must include and what it must prove. “Add examples” often produces three variations of a sentence that already made sense. Ask for a worked calculation, before-and-after edit, failure recovery, decision table, or complete scenario.

Add the subject's care line: no medical promises, food temperatures verified, cultural claims sourced, commands tested, venue details checked, financial figures dated, or animal welfare prioritized. Care requirements belong beside the assignment, not in a policy document everyone is expected to remember telepathically.

End with acceptance tests

Write a checklist a reviewer can answer yes or no:

Does the opening answer the primary question?
Does every required section deliver its named outcome?
Are time-sensitive claims current and sourced?
Do numbers and examples reconcile?
Do links resolve to intended targets?
Does metadata promise only what the body provides?
Is the output in the required file structure?

Use the pre-publication audit as the matching review system and editing systems for specialized passes.

Finally, name open questions and who decides them. A good brief does not eliminate creative judgment. It prevents the writer and reviewer from discovering at line 1,407 that they were producing different articles with the same noun.