WEBSITE PROJECT BRIEF
A blank planning template by been.design
https://been.design/resources/website-project-brief
Version: 30 October 2026

Use this with your team or any studio. No account or email is required.
Replace the prompts with your own answers. Write "unknown" where needed.
This template is a planning aid, not a quote, guarantee or contract.
Do not include passwords, private customer records or secret access keys.

1. PROJECT AND AUDIENCE
Company / product:
Current website, if any:
Main audience and their situation:
The offer in one plain-language sentence:
The visitor's main task or question:
Desired next action (e.g. enquiry, demo or purchase):
What happens after that action:

2. WHY THIS PROJECT
The concrete problem with the current experience:
What has changed in the business or product:
What should stay:
What should change:
What is explicitly out of scope:

3. PAGES AND CONTENT
For each required page: purpose, audience, owner, current URL, proposed URL.
Page / purpose / owner / current URL / proposed URL:

Existing copy and brand files:
Approved product visuals:
Case studies or customer examples:
Quotes: exact wording, attribution, permission and source:
Metrics: definition, source, date range, sample and limits:
Material that is still missing, its owner and readiness date:
Content types the team will update after launch:

4. DESIGN AND BUILD
Current platform and content system:
Preferred platform, if decided, and the reason:
Who will edit content and what they need to change:
Required forms and their destinations:
Required third-party systems:
Custom application or backend behaviour, if any:
Accessibility or localisation requirements:
Domain, hosting and publishing account owners:
Who will maintain code, integrations and subscriptions:

5. MIGRATION
Current sitemap or URL inventory:
Pages, files and legacy routes that must remain available:
URLs that need a relevant redirect:
Important incoming links, if known:
Current search and analytics baseline, with dates:
Launch dependencies and rollback decision owner:

6. SCOPE AND DELIVERY
Budget context and separate recurring costs:
Deadline and the reason for it:
Content/factual approval owner:
Design and technical decision-makers:
Feedback process:
Legal or third-party dependencies:
Required handover files and account access:
Maintenance owner after launch:

7. MEASUREMENT
What useful action will be measured:
How a click differs from a completed action:
Available baseline and comparable date range:
Analytics/consent requirements:
Who reviews the data and the decision it can support:

8. OPEN QUESTIONS
Decisions that still need investigation:
Risks or dependencies to discuss:

Keep this completed brief privately until you choose whom to share it with.
Project questions: https://been.design/call