Web Design3 min read

What Should You Send a Web Designer? A Practical Website Brief Template

A short, specific brief gives a website supplier a better basis for discussing scope. Describe the customer task, the material available and the decisions still open, then use the same brief to compare proposals.

By Menerai · Published

Begin with the customer and the task

Write a short description of the business, the customers you want to serve and the action the website should support. For example: help suitable renovation prospects understand the work offered and request an initial conversation. That gives the project a clearer purpose than ‘make the site modern.’

CIRA’s website-hiring guide discusses describing the business and audience when briefing a supplier. The template below is our working structure for turning that context into decisions the project team can review.

If the existing site has a specific problem, include its URL and a reproducible example. Describe what happens, what should happen and which customer task is affected. Our conversion-audit guide can help organize that first observation.

Use a brief that exposes the important decisions

An original website-project brief template
Brief itemWhat to write down
Business and audienceServices, genuine coverage, ideal customer and useful inquiry.
Primary taskWhat a visitor should understand and be able to do.
Pages and evidenceService pages, real project examples and existing useful content.
Required functionsForms, booking, payments, accounts or integrations, with their purpose.
Content responsibilitiesWho writes, verifies, supplies and approves each item.
Budget and timingWorking constraints and any genuine launch dependency.
Launch and ownershipDomain, hosting, access, migration and handover needs.
Ongoing careWho updates content, maintains software and handles faults.

Mark unknowns explicitly. If you are unsure whether the site needs a customer portal, describe the workflow that makes you consider one. The supplier can then discuss whether an integration, a simpler process or custom software is appropriate.

Inventory content and account responsibilities

List existing pages worth preserving, approved project details, brand files and service information. Identify missing material and who can produce it. Our case-study template can help turn completed work into usable project evidence.

Record who controls the domain, hosting, analytics and connected services. A brief should identify the account owner and required collaboration; passwords do not belong in a general project document. Use an appropriate access-sharing process when the project actually needs it.

For a redesign, include the existing URL inventory and any known search concerns. Our migration checklist explains what should survive the transition. Discovering those requirements before quoting makes the scope easier to assess.

Define review and acceptance responsibilities

Name the person who can approve scope, content and design. Describe how feedback will be gathered and which team members need to check the work. Separate a stylistic preference from a functional requirement so the supplier can respond appropriately.

Include accessibility in the project requirements from the beginning. The W3C planning resources address planning and managing accessibility. For the brief, identify important journeys such as keyboard navigation, reading service information and completing an inquiry, and ask how they will be checked.

  • Agree which deliverables are reviewed at each stage.
  • Specify the browsers, devices and important tasks included in acceptance.
  • Record content and integration dependencies that affect the schedule.
  • Define handover material and the process for reporting a launch issue.

Compare proposals against the same brief

Ask suppliers to identify inclusions, assumptions, exclusions and open decisions against the brief. A lower figure may describe less content, fewer integrations or a different support arrangement. Resolve those differences before treating proposals as comparable.

Use the website-cost guide and website timeline guide to prepare the discussion. Keep the project brief short enough to maintain, with supporting detail linked where needed.

Menerai’s North Vancouver service page describes our website project process. You can send us your current site, primary goal and available material to begin a scope conversation, even if some decisions are still open.

Sources & further reading

Have a website project in mind? Talk with the people who will design and build it.

Start a Project ↗

Keep reading

All articles ↗
Web Design

How Much Does a Website Cost in Vancouver?

The useful question is what the quote includes. A focused business site, a considered redesign and a custom platform are different projects — even when they have the same number of pages.

Development

How Long Does It Take to Build a Business Website?

A useful timeline names the work, the decisions and the people responsible. ‘A few weeks’ means very little without knowing when the content is ready and what counts as finished.