Go-live is not the same thing as handover. An organisation should leave a website project knowing what it owns, where the platform runs, who has access and what happens when something needs to change. The handover should reduce dependency without creating unmanaged technical risk.
Administrator and platform access
The client should know which accounts control WordPress or the CMS, hosting, domain registration, DNS, analytics and other critical services. Shared passwords sent informally are not a sustainable access model.
Documentation and configuration record
Document the important plugins, integrations, licences, environments, forms, email routing and any non-obvious configuration. The next person maintaining the site should not have to reverse-engineer the project.
Backup and recovery information
Handover should explain where backups are stored, how often they are created, how long they are retained and who can restore them. A backup that nobody can locate or restore is not useful.
Training and content ownership
Editors need to know how to perform routine content tasks without touching technical settings. Training should reflect the actual responsibilities of the team rather than trying to turn every editor into a developer.
Post-launch responsibility
Clarify the warranty period, maintenance arrangement, support channel, response expectations and which changes are billable. The organisation should know who owns the next problem before the first problem happens.
What to do next
Use this as a working checklist for your organisation, then adapt it to the actual platform, risk and procurement context. If you are preparing a website project, takeover or ongoing support requirement, WebNT can review the scope with you before implementation begins.