Start with the job the page needs to do
A content brief is a short plan for one page. It gives the writer, reviewer and page builder a shared answer to a basic question: what should a visitor be able to do after reading this? For a small organization, the brief does not need to be a long document. A page of notes is often enough if it prevents conflicting expectations and repeated rewrites.
Write down the page type, its intended reader and its primary goal. A community workshop page, for example, might serve people deciding whether to attend. Its goal could be to help them understand the session and register. That is more useful than a vague goal such as “raise awareness,” because it suggests what information belongs on the page and what action should be easy to find.
Choose one main action, then note any secondary actions. A visitor who is not ready to register might need a contact option or a link to accessibility information. Keeping those options in the brief helps the team support different needs without making every link compete for attention.
Describe the reader and their questions
You do not need an elaborate audience profile. Describe the situation that brings someone to the page and what they may already know. For the workshop page, a reader may have heard the event name but not know who it is for, where it takes place or whether it costs anything. Avoid treating internal terminology as familiar to everyone.
List the questions the page must answer, in the rough order a visitor would ask them. For an event, that might be: What will I learn? Is it suitable for me? When and where is it? How do I sign up? What if I need assistance? This list becomes a practical check on the draft: if a reader cannot find an answer, the page is not finished.
Include any concerns that could stop someone taking the next step. Perhaps the registration form asks for details that need an explanation, or attendance requires equipment. Naming these points early encourages clear, reassuring copy instead of leaving important details to a separate email exchange.
Set the content boundaries and page structure
A good brief says what to include and what to leave out. Identify the essential facts, the person responsible for confirming them and any related pages that should carry supporting detail. On a workshop page, the date, location, cost and registration method are essential. A full history of the organization probably is not; a short link to an about page may serve readers better.
Sketch a simple heading outline rather than drafting every sentence. For example: workshop overview, who it is for, practical details, what to expect and how to register. Place the most decision-making information near the top. If the team has a preferred page template, note which parts of the outline fit its existing fields and which may need a different layout.
Add a short voice note, such as “welcoming and direct; explain specialist terms.” This is more actionable than asking for copy that is simply “engaging.” If search visibility matters, record the everyday phrase a reader might use to find the page, but write headings to clarify the content rather than repeating a phrase unnaturally.
Build accessibility into the brief
Content choices affect whether people can use a page. Ask the writer to use descriptive headings, short paragraphs and links that make sense out of context. “Register for the workshop” tells a reader more than “Click here.” If the page includes an image, note what it adds and whether it needs a text description; a purely decorative image may not need one.
Also record details that make the offer itself easier to assess. An in-person event page may need venue access information, while an online session page may need to explain the format and any participation requirements. The brief should identify who can confirm these details rather than encouraging the writer to guess.
Keep the planned action clear in the page copy and in the form or button that follows it. If registration opens a lengthy form, say so where that context would help. A content brief cannot replace testing the finished page, but it can make these checks part of the work from the start.
Agree on review, ownership and a simple measure
Finish the brief with a workflow. Name who drafts the page, who checks factual details and who gives final approval. Ask reviewers to check the agreed goal and reader questions before suggesting stylistic changes. This keeps feedback focused and reduces the chance that late additions obscure the main message.
Decide what would indicate that the page is helping, without expecting one number to tell the whole story. For a workshop page, the team might check whether visitors reach the registration link and note recurring questions sent by email. If people keep asking about location, the page may need a clearer practical-details section, even if it receives plenty of visits.
Finally, record when the content should be checked again. A one-off event page needs attention after the event, while an evergreen service page may only need a scheduled accuracy review. The brief is useful when someone can pick it up later, understand why the page exists and update it without starting the planning process over.
