The point where work gets scattered
A page count alone does not resolve content loading, form behavior, redirects or access handover. Those details often surface near launch unless the scope assigns them early.
Separate pages, behavior and content
Describe deliverables in the way the client will inspect them. “Contact page” is incomplete without the fields, recipient and success response of its form. Record assumptions about the existing site instead of silently treating them as facts.
- List page inventory and reusable layouts separately.
- State how many content items will be loaded and who checks accuracy.
- Identify redirects or migrations by a named list, not “all existing content.”
Make acceptance observable
Use checks someone can repeat: a named form arrives at the test recipient, navigation reaches each page and the client can edit a named text field. Choose supported devices and browsers together.
- Keep proposed checks distinct from results actually observed.
- Assign one reviewer and a feedback date to each milestone.
- When inputs arrive late, agree revised dates instead of implying the original schedule still holds.
Scope review checklist
Read the scope alongside the proposal and flag differences before using either document to start work. This planning template does not replace an appropriate agreement.
- Content counts, integrations and exclusions are specific.
- Every dependency names an owner and date.
- Acceptance checks cover actual deliverables.
- A change records effects on work, price and timing before approval.
- Launch authorization and later maintenance are separate decisions.
The working template
Use the complete text below, or download the text file and edit it in your preferred document editor.
WEBSITE SCOPE OF WORK Project / version / date: [details] Related proposal or agreement: [reference and version] Objective: [visitor task and business purpose] Pages: [named pages and purpose] Layouts: [unique templates and where used] Functionality: [behavior; limits; external service owner] Content inventory: [type; quantity; supplier; loading owner] Migration / redirects: [specific list, or excluded] Client inputs: [item; owner; due date] Milestones: [deliverable; target date; reviewer] Acceptance checks: [check; expected result; inspection environment] Revisions: [rounds; consolidated feedback process] Exclusions / assumptions: [limits; unresolved questions] Change request: [difference; cost/timing effect; decision owner] Launch: [authorizer; required outstanding checks] Handover / ongoing work: [files/access notes; support scope or exclusion] Next decision: [owner; date]Download text template
A filled example
Fictional example for illustration. Replace its facts and amounts with the details you actually agree.
FICTIONAL FILLED EXAMPLE Cedar Cycle scope v2 covers Home, Repairs, Workshop, About and Contact using three layouts. Mira loads five final text documents and six client-approved photographs. The enquiry form has name, email and message fields; Jo receives a test enquiry and confirms arrival before launch. No shop, booking integration, old blog migration or ongoing maintenance is included. Cedar owns domain renewal and supplies its approved connection method without putting passwords in the scope. Review checks are: every menu link reaches its named page; the form shows its confirmation; Jo can change workshop text; and agreed mobile and desktop checks are recorded. Jo reviews the staged build on 27 March. A request for a sixth page is logged with a separate price and revised date before proceeding. Launch remains a separate explicit decision after outstanding issues are resolved.
Keep the context with the conversation
Keep a reviewed scope reference in the relevant Bankeiz conversation. Messages can help prepare a clear change request using chosen context, while you decide the actual deliverables and any payment terms.
Understand your Twin · See Business access and metered AI usage