A useful website brief connects a business goal with an agreed set of deliverables. It does not need to be a long document. It does need enough detail for you and your developer to understand what success looks like and what is included.
Start with the visitor and the goal
Explain who will use the website and what they need to do. A local service business may need qualified enquiries, while an online store may need a clearer product-selection and checkout journey. List the most important visitor questions and choose one primary action for each main page.
Agree the page list and content responsibilities
List the pages required at launch, including supporting pages such as contact, privacy and error recovery. For each page, identify who provides the text, images, downloads and approvals. Distinguish final content from temporary working material. A finished layout is only one part of a finished page.
If the project is a migration, include the existing domain, useful URLs and any content that needs to be retained. A theme archive is not the same as a complete website backup: database records and uploaded files also matter.
Describe features in concrete terms
Instead of requesting a “modern contact form”, describe the fields, required information, destination inbox, confirmation message and spam controls. For bookings, payments or integrations, name the system, required access and expected data flow. Confirm any recurring costs and who owns the related accounts.
Set review and acceptance checks
Agree when you will review work and how feedback should be collected. Useful acceptance checks include readable mobile layouts, functioning navigation, successful enquiry delivery, meaningful page titles and important links that reach the correct destination. If accessibility or performance targets are contractual requirements, specify how they will be measured.
Plan the launch and handover
Name the person responsible for backups, domain changes, SSL, redirects, caching and post-launch checks. Keep the domain and hosting in accounts controlled by your business. Use individual access rather than sharing a main account password, and review permissions when the project ends.
Make ongoing work explicit
Discuss updates, backups, content changes and support after launch. Confirm what the initial project includes and what needs a separate arrangement. Clear boundaries help both sides estimate work accurately and deal with changes before they affect the schedule.
Ready to prepare your brief? Read how we work, explore website development, or send a project enquiry.