Hand off a simple website clearly

Name the owner

A buyer should control the live domain and production account. Explain access you keep, the maintenance scope and who receives renewal notices. Do not bury an ongoing paid plan inside a one-time design offer.

Separate a demo from a live service

List which buttons are placeholders, which forms actually send information and which pages were tested. A local sample is not a production site. Never mark a contact form working solely because its button changes color.

Give a short handoff note

1. Review URL and delivery date.
2. Editable source or agreed account access.
3. Approved copy and assets, including licensing notes.
4. Hosting/domain owner and recurring costs.
5. Tested links, screen widths and keyboard focus.
6. Known limitations and the agreed support period.

Check the real next step

For a live project, follow the contact or booking route and confirm the intended recipient receives the result. Get permission before publishing, changing DNS or collecting personal information. These actions are outside a fictional practice sample.

Leave one useful next instruction

Explain how the owner changes a phone number or service detail and where a backup lives. A handoff is complete when the owner can use the result and understands its limits, not when you merely send a link.

Use this checklist alongside the landing-page design method.