← All insights · Web Design

How to Write a Website Design Brief—with a Free Template

You do not need technical expertise to write a useful website brief. Explain the business, the problem and the decisions that matter, using this free template.

Share

A website brief gives an agency enough information to understand the work you are considering. It helps you receive proposals that address the same requirements and exposes questions that need resolving before the project begins.

It does not need to specify every feature or tell the designer how to arrange each page. You can leave room for advice. What matters is explaining the business, the audience, the problem and the boundaries of the project.

If you are approaching agencies for website design in London, send the same core brief to each one. You will learn more from the differences in their responses when they have the same starting information.

Describe the problem before the solution

“We need a modern website” leaves a lot open to interpretation. Does the current site make the business look outdated? Is it difficult to use on a phone? Does it fail to explain a new service?

Describe what is happening and what should change. For example: “We now work with larger organisations, but the website still presents us as a one-person consultancy. Prospects cannot find relevant project examples, and staff rely on emailing PDFs.”

That is a fictional example, but it gives an agency a clearer design problem than a request for something modern.

Separate requirements from preferences

A requirement describes something the website must support. A preference describes something you would like.

“Our team must be able to publish vacancies without a developer” is a requirement. “We like the navigation on this website” is a preference. Both are useful, but they should not carry the same weight when decisions are made.

Mark functionality as essential, desirable or suitable for a later phase. Explain any fixed constraints, including existing systems that must remain in use.

Copy this website brief template

Complete the fields you can answer. Write “to be discussed” where you need advice; uncertainty is more useful than a guessed technical specification.

1. Organisation and project contact

  • Organisation name:
  • Current website:
  • Main contact and role:
  • What the organisation does:
  • Main services, locations and audiences:
  • People involved in approving the project:
  • Person with final sign-off:

2. Why the project is needed

  • What is wrong or missing on the current website?
  • What has changed in the business?
  • What should be retained?
  • Why is the project happening now?

3. Objectives and evidence of success

  • The three most important outcomes:
  • The actions visitors should take:
  • Available evidence about current performance:
  • How success will be assessed:
  • Who will review the results:

4. Audiences and tasks

  • Primary audience:
  • Other important audiences:
  • What each audience needs to find or do:
  • Questions visitors need answered before contacting us:
  • Known accessibility, language or device needs:

5. Content

  • Likely main pages or sections:
  • Existing content to retain, update or remove:
  • Articles, case studies, documents or other material to migrate:
  • Who will write and approve new copy:
  • Available photography and brand assets:
  • New imagery or copywriting required:

6. Functionality and systems

  • Essential functions:
  • Desirable functions:
  • Features suitable for a later phase:
  • Systems the website must connect to:
  • Existing booking, recruitment, payment or CRM arrangements:
  • What staff need to edit themselves:
  • Any access, permission or approval requirements:

7. Design and brand

  • Existing brand guidelines:
  • What the website should communicate about the organisation:
  • Examples we find useful, with reasons:
  • Design approaches we want to avoid, with reasons:
  • Brand work required before or alongside the website:

8. Search and migration

  • Important services and locations for search:
  • Existing pages known to generate relevant visits or enquiries:
  • Access to analytics and Search Console:
  • Planned domain changes, if any:
  • SEO work already being carried out and by whom:

9. Budget and schedule

  • Available project budget or budget range:
  • Whether that budget includes content, photography and ongoing costs:
  • Preferred launch date:
  • Reason for the deadline:
  • Dates when decision-makers are unavailable:
  • Procurement or approval stages:

10. Quality, handover and support

  • Accessibility standard and testing evidence required:
  • Other acceptance requirements:
  • Training required:
  • Ownership and account access expectations:
  • Hosting and maintenance requirements:
  • Expected support after launch:
  • What the agency’s proposal should include:

A short completed example

The following example is fictional and is included to show the level of detail that helps.

Organisation: A London building consultancy serving commercial property owners.

Problem: The existing website describes services briefly and has no useful project library. Prospective clients cannot easily identify relevant experience.

Objectives: Explain three core services, publish structured project examples and improve the relevance of enquiries.

Audience: Property directors and facilities managers assessing consultants for planned work.

Scope: Home, about, three service pages, project library, individual project pages, insights and contact. Staff must be able to publish projects using consistent fields.

Responsibilities: The client supplies technical facts and approved project photographs. The proposal should price copywriting and content entry explicitly.

Success: Assess qualified enquiries, the services requested and feedback from the sales team. Establish the current baseline before launch.

This gives an agency enough context to ask useful questions without dictating the final design.

What happens after you send the brief?

Expect clarification. An agency may identify a missing dependency, suggest a simpler approach or ask which objective matters most if the budget becomes tight.

Ask for the final proposal to record those decisions. It should distinguish included work from options and explain what the agency needs from you.

When you are ready, send your brief to Think Digital. We can discuss the requirements for your new website, including the questions you have not yet answered.

Share
Start a project

Let's build it properly.

We'll tell you exactly what we'd build, how long it would take and what it would cost.

Start a Project →