Design brief template: give your studio the context it needs

A useful design brief gives a studio enough context to make good decisions. It explains the business, the people you want to reach, the change you need, and the constraints the work must respect. It does not require you to choose the typography, sketch a logo, or arrive with every answer.

For a service business, the hardest part is often translating work that feels obvious to you into information someone else can understand. You know why clients choose your firm. A designer needs evidence of that difference, examples of the situations you handle, and a picture of where the identity will be used.

Use the design brief template below as a working document. Copy the questions into your own notes and answer them in plain language. Mark uncertain answers as questions. A short, honest brief is more useful than a polished document that quietly mixes facts with assumptions.

Start with the decision the project needs to support

“We need a more professional look” describes a feeling. It does not explain which business decision the design needs to help with.

Try a more concrete starting point: “We are approaching larger organizations, and our proposals still look like documents from a solo practice.” That gives the studio an audience, a touchpoint, and a reason for change. It also makes the work easier to review later.

Choose one main objective. You may have several problems, but they will not all have equal importance. Identify what must become clearer, more recognizable, or easier for your team to use. Keep sales targets separate from design deliverables: an identity can support a buying decision, but design alone cannot guarantee a commercial result.

The design brief template

The following questions work for an identity project, a refresh, or a collection of business materials. For a website, add the pages, content responsibilities, platform requirements, and integrations to the scope discussion.

1. Business context

• Business name and current offer: What do you sell, and how is the work delivered?
• Reason for this project: What has changed in the business, audience, offer, or existing materials?
• Current position: What works already? What should be preserved?
• Source material: Which website pages, proposals, client comments, or examples explain the business accurately?

Explain the work in a few sentences before introducing internal package names. Include a source beside claims that matter. If “clients value our practical approach” comes from conversations, include an anonymized example or an approved client comment rather than presenting it as a measured finding.

2. Audience and buying situation

• Primary audience: Who needs to understand and choose the service?
• Situation: What is happening when they look for help?
• Decision: What do they need to feel confident doing next?
• Questions or concerns: What might make them hesitate?

Job titles can help, but they are not the whole audience definition. “An operations director preparing to merge two teams” gives more useful context than “professionals aged 35 to 55.” If several people influence the purchase, explain their different roles.

3. Objective and review criteria

• Main objective: What should this project improve in the presentation of the business?
• Practical evidence of success: What will you be able to inspect at handoff?
• Priority touchpoints: Where will the new work appear first?
• Preservation criteria: What must stay recognizable or functional?

Use criteria you can discuss: a proposal template can accommodate a long project title; the logo remains legible at profile size; the identity supports a website and presentation without improvising new styles. These criteria make reviews more useful than a general vote on which option people like.

The graphic groups the questions. The complete template remains available as text so you can copy it into your own document.

4. Scope, assets, and constraints

• Requested deliverables: List the pieces you need and how each will be used.
• Existing assets: Where are the current logos, fonts, photographs, copy, and editable source files?
• Required constraints: Include genuine requirements such as an established business name, partner rules, accessibility needs, or print specifications.
• Reference material: What qualities do you admire, and why?
• Investment and timing: What budget context and real deadlines should the studio know?

Separate essentials from possibilities. “Proposal template for the sales team” is an essential if it is used every week. “Maybe a podcast cover later” can remain a future need. Tell the studio which files you own and where licensing needs checking. Avoid sending passwords in the brief; establish appropriate access separately if the agreed project requires it.

5. People and approvals

• Project contact: Who gathers files and answers ordinary questions?
• Final approver: Who can approve the direction and scope?
• Contributors: Whose expertise or feedback is needed, and at which stage?
• Feedback method: Who will consolidate comments into one response?

An approval role is more useful than a long list of people copied into every message. If two partners disagree on an objective, surface that before asking the designer to resolve it through visual options. The studio can help clarify the question, but your business needs a way to make the decision.

6. Open questions

• Unknowns: Which answers still need discussion or research?
• Dependencies: What information or decision must arrive before another part can proceed?
• Out of scope: What should this project avoid taking on?
• Next conversation: What do you want to decide with the studio first?

Unknowns do not make a brief incomplete in a harmful way. Hidden unknowns do. State them directly so they can become part of the scope conversation.

A completed design brief example

The following consultancy is fictional. It illustrates the level of detail that helps a designer; it is not a Studio FLACH client or an account of a completed project.

Business and audience

Business: Fieldwork People Advisory helps growing professional-services firms improve manager development and team communication. Work includes leadership workshops and advisory engagements with senior teams.

Reason for change: The practice now sells through a small team. Its existing materials rely on the founder's portrait and several unrelated document templates. The partners want the identity to represent the firm while keeping its approachable tone.

Primary audience: Managing partners and people directors whose firms have grown beyond informal management. They need to understand the approach and decide whether a workshop or a longer advisory engagement fits their situation.

Evidence available: Approved descriptions of both services, biographies, sample workshop agendas, and two client comments cleared for public use. There are no verified claims about revenue or retention improvements to include.

Objective and scope

Main objective: Present the consultancy as one coherent team across its website, proposals, and workshop materials.

Review criteria: The proposal cover must work for different service names. The presentation needs usable title, content, exercise, and closing slides. The identity should feel thoughtful and practical rather than formal or theatrical.

Requested deliverables: A core identity system, practical guidelines, a proposal cover, and a presentation template. Website redesign is a separate decision; the current website will receive approved identity assets only if that application is agreed in scope.

Assets and constraints: Keep the business name. Review whether the current symbol is worth retaining. All existing materials are in one shared folder. The partners must verify the licenses for current fonts and photographs before reuse.

References, people, and open questions

References: An editorial report for its calm hierarchy; a workshop workbook for the clarity of its exercises; a consultancy website for the way it separates service routes. The aim is to learn from those qualities, not reproduce their layouts or identities.

Approvals: One partner is the final approver. The operations manager gathers assets and consolidates feedback. Workshop facilitators review the practical slide layouts before handoff.

Timing and investment: The firm wants new presentation materials before an upcoming event. The event date and the minimum useful delivery are to be discussed with the studio. Budget and any staged delivery will be agreed before work begins.

Open questions: Should the founder remain prominent in the identity? Can the current name support future services? Does the proposal template need a simple editable layout or several detailed page types?

Fictional example. Notice how each request has a business use, a source, or a decision attached to it.

Explain references without asking for a copy

A reference is most useful when you name the quality you are responding to. “I like this website” gives the studio many possible interpretations. “I like how the service names remain clear even when the page is expressive” gives a design principle to discuss.

For each reference, record three things: what you admire, where that quality could help your business, and what should not carry across. You might admire generous spacing but need denser proposal pages. You might like a confident palette while recognizing that the example serves a different audience.

Use references to communicate qualities. Your business context decides how those qualities should be interpreted.

Keep the brief useful during the project

Treat the brief as a shared point of reference, not a test the designer must pass without discussion. At the start, clarify unclear answers and confirm the deliverables in the proposal. During review, refer back to the audience, objective, and practical criteria.

If a new request appears, say what changed. A new audience, name, or major deliverable can affect the scope. Record the decision rather than quietly inserting it into feedback on an already developed direction.

At Studio FLACH, True Mark starts with business context and visual direction before the identity is developed. If both identity and website need work, Signature Suite brings those parts into one project. Bring your brief, including its unanswered questions, to the conversation. The first useful outcome is deciding what the project actually needs to solve.