Why this matters more than you think
Agencies write the brief if you don't, and they write it for the work they want to make, not the work you need to ship. The brief you provide becomes the criteria the work is judged against, the basis for revision conversations, and the line between "in scope" and "out of scope" — which is the line that determines whether the project finishes on budget or doesn't.
The seven sections every brief needs
Skipping any of them creates a gap the agency will fill with assumptions. The shorter the brief, the more important it is that every section is present.
1. The business context — three sentences
What the company does, who it serves, where it sits in the market today. The agency doesn't need your full company history; they need enough context to understand what success looks like for this business specifically. Three sentences is usually right.
2. The reason for the project — what's the problem this work is solving
Not "we need a new logo." Why do you need a new logo. "Our brand is being mistaken for [competitor], we're losing 3 pitches a quarter to them on the same shortlist, and our chairman wants this fixed before Q3 board." That's a brief an agency can do something with.
3. Audience — who specifically you're trying to reach
Not "young professionals." The actual humans. Their job, their decision context, what they're already aware of, what they currently use, what would make them switch. If you can't describe one person who fits the audience, the audience is too vague to design for.
4. Deliverables — what you actually need produced
List items, with quantities. "A logo system" is incomplete; "primary logo (horizontal + stacked), monogram, three colour variations, vector + raster export, brand book up to 30 pages" is the right level of specificity.
5. Constraints — what's fixed
Budget range. Launch date. Tech stack (for web work). Pre-existing assets that must stay. Languages required. Stakeholders who must approve. The agency designs around constraints; pretending you have none means they'll discover them halfway through and the project goes off-track.
6. References — what good looks like
Three to five examples of work you admire, with one sentence each on what specifically you admire about them. Not just style references — also pacing, tone of voice, layout, motion language. The references aren't the answer; they're a calibration tool so the agency knows what's in your taste range.
7. Decision-making — who picks
The single most-skipped section. "The CEO decides" vs. "The marketing committee decides" vs. "I decide and tell my team" produce wildly different processes. Name names where possible. The agency builds review schedules around this.
A working template
Adapt to the project — branding, web, motion, campaign. The skeleton stays the same.
Project: [name]
Date: [date] Project lead: [name and email] Deadline: [hard or soft, with reasoning]
Business context (3 sentences max)
What we do. Who we serve. Where we sit today.
Why this project, why now
The specific business problem this work is solving. Include any deadline drivers (event launch, fiscal year, regulatory milestone).
Audience
Who. What they currently know. What they currently use. What we want them to do after seeing the work.
Deliverables
Itemized list with quantities. Indicate which are launch-critical and which are nice-to-have.
Constraints
Budget range. Timeline. Tech stack. Languages. Stakeholders. Anything fixed that can't change.
References
3–5 specific examples with one sentence each on what you like about each.
Decision-making
Who reviews and approves. How many rounds before things get expensive.
Common mistakes that derail projects
- Adjective stew — "modern, minimalist, bold, fresh, friendly, professional" describes nothing
- Audience as demographic instead of behaviour — "women 25–44" tells the agency nothing useful
- References that are all the same — three minimalist sites isn't a calibration, it's an aesthetic preference
- Hidden constraints — "oh, also it has to work in Arabic" mentioned at week 6 is a project-killer
- No success criteria — if you can't say what good looks like, you can't say when the work is done
- Brief vs spec confusion — a brief explains what to make and why; a spec defines exactly how. Don't write specs in the brief or you'll get spec-shaped output.
The honest line
A great creative brief is rarely longer than two pages. The discipline of writing it tightly is part of why it works — every section forced you to be specific. Spend an hour on the brief and save four weeks on the project. The math is unambiguous.