The website brief that prepares real decisions

Begin with the problem, not the desired interface. Explain why the project is necessary now, where the existing site underperforms and what change the business expects. “Look more modern” is a direction; “generate more qualified enquiries for service X” is a testable objective.

Add a baseline using available evidence: important entry pages, monthly enquiries, known search terms, recurring support questions or sales feedback. Google recommends content created primarily to help people, with a clear intended audience. The brief should make that audience and context tangible.

Do not stop at demographic personas. Describe situations: what does the visitor need to decide, what are they worried about and what evidence will help? Those questions generate page types and content. A service page needs different proof from an article; a careers page has different tasks from support.

Create a content matrix with purpose, core message, evidence, next action, existing material and owner for every page. Missing photography and approvals become visible early, preventing development from finishing while crucial copy remains placeholder text.

Describe functions as workflows. Instead of “CRM integration”, specify which form data enters which system, who is notified and what happens on failure. Instead of “multilingual”, define languages, URL structure, translation ownership and publishing workflow.

Boundaries matter equally. Which browsers are supported? What can the team edit? Which data must not be processed? Which dependencies involve IT, privacy or external partners? A good brief does not suppress creativity; it creates a safe space for relevant design.

State a realistic budget corridor. Without one, a supplier may optimize for an entirely different solution class. Separate target date, hard dependencies and internal approval capacity. Timelines are often delayed by missing content and decisions rather than engineering.

Close with three to five success criteria. They may be quantitative—qualified leads, organic entries, load times—or qualitative, such as a clearer sales narrative or easier editing. Name the data source, baseline and first review date. The brief then becomes the beginning of a learning system.