Name the offer, intended audience, actual coverage and primary action. A customer should be able to understand the service before being asked to act. Mark assumptions and unknowns so they can be resolved deliberately.
Guide / comparison
A website project checklist that starts with the job.
Gather the decisions that change a website scope, without pretending every answer has to be known before the first conversation.
01 / Guide / comparison
Describe the business and the visitor task
02 / Guide / comparison
Prepare the goal and unresolved decisions
This blank worksheet stays in the page. Use roles and non-sensitive examples. Unknown values identify decisions to resolve; they are not a score.
Use roles and hypothetical examples. These fields stay in this page; no information is submitted or saved.
Example: local homeowner can check job fit and prepare a request; online payment is outside this scope.
Give each page a distinct useful job.
Missing content needs a responsible role and next action.
Never enter passwords or private account IDs.
Record what happens when the brief changes.
Include rollback, account/billing ownership, edit training and receipt.
Unknown is acceptable; it must not become an invented commitment.
03 / Guide / comparison
Use a small sitemap with a job for each page
| Page | Purpose | Content owner / status | Launch evidence |
|---|---|---|---|
| Home | Understand the business and select the relevant offer | Business editor / facts need review | Visitor identifies the offer and next route. |
| Service | Check fit, deliverable and boundaries | Practitioner / source material missing | Claims, exclusions and descriptive links checked. |
| Contact | Take the actually supported next step | Operations owner / intake decision unresolved | Actual ordinary/error/receipt/delivery states tested as applicable. |
04 / Guide / comparison
Give each page a job and an owner
- URL and one primary buyer question
- Facts, examples and assets needed to answer it
- Content owner and factual approver
- The page’s parent and useful related routes
- The next action and how its real result will be checked
05 / Guide / comparison
Inventory content, assets and accounts
List the current domain, hosting, platform, important pages, licensed material, forms and connected tools. Establish who owns each account and which assets can legally be reused. Do not gather passwords in the project document.
06 / Guide / comparison
Separate standard pages from connected functions
Bookings, stores, memberships, custom integrations, complex migrations and sensitive data handling need their own dependencies and tests. Decide whether they are essential for the first release or a separately scoped addition.
07 / Guide / comparison
Agree the review and release path
Name one approver, review stages, inputs and acceptance checks. Include mobile and keyboard tasks, form/error paths, URL behavior, intended indexing and the handover. A launch date depends on those inputs as well as implementation.
08 / Guide / comparison
Turn the unknowns into a brief
Use the brief builder to record the goal and open questions. It creates an editable local note, not a submitted request or a booking.
If a different decision is blocking you: Choose another question in this topic