A website brief should explain what people need to understand and do. Visual references help, but the scope also depends on content, navigation, integrations and the way the website will be maintained.
Start with the visitor’s task
List the main reasons people visit. They may need to understand a service, compare project work, find practical information or make an enquiry. Identify which actions matter most to the business. These tasks give the structure a purpose and help the team decide what belongs on the main pages.
Take stock of the existing website
Share the current URL, important pages and any known problems. Include analytics or search data if available, and distinguish measured issues from preferences. Record content and URLs that need to be preserved. A redesign should account for the existing site rather than beginning with a blank page by default.
Identify content and its owner
List the information needed for each main page. Include services, project examples, images, contact details and legal materials. Decide who will write, check and supply each item. If the website uses case studies, identify what can be published and which results have supporting evidence.
Describe the enquiry path
Decide what visitors should do after reading a service or project page. A form needs an agreed destination and useful fields; the team also needs to know how enquiries will be handled. If booking, payments or customer accounts are required, describe the actual workflow rather than only naming a feature.
List technical requirements
Include existing hosting, domains, content management systems and integrations. Explain access requirements, languages, accessibility needs and any constraints imposed by other systems. Confirm who will maintain the site after launch and what ongoing support belongs in the project scope.
Use project examples to discuss fit
TrustNoteD’s identity and website show a digital presentation connected to a technology brand. Kulm Immobilien’s project connects a visual identity with a real estate business’s webpage. Use examples to explain the kind of information, tone and brand relationship your website needs.
Agree how the result will be checked
Make the acceptance criteria concrete. Important journeys should work on mobile, forms should validate and send correctly, links should reach their intended pages and content should remain usable with a keyboard. Identify the people responsible for checking content and the delivery requirements before launch.
Explore TROKIT’s web design and development work, then share your website brief to discuss the scope.