Website handover is the process of ensuring the business owner can operate, maintain, and continue developing the website after the work is handed over. What is checked includes work results, account access, documentation, backup, training, and division of responsibilities. Websites that have appeared on the internet are not automatically ready to be managed if important access is still unknown or problem reports have no recipient.
Preparation should start from the time the project scope is drawn up. FourVM puts the need for post-launch management as an area that needs to be discussed with website owners. In this way, handover can be assessed through agreed evidence, not just through a statement that the work has been completed.
Match the results with the final scope
Use approved work lists along with authorized changes. Check the pages, functions, materials, integrations, and training requirements included. If a part is postponed, write down the reasons, the person responsible, and the decision to handle it.
Perform important user tasks, such as searching for services, sending requests, or updating information. The inspection needs to follow a flow until the results are received by the correct party. A form displaying a success message does not yet prove that the request has reached the sales team.
Record findings with location, inspection steps, expected results, and actual results. Avoid mixing implementation errors with new feature requests. Both can require different decisions, especially when affecting costs and completion timelines.
Create a list of accounts and their authority
Inventory of domain accounts, hosting, content management systems, email services, analytics, and third party services used. For each account, note the administrator, recovery address, access authority, and relevant billing information. Lists do not need to contain passwords in widely shared documents.
MDN explains a domain as a name used to access an internet address, managed through a domain registrar. During the handover, make sure the organization knows the applicant's account and renewal schedule. Website editor access alone does not replace control of a domain account or hosting service.
Use organizational accounts and assign roles as needed if the platform supports it. After the move, review what access the vendor still requires. Don't immediately remove all access before support responsibilities and recovery methods are confirmed, but avoid retaining excessive authority without purpose.
Explain code and license submission limits
If the project includes code submission, specify its form, location, version, and how to use it. The code received needs to be accompanied by sufficient preparation instructions for those who will continue the work. Files without dependency explanations can be difficult to maintain even if the size appears complete.
Separate project-specific code from third-party components, themes, plugins, and subscription services. Note the license and account used as agreed. Assignment of code does not automatically mean that all rights to all components are transferable indefinitely.
If using GitHub, the official documentation explains that moving a repository involves management authority and consequences. The receiving party needs to check the collaborators and their arrangements. Moving a repository also does not automatically move the domain, server, or payment account used by the website.
Request documentation for daily work
Documentation needs to address the tasks the editor will actually perform: updating services, changing photos, publishing posts, or changing contacts. Use examples that suit the website. Generic guides that do not match the system interface will be difficult to use when incumbents are not available.
Complete with technical information relevant to maintainers, such as system environment, dependencies, and update processes. Determine which materials editors can access and which need to be restricted to administrators. Documentation needs vary according to the complexity of the website and the division of management.
Test the training through practice by the recipient. Have the editor complete one change in a safe environment, then check the results. Attendance at training sessions does not prove that officers can perform their duties without constant assistance.
Make sure the backup can be used for recovery
Ask what is backed up, where it is stored, who can access it, and when the backup was created. On WordPress, the official documentation differentiates between files and databases; both are required for complete website recovery. Just copying an image is not the same as backing up the entire system.
Request proof of recovery checks according to the scope and risks of the website. Testing should be performed in a separate environment so as not to disrupt active services. Note versions, dates, and check limits, including sections that depend on other service providers.
Establish backup processes after handover. The copy on launch day is not enough to protect changes made months later. Schedules and storage need to keep up with the frequency of changes and operational needs, not just default settings that are never reviewed.
Separate warranty, maintenance, and development
Write down the type of problem handled during the correction period, the time limit, and how to report it. Differentiate from routine updates or changing business needs. The term “free support” is too revealing without the scope, hours of service, and exclusions.
Also explain customer responsibilities, for example providing the correct materials and maintaining staff access. Changes by other parties need to have a way of recording so that the source of the disturbance can be traced. Avoid promising all problems will be resolved in the same time without considering the cause.
For future development, keep a separate list of requirements with priority reasons. That way, the work completed does not continue to change due to additional requests that have not been agreed upon. Advanced lists also help business owners prepare budgets based on real needs.
Simulation case study: editor can log in, domain unknown
This simulation is not a FourVM customer report. A company has been using a website for some time and has an editor account. When they needed to renew the domain, the team discovered that the registrant's account information and recovery address had not been included in the handover document.
The team inventoried services, asked administrators for clarification, and followed provider procedures to organize access. They record the extension schedule as well as the officer in charge. The inspection does not stop at successful entry into the content management system.
The lesson is that access must be mapped according to function. The editor, administrator, domain account holder, and billee may be different parties. The relationships between them need to be recorded so that the organization does not rely on one person's memory.
Simulation case study: backup available, recovery has not been attempted
An organization receives a folder called backup when a project is completed. When a new maintainer checked it, the folder only contained application files without a database and setup instructions. They have not been able to confirm that the copy is sufficient to run the website again.
The recipient requests coverage clarification and sets up inspections in separate environments. Parts that are not completed according to the agreement, then recovery steps are recorded. After that, the organization determines who maintains the backup and checks the results periodically.
The lesson is that the existence of a file is not proof of recovery readiness. The handover needs to show the use of the materials received. Check limits also need to be honest, as one test does not prove all future disruption circumstances have been covered.
Frequently asked questions
Do all handovers require moving hosting accounts? Follow service models and project agreements. What must be clarified are the management, authority, access to information, and the process if the service relationship ends. Don't assume one model applies to all providers.
When is the handover list compiled? Start discussing website creation proposal , then update following scope changes. Together with FourVM, use the list to test operational readiness before declaring work results acceptable.
Source
- MDN Web Docs — What is a Domain Name? Domain basics and management . The date of publication is not recorded; accessed 14 November 2026.
- GitHub Docs — Transferring a repository. Authority and consequences of moving the repository . The date of publication is not recorded; accessed 14 November 2026.
- WordPress Developer Resources — Backups. File and database backup . The date of publication is not recorded; accessed 14 November 2026.