Branding

How to write a useful brief for a designer

Give a designer the context, deliverables and decision process needed to discuss an achievable creative project.

By Graphic Core   /   Published
Monthly guide series: September 2019

A clipboard with a geometric layout sketch, colour swatches, pencil and ruler.

Describe the problem before the solution

A design brief helps a designer understand what needs to change and how the result will be used. Begin with the situation: perhaps customers cannot distinguish two services, your printed materials use inconsistent contact details, or a new business needs an identity that works on a small website and a vehicle. Explain why this matters and who needs to use the result. ‘Make it modern’ can be useful as a preference, but it does not tell a designer what the work must accomplish.

Explain the business and its audience

Describe the service you actually provide, the customers you want to help, your genuine coverage and the questions people ask before buying. Share any existing research, while making clear which ideas are assumptions. Include practical constraints such as a multilingual audience, accessibility needs, regulated wording or a small team that must maintain the finished material. For an established organisation, identify what customers already recognise and what should be reviewed rather than assuming that every existing asset should be discarded.

List the work and the intended uses

Separate the decision you need from the files you expect. A logo exploration might involve several directions, a selected identity and agreed variations; a website project could include content planning, design, development and testing as separate stages. List the places the work will appear, such as print, web, signs or social profiles. Ask which sizes, formats, editable files and colour versions are included. Mention if you need suppliers or staff to reuse templates. A clear list makes it easier to compare proposals and identify exclusions.

Describe a finished deliverable in terms of what the team must do with it. An editable quote template, for example, needs to remain readable when the text is longer than the sample. A logo may need versions for a dark website header and a small social profile, with the agreed file types supplied at handover. If the project includes a website, list the pages and important journeys to be designed and tested. Ask whether copy, image preparation, accessibility checks and implementation are included or need separate estimates.

AT A GLANCE

What a useful design brief includes

  1. PurposeThe problem and audience
  2. ScopeDeliverables and intended uses
  3. ConstraintsBudget, timing and dependencies
  4. ApprovalWho reviews and decides
  5. HandoverRights, files and responsibilities
The brief is a shared basis for discussion, not a substitute for an agreed project scope.

Share useful references without demanding copies

Examples can help you discuss the qualities you like: clear navigation, generous spacing, a readable sign or a particular level of formality. Explain what you would like the reference to achieve for your audience. Do not ask the designer to copy another organisation's logo, photographs or wording. Share your own existing materials and any relevant brand guidance, with permission for the designer to use them. Identify any photographs, fonts or other assets whose licences need to be checked before they are incorporated into final work.

Set constraints and decision responsibilities

Provide an honest budget range if you have one, the reason for a deadline and any dependencies such as copy, product information or a printer's specifications. A date is more useful when both parties know who supplies and approves each item. Name the person who collects feedback and has authority to sign off the work. Agree how many review rounds are included, how feedback will be consolidated and what happens if the scope changes. Ask a prospective supplier to identify uncertainties instead of treating a rough outline as a fixed promise.

A useful timetable shows dependencies as well as a preferred finish date. For example, the first draft may depend on receiving approved service descriptions, while a printed piece may need a production proof before it can be ordered. Identify who supplies each item and how quickly feedback can reasonably be gathered. If a decision cannot be made by one person, name the people whose input is needed and agree how conflicting comments will be resolved. Record which version of the brief everyone is using so corrections are not lost between emails. Ask the supplier to flag any deadline that depends on a third party rather than treating an unconfirmed date as a promise.

Agree rights, handover and ongoing care

Before work starts, discuss copyright ownership or the licence you will receive, including third-party fonts, stock imagery or software. Ask how original and editable files will be delivered, whether accounts will be in the business's control and what training or documentation is included. If there is a website, identify who is responsible for hosting, domain access, updates, redirects and testing. Record the arrangement in the project agreement. A completed visual design is not the same thing as a functioning, maintained website.

Illustrative example: a small organisation

Imagine a fictional Hertfordshire organisation that needs clearer event posters and a matching website update. Its brief states the audience, the event details that must remain accurate, the planned print sizes, an accessible contact route and who approves changes. It provides the designer with a current logo and confirms which photographs it has permission to use. The quote then separates design, printing and website implementation so the organisation can compare like with like. The example is invented and does not describe an actual Graphic Core project.

Make feedback specific

Ask reviewers to describe the problem they noticed and the task they were trying to complete. ‘The service name is difficult to read on a phone’ gives a designer more useful information than ‘make it pop’. Separate factual corrections from personal preferences and check that the people approving the work agree on priorities before sending comments. If a suggestion introduces a new deliverable, such as an additional brochure, treat it as a scope discussion rather than expecting it to be absorbed silently.

Check the brief before sharing

Ask whether a supplier can identify the problem, intended users, required deliverables, constraints and decision-maker without a further meeting. Mark any information you still need to confirm, including ownership of materials and the timing of feedback. Remove personal details that are not necessary for the initial discussion. Invite questions and allow the designer to propose an alternative approach when it would meet the same need. Update the brief if the scope changes so both sides can refer to the agreed version.

YOUR NEXT MOVE / 01

Ready to make
more of your business?

Tell us about your website, your services and where you want to grow.

START A CONVERSATION