What Goes in a Content Brief for a Writer?

You sent a freelancer a title, a keyword and a deadline. The draft arrived on time and missed the mark. It was pitched at beginners when your buyers are senior, and it answered a question nobody searched. Two revision rounds later, you're rewriting it yourself.

A content brief for a writer needs five things settled before anyone drafts. First, the business goal and the one question the piece answers. Second, a specific reader. Third, the search intent and the gap the piece will fill. Fourth, the scope of what it is and is not. Fifth, the working material: sources, tone and format. Fit it on one page, and treat every line as a decision the writer would otherwise have to guess.

What must every content brief decide first?

Start with the goal, stated in the first line, in terms you could check later. "Build topical authority" is a direction, not a goal. "Get small-agency owners to book a walkthrough after reading" tells the writer what the last paragraph is for and what the piece is allowed to ignore.

A useful test is to write one sentence answering two questions. What is the reader doing now, and what do you want them to do instead? If you can't answer both, the piece isn't ready to brief. It's still an idea, and no writer can fix that for you.

Next comes the single question the piece answers. A writer handed a topic will cover the topic. A writer handed a question will answer it, which is shorter, sharper and far more likely to match what someone typed into a search bar.

Then define the reader, and be specific enough to be wrong. "Marketers" describes everyone, so it helps no one. "An in-house growth lead at a mid-size SaaS company who has run paid search but never owned the blog" tells the writer three useful things:

• Depth: what this reader already knows, so the writer can skip the basics.
• Examples: which situations they will recognise as their own.
• Pain: the problem that sent them looking.

Knowledge level shapes the draft more than any other line in the brief. Get it wrong and every paragraph is pitched at the wrong height.

Finish this part with the key messages. Three to five points at most, plus what the reader should think or do once they've finished. More than five and you've briefed a series, not an article.

Which SEO details belong in the brief?

Give the primary keyword with a one-line intent statement attached. The keyword alone is ambiguous. Someone searching "content brief template" wants a usable list of fields they can copy, not a 2,000-word essay on the philosophy of briefing. That intent line stops the writer producing the wrong format of a correct answer.

List the secondary terms worth working in, and say plainly that they should read naturally. A writer told to hit a density target will produce prose that reads like it was written for a crawler, and readers notice before rankings do.

The most valuable SEO line is the gap. Before you brief, read what currently ranks and write down what those pages miss. Maybe they all list steps but none offers a template. Maybe they all target beginners and skip the trade-offs. That gap is the angle, and it is the difference between the thousandth version of an article and one worth linking to.

Then add the structural suggestions:

• Title and meta description: a working version of each.
• Outline: a rough H2 plan.
• Internal links: the exact URLs you want included, not "link to relevant pages".
• External sources: a note on which kinds are acceptable.

Mark the outline and title as proposals. A good writer will improve them, and a brief that forbids pushback gets compliance rather than judgment.

One thing to resist is setting word count by averaging the top-ranking pages. Length should follow what it takes to answer the question well for that reader. Copying the average of pages you're trying to beat is a reliable way to sound like them.

What should the writer not have to guess?

Scope. Say what the piece is and is not. This matters most inside a topic cluster, where the temptation is to cover everything. If the piece explains how to brief a writer, it shouldn't drift into deciding what to write about on your blog, because that is a different article with a different reader moment. One "not this" line prevents more scope creep than any amount of editing afterwards.

Sources and experts. Link the credible material you already trust, and say how this piece should differ from it. If someone internal knows the subject better than any published source, name them and say how to reach them. A writer interviewing your head of paid search will produce something no competitor can copy.

Tone. Link the style guide rather than describing it in adjectives. "Professional but friendly" means something different to every writer who reads it. An example of a past piece you thought hit the voice is worth more than a paragraph of description.

Format and logistics. These are the lines writers most often have to email back about:

• Length: a word count range.
• Call to action: the one you want, or an explicit "none".
• Placement: where the piece will live on the site.
• Dates: the draft deadline and the publish date, as separate dates.
• Approval: who signs off, and what happens at review.

Give the project a descriptive name too. "June blog post" is useless six months later in a shared drive. A working title is not.

How long should a content brief be?

One page, two at most. A brief longer than that has stopped making decisions and started transferring research. The writer then has to do the editorial work you skipped, which is exactly what the brief was meant to prevent.

The way to keep it short is to separate two kinds of information:

• Standing context: brand voice, style rules, product positioning and who your customers are. This rarely changes between pieces.
• Per-piece decisions: goal, reader, question, gap, scope and logistics. These change every time.

Standing context should live in one place and be referenced, not re-pasted into every brief. When it is re-pasted, it drifts. Each version gets edited slightly differently, and six months on your writers are working from five different descriptions of the same brand.

A content brief template enforces that split. Fixed fields for the per-piece decisions, plus a link to the standing material, means nothing gets skipped and nothing gets duplicated. The template matters more as volume rises. Once you've settled how many posts a month you actually need, a weak template is a cost you pay on every one of them.

Review the template every quarter or two, and ask your writers two things. Which lines did they ignore? Which questions did they still have to ask? Ignored lines can go. Repeated questions are fields you're missing.

The same discipline applies when the writer is an AI model rather than a person. A human freelancer who lacks context will usually ask. A model will guess, fluently and with confidence. Everything above matters at least as much when the draft comes from software, and the standing context matters most of all.

Conclusion

A content brief exists to turn guesses into decisions before drafting starts. The goal, the specific reader, the search intent and gap, the scope, and the working material are the decisions that matter. Keep them on one page, keep standing context in one place, and let the writer spend their effort on the writing rather than on working out what you meant.

See how SproutMe Knowledge holds each workspace's brand guidelines, tone of voice and ICP definitions, so every brief references them instead of re-pasting them.