A design brief needs to answer six things: the project’s goal, the audience, the scope of what’s included, the deliverables and formats, any existing brand constraints, and the timeline and budget. Most clients who hire a solo designer will not hand over a document covering all six unprompted. Many will say some version of “just make something nice,” which is not a brief at all, it’s a starting point for a conversation you have to run yourself. The core sections below matter, but the harder and more common problem is getting them out of a client who was never planning to write them down.
The Core Sections, In Order
A workable brief covers six things, and the order matters because each later section depends on the one before it being answered honestly rather than skipped.
| Section | What it needs to answer | What happens if it’s vague |
|---|---|---|
| Project goal | What the design needs to accomplish, not just what it should look like | Work optimizes for “looks nice” instead of the actual outcome |
| Audience | Who the design is actually for, specific enough to picture one person | Design tries to please everyone and lands for no one |
| Scope | What’s included in this engagement, and just as importantly what isn’t | The project quietly grows without anyone agreeing to the growth |
| Deliverables and formats | The exact files, sizes, and file types needed at the end | A finished design in the wrong format for how it’ll be used |
| Brand constraints | Existing colors, fonts, or guidelines that can’t be redesigned away | Work gets rejected late for conflicting with something that already existed |
| Timeline and budget | The two numbers that determine how much of the above is realistic | Scope and schedule mismatch discovered mid-project instead of before it |
This matches what most design-brief templates from project-management and design-tool vendors already cover. Getting explicit agreement on all six before starting work prevents the large majority of scope disputes that surface later, and the “what happens if it’s vague” column is the part most templates leave out. It’s also the reason to ask, not just to fill in a form.
Why “Just Make Something Nice” Is a Symptom, Not a Brief
When a client hands over a vague instruction instead of specifics, it’s rarely because they don’t care. More often they don’t know what a brief is supposed to contain, or they assume that’s the designer’s job to figure out. Treating “make something nice” as a lack of direction to fight against is the wrong frame. It’s a signal that the brief has to be built through structured questions rather than received ready-made, and building it that way is a normal, expected part of running a solo design practice, not a workaround for a difficult client.
Running a Designer-Led Brief
Instead of sending a blank template and waiting, a designer-led brief works the other way around: you run a short structured conversation covering the six sections above, take notes, and write the brief yourself. Then you send that document back to the client to confirm or correct, rather than asking them to originate it from nothing. This does two things a blank template can’t. It gets you a usable brief even from a client who was never going to fill one out unprompted, and it puts the burden of correcting a wrong assumption on the client, which is a much easier ask than “please write me a brief.”
The specific question order that makes this conversation efficient, including which questions catch the most expensive gaps, is covered in the questions to ask before you open the design file.
When the Client Won’t Commit to an Answer
A specific and common non-answer is “you’re the expert, you decide.” It sounds like flexibility but it leaves you making decisions the client can later say they never agreed to. The fix is not to re-ask the same open question, it’s to narrow the choice: show two concrete, contrasting real-world reference points and ask which one is closer to what they have in mind. A specific choice between two things is much easier for a non-designer to answer than an open-ended one, and the answer becomes part of the written brief either way.
Scaling the Brief to the Job
Not every project needs the full six sections written out at the same depth. A single-logo job might get one or two sentences per section and still cover all six; a full brand identity or a multi-page site genuinely needs more detail in scope and deliverables specifically, because that’s where ambiguity is most expensive on a larger job. The rule that doesn’t scale down, regardless of project size, is getting all six sections answered in some form before design work starts. A short brief that covers everything is far safer than a long brief that skips scope.
When the Brief Changes Mid-Project
A confirmed brief isn’t a permanent lock, clients legitimately learn things partway through a project that change what they need. The distinction that matters is between a genuine change and scope creep dressed up as a small tweak. When a client asks for something outside the confirmed brief, the response isn’t to refuse it or to quietly absorb it into the existing scope. It’s to name the change explicitly, “that wasn’t in the original brief, here’s what it adds,” and get agreement on the new terms before doing the work. This keeps the brief functioning as a real reference document throughout the project rather than a formality that gets ignored the moment something shifts.
Getting the Brief Back in Writing Before You Start
A brief that exists only as your own notes from a phone call is not yet a brief the client can be held to. Once you’ve written it up, send it back and get a specific confirmation, an email reply, a signed document, anything that puts the agreement somewhere other than your memory. This step is the same discipline that carries into the kickoff call, where the brief gets confirmed live rather than assumed: see how to run a kickoff call for a design project. It’s also the first checkpoint referenced in the full six-stage process at the design project, start to sign-off.
FAQ
What are the most important parts of a design brief?
Project goal, audience, scope, deliverables and formats, brand constraints, and timeline and budget. Getting agreement on all six before starting prevents most scope disputes that surface later in the project.
What if my client won’t write a design brief?
Run a short structured conversation covering the core sections yourself, write the brief based on their answers, and send it back for them to confirm or correct. This is normal for solo client work, not a sign of a difficult client.
How do I get specifics from a client who says “you decide”?
Narrow the question. Instead of asking open-ended, show two concrete, contrasting examples and ask which is closer. A specific choice is far easier to answer than an open one, and it gives you something concrete to record.
Should the brief be confirmed in writing?
Yes. A brief that exists only in your notes from a call isn’t something the client can be held to later. Get a written confirmation, even a short email reply, before starting design work.