Know where the website lives
A website usually depends on more than one account. The domain, hosting, email, content system and any third party services may all be managed separately. Keep a record of the provider, the account owner and the person responsible for renewals.
Where practical, essential business accounts should be controlled by the business, with appropriate access granted to the people doing the work. That makes a change of supplier less disruptive and keeps renewal notices with the right team.
Be clear about the files and the rights
Ask which source code, design files, content and media are included in the handover. Third party fonts, photographs, plugins and other assets may have separate licences or subscriptions. Those should be identified rather than assumed to be part of a single purchase.
The project agreement should explain ownership and permitted use. This article is a practical checklist, not a replacement for that agreement or advice on the legal terms of a particular project.
Ask for a working guide
Useful documentation explains the tasks your team will repeat. That might include publishing a project, replacing an image, checking an enquiry, changing a product or creating a backup. It should also identify changes that need development work.
For a custom application, the handover may need build and deployment instructions, configuration guidance and an overview of connected systems. The depth should match the project and the people who will maintain it.
Separate launch from ongoing care
Decide who owns updates, backups, monitoring and incident response after release. If support is included for a period, be clear about what it covers and how to report a problem. New features and routine content changes may need a different arrangement.
A maintenance plan does not have to be complicated. It does need named responsibilities, a way to request help and clarity about recurring costs. Avoid leaving these decisions until the first renewal or failure.
Check the handover by using it
Before closing the project, sign in with the account owned by the business and complete a routine task together. Confirm that the agreed files and documents are accessible, and that the right people receive form and system notifications.
The aim is simple: your team should know what it has, how to use it and where to turn when something changes. A good handover makes the website easier to own, not just easier to admire.
Have a project in mind or a question about your current website?
Talk to KalkiWeb