A website opening in a browser does not mean the entire project has been handed over. Who controls the domain, can a backup be restored, where are enquiries stored and whom do you contact when something fails? Without prior agreement, even a small change can become difficult. A handover checklist creates shared expectations for the client and team. Specific scope and support commitments belong in the contract rather than being assumed because the website is online.
1. List assets and responsibilities
Record who owns the domain, hosting, database, code, design source files and third-party accounts. Ownership and day-to-day administration are not identical. Check domain renewal dates and notification addresses separately. Payment responsibility, licence transfer and account sharing may depend on service terms. A simple inventory helps a replacement team locate resources. However, placing every password in an openly shared document is not a safe handover: choose a protected method of providing access and managing later changes.
2. Verify admin access and roles
Give the client an appropriate role without unnecessary maximum privileges. A manager should access only what the job requires. Review test accounts, temporary passwords and unused access. Arrange secure password transfer and changes, adding multifactor protection where available. A working login page is not enough: verify that users cannot open another customer's information. Permission checks must go beyond hiding menu items; the server must reject unauthorised actions and requests even when someone knows the address.
3. Plan backups and restoration together
Creating a copy and successfully restoring the system are different tasks. Agree whether database records, files and uploads are included, where copies are stored and how long they are retained. Test restoration in a separate safe environment, not over live data. Restrict access to backup contents. A single copy on the same server may offer limited help if that server is lost. Choose a storage strategy appropriate to the system and the acceptable amount of lost data.
4. Run acceptance tests on core functions
Submit a form, find the enquiry and check notifications and statuses. For payments, use the provider's permitted test mode rather than treating a real transaction as a harmless test. Include languages, mobile layouts, search and error pages. Define the expected result of each scenario in advance. Attractive screenshots are not sufficient: correct data storage and role-appropriate visibility are central acceptance criteria. Test invalid values, repeated submissions and an understandable recovery path after a connection problem too.
5. Document updates and monitoring
Code and dependency updates need testing and a rollback plan. Confirm that production diagnostics are not exposed publicly. Track certificate, domain and hosting expiry dates. Decide who receives error alerts and ensure the address is active. Where queues or scheduled tasks exist, verify them after deployment. Providing an FTP password alone does not establish a change process or system responsibility. The team should know how to check an update and safely reverse an unsuccessful change without sacrificing current data.
6. Clarify support boundaries
Bug fixes, new functions and content updates are different types of work. Record the contact channel, working hours, response expectations and approval of additional tasks. Prepare a short operating guide and handover record. StarWeb plans websites, applications and business systems against requirements, with final pricing, timelines and support agreed contractually. A clear acceptance process helps clients manage the system and technical teams maintain it without creating unspecified promises about every future change or external service issue.
Frequently asked questions
Does having a backup guarantee recovery?
No. Its completeness and the restoration process need testing. Storage, access and review arrangements should be planned separately.
Are all future changes included in handover pricing?
That depends on the agreed scope. New features and ongoing support should be defined separately in the contract.
Final checklist
- Domain, hosting and account responsibilities are recorded.
- Roles and core functions are tested.
- Backup contents and safe restoration are verified.
- Updates, monitoring and support terms are agreed.
Next step
Configure your project and discuss its requirements with our team.