Website brief checklist.
A useful website brief starts with the business goal, the visitor's next action and the systems behind it. You do not need to choose a framework or write a technical specification before talking to a studio.
Start a projectStart with the goal
Write down what should be different after the website is launched. More suitable enquiries, easier product management and fewer booking emails are different goals. Choose the main one so design decisions have a purpose.
Then name the audience and the action they need to take. A quote request may need project details and attachments. A purchase needs product information, payment and delivery decisions. A booking needs availability and a confirmation journey.
- Who is the website for?
- What should they understand before contacting you?
- What is the main action, and what happens after it?
Take stock of content
Separate content you already have from content someone still needs to prepare. List the pages, product information, photographs, brand assets and approved legal copy. Mark who owns each item and whether it is ready for use.
For an existing website, identify the pages that are useful today. Keep a record of their addresses, especially pages that already receive visits or enquiries. If addresses change, plan their redirects instead of leaving visitors and search engines at dead ends.
- Current website and domain access
- Approved logo, copy and photographs
- Product or service information and its owner
- Content that must be retained or migrated
Map the next step
The form is not the whole enquiry process. Decide where a submission goes, what the customer sees and who is responsible for replying. If it should create a customer record or a project, identify that system and the details it needs.
List the tools the site must connect to. Access permissions, available APIs and subscription requirements need checking before a connection is promised. Do not share account passwords or customer records in a public brief; arrange an appropriate access method when the project is scoped.
- Enquiry recipient and response owner
- Confirmation on screen and by email
- Booking, payment, CRM or other connections
- What your team needs to edit after launch
Agree the first release
Separate essential launch requirements from improvements that can follow. Explain any genuine deadline and what creates it. A target date alone does not establish whether content, integrations and approvals can be ready in time.
Ask for a written scope covering deliverables, exclusions, responsibilities and acceptance checks. Hosting, third-party subscriptions and ongoing support should be clear. The handover should explain how to operate the site and who owns the relevant accounts.
- Must-have requirements and later improvements
- Budget range or a request for scoped options
- Content and approval responsibilities
- Launch checks, handover and ongoing support
Your next step
A good brief makes the next conversation useful. Describe the business change you want, what exists today and what must happen after a customer acts. The technical approach can follow the agreed scope.
The project brief helps you describe what exists today and what should improve. For scope and handover, read how delivery works and what affects project investment.
