Short answer
A design brief is a shared written agreement about the problem a design project should solve, who it serves and what must be delivered. A useful design brief template includes background, goals, audience, scope, constraints, visual references, timing, budget and approval responsibilities, with unknowns labeled rather than guessed.
What is a design brief, and who writes it?
A brief describes the assignment before the solution exists. “Help first-time visitors understand what this workshop offers” describes a problem. “Put a large coral button in the top-right corner” proposes a solution that may not address it.
The commissioning person can draft the background, audience and constraints. The designer can clarify scope and identify missing inputs. Treat the brief as shared: both sides should know what is agreed, what is open and who can decide.
For a student or personal project, write the same sections with the information available to you. Identify a self-imposed constraint as such; do not invent a client interview or claim to know what an audience wants. A short honest brief is more useful than a polished document filled with assumptions presented as research.
Design brief vs creative brief: choose useful detail
The terms overlap, and teams use them differently. A creative brief often emphasizes the communication idea: the audience, message, tone and intended response. A design brief often adds the practical definition of the work: deliverables, dimensions or contexts, existing assets, constraints and approval criteria. Neither label guarantees a particular format.
- Graphic design brief
- Define the communication purpose, content owner, formats, visual references and delivery files. State which supplied elements are fixed and which can change.
- Website or interface brief
- Identify key user tasks, content, page or screen scope, accessibility expectations and technical boundaries. Separate visual design from implementation responsibilities.
- Product design brief
- Describe use, environment, intended users, materials or manufacturing constraints and how proposals will be evaluated. Flag safety and testing requirements for appropriate review.
Copyable design brief template
Copy these prompts into a document or notebook and replace the bracketed fields. Keep unanswered questions visible. If a field does not apply, say why; if a decision is pending, name its owner instead of writing a confident placeholder.
- Project and background: [Project name]. We are [organization or context]. The current problem is [observable issue]. Relevant history and existing work: [links or files].
- Goal and evaluation: The design should help [audience] do or understand [task]. We will review success against [specific criteria], using [available evidence or review method].
- Audience and context: The primary audience is [group] in [situation]. Known needs: [evidence]. Assumptions to check: [questions]. Secondary audience: [if relevant].
- Message and tone: Communicate [main message]. The work should feel [qualities], because [reason]. Avoid [misleading or unsuitable impression]. Required content: [approved text or assets].
- Deliverables and boundaries: Produce [items], for [formats or contexts], with [agreed requirements]. Included work: [scope]. Not included: [exclusions]. Final handoff: [files and owner].
- Constraints and inputs: Keep [fixed elements]. Respect [technical, material, accessibility or production requirements]. Assets and permissions supplied by [owner]. Missing inputs: [items and due dates].
- References and visual direction: Use [board or reference links]. Borrow [specific qualities], not [elements to exclude]. Sources and usage permissions: [notes]. Direction approval owner: [name or role].
- Timeline and dependencies: Start after [required inputs]. Review concepts at [date]. Review refinements at [date]. Deliver at [date]. Dependencies and availability risks: [list].
- Budget and resources: Agreed project budget or range: [amount, currency and scope]. Separately approved costs: [items]. Available people, equipment and materials: [resources]. Unknown costs owned by [role].
- Approval and changes: Final approver: [one accountable role]. Feedback coordinator: [role]. Review criteria: [list]. Revision scope: [agreement]. New requests require [process] before work proceeds.
This is a project-planning outline, not a contract or a substitute for professional specifications. A PDF can record an approved version; an editable document can support discussion. Whichever format you choose, include a version date so an old attachment does not become the accidental source of truth.
A fictional design brief example
The following studio and assignment are entirely fictional. They illustrate how to make the template concrete; the scope and sequence are not recommendations for what real design work should cost or how long it should take.
- Project and background
- Paper Orchard is an invented weekend bookbinding workshop. Its fictional information page at https://example.com/workshop needs a one-page visual redesign because the draft mixes practical details with decorative material.
- Goal and audience
- Help a first-time visitor find the workshop activity, required experience, supplied materials and how to send an inquiry. The audience is defined for this exercise as adults considering their first bookbinding class; audience research has not been conducted.
- Message and direction
- Communicate a patient, hands-on introduction. Use a paper-and-linen mood board to explore warmth and tactile detail, while keeping practical information plain and easy to scan. Avoid decorative handwriting for instructions.
- Deliverables and exclusions
- Provide one desktop page concept, one narrow-screen layout and annotated component guidance. Website development, booking functionality, photography and logo work are excluded. The fictional coordinator supplies approved copy and photographs with recorded usage permission.
- Constraints and evaluation
- Keep the existing fictional name and wordmark. Show all four required information groups without relying on photographs to explain them. Review the layouts for readable hierarchy, clear inquiry wording and a workable narrow-screen arrangement; do not claim a conversion result.
- Timeline and resources
- For this exercise, review a first concept after approved copy and assets arrive, then schedule one consolidated refinement review before handoff. No commercial budget is assigned; any paid asset would require a separate decision before use.
- Approval
- The fictional workshop coordinator gathers feedback and gives final approval. A request for an extra page or a new booking flow is a scope change, not an implied revision to the agreed one-page assignment.
Notice what the example does not do: it does not invent research results, promise business outcomes or leave “website design” as an undefined deliverable. A designer still has creative freedom, but the boundary between a good proposal and an unrelated idea is visible.
Use a mood board to explain direction, not replace the brief
A visual reference can make an adjective concrete. Put a warm paper texture beside a note saying “material character, not a distressed background.” Put a restrained layout reference beside “clear hierarchy, not this exact typeface.” Those annotations identify what the designer should learn from each image and reduce accidental imitation.
For identity work, a brand mood board can compare two coherent directions before a logo is developed. For a room project, an interior design mood board can separate atmosphere references from actual finish samples. Keep the written requirements authoritative when a beautiful reference conflicts with a practical need.
Attach source information and distinguish inspiration from approved assets. A reference on a board is not automatically licensed for the final design. When a direction is chosen, record what was approved and what still needs testing; do not assume approval of the board means approval of every depicted object or technical detail.
See mood board examples for structures that combine references with decisions. The visual board and written brief should answer different questions while pointing toward the same result.
Review goals, scope and approvals before work begins
Read the draft with the people who commission, make and approve the work. Ask them to describe the assignment back in their own words. If one person expects a finished website and another expects static layouts, fix the deliverables now. If “premium” means ornate to one person and restrained to another, replace it with concrete evidence.
- Can the goal be evaluated without inventing a metric or promising an outcome?
- Are audience evidence and assumptions clearly separated?
- Are quantities, formats, exclusions and handoff responsibilities explicit?
- Are missing assets, permissions and dependencies assigned to an owner?
- Is one person accountable for consolidated feedback and final approval?
- Does everyone know how a new request changes scope, timing or cost?
Turn “make it modern” into an instruction such as “reduce decorative detail and use a clearer information hierarchy.” Turn “a few social graphics” into a named set of formats and quantities. Precision should remove ambiguity without locking the designer into a solution before exploration starts.
Keep the brief current without moving the goalposts
A brief can change when genuine new information arrives. Record the change, why it matters and which deliverables or dependencies it affects. Agree on the impact before treating the revised request as part of the original assignment. Preserve a dated approved version so decisions remain traceable.
For projects with substantial reference material, organize research visually while keeping the current brief easy to find. Put unresolved questions in a separate area and bring only decisions back into the approved document. That keeps a growing collection of ideas from quietly becoming an expanding scope.
At handoff, review deliverables against the agreed criteria. Record limitations and identify who receives source files and approved assets. The brief should help people evaluate the result without relying on memory.
Questions and answers
How do I write a design brief?
Start with the problem, audience and goal, then define deliverables, constraints, references, timing, budget and approval. Review it with the people doing and approving the work, labeling unknowns instead of filling them with guesses.
What are the four parts of a design brief?
A compact brief can group information into purpose, audience, work to deliver and project boundaries. Expand the boundaries to include constraints, timing, resources and approval; there is no universal required four-part format.
What are the seven main specifications of a design brief?
There is no single mandatory seven-item list. One useful grouping is goal, audience, deliverables, constraints, visual direction, timing and approval, with budget and supplied inputs recorded explicitly where relevant.
What does a design brief include?
It includes the project background, intended outcome, audience, scope, practical requirements, references, schedule, resources and decision responsibilities. The detail should match the assignment rather than an arbitrary document length.
Is a creative brief template the same as a design brief template?
They can share an outline. A creative brief often gives more attention to message and tone, while a design brief may need more detail about formats, specifications and handoff; define the actual information your team needs.