A weak brief is the single biggest reason design projects run over budget, miss deadlines, and end up in endless rounds of "make the logo bigger" revisions. Agencies don't fail because they lack talent, they fail because they're working with incomplete information, guessing at goals that were never written down, and trying to read a client's mind instead of a document.
The good news: writing a strong creative brief is a learnable skill, not a mysterious art. This guide walks through exactly what to include, what to leave out, how much detail is "enough," and how to avoid the mistakes that turn a six-week project into a six-month one.
Whether you're briefing an agency for a full brand identity, a website redesign, a marketing campaign, or a single landing page, the same core principles apply. Let's get into it.
Why a Proper Brief Matters More Than You Think
Design agencies don't bill by the hour of talent, they bill by the hour of clarity. Every ambiguous instruction, missing detail, or assumption left unstated gets resolved eventually, but it gets resolved through email threads, revision rounds, and change orders instead of through a document that took an afternoon to write.
A few patterns worth sitting with:
- Industry surveys of design and marketing agencies consistently name "unclear client expectations" and "scope creep" among the top reasons projects go over budget or miss deadlines.
- Agencies routinely report that most revision requests trace back to information that was never in the original brief, not to designers misunderstanding clear direction.
- Projects that start with a written, agreed-upon brief tend to need far fewer rounds of revisions than those that start with a verbal conversation or a short email.
A brief is not paperwork. It's the cheapest insurance you can buy against a project going sideways. It also protects the relationship: when goals and constraints are documented upfront, disagreements later become "let's check what we agreed" conversations instead of "that's not what I meant" conversations.
What a Design Brief Actually Is (and Isn't)
A creative brief is a written document that tells an agency what you need, why you need it, who it's for, and how success will be measured, without prescribing exactly how the agency should design it.
That last part matters. A brief is not:
- A pixel-by-pixel description of the layout you want
- A list of your personal color preferences with no reasoning behind them
- A copy-paste of a competitor's website with "make it like this"
- A one-line email that says "we need a new logo, something modern"
Think of it as the difference between telling a chef "make this taste like my grandmother's cooking, using these five ingredients, for six people, ready by 7pm" versus handing them a photo of a finished plate and saying "just make it look like this." The first gives a professional room to apply their expertise toward a clear outcome. The second either gets you a shallow copy or forces the chef to guess at everything that photo doesn't show, the seasoning, the technique, the reasoning.
Who Should Be Involved in Writing the Brief
Before you open a blank document, get the right people in the room, or at least their input captured. A brief written by one person in isolation is a common source of surprises later, when a stakeholder who wasn't consulted sees the first draft and says "this isn't what we're about at all."
| Stakeholder | What they contribute |
|---|---|
| Marketing / brand lead | Positioning, messaging, target audience, brand voice |
| Sales team | What customers actually ask, common objections, competitor comparisons |
| Product / founder | Vision, non-negotiables, long-term direction |
| Finance / ops | Budget ceiling, timeline constraints |
| Customer-facing staff | Real customer language, pain points, FAQs |
| Legal / compliance | Regulatory constraints, trademark issues, mandatory disclosures |
You don't need a twelve-person committee, that creates its own problems. But a five-minute conversation with sales or customer support before you write the brief often surfaces insights that would otherwise never make it to the agency.
The Core Components of a Strong Design Brief
Below is the structure most experienced agencies wish every client would use. Not every project needs every section in full depth, but skipping a section should be a deliberate choice, not an oversight.
1. Project Overview and Background
Start with context. Who are you, what does your business do, and why is this project happening now? An agency that understands your business model, revenue streams, and market position will make sharper design decisions than one that only sees the deliverable in isolation.
Include:
- A short company summary (a paragraph is enough)
- What prompted this project (rebrand after a merger, new product launch, outdated website, expansion into a new market, etc.)
- Anything unusual about your business the agency should know upfront
2. Goals and Objectives
This is the most important section in the entire brief, and the one most often written poorly. "We want a modern website" is not a goal, it's a style preference disguised as one.
A real goal answers: what should be different after this project than before it?
Good examples:
- Increase demo requests from the homepage by making the value proposition clear within 5 seconds of landing
- Reposition the brand as a premium option to justify a price increase already planned for next quarter
- Reduce cart abandonment during checkout, currently at 68%
- Unify three regional sub-brands under one visual identity ahead of a global product launch
Weak examples to avoid:
- "Make it look more professional"
- "We want something that pops"
- "Just make it better than our current one"
If you're struggling to articulate the goal, ask yourself: if this project is wildly successful, what will have changed in six months? The answer to that question is your objective.
3. Target Audience
Designers make hundreds of small decisions, typography weight, color saturation, spacing, tone of copy, and every one of those decisions should be filtered through "who is this for?" Without a clear audience, an agency defaults to designing for a generic, imagined user, which usually means designing for no one in particular.
Include as much of the following as you have:
- Demographics (age range, profession, income bracket, geography), only where relevant to the decision
- Psychographics (values, motivations, what they care about)
- Where they currently encounter your brand (search, social, referral, in-person)
- What they know and don't know about your category
- A short persona or two, if you have them
- What a competitor or comparable brand they already like looks like, and why
If you serve multiple distinct audiences (e.g., a B2B software company selling to both IT admins and finance executives), say so explicitly and note whether the design needs to serve both simultaneously or is primarily aimed at one.
4. Scope of Work
Vague scope is the number one driver of change orders and disputes over "extra" work. Be explicit about exactly what is and isn't included.
Example scope table, website project:
| Item | In scope | Out of scope |
|---|---|---|
| Unique page templates | 6 (home, about, product, pricing, blog, contact) | Additional landing pages |
| Copywriting | Editing existing copy | Writing copy from scratch |
| Photography | Selecting stock images | Original photoshoot |
| CMS setup | Yes, on chosen platform | Custom backend development |
| Responsive design | Desktop, tablet, mobile | Native app design |
| Revision rounds | 2 rounds included | Additional rounds billed hourly |
Doing this for your own project, even in a simplified form, removes the single most common source of friction between clients and agencies.
5. Deliverables
List exactly what you expect to receive at the end of the project, in what format, and in what file types. This sounds obvious, but it's astonishing how often "deliverables" turns out to mean different things to the client and the agency.
Example deliverables list for a brand identity project:
- Primary and secondary logo, in vector (.ai/.eps), .svg, .png (transparent), and .jpg formats
- Full brand guidelines document (color codes, typography, logo usage rules, spacing)
- Business card and letterhead templates
- Social media profile and cover image templates
- Source files (editable, not just exports)
If you need source files (not just final exports), say so in the brief, this is sometimes a separate negotiation depending on the agency's standard contract.
6. Brand Identity and Existing Assets
If you already have brand guidelines, a style guide, past design work, or even just a rough sense of "colors we like and colors we hate," share it. Agencies aren't starting from zero even on a full rebrand, there's almost always something to build on or deliberately depart from.
Provide, if available:
- Existing logo files and brand guidelines
- Brand voice / tone documentation
- Examples of past marketing materials
- Any legal or trademark restrictions on colors, names, or imagery
- Accessibility requirements (e.g., WCAG contrast compliance)
7. Competitive and Inspirational References
References are powerful, but they need context or they backfire. "We like this" without explanation gets you a surface-level copy of someone else's brand. "We like this because the typography feels confident without being aggressive, which matches how we want to come across" gives the agency something they can actually apply.
| Reference | What we like about it | What we want to avoid |
|---|---|---|
| Competitor A's website | Clean navigation, clear pricing table | Feels too corporate / cold for our brand |
| Brand B's Instagram | Photography style, color palette | Their messaging is too playful for us |
| Our current site | Nothing, starting fresh | Cluttered layout, outdated typography |
Always include at least one "avoid" reference. Knowing what you don't want is often more useful to a designer than knowing what you do.
8. Tone, Voice, and Personality
If your brand were a person at a party, how would they act? This exercise sounds soft, but it translates directly into design decisions, a "playful and irreverent" brand gets different typography, color saturation, and spacing than a "quietly confident and premium" one.
A useful shorthand agencies often ask for is a set of personality sliders. Mark where your brand sits on each spectrum:
- Playful ←—●———→ Serious
- Bold ←———●——→ Understated
- Modern ←—●———→ Classic
- Minimal ←———●——→ Maximalist
- Luxury ←————●→ Accessible
This takes two minutes and prevents an entire category of "this isn't us" feedback later.
9. Technical Requirements
For anything involving a website, app, or digital product, technical constraints shape design decisions from the start, retrofitting a beautiful design onto a platform it wasn't designed for is expensive and often ugly.
Cover:
- Platform / CMS (WordPress, Webflow, Shopify, custom-built, etc.)
- Any existing tech stack constraints
- Integration requirements (CRM, email platform, payment processor, analytics)
- Browser and device support requirements
- Accessibility standards you need to meet (WCAG 2.1 AA is the common baseline)
- Page speed or performance requirements
10. Budget
This is the section clients most often want to leave blank or vague, out of fear of "overpaying" if they reveal a number. In practice, withholding budget rarely saves money, it just means agencies either propose scope that doesn't fit what you can spend, or you waste weeks going back and forth on proposals before anyone finds out the numbers were never compatible.
You don't need to reveal your absolute maximum, but a realistic range lets an agency propose the right scope from the first conversation, instead of a scope built for a budget three times larger or smaller than yours.
If you genuinely don't know what a project like this should cost, say that directly and ask the agency to propose two or three scope options at different price points. Most agencies are glad to do this, it's far better than pricing something perfectly and then hearing "that's way outside what we had in mind" after a full proposal has been written.
11. Timeline and Key Dates
List any date that isn't flexible, a product launch, an investor meeting, a trade show, a seasonal sales window, and be honest about which dates are hard deadlines versus soft targets. Agencies build in buffer for revisions and approvals; if you compress that buffer by treating every date as equally fixed, quality is usually what gets sacrificed first.
| Milestone | Target date | Flexible? |
|---|---|---|
| Kickoff call | [Date] | No |
| Discovery / research complete | [Date] | Slightly |
| First concepts presented | [Date] | Slightly |
| Feedback returned | [Date + 5 business days] | No, depends on your team |
| Final design approved | [Date] | No |
| Launch / go-live | [Date] | No, hard deadline |
12. Approval Process
Name the single person who has final sign-off authority. This is one of the most overlooked parts of a brief and one of the most damaging when it's missing. Agencies routinely encounter a project that gets "approved" by one stakeholder, only to have a more senior person weigh in during a later round with sweeping changes.
Answer clearly:
- Who is the single point of contact for feedback?
- Who has final approval authority?
- How many people need to sign off before feedback is considered "final"?
- What is the process for consolidating feedback from multiple stakeholders before it reaches the agency?
Consolidate feedback before it goes to the agency. Nothing slows a project down like five stakeholders sending five separate, sometimes contradictory rounds of comments. Assign one internal person to gather all feedback, resolve internal disagreements first, and send the agency a single, prioritized list.
A Sample Brief Outline You Can Copy
Here's a condensed template you can adapt for almost any design project, brand identity, website, packaging, or campaign.
- Project Overview, Who we are, what prompted this project
- Goals, What success looks like, in measurable terms
- Target Audience, Who this is for, and what they currently think/feel
- Scope of Work, What's included, what's explicitly excluded
- Deliverables, Exact files, formats, and quantities expected
- Existing Assets, Brand guidelines, past materials, legal constraints
- References, What we like/dislike, and why
- Tone & Personality, How the brand should feel
- Technical Requirements, Platform, integrations, accessibility, performance
- Budget Range, Realistic ceiling and floor
- Timeline, Key dates, hard vs. soft deadlines
- Approval Process, Single point of contact, sign-off authority
Even a rough first draft using this outline will put you ahead of the vast majority of briefs agencies receive.
Common Mistakes to Avoid
Being too prescriptive about execution
There's a difference between giving direction and designing the project yourself before you've hired anyone to design it. "We want the header in blue, Arial font, logo on the left, navigation on the right" removes the very expertise you're paying for. Describe the outcome and constraint; let the agency propose the execution.
Being too vague
The opposite failure is just as common. "Surprise us" or "you're the expert, just make it great" feels like it's giving creative freedom, but it actually gives the agency nothing to design toward. Freedom without direction produces generic work, because there's no specific problem being solved.
Skipping the "why"
Every instruction in a brief should ideally have a reason attached. "Use a serif typeface" is an instruction. "We want to feel more established and trustworthy than we currently do, especially compared to a specific competitor" is a reason that lets the agency solve the problem, maybe with a serif typeface, maybe with something else entirely that achieves the same effect better.
Not including a real budget range
Covered above, but worth repeating: vague or withheld budgets waste more time than they save.
Treating the brief as final and unchangeable
A brief is a living document during the discovery phase. If an agency's initial questions surface a gap or contradiction in your thinking, that's the brief working as intended, not a sign you did it wrong. Expect a round of clarifying questions and be ready to update the document.
Forgetting internal alignment
If your own team disagrees about the target audience, the goal, or the brand tone, that disagreement doesn't disappear when you send the brief, it just resurfaces later, as confusing or contradictory feedback partway through the project. Resolve internal disagreements before the brief goes out, not during revisions.
Copy-pasting a generic template without customizing it
Templates (including this one) are a starting point, not a finished product. A brief filled with generic answers, "our audience is 25–45 year olds interested in quality", gives an agency almost nothing to work with. Specificity is what makes a brief useful.
What to Expect After You Send the Brief
A good agency won't just accept your brief at face value and start designing. Expect:
- A kickoff call to walk through the brief together and ask clarifying questions
- Follow-up questions, sometimes probing ones that reveal gaps in your own thinking, this is normal and valuable, not a red flag
- A restated understanding of the brief from the agency, often in the form of a proposal or discovery document, that you should read carefully and correct if anything is off
- A discovery or research phase before any visual concepts appear, especially for brand identity or larger website projects
If an agency skips straight to visual concepts without any of the above, that's often a sign they're pattern-matching to a template rather than solving your specific problem, worth asking about before the project goes further.
Brief Length: How Much Detail Is Enough?
There's no fixed word count, but as a rough guide:
| Project type | Typical brief length |
|---|---|
| Single landing page or small campaign asset | 1–2 pages |
| Full website design | 3–6 pages |
| Brand identity / full rebrand | 5–10 pages |
| Multi-channel campaign | 4–8 pages |
The right length is "as much as it takes to remove ambiguity, and not one page more." A 15-page brief that's mostly padding is arguably worse than a tight 3-page one, agencies have to extract the signal from the noise either way, and unnecessary length just makes that harder.
Final Checklist Before You Hit Send
Before sending your brief to an agency, run through this list:
- Goals are written as measurable outcomes, not style adjectives
- Target audience is specific enough that two different designers would picture the same person
- Scope of work explicitly states what's excluded, not just what's included
- Deliverables list exact file formats and quantities
- At least one "avoid" reference is included, not just "like" references
- Budget range is included, even if approximate
- Hard deadlines are distinguished from soft ones
- A single point of contact and final approver are named
- Internal stakeholders have already aligned on the answers before this goes out
- The brief has been reread by someone outside the project, to catch assumptions that seem obvious to you but aren't stated
Bringing It All Together
A great brief doesn't guarantee a great design, that still depends on finding the right agency and giving good feedback throughout the process. But a great brief removes the single biggest source of wasted time, wasted money, and frustration on both sides of the table: misunderstanding.
The upfront work of writing a real brief, gathering input, resolving internal disagreements, being specific about goals and honest about budget, usually takes a few hours. The alternative, working it all out through six rounds of revisions and a strained relationship with your agency, takes weeks and costs far more, in money and in the quality of what you end up with.
Write the brief your project deserves, and the rest of the process gets dramatically easier.