← Syntax Orbit home

Syntax Orbit · Project guide

How to prepare a useful web project brief

Turn a website idea into a clear brief with user journeys, content ownership, scope, and acceptance criteria.

Start with a task, not a list of pages

“We need a modern website” leaves the most important decisions open. Describe who is visiting and what they need to accomplish. For a service business, that might be comparing an offering and sending a qualified enquiry. For a restaurant, it might be finding a dish, checking its price, and understanding dietary information.

Write one primary journey in ordinary language: a visitor arrives, finds the relevant information, checks a detail, and takes an action. Use this journey to decide which pages and features belong in the first release.

Inventory the content and its owner

List the copy, images, product information, prices, and contact details that each journey needs. Mark what already exists and who will provide or approve the missing material. A design can be complete while a launch remains blocked by an unapproved menu or missing photographs.

For each item, record where the current version lives and who maintains it after launch. This helps decide whether a content management system is necessary and what its editing workflow should support.

Separate essentials from later improvements

Create two lists: what must work for the first useful release, and what could improve it later. A working contact route might be essential; a complex customer portal may be a later project. Record integrations and external dependencies separately so they can be evaluated before estimates are treated as commitments.

For example, a restaurant brief could require readable categories, current prices, and a mobile-friendly contact link. Ordering, payment, and loyalty accounts add different operational responsibilities and should each have an explicit scope.

Define what “ready” means

Replace vague acceptance criteria such as “looks professional” with observable checks. Can a visitor complete the primary journey on a phone? Do links reach the intended destination? Does the form explain success and failure? Who checks the final content?

Finish the brief with the goal, audience, core journey, content inventory, integrations, constraints, and approver. Share representative examples without including production passwords or private customer records. A clear brief gives both sides a basis for decisions when priorities change.