You filled in the briefing form. Answered every question as honestly as you could. Three weeks later, the first designs arrive and none of them land right. The brand feels off. The layout is unfamiliar. You spend a Tuesday afternoon writing a long email trying to explain what you actually meant.
This happens more often than any agency will tell you. And the brief is almost always where it started to go wrong.
Design is a conversation, not a form submission. But the brief is where that conversation begins, and if it doesn't give the agency what they actually need, the creative work that follows reflects that gap. More feedback rounds, more frustration, more "yes, but could we just." The project takes longer than it should, and the result is shaped by misunderstanding rather than by your actual problem.
This post covers the six things a design brief genuinely needs. Not a checklist of obvious questions, but the specific gaps that consistently produce expensive revision rounds when they're left empty.
What a design brief actually does
Most clients treat the brief as admin. Paperwork that has to be completed before the real work starts. The agency sees it very differently.
Your brief is the only document both sides of the project will refer back to when they disagree about whether the work is right. And at some point in almost every project, both sides will disagree. A clear brief resolves that quickly. A vague one turns it into a negotiation.
Here is the thing most design guides get wrong: a brief does not describe what the design will look like. It describes the problem the design needs to solve. Those sound like the same thing. They are not.
"We want a modern, professional website" tells the agency what you want to see. "Our current site has a 72% bounce rate and the enquiries we get are low quality compared to our traffic" tells them what they need to fix. One asks them to interpret your aesthetic preferences. The other asks them to solve a business problem. The creative freedom that comes from the second brief produces better results almost every time.
A strong brief makes creative ambition possible. A weak one forces the agency to guess. Guessing is expensive for everyone.
1. A problem statement, not a solution description
The single most important part of any brief is the problem statement. It is also the part most clients skip or bury under aesthetic preferences.
"We want it to feel fresh" is not a problem statement. Neither is "we're looking for something modern and clean." Both of those tell the agency what the finished design should look like in your head. They give the designer a mood to interpret rather than a problem to solve, and the gap between your imagined mood and theirs is exactly where the revision cycles begin.
A strong problem statement explains why the project exists. What is broken, who it is failing, and what a good outcome would make possible. Some prompts that tend to surface the real problem: what is wrong with what you have now? Who is it failing and how? What do you want people to do when they arrive, and what are they actually doing instead?
The answers to those questions are your problem statement. They give the agency something real to work against. And when the first designs come back, both sides already know what success looks like, because you wrote it down at the start.
2. A description of your audience that a designer can use
"Professionals aged 30 to 55" is a demographic slice, not an audience description. It tells the designer almost nothing useful.
A useful audience description is specific about behaviour and mindset. What does the person already know when they arrive? What are they worried about? What would persuade them to take the next step? The designer is making decisions at every level about what that specific person experiences. Generic demographics produce generic design.
If you have analytics data, share it. Where do users drop off on your current site? Which pages perform best? Where do your best enquiries come from? Real behavioural data is more useful than any persona description you could write from memory.
You don't need a polished research document. A few paragraphs of honest observation about the people you're trying to reach will produce better work than a demographic table.
3. Reference materials, shared without prescription
Visual references are one of the most valuable things you can put in a brief. They are also one of the most misused.
"We like this website" is almost useless. "We like this website because the navigation is simple and the calls to action are never more than one scroll away" is useful. The difference is explanation. References without explanation leave the designer guessing at what specifically you want them to take from them.
The most common mistake is turning references into a specification. If you hand over five websites and ask the designer to combine the best elements of each, you are asking them to copy rather than create. The result looks like a pastiche and solves nobody's actual problem. Wrong brief, predictable outcome.
Since 2023, clients have had a new and genuinely useful option here. AI image tools including Midjourney, DALL-E, and Adobe Firefly let you generate a rough visual reference from a text description. You can show the agency a scene, a feeling, or a composition you cannot put into words. That changes the starting point of a briefing conversation in a meaningful way.
You are still explaining what the image is about, not handing over a finished design. But the ability to show rather than just describe removes a significant layer of creative guesswork.
If you have existing brand guidelines, include them. If you don't, say so clearly. That absence becomes part of the scope.
The test for every reference you include: can you explain why it is in the brief? If you cannot, it probably doesn't belong there.
4. Scope, outputs, and file formats
Scope creep almost never starts with bad intentions. It starts with outputs that were never specified in the first place.
Every design project should list exactly what is included before work begins. Not in general terms. Specifically. For a website: which pages, how many, whether mobile variants are in scope. For a brand project: the logo in how many formats, whether social media templates are included, whether print assets are part of the brief.
File formats matter and are regularly left out. Will you need editable source files? SVG for the web, CMYK PDF for print, WebP for the site? If you are working with a web design agency, they should be proposing these as part of the scope, but the brief is where you surface any specific requirements you know you will need.
Anything vague here becomes a difficult conversation mid-project when the timeline is already tight.
5. An honest budget and timeline
Most guides tell you to include your budget. Very few explain why.
Withholding your budget doesn't protect you from being overcharged. What it does is force the agency to guess. They don't know whether you're thinking about a focused rebrand or a full brand identity project. Without that information, they scope to what they think the average client in your situation might spend. That might be too much or too little for what you actually need.
A budget range gives the agency real constraints to work within. What's ambitious within your ceiling? What would be ideal if budget stretched? That information produces a proposal that's actually useful to you. Without it, you get a proposal shaped by the agency's assumptions.
Timelines work similarly. Work backwards from the date that genuinely matters, not the date you'd ideally like it finished. Is there a hard launch tied to an event, a campaign, or a financial period? That is different from "as soon as possible." Say which one applies and the agency can plan around it. The brief should name the hard deadline if one exists, the target completion date, and any milestones in between that matter.
6. Who approves the work, and how
This is the section almost every brief leaves out entirely. It is also the one that most often determines whether a project ends well or badly.
The number of people in your approval chain directly affects how many revision rounds a project will take. If feedback goes from one person, gets reviewed by a manager, then goes to a board for final sign-off, each stage is a potential reset of the previous round's decisions. Agencies quote for projects, not for cycles of rework.
Your brief should name a single point of contact on the client side. One person who collects and consolidates feedback before it returns to the agency. That doesn't mean others don't have input; it means one person is responsible for turning that input into a clear, consolidated response.
State how many rounds of feedback are expected. Two or three is typical for a well-run project. More than that usually points to an unclear brief or an unclear approval process. D&AD guidance on briefing creative teams consistently identifies this as the most underspecified element of any brief. Define the approval process upfront and revision rounds reduce significantly.
What's changed since AI design tools arrived
The original version of this post was written in 2023, before AI image generation became part of everyday creative workflows. Some of what belongs in a brief has changed since then.
AI tools including Midjourney, DALL-E, and Adobe Firefly are now standard in many agencies' processes. They are used for generating initial concept directions quickly, exploring visual approaches before committing to detailed work, and producing reference imagery at early project stages. Some clients now use them when putting together their own briefs.
This changes a couple of things practically. First, you can generate rough visual references rather than just describe them. An AI-generated image that communicates a mood or layout direction is a useful starting point, even if the result looks nothing like the finished design. The value is in the conversation it opens.
Second, briefing AI tools is rapidly becoming its own discipline. The skills it requires are identical to what makes a human design brief work: specificity, a problem rather than a solution, and clarity about who you are designing for. If you have ever tried to get useful output from Midjourney with a vague prompt, you have experienced exactly what a designer experiences when they receive a vague brief. Same problem, different context.
Some clients now use ChatGPT to help structure their brief. That is a reasonable starting point. But no AI can fill in the parts that actually matter: your specific business problem, your audience behaviour data, your budget, the one hard deadline everything has to work around. Those have to come from you.
Where to start if you have no idea what to say
Start with the problem.
What is wrong with what you currently have, and who is suffering because of it? Answer that in plain language, without worrying about how it sounds. Getting the core problem written down is the most important thing, because everything else in the brief exists to help the agency solve it.
If you have absolutely no idea where to begin, book a discovery call before you write anything. Most reputable agencies will help you structure the brief from a conversation. The document that emerges is almost always better than one produced by filling in a cold template alone.
Before that call, gather what you have. A Google Analytics report if you have access to it. Your current brand guidelines if they exist. A list of competitor sites you admire or want to stand apart from. You don't need strong opinions about any of it yet. Having it in front of you when the conversation starts is enough.
A brief does not have to be long. One well-written page covering all six elements above is more useful to a brand identity agency than six unfocused pages circling the same point. The Design Council has long argued that brief quality correlates more closely with project success than budget or portfolio credentials. Length is not quality.
What a well-briefed project actually looks like
The difference shows up most clearly in revision rounds. Two or three instead of six or seven is a realistic outcome when the brief is clear. Not because the agency is faster, but because both sides started with the same understanding of what the work needed to achieve.
Creative ambition also increases when the constraints are clear from the start. A designer who understands the real problem has something to design toward. A designer who is guessing at what you want to see is designing to avoid rejection. Those produce very different results.
For design that actually converts visitors into customers, the brief is where the conversion goal has to be established. Not in the first feedback round.
If you are about to commission a design project and want to understand what the finished site should achieve before you start building it, the Traffic Projection Report maps the traffic and enquiry opportunity your site could realistically be generating. It gives you a clearer sense of what success looks like before you write the brief, which means the brief has a target to aim at.
Traffic Projection Report — find out what your site could be doing before you decide what to build.
Frequently asked questions about writing a design brief
How long should a design brief be?
One to three pages is typical for most design projects. The length should reflect the complexity of the project, not the volume of information you have managed to gather. A concise brief covering all six elements clearly is more useful than a long document where the key points are buried in background. If a brief runs beyond five pages, it usually means the scope or the problem statement has not yet been clarified.
Should I include my budget in a design brief?
Yes. Withholding your budget does not give you negotiating power; it forces the agency to scope the project without knowing the real constraints. A budget range, even a broad one, gives the agency the information they need to propose something realistic. Without it, proposals are shaped by the agency's assumptions about what you might be willing to spend, which may differ significantly from what you actually have available.
What is the difference between a design brief and a creative brief?
A design brief focuses on the specific outputs and constraints of a design project: the problem to solve, the audience, the scope, the budget, the timeline. A creative brief is typically broader and sits upstream of the design work, covering the strategic and communications goals behind a campaign. For a website redesign or brand project, a design brief is what the agency needs to begin. For a broader marketing campaign, a creative brief usually comes first and the design brief follows from it.
What happens if I don't have brand guidelines?
Be honest about it in the brief. Many businesses commission design work precisely because they don't yet have a coherent visual identity, and that is a completely normal starting point. The absence of brand guidelines may expand the scope of the project, since the agency may need to develop the visual language as part of the work. Being upfront about this in the brief means they can account for it in the proposal rather than discovering it mid-project.
