How to Write a Content Brief That Actually Gets Used

Last reviewed on 2026-05-12.

Most disagreements about a finished piece of writing are really disagreements about what the brief contained. When a draft comes back wrong, the brief is usually where the wrong direction was set — or where the right direction was never set in the first place. A good brief saves a round of revisions; a great one saves three.

The trouble is that briefs tend to fall into two failure modes. Some are too thin: a sentence in Slack saying "can we get a post on X by Friday". The writer has to invent decisions the brief should have made. Others are too thick: a multi-tab spreadsheet that nobody updates and writers eventually stop reading. The version that actually works lives between those two.

What a useful brief contains

A brief that does its job covers a handful of decisions clearly. None of these need to be long; they need to be made.

The reader

One short paragraph about who the piece is for. Not a persona document — a sentence or two on what they already know, what they are trying to do, and where they are likely to encounter this piece. "An engineering manager evaluating monitoring tools for a 30-person team, three months into a search" beats "B2B decision-maker, 35-50".

The job-to-be-done

What is this piece supposed to make happen? Inform a reader so they can make a decision, change a search ranking, prepare a sales call, justify a budget request. The job is not "publish a blog post"; that is the deliverable, not the goal.

The angle

What is the one thing this piece argues, or the one question it answers? If the answer is "it covers everything about X", the brief is not done yet. A piece without an angle hedges; a hedged piece reads as forgettable.

The keyword or query

If the piece is search-driven, the primary query goes here, with one or two supporting queries. Include the current ranking page if there is one — the brief is not just about what the new piece says, but about what it has to beat.

Structure cues

Word range, recommended sections (not a full outline — outlines belong to writers), required elements like a comparison table, a worked example, or a callout. List what the piece must include and what it should not.

Voice and tone notes

One or two lines, ideally pointing at an existing piece on the site whose tone the new piece should match. "Like this article, but slightly more cautious about claims" is more useful than a list of adjectives.

Sources

Internal documents, primary research, expert interviews available, competitor content the piece should engage with. If the writer is expected to find their own sources, that is a decision the brief should make explicit.

Success measure

How will we know in three months whether this piece worked? Traffic to a specific URL, conversions on a CTA, citations from an industry source, a measurable shift in a sales-call objection. Write it down before the piece exists.

Who fills in which part

This is where briefs usually break: the wrong person is asked to make the decision. As a rough division:

  • The requester (marketer, founder, product lead) owns the reader, the job-to-be-done, the angle, and the success measure. These are business decisions.
  • The SEO or content strategist owns the keyword, the supporting queries, and the structural cues that come from how Google or AI surfaces this kind of topic.
  • The writer proposes the outline, voice tweaks, and word range, all of which can be discussed before drafting starts.

When the writer is filling in the angle or the job-to-be-done, the brief is not finished. Send it back.

Common mistakes

The four briefs that produce the worst drafts:

  1. The kitchen-sink brief. Five target audiences, eight keywords, three calls to action. The writer has to pick one quietly, and probably picks wrong.
  2. The empty brief. A title and a deadline. Whatever the writer produces will be evaluated against expectations nobody wrote down.
  3. The brief by committee. Six reviewers, no single approver. The brief is whichever set of edits arrived last. Same problem hits the draft later.
  4. The brief that buries its lede. The actual important constraint — "this has to stop our competitor's page from ranking" — is on page four. The writer optimises for something else.

A worked example

Compare two versions of the same brief.

Bad brief: "Blog post on content audits. 1,500 words. SEO. Due 14th."

Better brief:

  • Reader: A marketing lead at a 50–200 person B2B SaaS company. They run a blog but have not audited it in over a year. They are looking for a workable process, not a 50-step framework.
  • Job: Make them feel that an audit is doable in two to three weeks, and have them book a strategy call to get help.
  • Angle: Audits do not have to take a quarter. Most of the value comes from a focused review of the top fifty pages.
  • Primary query: "how to run a content audit". Current top result: a 4,500-word ultimate guide; we want a tighter, more practical alternative.
  • Must include: a decision tree for what to do with each piece (keep / update / merge / delete), a worked example, and a callout to our case study.
  • Voice: Direct, slightly contrarian about overcomplication. Match the tone of our E-E-A-T piece.
  • Success measure: 500+ organic visits/month within six months and at least two contact-form submissions per month attributed to this page.

One of these briefs will produce three rounds of revisions. The other will produce a publishable first draft.

Where this fits

This guide is part of a small set of resources on the operational side of content writing. If you are scoping a new programme, the content audit guide and content KPIs guide are the most useful companions. If you are evaluating whether to bring in outside help, the services overview and case studies are the relevant pages.

If you would like a brief template adapted to your team's workflow, the fastest path is a short email to [email protected] or the form on the contact page.