You edit the blog at a small nonprofit, where articles come from staff, volunteers and the occasional freelancer, and every draft arrives in a different shape. Reviewers disagree about what the piece was meant to do, because nobody wrote it down. A one-page content brief fixes that: a short document, filled in before writing starts, that says who the piece is for, what question it answers and how everyone will judge it. This guide gives a twelve-field template, a worked example and notes on each field.
What a one-page content brief is, and why one page
A content brief explains what a piece should do before anyone writes it. The length limit is the point. A brief that runs to five pages gets skimmed, and a brief that fits on one page forces the person writing it to decide what matters. If the brief won’t fit, the idea usually isn’t clear yet.
The brief also gives reviewers something to review against. Instead of arguing about taste after the draft is done, the editor, the subject expert and the writer can all check the draft against the same page.
The one-page content brief template
Copy the table into a document or a form. The “Rule of thumb” column keeps each answer short.
| # | Field | What to write | Rule of thumb |
|---|---|---|---|
| 1 | Working title | A rough headline stating the topic | It can change later |
| 2 | Reader | Their role, what they know, what they are trying to do | Two sentences |
| 3 | Purpose or search intent | What the reader is looking for, or what the piece must achieve | One sentence |
| 4 | Core question | The single question the piece must answer | Write this first |
| 5 | Angle | The view or argument that sets it apart | One sentence |
| 6 | Outline | Sections in order | Four or five bullets |
| 7 | Sources and examples | Links, data, interviews, claims that need proof | Name each one |
| 8 | Voice | Three words and one sample | “Practical, warm, no jargon” |
| 9 | Links | Internal pages to link to, external sources to cite | List the URLs |
| 10 | Length and format | Word range, headings, lists, images | A range, not a number |
| 11 | Call to action | What the reader does next, if anything | One step |
| 12 | Deadline and review | Delivery date, reviewers, number of revision rounds | Names and dates |
Walkthrough: filling in the one-page content brief
Example (illustrative): the topic is giving feedback to a team member. A completed brief might read:
- Working title: How to give feedback without damaging the relationship
- Reader: First-time managers in small teams who have had no training and avoid difficult conversations.
- Purpose: Show them how to give specific, kind and useful feedback.
- Core question: How do you say something difficult without harming the working relationship?
- Angle: Treat feedback as a conversation, not a verdict.
- Outline: Why feedback feels hard; a simple three-part structure; two worked examples; mistakes to avoid; a checklist.
- Voice: Practical, warm, plain.
- Length and format: 1,200 to 1,500 words, H2 headings, one table.
- Call to action: Download the one-page feedback planner.
- Deadline and review: First draft 10 days before publication; one review by the operations lead; one round of edits.
None of that is long, and a writer reading it knows who they are writing for, what to argue and where to stop. Notice what it leaves out: it doesn’t dictate sentences, and it doesn’t list every point. The writer’s job is still to write.
Notes on the fields that cause most trouble
Reader and core question
These two fields do most of the work. Digital.gov, the US government’s plain-language guide, calls writing for your audience the first rule of plain language and asks writers to take the audience’s current level of knowledge, expertise and interest into account. Put those three things into field 2.
For field 4, GOV.UK’s guidance on identifying user needs offers a format worth borrowing: “As a…”, “I need to…” and “So that…”. It says to focus on actions or tasks, to avoid needs built only on “understand” or “know”, and to avoid naming a solution. A question such as “How do I decide whether to hire a freelancer?” works. “Explain our hiring service” doesn’t, because it describes the writer’s job and not the reader’s need.
Purpose or search intent
If the piece is meant to be found in search, field 3 should say what a person typing the query wants: an answer, a comparison, a template, a step-by-step method. Google’s guidance on helpful, reliable, people-first content asks, among other things, whether the content provides original information, reporting, research or analysis. So the brief should also say what only your organisation can add: your data, your cases, your process.
Sources and examples
List every source the writer should use and every claim that needs one. Name the type of source you accept (official guidance, published research, your own figures), and say what to do when none exists: soften the claim or drop it. This one line prevents most fact-checking disputes later.
Check for overlap before you commission
Before the brief goes out, search your own site. GOV.UK’s guidance on planning new content says a user need should be met in one place only, so the same question shouldn’t be answered twice. Your site isn’t GOV.UK, but the principle holds for any blog: two pages answering the same question compete for the same reader.
If a page already answers field 4, you have three options: update it, extend it with a section, or choose a different question. Note the decision in the brief and add the existing URL to field 9.
Make the brief testable
The same GOV.UK page on user needs recommends writing acceptance criteria: a list of what must happen for the need to be met. You can adapt the idea as a “definition of done” under field 12. For the feedback example, it might read:
- A reader can name the three parts of the structure after reading
- Both worked examples show a realistic response from the employee
- Every claim about workplace research has a linked source
Then test the finished draft on a real reader. Digital.gov’s guidance on testing for understanding describes paraphrase testing, with individual interviews that suit short web pages and short documents. A light version costs ten minutes: ask one person from the target audience to explain the piece back in their own words, and compare it to field 4.
A brief is a promise about what the piece will do, written down before anyone has a reason to forget it.
Using the brief across a team
Share it with everyone who will review the draft and get a quick “yes” from each before writing starts. Disagreements are cheaper to settle at the brief than on a finished draft.
Keep the template in one shared location, and revise it after every project. If a draft went wrong because something was missing, add a field or a prompt. GOV.UK’s guidance on managing existing content describes review dates that editors set, so that a team can see when content is overdue for a check. Adding a “review by” date to field 12 does the same job for your own pages.
When a brief isn’t needed
Quick updates, internal notes and short social posts don’t need a formal brief. For anything that will be published, reused or sent to many people, one page is a small investment. It pays back in fewer revision rounds and a clearer result. A reasonable cut-off: if more than one person will write, review or approve it, write the brief.
Common mistakes
Letting the brief grow. When it passes a page, cut the outline to bullets and move background into a linked document.
Writing the outline before the question. A sensible outline can’t exist until field 4 is clear. Write the question first and test it by saying it aloud.
Describing the reader as “everyone”. A piece for everyone is a piece for no one. Pick the primary reader and name them.
Forgetting the reviewers. A brief nobody else has seen is only your opinion.
One-page content brief checklist
- Core question written first, as something the reader would ask
- Reader described by role, knowledge and goal
- Purpose or search intent stated in one sentence
- Angle chosen, and existing pages on the site checked for overlap
- Four or five outline bullets, in order
- Sources listed, with claims that need proof marked
- Voice described in three words with a sample
- Internal and external links listed
- Length, format, call to action and deadline set
- Definition of done written, and all reviewers have seen the brief
The takeaway
A one-page content brief is twelve short answers, written before the draft, that everyone involved can read in two minutes. Start with the core question and the reader, check that the site doesn’t already answer it, and add a definition of done so the draft can be judged. Share it with reviewers, then improve the template after each project.
