AOMARK DIGITAL — WEBSITE PROJECT BRIEF
Editable planning worksheet

How to use
Save a copy, answer what you know and mark open questions as "to confirm".
Share it with the people making decisions before requesting a proposal.
Keep passwords, API keys and private customer information out of this file.

1. BUSINESS AND CONTEXT
Business name:
Current website (if any):
Project contact and decision maker:
What does the business offer, and where does it operate?
What has prompted this project now?

2. AUDIENCE AND MAIN TASKS
Who are the primary visitors?
What do they need to understand or do on the website?
What information helps them choose your business?
What questions or objections do sales/support hear repeatedly?
Are there language, location or accessibility requirements to account for?

3. GOALS AND EVIDENCE
Primary business goal:
Secondary goals:
What would a useful outcome look like?
What baseline information is available?
How will the team review enquiries, orders or other relevant outcomes?
Who owns that review?

4. SCOPE AND PRIORITIES
Must-have pages and functions:
Useful additions that can wait:
Explicitly outside this project's scope:
Forms and the information each needs to collect:
Products, listings or other structured content:
Required integrations and their existing owners:
Anything the current website does well that should be preserved:

5. CONTENT AND BRAND
Approved logo, fonts, colors and brand references:
Existing text and images that can be reused:
New content required and who will provide it:
Evidence supporting any claims, testimonials or results:
Who approves content and checks image usage rights?
Who will maintain the website after launch?

6. SEARCH AND EXISTING URLS
Important current pages and their purpose:
Existing search/reporting access available to the project team:
Known URL changes or content that may be removed:
Who will review URL mappings and redirects if needed?
Who approves which pages should be available to search engines?

7. DELIVERY AND RESPONSIBILITIES
Target date and the reason for it:
Budget range or decision process:
Project owner:
Content owner:
Technical/hosting owner:
Final approval owner:
Known dependencies, constraints and open questions:

8. ACCEPTANCE AND HANDOVER
Essential visitor journeys to check:
Devices and browsers most relevant to the audience:
Who will confirm form delivery and reply handling?
Who will approve production URLs and search settings?
Training or editing documentation required:
Backup, recovery and maintenance responsibilities:
What evidence must be recorded before launch approval?

NEXT STEP
Review missing answers together, agree the first priorities and assign each
open question to an owner. This brief is a starting point for scoping work;
it is not a contract, estimate or promise of a particular result.

Aomark Digital
https://aomarkdigital.com/services/web-development/