Insights
Website handover: checks before final approval

A polished preview is only the start. Check enquiries, copy, account ownership and ongoing care before closing the project.
Turn the scope into a checklist
Convert the accepted proposal into pages, functions and deliverables. Record a test result and observation for each item. Distinguish a missing agreed feature from a new idea for later. Both parties then know which items need correction and which need a separate commission.
Test customer tasks
Find a service, read its conditions, submit an enquiry and check the response. For a shop, complete a test order in the agreed mode. Test missing fields and invalid formats too. Record device, URL, reproduction steps and expected outcome instead of only saying something is broken.
Review copy and mobile layout
Compare names, services, phones, languages and prices with approved materials. Open a long heading and menu on a small screen. Use the keyboard to check focus, field order and closing dialogs. Flag placeholder copy and missing image descriptions where included in the agreed project.
Receive accounts and instructions
Agree ownership of domain, hosting, analytics and licences. Transfer access through an agreed secure channel. Request editing, backup and issue-reporting instructions. Confirm who maintains the site after acceptance. An administrator password alone does not establish ongoing care responsibilities.
Record the handover clearly
List files and access delivered, accepted functions and unresolved points with resolution dates. Record the date and approving people. Keep passwords out of the document. The document generator can organise this record. Ongoing support needs its own scope, reporting process and agreed conditions.
Before the next step
- Checklist follows the accepted proposal
- Forms and mobile tasks tested
- Ownership, instructions and care agreed
Turn your plan into action
Use the free tool or explore the service related to this topic.
Open the tool → Explore the service →Good to know
A few useful answers.
Planning the scope or preparing your materials? These answers will help you get started.
Ask usWhat should I prepare first?
Checklist follows the accepted proposal Forms and mobile tasks tested Ownership, instructions and care agreed.
What comes after this checklist?
List files and access delivered, accepted functions and unresolved points with resolution dates. Record the date and approving people. Keep passwords out of the document. The document generator can organise this record. Ongoing support needs its own scope, reporting process and agreed conditions.