# Website handoff

ILLUSTRATIVE EXAMPLE · SMALL SERVICE BUSINESS

This sample shows the decisions a handoff can record. It is not a completed client project or a standard package. The accepted proposal defines the actual work.

Project: A four-page website that explains services and helps visitors make contact or open the business’s existing booking service.

Proposal reference: [Agreed scope/version]
Launch record: [Release date and version, once approved]

| Item | Example record |
| --- | --- |
| Agreed scope | Home, Services, About and Contact pages; inquiry form; link to the existing booking service. Custom booking software, customer accounts and ongoing content changes are outside this sample scope. |
| Ownership and access | Domain and hosting account: business-controlled in this example, with studio access by invitation. Website files: handoff location and usage rights recorded in the proposal. Fonts, images and other licensed assets: source and applicable license recorded separately. |
| Connected services | Booking: visitors leave the website to use the existing provider; availability, confirmations and cancellation rules stay there. Inquiries: form delivery provider and destination inbox recorded, with a delivery check agreed before launch. Provider subscriptions and renewal responsibility listed separately. |
| Content updates | Website wording, photographs and opening hours: updated in the website files by the agreed maintainer, then reviewed and published. No self-service editor is included in this example. Booking availability and service information: maintained by the business in its booking provider; any repeated website information is updated separately. |
| Launch checks | Record the actual date, result and any open issue for mobile layout, keyboard navigation, links, inquiry receipt and the booking destination. This sample has no completed checks. |
| Files and recovery | Record where the website files, asset notes, latest source archive and release history are held, plus who can restore an earlier release. Account access is shared separately. |
| Care and future changes | Record the chosen maintainer, how to request a change and any separately agreed care scope and charges. New pages or integrations are scoped before work begins. Response arrangements are agreed for the project. |

Before handoff: Confirm account control, content approval, provider costs, check results and any remaining work. Record the acceptance date and responsible roles in the project record.