A brief should reduce uncertainty

A useful website brief explains what the site must do, what materials are available and how the finished work will be accepted. It does not need to be a huge document. A short, agreed description is more useful than many pages of generalities.

Start with the business: services, audience, geography, primary visitor actions and constraints. Name the decision-maker and the person responsible for supplying content.

A brief defines the outcome: Business goal; Pages and languages; Content and assets; Integrations; Acceptance criteria
A brief defines the outcome

Record pages and content responsibilities

List the page structure, purpose, languages and main sections. Identify ready text, images and product data, and what the provider must prepare. For a migration, retain the old URL list.

Explain references specifically: perhaps their navigation, readability or comparison method is useful. “Make it like this site” does not define functions or grant permission to copy its content.

Describe scenarios rather than vague preferences

Vague: “an easy enquiry form”.

Testable: the visitor enters contact details and a request; required fields are validated; accepted data produces a confirmation; the responsible person receives the enquiry; repeated clicks do not create duplicates.

For booking, specify whether the form sends a request or actually reserves availability. For payment, define when the order status changes. These distinctions can affect scope more than the button colour.

Agree editing and integration behaviour

List the text, prices, photographs, cards and translations the owner can edit without code. Define user roles and access limits. Ask for an editing demonstration before acceptance.

For CRM, delivery and payment systems, describe fields, data ownership and failure handling. A service logo on a quote does not explain the implemented workflow.

Add acceptance criteria

  • Agreed flows work on the specified devices and browsers.
  • Long names, missing images and errors do not break the layout.
  • Important URLs, SEO fields and language links are preserved or migrated deliberately.
  • The owner receives access, instructions and a backup.
  • Bug-fix and support terms are clear.

For performance, agree measurement conditions and page types rather than an unsupported promise of an identical score on every device.

Define boundaries and changes

Record what belongs in the first release, what is excluded and how additional requests are estimated. Distinguish implementation defects from changes to an approved requirement. Agree review rounds and how content delivery affects the schedule.

The brief should support the project budget; see website cost components. Once agreed, it guides design, development and the launch checks.

Need a plan for your website?
Explore our services: Website creation, pricing or discuss your project.