WEBSITE PROJECT BRIEF
Replace the prompts below with your project details. Do not put passwords or customer records in this brief.

1. BUSINESS GOAL
Primary audience:
One main visitor action:
How we will tell whether the site is useful:
Project owner and approver:

2. PAGE AND FUNCTION SCOPE
Page list and purpose of each page:
Required functions (forms, booking, checkout, search, or integrations):
Specific behavior and success/error states:
Languages:
Existing platform and hosting, if any:
Design only, development only, or both:
Excluded work:
Budget and launch deadline:
Content-ready date and review checkpoints:

3. CONTENT AND RESPONSIBILITIES
Who supplies final copy:
Who supplies images, with usage permission:
Who enters content:
Who handles domain, hosting, subscriptions, and renewals:
Existing URLs that need a migration plan:
Who approves privacy, cookies, and other legal content:
Ongoing costs to list in the quote:

4. BUILD AND REVIEW
Required browsers and phone/desktop sizes:
Accessibility requirements and agreed testing scope:
Forms: validation, delivery, spam handling, and confirmation:
Editing tasks our team must be able to perform:
Performance expectations and measurement conditions:
Analytics or marketing integrations, only if required:

5. HANDOVER AND ACCEPTANCE
Check navigation, forms, links, mobile layout, and keyboard use.
Test one complete visitor journey with agreed sample data.
Receive source/export, asset inventory, license list, and instructions.
Confirm owner-controlled hosting and administrative access.
For database-driven sites, confirm both file and database backup.
Agree responsibility for DNS cutover, restore testing, and post-launch fixes.
Support duration and excluded maintenance:
Use secure delegated access; never send root passwords in a project brief.
Questions for the developer: