What we hand over
We describe the delivered pages, functions, content, browser support, integrations, and known limitations in plain language. A clear handoff helps the receiving owner understand what was completed and what remains outside the agreed scope.
For client work, we identify the domain, hosting account, business contact, approved content, and the people responsible for future changes. We list the key public pages, enquiry paths, third-party links, and any recurring services involved.
Ownership and access
We make ownership clear for the domain, hosting account, business profiles, and other services included in a delivery. Access is granted only to people who need it and removed when it is no longer required.
Passwords, recovery codes, private keys, customer records, and other confidential information do not belong in public pages, screenshots, or shared documentation. We use the provider’s access-management tools wherever available.
Launch and recovery
We keep a known-good release before high-impact updates and explain how the published experience is checked. We test direct page access, mobile navigation, contact handoff, appearance preferences, and installation or offline behaviour when those features are in scope.
Acceptance and future support
Before handoff, we compare the result with the agreed acceptance criteria, identify any remaining limitations, and confirm who owns ongoing content and maintenance. A successful launch is not a promise that future changes or monitoring are included automatically.
Read our website delivery guide and service scope guide for more detail.