Prepare a Website Project Brief Before Choosing the Build

A website brief should explain who the site serves, what visitors need to do and how the client will review the result. Define pages, content, editing needs and acceptance checks before selecting a template or promising a delivery date. A visual mockup alone does not establish that forms, editing or public pages will work.
This guide uses a fictional pottery-workshop website to explain a small service brief. The planning deliverable records the proposed work, responsibilities and acceptance tasks so the client can review the scope before a build begins.
Start with goals instead of a tool list
MDN's planning guidance puts the project's goals before technical choices. It asks what the site should accomplish, how it supports those goals and what needs to be done in sequence. That is a useful starting point for a brief, although the guide does not choose a technology or commercial scope for a particular client.
Source: MDN's guidance on thinking before coding. Read 2026-10-26.
Ask the client to identify the main visitor and the action the site should support. Reading opening information, sending an enquiry and purchasing a product are different journeys. Decide which is included rather than putting every possible feature into an initial quote.
Separate an observable action from a business prediction. You can define a working enquiry flow and how it will be checked. You cannot establish future enquiries or sales merely by building it. Put the measurable delivery requirements in the brief and leave unsupported forecasts out.
Map pages and the visitor journey
List the included pages and the purpose of each. Identify how a visitor reaches the main information and the next action. A page count without that relationship can conceal missing navigation or a repeated page that serves no distinct need.
For each action, describe the expected result. If there is an enquiry form, identify the fields, the recipient, the confirmation and the way failures will be reported. A successful button click is not proof that the intended person received a message.
Mark services or integrations that need separate access and approval. Do not assume permission to change a domain, mailbox, payment account or production system because the client approved a design concept. Keep those boundaries visible in the project scope.
Gather content and usable assets
MDN's first-website guide discusses planning information, appearance and assets before coding. It includes sketching a design and choosing colours, images and fonts. Its example is deliberately simple; it is not a complete client-content checklist or a licence to reuse images found online.
Source: MDN's first-website planning guide. Read 2026-10-26.
Create a content inventory with an owner and status for each item. Include the real business name, service descriptions, contact details and images the client can authorize. Mark missing material as missing. Do not fill a design with invented testimonials, staff identities, awards or claims of experience.
Record the intended use and permission for each asset. Ask whether the client needs editable source files or only the final web version. A reference site can communicate a desired structure or atmosphere without authorizing copied text, identity or distinctive artwork.
Define what the client must be able to edit
Ask which content will change after handover and who will maintain it. A client who needs to update services or opening information has a different requirement from someone who expects to request every change from the developer.
Turn the answer into an acceptance task. For example, the client should be able to edit an agreed piece of text through the intended interface and see the correct public page reflect that change. A screenshot of an administration screen does not establish that the public output updates.
List any content outside that editing scope. Explain what requires a developer, an additional integration or a separate maintenance arrangement. Avoid promising that every visible element is editable when only a few fields have been prepared for changes.
Build a small fictional brief
For an invented example, plan a website for a community pottery workshop. Define visitors who need the session description, location and a way to ask a question. Include an opening page, a session-information page and an agreed enquiry path, without inventing real customer feedback or booking numbers.
Add the content owner, asset list and review responsibilities. If dates change regularly, specify how the workshop organizer will update them. If the client has not decided whether enquiries should become bookings, leave that as a decision rather than silently adding payments.
Write a short acceptance list for the actual journey. A visitor should find the location on a phone, follow navigation to the relevant session and complete the agreed enquiry test. Use this fictional exercise to check whether each requirement has an owner, a review step and an observable result.
Plan checks beyond the attractive screenshot
Identify the devices and page states that need review. Include readable text, visible controls, navigation, keyboard use, images and unexpected horizontal scrolling or clipping. A desktop screenshot is only one observation of one state.
If the scope includes forms, content editing or external services, define a real result check for each. Agree on test data, who can inspect the result and how sensitive information will be kept out of screenshots and ordinary reports. Do not use a build success as a substitute for checking the live flow.
Keep review criteria separate from launch authority. A local preview, a staging site and a public deployment have different evidence and access requirements. The brief should say which environment is the final acceptance target and what authorization is needed to change it.
Define the accessibility evaluation scope
If the brief includes accessibility evaluation, name the WCAG version and target level, the site area being evaluated, and the supported browser and assistive-technology combinations. W3C's WCAG Evaluation Methodology (WCAG-EM) 2.0 provides a process for this work. It is informative evaluation guidance and adds no WCAG requirements. Its stated expertise requirements also help you decide who should conduct the review.
Distinguish the evaluation scope from the pages selected for testing. WCAG-EM explains that evaluating a sample alone does not establish conformance of an entire website. For a small site, evaluating every page can be practical. When a selected page belongs to a process, include the other steps in that process and the important alternative paths. The method's interaction checks cover error feedback as well as successful completion.
Apply that distinction to the fictional pottery-workshop brief. Write an enquiry test that starts from the session page, opens the form, submits an incomplete enquiry, corrects it and reaches the confirmation. Record how to reproduce each state, including any view that keeps the same URL. Assign a reviewer and keep their findings with the version they checked. Include any external form that handles part of the journey in that review plan, and confirm access before quoting the evaluation. This makes the quoted review work and its remaining issues visible to the client.
Source: W3C's WCAG-EM 2.0, especially Scope of applicability, Relation to WCAG 2 conformance claims, and Steps 1, 3.3, 4.2 and 5.1. Read 2026-11-17.
Agree on handover and later changes
List the final files, access arrangements and instructions the client needs. Clarify ownership and control of the domain, hosting and included third-party services without collecting unnecessary credentials in the brief itself. Include a way to recover affected material before an authorized live change.
Set the content deadline, review rounds and process for new requirements. Additional pages, languages, payments or integrations can change the work. Count clarification, content preparation, checking and handover alongside implementation; this guide provides no fee benchmark or forecast of demand.
For related services, compare desk research briefs and slide preparation. A useful next step is one clear sample brief with explicit exclusions and testable acceptance tasks. It should make the proposed work reviewable before anyone commits to a build.