Agree the decisions before the design.
A scope should describe what will be delivered and how you will know it is ready.
By Kumar Saurabh Mishra, founder of SiteSutra. Planning examples are original demonstrations.
Pages and content
List the page types, approximate content volume, and who writes, supplies, and approves each item. A five-page brochure and a catalogue with hundreds of products are different projects.
Functions and integrations
Describe each visitor task: enquire, book, buy, search, or download. Name the systems it depends on and assign responsibility for accounts and access.
Acceptance and ownership
Agree device and browser checks, revision rounds, launch responsibilities, editable files, and ownership. Record exclusions as carefully as inclusions.
A hypothetical service-business scope
Example only: a fictional home-repair business needs Home, Services, About and Enquiry pages. Include one booking provider, supplied copy and photos, mobile navigation, an acceptance checklist and handover. Exclude online payments, customer accounts and a multilingual content system. Those would need a separate scope.
A hypothetical agency pilot
Example only: implement an approved three-section campaign landing page with a labelled enquiry form, success/error states and responsive layout. The agency supplies approved copy and design files; the provider account owner verifies receipt. Include one agreed review stage and source handover, with dates and fees established in the proposal.
Bring the decisions into one document
Complete the editable brief and checklist below. They are planning tools, not a contract or an automatic quote.
Discuss your website scope ↗