What a creative brief is
A creative brief is a short document, ideally one page, that states what a project is for, who it serves and what limits apply. It is written before the work begins and shared with everyone involved. When people later disagree about direction or wonder whether an idea fits, the brief gives them something to point to.
Briefs are used for videos, articles, illustrations, campaigns, podcast series and nearly any other creative work. A solo creator can write one for themselves. It can feel unnecessary when no one else is involved, but writing it forces decisions that would otherwise be made halfway through the work, when changes cost more.
Why keep it to one page
Length is not a virtue here. A long brief tends to go unread, and a brief that tries to specify everything leaves no room for creativity. One page forces choices about what matters most. If you cannot state the purpose in a sentence or two, the project may not be ready to start.
What to include
The exact headings vary, but most useful briefs cover the following.
Project name and summary. A sentence or two describing what will be made.
Purpose. Why is this being made? What should be different afterward? Aim for one main purpose. For example, “help first-time readers understand how a recipe card is organized” is clearer than “inform and entertain everyone.”
Audience. Who is it for? Describe them in practical terms: what they already know, what they need, where and how they will encounter the piece. Your own audience research or a short reader profile can feed this section. Avoid “the general public,” which gives no guidance.
Key message or takeaway. What should the audience remember or do? Limit it to one or two points.
Tone and style. How should it sound and look? A few adjectives are useful, such as “friendly, plain and unhurried,” ideally with a note on what to avoid. Reference examples can help, as long as you describe what you like about them and do not ask anyone to copy them.
Format and deliverables. Exactly what will be produced: length, file types, number of items, sizes and where they will be published. Include accessibility requirements here, such as captions for video or text descriptions for images.
Constraints. Deadlines, budget, available time, tools, legal or ethical limits, and anything that must be included or avoided. Mention rights and permissions: which material may be used, who needs to be credited and whether people appearing in the work have agreed.
Roles and approvals. Who is doing what, who gives feedback and who has the final say. This single item prevents a large share of project disputes.
Timeline. Key dates for drafts, reviews and delivery. Keep it realistic.
How success will be judged. In plain terms, how will you know it worked? It may be a qualitative judgment, such as whether reviewers found the piece clear, or a simple measure. Be cautious about promising specific numbers, since results vary.
A short hypothetical example
Imagine a small community group making a two-minute video about a library’s free workshops. A brief might read:
- Purpose: Help local adults learn that the workshops are free and open to beginners.
- Audience: Adults in the neighborhood who have not visited the library recently; many read on phones, some prefer large print.
- Key message: The workshops are free, no experience is needed, and sign-up is easy.
- Tone: Warm and plain; no jargon.
- Format: One video of about two minutes, with captions, plus a text version of the schedule.
- Constraints: Complete in six weeks; volunteers only; anyone shown on camera must agree in advance.
- Approvals: The coordinator approves the script; the library manager approves the final cut.
This example is invented for illustration. The point is that every line makes a later decision easier.
Writing it well
- Be specific. Replace “engaging” with a description of what the audience will feel or do.
- Use plain language. The brief should be understood by someone who has never seen the project.
- Separate facts from assumptions. If you believe something about the audience but have not checked, say so.
- Include what the project is not. Stating boundaries stops scope from growing quietly.
- Get input. Ask the people doing the work or affected by it to read the draft and point out gaps.
Using the brief during the project
A brief is only useful if people go back to it. Check drafts against the purpose and audience at each review. When someone suggests a new idea, ask whether it serves the brief. If it does not, you can add it to an idea bank for later.
Briefs can change. If circumstances shift, update the document, note the date and tell everyone. A changed brief is better than a project drifting away from an outdated one without anyone noticing. Brief changes also connect to the question of wider planning, which content strategy handles across many pieces.
When a brief is not enough
A brief does not guarantee a good result. It cannot substitute for skill, feedback or time. It also cannot predict everything; surprises come up. But a clear brief makes surprises easier to handle, because the team has agreed on what matters. Spending an hour on it before starting is often among the most efficient uses of time in a project.