Website planning

Website brief template: a practical starting point

Copy this website brief template to explain your goals, audience, content, functionality, budget assumptions and approval process to a supplier.

Website brief template: how to use it

A website brief template helps a supplier understand the work before proposing a solution. It should explain the problem, the people using the site and the decisions already made. You do not need to choose a framework or write a technical specification before asking for help.

Copy the prompts below into a document and replace the bracketed text. Leave unknowns visible. A question such as which booking system will fit our process is more useful than an unsupported requirement for a particular integration. Ask the supplier to identify what needs investigation before a dependable quotation is possible.

GOV.UK's discovery guidance recommends understanding users and constraints before committing to a service. The same starting questions can help with a commercial website brief, without importing the government's entire delivery process into a smaller project.

1. Background, audience and outcomes

Business and project: [Name, existing website, what the organisation does and why the project is happening now.] Project owner: [Person responsible for decisions and the best contact route.] Describe the current difficulty in plain language, including who experiences it.

Primary audience: [Who will use the website, what they need and the context in which they visit.] Main task: [The most important thing they should be able to understand or do.] Other audiences: [Existing customers, applicants, partners or colleagues, where relevant.]

Desired outcomes: [Observable improvements and how you will review them.] Existing evidence: [Relevant feedback, recurring enquiries or available measurements.] Avoid writing only modern, engaging or easy to use. Explain what would make the experience easier for a real visitor.

2. Pages, content and assets

Proposed pages: [Page name, purpose, intended audience and content owner.] Existing material: [What can be retained, what needs checking and what must be written.] Copy responsibility: [Who drafts, reviews and approves it, with expected availability.]

Brand assets: [Logos, colours, fonts and any established guidance.] Images and other media: [What is available, who owns it and whether its intended use is permitted.] Include meaningful image descriptions where needed, rather than asking the supplier to fill every image field with a keyword.

Existing URLs and documents: [Items that must remain accessible and any planned changes.] If this is a redesign, ask for a content inventory and migration plan. Keep this part focused on the scope of the brief; the detailed old-to-new URL mapping can be a separate working document.

3. Functionality and boundaries

Required journeys: [What happens from the visitor's first action to confirmation.] Forms: [Purpose, essential fields, destination and who responds.] Integrations: [Existing booking, payment, customer-management or other services, with a contact who can confirm access and technical constraints.]

Editing needs: [Who updates the site, what they need to change and any approval steps.] Accounts or permissions: [Who may see or change restricted information.] Explicit exclusions: [Features or audiences not included in the initial project.]

For every requested feature, add a reason and an acceptance example. The example could say that an enquiry reaches the nominated team and the visitor sees a clear confirmation. Do not include live personal records, passwords or secret access details in the brief.

4. Quality, timing and budget

Accessibility and usability: [Known audience needs, required assessment and who reviews the results.] Devices and performance: [Important usage contexts and checks to agree.] A quick automated test is not a complete accessibility assessment; W3C's preliminary guidance explicitly describes the limits of basic checks.

Timing: [Preferred launch date, why it matters and dependencies such as content approval or an existing contract ending.] Budget: [Available allocation, whether it includes VAT, and whether hosting, content and ongoing support need separate allowances.] State unknown costs as questions.

Approval and handover: [Who signs off scope, content and launch; who receives account access, documentation and training.] Ongoing responsibilities: [Who handles updates, enquiries, technical issues and future changes.] Ask the proposal to explain any gaps rather than silently assuming the supplier owns them.

5. An illustrative completed entry

Example only, not a client result: Main task: A visitor should be able to check whether our service covers their area and send an enquiry. Required fields: Contact details, area and a short description of the work. Acceptance: The nominated team receives a labelled test enquiry, and the visitor sees a confirmation explaining the next step.

This entry makes the intended journey concrete without specifying an unnecessary account system or promising a response time the organisation has not agreed. Complete the same exercise for the site's other essential tasks, then remove requirements that do not support an identified need.

Before sending the brief, ask a colleague to read it without your explanation. Can they describe the audience, the main outcome, the boundaries and who decides? The best next step is a discussion of the unanswered questions, followed by a written scope everyone can check against the brief.

Further reading

Big idea. Small first step.

What could work
better for your business?

Tell us where you want to go. We’ll help you work out how to get there.

Let’s talk about it