A content brief is not a list of keywords handed to a writer. It is a shared definition of the article's job: who it should help, what decision it should support, what the business can credibly contribute and how the finished piece will be judged.
Without that definition, teams often discover disagreements after the draft arrives. The writer believed the piece was introductory; the marketer expected an advanced guide; the subject expert wanted a different argument; and the approver asks for the company to be mentioned in every section. A useful brief resolves those questions while changes are still inexpensive.
What a good brief should achieve
The brief should give the writer enough direction to make confident decisions without scripting every sentence. It needs to establish:
- the intended reader and their level of knowledge;
- the problem or question the article addresses;
- the search or discovery context, where relevant;
- the distinctive point of view or expertise available;
- the information that must be included;
- the action the reader should take afterwards;
- the standards for evidence, tone and accuracy.
If the document is longer than the eventual article, it may be constraining rather than guiding. If it consists only of a title and word count, it is not yet a brief.
The content brief template
Copy the following structure into your project tool or document and adapt it to the work.
Working title
Write a clear title that states the subject and useful promise. It can change during editing.
Example: How to prepare your team for a website redesign
Business objective
State why the organisation is publishing the article. Choose one primary objective, such as earning relevant search visibility, supporting a sales conversation, answering a frequent prospect question or establishing expertise in a priority area.
Avoid “increase awareness” unless you can explain awareness among whom and towards what outcome.
Primary reader
Describe the reader by situation rather than demographics alone.
Example: A marketing manager in a 20–100 person service business who has been asked to lead a redesign but has not managed one before.
Add what they already know, what they are worried about and what authority they have. This prevents an article for a first-time buyer from accidentally being written for a technical specialist.
Reader's question and desired outcome
Complete these statements:
- The reader arrives asking: “…”
- After reading, they should understand: “…”
- They should be able to do or decide: “…”
This is the most important section of the brief. It turns a topic into an editorial purpose.
Core answer
Summarise the article's main answer in two or three sentences. If the team cannot agree on this summary, it is too early to commission a draft.
The answer should be specific enough to guide the article. “It depends” is sometimes true, but the brief must identify what it depends on.
Scope and exclusions
List what belongs in the piece and what does not. This is especially useful for broad subjects.
Include: internal preparation, stakeholder roles, content inventory and realistic sign-off.
Exclude: platform selection and detailed technical migration, which will have separate guides.
Required sections
Provide a suggested narrative, not just a collection of headings. For example:
- why redesigns become difficult internally;
- decisions to make before appointing a partner;
- people and information needed;
- a preparation checklist;
- common mistakes;
- next step.
Mark truly mandatory points. Let the writer improve the order if a better argument emerges.
Original inputs and evidence
List the material that will make the article worth reading:
- an interview with a named subject expert;
- anonymised patterns from genuine client work;
- product or process documentation;
- first-party research;
- approved examples;
- authoritative external sources.
Do not invite writers to invent examples or dress assumptions as data. Note any claims requiring verification and name the person responsible for checking them.
Search and discovery notes
If organic discovery is an objective, record the main topic, closely related questions and the apparent intent. Include relevant terminology, but do not prescribe keyword repetition.
Review the current results and competing resources to understand what is already well served. The goal is not to reproduce the top-ranking page. It is to answer the need more clearly or from a more useful perspective.
Internal links and journey
Name the pages that genuinely help the reader continue. Explain why each link belongs. One may provide a deeper explanation; another may lead to a relevant service. Avoid forcing unrelated commercial links into informational paragraphs.
Call to action
Define one primary next step and the reason it is appropriate. “Contact us” is not a strategy. “Use the downloadable preparation checklist” or “Discuss your redesign requirements” gives the writer something concrete to build towards.
Voice and editorial rules
Specify a few meaningful principles:
- use UK English;
- write directly and calmly;
- explain technical terms on first use;
- avoid unsupported claims and manufactured urgency;
- do not patronise first-time buyers.
Attach a strong published example if one exists. A real example communicates voice more effectively than a long list of adjectives.
Deliverables and workflow
Record the target format, indicative length, owner, subject reviewer, final approver and deadlines. Define whether the assignment includes metadata, image notes, social copy or CMS entry. Agree how feedback will be consolidated so the writer does not receive contradictory comments from five people.
How to use the brief in practice
Hold a short briefing conversation when the topic is commercially important or technically complex. Ask the writer to play back the reader, argument and intended outcome. Misunderstandings exposed at this stage save days later.
During review, evaluate the draft against the brief rather than personal preference. Feedback such as “the risk section needs our operations lead's evidence” is actionable. “Make it punchier” is not.
After publication, update the brief with performance observations and recurring reader questions. It can become a useful record when the article is refreshed.
FAQ
Should every article have a content brief?
Not every short update needs a formal document. Use a fuller brief when several people are involved, the subject is complex, the article supports a valuable journey or mistakes would create reputational risk.
Who should write the brief?
The person accountable for the content outcome should own it, usually a content strategist, editor or marketing lead. Subject experts should contribute evidence and correct technical assumptions.
Does a brief limit creativity?
A good brief creates useful boundaries while leaving room for judgement. It clarifies the problem, not every sentence. Writers can be more inventive when they do not have to guess the assignment.
A strong brief improves both the work and the working relationship. If you need a content system that connects editorial quality to commercial goals, talk to Yieldberg Studios about strategy, messaging and production.