A content brief a writer can actually use

A brief is a decision document

A good content brief explains who the piece helps, what it must answer and what evidence is available. It should reduce uncertainty without dictating every sentence. Start with a reader task and a one-sentence promise, then give the writer the context needed to deliver it. A long list of keywords cannot replace those decisions. The practical goal is a draft that answers the right question, not a document that merely checks every box in a template.

Define one reader and one moment

Describe the audience in terms of the situation they are in. “A small retailer deciding whether to start an email program” gives more direction than “business owners.” Note what the reader already understands and what might stop them from acting. Avoid inventing an elaborate persona with fictional personal details that have no bearing on the article.

Write the primary question in the reader's language. Add a short list of related questions only when they support the same task. If a related question would need a different introduction and call to action, consider linking to a separate guide rather than expanding the assignment indefinitely.

Explain the page's role

State whether the piece is an introductory guide, a comparison, a process explanation or a reference. Identify where it fits in the site and which existing pages it should connect to. This helps the writer avoid repeating a nearby article and makes the intended depth easier to judge.

Define the next step in proportion to the topic. A beginner guide might invite the reader to try a worksheet. A detailed process page might point to a related implementation guide. The brief should not demand a sales pitch that interrupts an otherwise educational answer.

Make an evidence plan before drafting

Separate facts that require verification from editorial recommendations and illustrative examples. Provide primary sources where platform behavior or legal requirements are involved. If a proposed section depends on internal experience that has not been supplied, flag the gap instead of asking the writer to make it sound authoritative.

Label hypothetical examples explicitly. Do not dress an imagined result as a client story or add numbers to make the copy feel credible. If a number is merely an arithmetic example, say so and show the assumptions. Clear limitations make a useful piece more trustworthy, not less persuasive.

Outline in the order of the task

Create a working sequence of sections. Each heading should have a short note explaining what the section contributes, not just repeat a keyword variation. Put the answer and essential context early. Move advanced exceptions later, where they will not overwhelm a new reader.

Give the writer permission to improve the structure if research reveals a better order. Set boundaries on what the article will not cover. Specify required links, accessibility needs for any visuals and whether a screenshot or a simple table would actually help. More visual assets are not automatically better.

Agree on review criteria

Before assignment, define what makes the draft ready: accurate claims, a direct opening, descriptive headings, useful examples, working links and a next step that matches the reader's intent. Separate substantive review from line editing. There is little value polishing a sentence in a section that does not belong in the piece.

Keep feedback specific. “Explain how the reader chooses between these options” is actionable. “Make it more engaging” leaves the writer guessing. Once the article is published, retain the brief so future updates can preserve the original purpose while correcting outdated details.

A practical exercise

Try handing the brief to someone who was not involved in planning. Ask them to explain the intended reader, the central question and the evidence needed, without consulting you. Any uncertainty they identify is a useful revision target. Resolve contradictory instructions before assigning the draft. Save a final version alongside the article rather than losing it in a message thread. That record becomes a practical reference when someone later wonders whether a proposed section belongs on the page.

Briefing questions

How long should a brief be? Long enough to resolve important decisions; a short clear brief is better than several pages of conflicting instructions.

Should it prescribe an exact word count? Use a range to communicate scope, but let the reader's task determine necessary depth.

What is the simplest useful version? Audience situation, main question, promised outcome, evidence, outline, exclusions and next step make a practical starting set.