Website handover checklist.
Prepare the files, access, and setup notes your client needs.
1. Agree on the delivery.
Confirm the approved version and what the client receives: a published website, source files, hosting setup, training, or maintenance. Record the delivery location, remaining tasks, and responsibility for future changes.
Download ZIP exports saved project source. Account, workspace, domain, and external subscription ownership do not transfer with it. Arrange those access details separately.
2. Check the exported project.
Save the approved project, open Publish, and choose Download ZIP. Extract it and follow the setup you will give the client.
- The archive matches the approved saved version.
- Dependencies install and the project builds.
- Images, fonts, pages, and interactions work outside Adaptar.
- Setup notes cover build commands and required settings.
Check asset permissions and test connected services. Read the source export overview for the full workflow.
3. Put the right people in control.
Use the agreed accounts and invite the people responsible for maintaining the site.
- Domain and DNS owner, with renewal responsibility.
- Hosting owner, billing contact, and deployment access.
- Form recipients, booking accounts, and analytics access.
- Repository or archive access for the maintainer.
Share secrets securely. Keep credentials out of public source files and ordinary handover notes.
4. Review the final domain.
- Pages, redirects, secure connections, and not-found responses work.
- Titles, descriptions, canonicals, robots rules, and sitemap use the live domain.
- Public pages intended for search are crawlable and free of draft noindex settings.
- Mobile layouts, keyboard navigation, and reduced-motion behavior are reviewed.
- Forms, bookings, downloads, and confirmations work end to end.
- Approved content replaces every placeholder.
Where search is in scope, arrange reporting access and inspect the public pages after launch.
5. Leave a useful handover record.
Copy these fields into the delivery notes. Link to setup instructions and service accounts.
- Approved version
- Project name, date, and approval reference
- Website and source
- Live URL and archive or repository location
- Setup
- Runtime, install, build, and deployment instructions
- Service owners
- Domain, hosting, forms, bookings, and analytics
- Checks and open tasks
- Completed review and remaining work
- Maintenance
- Responsible person, support scope, and renewals
Walk the client through the site and confirm they can access the agreed files and services.
Related guides
Bring your next client brief.
Join the waitlist for access.