What to include in a business website scope and handover
Define deliverables, ownership, recurring costs, content responsibilities and support before development starts.
By Vitality Solutions
Specify pages and functionality
A quote should identify the pages, reusable templates, integrations and customer actions being delivered. An enquiry form, a booking integration and a custom customer portal have different requirements. Explain how additional requests will be scoped after agreement.
Assign content responsibilities
Agree who supplies copy, images, product information, policies and approvals. Identify any purchased assets and their permitted uses. Content availability affects scheduling, so milestones should make those dependencies clear.
Separate ongoing costs
Identify domain registration, hosting, subscriptions, premium plugins or themes and maintenance. Record whose account owns each service and who renews it. Development pricing alone does not describe the total cost of operating a website.
Define launch acceptance
Agree checks for mobile layouts, key links, form delivery and important customer journeys. Include migration redirects and analytics where applicable. Set an approval process and clarify how reported defects differ from new features.
Request a practical handover
Confirm access to the domain, hosting, platform accounts, agreed code and editable assets. Request editing guidance and a record of important integrations. Define ongoing care, response expectations and backup responsibility so ownership is useful in practice.