Writing a design brief your designer can actually act on: scope, references, and the approval path
Clear approval paths and annotated references prevent expensive design surprises.
Most design projects don't fail in execution. They fail somewhere in translation, in the gap between what a client imagined and what a designer received permission to build.
Here is how it usually goes. A designer opens a brief, reads three sentences about "making it pop" and "keeping it clean," scans a Pinterest board containing seventeen aesthetically irreconcilable images, and does what any rational professional does under the circumstances: they guess. The client, meanwhile, is somewhere across town confident they communicated something specific. Both parties will be surprised at the first review. Neither will fully understand why.
This is not a designer problem. It is a brief problem, and it is, with almost embarrassing regularity, avoidable.
Scope Is Not a Vibe
The most common error clients make is conflating the feeling they want with the work they are requesting. These are related. They are not interchangeable.
Scope answers concrete questions: what are the deliverables, exactly? What formats, what dimensions? How many concepts in the first round, and how many revision cycles are included before the engagement needs to be renegotiated? When a brief doesn't answer these, the designer answers them unilaterally, and the client discovers that answer during a deadline conversation nobody scheduled.
Because scope feels transactional, clients skip it. They're excited about the creative idea, and writing down "three logo lockups in vector format plus a one-page brand guide" feels pedestrian next to an inspiration board. I've watched this play out enough times to have stopped being surprised by it. The project kicks off on a wave of mutual enthusiasm, and the first review lands like a slow-motion collision that everyone should have seen coming. Vagueness isn't creative latitude. It is a disagreement waiting for the worst possible moment to surface.
A workable scope statement names the deliverables, specifies medium and file format, establishes how many initial concepts you want, defines what actually constitutes a revision, and sets a timeline with checkpoints. If that takes more than a page, the project is probably larger than the budget.
References Are Evidence, Not Atmosphere
This is where briefs go sideways in the most well-intentioned way possible. The client assembles a reference collection they're genuinely proud of. It has texture, range, a certain curatorial confidence. The problem is that it is not telling the story they think it's telling.
A single reference image communicates several things simultaneously: color palette, typographic register, layout density, compositional rhythm, tonal personality. Send ten references, each one contradicting the others across those dimensions, and the designer must now reconcile conflicts the client didn't know they'd introduced. I've sat in reviews where a client said, with complete sincerity, "I don't know why this doesn't feel right, it has everything I asked for." It had everything from the board, yes. The board just happened to contain four different industries, two distinct eras, and at least one unresolved identity question.
References are evidence. They tell the designer what visual language you already understand and respond to, which is genuinely useful. That usefulness compounds when references are annotated, not exhaustively, but specifically. "The typography here, not the color." "I like the spatial breathing room in this layout; the photography is irrelevant." One sentence eliminates a whole category of guesswork.
Some argue that annotating references defeats the purpose of hiring a designer with their own aesthetic judgment. That argument has merit and also slightly misses the point. You are not directing the designer's sensibility; you are establishing a shared working vocabulary so their judgment has somewhere defensible to land. The annotation is not a creative constraint. It is a starting coordinate.
The Approval Path Is Where Projects Actually Die
Scope defines the work. References calibrate the vision. The approval path determines whether any of that survives contact with organizational reality.
Design projects stall not because the creative work was wrong, but because the right person didn't see it until the wrong moment. A stakeholder who wasn't in the briefing appears at the penultimate review with foundational objections. The designer revises. The budget absorbs the cycle. The launch date moves. Nobody is technically culpable, but everyone is genuinely frustrated, which, in a professional context, produces the same outcomes as culpability anyway.
That raises an obvious but frequently unasked question: whose job is it to map the approval path before work begins?
Conventionally, clients own the brief. But that division of labor creates a specific blind spot, because designers, through accumulated project experience, know exactly where approvals go wrong. The best working relationships I've been part of involve the designer actively contributing to the brief's structure, at minimum flagging where approval ambiguity creates foreseeable rework. Who reviews first-round concepts? Who has veto authority, and at what stage? Is there a legal or compliance review, and does it happen before or after design completion? What does "approved" actually mean: one sign-off, group consensus, or silence after a defined window?
These questions feel bureaucratic until the moment you urgently need answers and nobody has them.
What a Functional Brief Actually Contains
A brief worth acting on doesn't need to be long. It needs to be specific about the right things.
Project context: one short paragraph on the business objective and the relevant audience. Not the company history; the context that actually bears on this deliverable.
Scope: deliverables, formats, quantities, revision rounds, timeline. If any of these are genuinely undetermined, say so explicitly rather than leaving them implied.
Annotated references: what you respond to, what you don't, and the reason. Even "I dislike this but a stakeholder wanted it included" is usable information. It tells the designer where the political constraints live.
Constraints: brand guidelines, technical requirements, accessibility standards; anything the designer must work within rather than around.
Success criteria: how will you know the work is finished and correct? This one trips people up more than any other. If you cannot articulate it, the designer cannot either.
The approval path: named, sequenced, and defined.
That is not an exhaustive list, and real projects frequently surface idiosyncratic requirements that don't fit neatly into any framework. But those six elements cover the territory where most projects accumulate their expensive surprises.
The Brief Is Not Administrative Work
Here is the opinion the industry doesn't say loudly enough: a weak brief is a tax, and the designer pays most of it. Revision cycles built on misread direction. Concepts restructured the night before a client presentation because a senior stakeholder saw the work for the first time at the wrong moment. I've been the designer in that room. It is not an experience that builds professional affection.
The brief feels like upfront overhead because, in a narrow sense, it is. But the cost of skipping it is almost invariably larger, more diffuse, and critically, harder to trace back to its actual origin. Writing a specific, annotated, approval-mapped brief requires the client to resolve ambiguity before the designer encounters it. That process frequently reveals that the client wasn't as certain about the direction as they believed.
That discovery costs nothing when it surfaces in a document. It costs considerably more when it surfaces in round three, on a Friday, with a Monday deadline.
It is also worth considering who bears the reputational risk when a project unravels in revision. The client absorbs some of it. The designer absorbs the rest, usually disproportionately, because the artifacts are theirs. The brief is the one instrument that protects both parties, and it is the one instrument both parties treat as optional right up until the moment they desperately needed it.
