A website handover that answers the next question.

1. List what shipped

Name the pages, features and files actually delivered. Link to the live site and document any known limitations. Avoid calling incomplete work finished.

2. Confirm ownership separately from access

A client may be able to edit a site without owning its hosting account. List the owner of each service, who pays its bill and how access will be transferred. Confirm receipt through the provider's own controls. Do not put passwords or recovery codes in the handover file.

3. Make open items explicit

For every unfinished task, write the next action, owner and target date. Distinguish a bug within agreed scope from a new request. An open item is not complete because it appears in a report.

4. Explain the first routine task

Include a short, accurate guide to changing common content and checking the result. State who handles backups and updates. Only promise maintenance that you have agreed to provide.

5. State the support boundary

Restate the existing support period and contact route. Do not invent a deadline or assume that silence means acceptance. Ask the client to confirm any unresolved decisions.

Copyable final review

• Live site checked on desktop and mobile
• Client can access the accounts they should control
• Deliverables and known limitations recorded
• Open items have owners and dates
• Maintenance and billing owners identified
• Support terms match the actual agreement