How to Brief a Graphic Designer
A good design brief does most of the work before a designer opens a file. It tells them what the project actually needs to achieve, who it needs to work for, and what "done well" looks like, so the first round of concepts lands close to right instead of starting from a guess. Most of what goes wrong in a design project traces back to a brief that skipped one of those three things.
This isn't a form to fill in mechanically. It's a way of thinking through the project before you hand it over, so the person doing the work has what they need to do it properly the first time.
- A brief needs three things at minimum: the business context, the practical scope, and how the result will be judged.
- Vague references ("modern", "clean", "pop") slow projects down more than no references at all. Specific examples of what you like and don't like do the actual work.
- The clearer the brief, the tighter the quote. Loosely scoped projects get priced with buffer built in, because the designer is pricing for the unknowns.
- Revisions should be agreed before the work starts, not negotiated after the first round lands.
- A one-page brief beats a ten-page one. Depth matters more than length.
Why most design briefs fail
The common failure isn't too little information, it's the wrong kind. Business owners often over-explain what they want the design to look like and under-explain what it needs to do. A designer can work with "we need this to read as premium to a 45-plus audience buying a considered purchase" far more easily than "we want it to look modern and clean", because the first sentence gives them a decision-making framework and the second gives them nothing to push against.
The other recurring problem is scope drift baked in from the start. A brief that says "logo design" but means "logo, business card, letterhead, and social templates" isn't a small brief with extras, it's a different project. Naming the full deliverable list upfront is what keeps the quote accurate and the timeline realistic.
What to include in a design brief
Business context
Start with what the business actually does, who it sells to, and where it sits in its market. A designer working blind on brand tone will default to safe, generic choices. A designer who knows you're the higher-priced, more considered option in a market full of cheap competitors will design differently from the first concept.
Include how long the business has been running, whether this is a refresh or a first-time build, and anything about the competitive landscape that matters. If there's a competitor whose visual identity you specifically don't want to resemble, say so directly.
Project scope and deliverables
List exactly what you need, not just the headline item. "Logo" and "logo plus a full brand identity system" are priced and executed differently, and a designer can't quote accurately against an assumption. If you're not sure yet whether you need the full system, say that too. It's a reasonable starting position, but it needs to be stated rather than left implied.
Specify file formats and end use if you know them: print, web, signage, merchandise, social. A logo designed only for a website favicon behaves differently to one that needs to work embossed on a product box.
Audience and use case
Name who the design needs to work for, specifically. "Everyone" isn't an audience. "Tradies aged 30 to 55 comparing quotes on their phone" is. The more concrete the audience, the more the designer has to work with when making decisions about tone, colour, and complexity.
Where the design will actually be seen matters as much as who's seeing it. A mark that needs to read clearly on a ute signwritten from thirty metres away has different constraints to one that only ever appears on a business card.
Style references and things to avoid
References do more work than descriptions. Three to five examples of visual styles you respond to, with a sentence on what specifically you like about each, gives a designer something concrete to interpret. "I like the colour restraint in this one" is more useful than the reference image alone, because it tells the designer which part of it mattered to you.
Equally useful: examples of what you don't want, and why. A short list of competitors or styles to avoid resembling saves a full round of revisions that would otherwise be spent finding that out the hard way.
Budget and timeline
State a budget range, even an approximate one. Designers scope differently for a $500 job than a $5,000 one, and a brief with no budget indication forces a guess that's rarely accurate in either direction. If budget is genuinely open and quality is the priority, say that explicitly, since it changes how the designer approaches the work.
Give a real deadline, not an aspirational one. If there's a hard external date (a launch, a print deadline, an event), name it and explain why it's fixed. Soft deadlines dressed up as hard ones tend to get treated as negotiable, which causes friction later.
Revision expectations
Agree on how many rounds of revision are included before work starts, not after the first concepts land. Two to three rounds is typical for most projects. State this in the brief so it's part of the agreement both sides are working from, rather than something that gets negotiated mid-project when expectations have already diverged.
How your brief affects the quote you get
A tight brief and a vague one produce different numbers for the same nominal project, and the gap isn't padding, it's the designer pricing the uncertainty. A designer working from "logo design, unclear scope, no references, open timeline" has to quote for the version of the project that takes longest to land, because that's the realistic risk. A designer working from a brief with clear deliverables, real references, and a defined revision count can quote tighter, because most of the guesswork has already been removed.
This is worth knowing before you request quotes from multiple designers, since comparing prices only tells you something useful if everyone quoted against the same brief. Send the same information to each one.
A simple brief template
Use this as a starting structure, not a rigid form. Adjust it to the size of the project.
Business: What you do, who you sell to, how long you've operated, what's changing.
Project: What you need designed, and the full list of deliverables and formats.
Audience: Who the design needs to work for, and where they'll encounter it.
References: Three to five examples of styles you respond to, with a note on what you like about each. Include anything you specifically want to avoid.
Budget: A range, even approximate.
Timeline: A real deadline, and whether it's fixed or flexible.
Revisions: How many rounds you expect to be included.
Decision-maker: Who signs off on the final design, if it isn't you.
Common mistakes to avoid
Sending reference images with no explanation of what you like about them leaves the designer guessing which element mattered. A folder of ten unrelated references without commentary is close to no references at all.
Leaving the audience vague because "it's for everyone" almost always means the design ends up speaking to no one in particular. Every strong piece of design work has a specific person in mind, even when the business itself serves a broad market.
Treating the brief as fixed once it's sent. A brief is a starting point for a conversation, not a locked specification. If a designer asks a clarifying question, that's a sign the brief is being read properly, not a sign it was written badly.
FAQs
- How long should a design brief be?
- Most briefs work best at one to two pages. Depth on the few things that matter (business context, scope, audience, references) beats length padded with detail that doesn't change how the work gets done.
- Do I need a formal document, or can I just explain it over a call?
- A call works, but write it down afterwards. A brief that only exists as a conversation gets reinterpreted differently by both sides over the course of a project. A short written summary, even five bullet points, keeps everyone working from the same version.
- What if I don't know exactly what I want yet?
- Say that in the brief rather than guessing. "I know the problem I'm solving but not the visual direction yet" is a legitimate starting brief, and a good designer will use references and questions to narrow it down with you rather than needing it pre-solved.
- Should I include a budget if I'm not sure what things cost?
- Yes, even a rough range. If you need a starting point, logo design pricing in Australia breaks down what drives cost at different budget levels, which can help you land on a realistic range before you brief anyone.
- Can I brief more than one designer with the same document?
- Yes, and it's worth doing. Send the identical brief to each designer you're getting quotes from. It's the only way to compare quotes fairly, since a vague or inconsistent brief produces wildly different numbers depending on what each designer assumed.
Design Junction doesn't take briefs or offer design services, more on why here. For more resources like this, browse the tools and guides collection, or get in touch if there's a topic you'd like covered.