How to write a website brief that aligns your users and stakeholders
A website project can begin with several perfectly reasonable requests. Marketing wants clearer storytelling. The service team needs fewer repetitive enquiries. Leadership wants the organisation to look ready for its next stage. Each request deserves attention, and the brief needs to bring them into a shared direction.
We recommend starting with the decisions your website must help people make. That gives everyone a useful reference when you discuss content, design and functionality. It also helps your agency identify what needs further investigation before estimating the work.
Start with the change you need
Write a short account of why the project matters now. Perhaps your services have evolved, your audiences struggle to find the right route, or your current site makes straightforward updates difficult. Describe the consequences you can observe.
For example, “Our enquiry team regularly explains the difference between our two services” gives a designer something to investigate. Bring examples of those enquiries, the pages involved and any reliable analytics. If the evidence is incomplete, record the question you need to answer.
Agree which outcome takes priority when requests compete. A website that supports several audiences still needs a clear view of its most important tasks.
Use this website brief checklist
You can use these eight prompts as the first draft of your brief. Short, specific answers are more useful than polished language.
- Purpose: What has changed in your organisation, and what must the website help you achieve? Explain what would make this investment worthwhile.
- Users: Who needs the site, what brings them there, and what do they need to accomplish? Include people with access needs and colleagues who maintain the content.
- Evidence: What do enquiries, interviews, search data and website behaviour tell you? Separate findings from assumptions that need testing.
- Content: What exists, what needs rewriting, and who can approve it? Identify missing photography, evidence, translations or service information early.
- Functionality: Which tasks require forms, search, booking, payments or connections to another system? Describe the task and the system involved before prescribing a technical solution.
- Constraints: What budget range, fixed commitments, procurement requirements and organisational standards shape the project? Explain the reason behind each deadline.
- Ownership: Who leads the project, contributes specialist knowledge and gives final approval? Identify who will manage the website after launch.
- Success: Which user and organisational outcomes will you review, how will you measure them, and who will act on the findings?
Add a separate list of open decisions. An honest question about your content or integration is easier to resolve than an assumption buried inside a requirement.
Prioritise tasks before features
Consider this illustrative example. A charity needs to help people find support, attract organisational partners and explain its impact. Someone proposes putting every programme on the homepage, while another person requests an animated opening sequence.
The team first agrees the visitor tasks: check eligibility for support, understand the partnership opportunity and find evidence of the charity’s work. Those tasks become a way to judge both suggestions. A clear route to eligibility information earns priority. The animation needs a specific purpose and an appropriate place in the experience.
For each proposed feature, ask: which task does it support, what evidence makes it necessary, and who will keep it useful? This makes prioritisation easier to explain and gives the project a practical boundary.
Bring the right people into the conversation
At MediaCity, our website work involved people with different relationships to the place. Co-design workshops helped us understand their needs and develop the structure and functionality. The project included a business directory, events information and a meeting-room booking system.
Our MediaCity website case study shows why listening to several audiences can influence much more than the appearance of a page. It shapes the information people need and the routes they take through it.
Your own participants might include communications, service delivery, customer support and the person responsible for your systems. Give each a clear role. User representatives can explain their experience; the project sponsor must still resolve competing organisational priorities.
Decide whether a workshop will help
A workshop is useful when the brief contains conflicting priorities, unfamiliar audiences or complicated functionality. It creates space to examine those questions together and record decisions everyone understands.
You may already have a well-evidenced brief with clear ownership. In that situation, a focused scoping conversation may be enough to identify the remaining gaps. The right approach depends on what is unresolved and the people needed to resolve it.
Before any session, share the evidence, agree the questions and identify the decisions it should produce. Afterwards, record the agreed priorities, outstanding actions and owners. Those outputs should feed directly into the brief and scope.
Give the project a clear next step
A strong brief can remain concise. It needs to make the purpose, users and decisions clear enough for a useful discussion. You can develop the detail as research and scoping answer the remaining questions.
Our website design and development work starts by understanding your organisation and the people it serves. If you are preparing a brief, bring your current site, your priorities and the questions your team is finding difficult to settle. We can explore what needs defining before design begins.