How to write a website design brief that gets useful answers

A completed hypothetical brief and a checklist you can reuse for your own project.

// Good businesses deserve better online.

Useful thinking.
A clear next step.

// THE SHORT ANSWER

A useful website design brief explains the business, intended audience, main customer action, required content and functionality, constraints and approval process. It gives a designer enough context to recommend a scope. You do not need to choose every layout or technical detail before starting; describe the decisions and problems the website must address.

Start with the problem people have.

“We need a modern website” leaves too much open. “Customers cannot tell which service fits their property, so enquiries arrive without the details needed to quote” describes a problem a website can help solve.

Explain the work you want more of, who buys it and what they need to understand before contacting you. Include the jobs, locations or customers outside your scope. A designer can then make choices about navigation, page content and forms with a clear purpose.

Use reference websites to explain preferences, such as a readable service comparison or helpful enquiry flow. Say what works and why.

A brief with decisions in it.

Hypothetical example: the following is an invented brief for a Christchurch home-maintenance business. It is not a Daniel James client, proposal, price or delivery promise.

Business and audience
We maintain owner-occupied homes in Christchurch. Our priority customers want planned maintenance and minor repairs. We do not offer emergency call-outs or large building projects.
Current problem
Our existing site groups all work under “services”. People cannot tell whether their job fits, and our team must request the same basic details by email.
Main website action
Submit a suitable job enquiry with suburb, work type, description and preferred timing. Show a phone number as an alternative.
Launch content
Home, services overview, planned maintenance, minor repairs, about, contact and privacy information. Retain useful existing addresses where possible. Review all old pages before removing any.
Evidence and assets
The owner supplies approved project photographs and accurate service details. The designer writes draft copy from one structured interview; the owner checks every service claim.
Functionality
One enquiry form delivered to the office inbox, a clear confirmation message and spam protection. No online payment, customer portal or automatic booking at launch.
Platform and editing
Recommend a platform against this scope. The office administrator must be able to edit service text and replace photographs after training.
Budget approach
Quote the defined launch scope as one project. Itemise recurring costs and price optional future booking functionality separately. If the scope does not fit our budget, identify specific deferrals.
Timing and decisions
Our requested target is twelve weeks after kickoff, subject to the agreed plan. The owner approves structure, copy and design; the administrator tests the editing workflow. We return consolidated feedback within three working days.
Success and handover
Record the starting enquiry volume and proportion of suitable jobs. Review those measures after launch. Handover includes account access, editing training, form tests and named maintenance responsibilities.

This brief helps the designer estimate the work and tells the business what to supply. The proposed schedule still needs agreement.

Describe what “working” means.

Replace broad labels with reviewable requirements. For example: a visitor can find the correct service from the main navigation; a form submission reaches the intended inbox; an administrator can update a page without changing its layout.

Include accessibility early. W3C’s form guidance explains that controls need labels describing their purpose and associated with the relevant input. Make form usability part of the brief, along with keyboard access and readable content. W3C’s Easy Checks offers an initial review approach, while making clear that simple checks are not a complete accessibility evaluation.

For search and AI discovery, brief the quality of the information: clear service explanations, accurate business details, useful answers and evidence for claims. Google’s helpful-content guidance emphasises information made for people, with original value and clear sourcing. Do not replace that work with a target number of keywords.

Copy this checklist.

  • What does the business do, and where does it actually operate?
  • Who is the priority audience, and what are they trying to decide?
  • What is the main action, and what makes an enquiry or sale suitable?
  • Which pages, assets and existing URLs need review?
  • Who supplies and approves copy, images and factual claims?
  • Which functions and integrations are essential for launch?
  • What must staff be able to edit afterwards?
  • What are the budget constraint, recurring costs and target timing?
  • Who approves decisions, and how will feedback be consolidated?
  • What will be tested, measured and handed over?

Mark unknowns honestly. “Please recommend” is useful when it identifies a real decision. Hidden assumptions are harder to resolve once the work is underway.

Use it to start the work.

Send the same core brief to anyone proposing the project. Ask them to explain their recommended scope, assumptions and exclusions against it. That makes their answers comparable and gives you a reason to choose beyond the appearance of a portfolio.

Daniel James is Christchurch-based and works across New Zealand. Bring your brief to a web design conversation, or send the problem you are trying to solve if the brief is still taking shape.

A few useful answers.

Do I need to choose a platform before writing the brief?

No. Describe the content, functions, editing needs and integrations first. Ask the designer to recommend a platform and explain the trade-offs against those requirements.

How long should a website brief be?

Long enough to make the important decisions and constraints clear. A concise document with specific requirements is more useful than a long collection of vague ambitions. Add supporting inventories or technical details separately.

Put it to work.

Planning a new website or working out what needs to change? Explore web design with Daniel James, or start a conversation about your business.

// The person behind the thinking

DAN SMITH.

Daniel James is Dan Smith: web design and digital growth, based in Christchurch and working with businesses across New Zealand. Strategy, structure and design—with a direct line to the person doing the work.

// Enough reading / A useful next step

GOOD THINKING.
BETTER DOING.

Let’s turn the right ideas into a website that does a better job for your business.