Name the required behaviors and acceptance tasks
Describe the completed buyer journey, named templates, integration boundary, responsibilities, exclusions and acceptance tasks on one page. Keep unresolved commercial facts visible to the project owner and outside unsupported public promises. The scope defines a reviewable outcome without relying on package tiers or an apparently simple page count.
Worked example — illustrative data.
| Scope field | Specimen entry | Acceptance/owner |
|---|---|---|
| Buyer journey | Find collection → select product → checkout | Store owner approves task |
| Pages/content | Named product and collection templates | Content owner supplies facts |
| Integration | Approved inventory connection only | Integration owner demonstrates states |
| Exclusions | Custom software and unapproved account work | Clear boundary and change route |
| Handoff | Named editor tasks and access responsibilities | Owner task session |
| Open decisions | Unconfirmed shipping/returns terms | Hold dependent copy |
List the smallest complete outcome and trace every deliverable to it. Describe what the business supplies, what the implementation team creates and what another provider remains responsible for. Define acceptance through visible tasks and records rather than vague language such as premium design. Record how a new requirement changes scope through an agreed review, without assuming it is already included. Use project-specific commercial terms from the approved proposal.
List behaviors separately from template counts
For the product template, identify ordinary purchase, unavailable variants, subscriptions, pickup and other required states. Attach each in-scope behavior to its acceptance task, dependency and content owner. Keep unsupported configurations and custom software outside the written boundary unless separately agreed. A change request should state which buyer task, deliverable and responsibility it adds.
One template can contain several distinct product behaviors
A page count can look fixed while the catalog needs several distinct product behaviors. Document the behavior and data boundary as well as the template count so important work is not hidden behind a simple number.
Approve scope when both sides can identify the finished outcome, exclusions and next unresolved decision. The specimen establishes no Amadeus contract, delivery guarantee or package entitlement.
Continue with Guides for stores, software teams and local businesses, Website design and development services and A redesign checklist for keeping pages buyers already use.