Introduction
A website project is not properly finished when the final page is published.
The client needs enough access and documentation to operate, maintain and transfer the website later.
A good handover protects both sides because ownership, credentials and responsibilities are clear.
This checklist can be used by clients, freelancers and agencies before closing a project.
Domain Access
Confirm who owns the domain registrar account.
The client should know the registrar, renewal date and recovery method.
Document DNS access and any important records.
Do not leave the domain permanently dependent on a developer's personal email.
Hosting Access
Provide the hosting provider name, account ownership and the appropriate technical access.
Explain billing and renewal responsibilities.
If the website uses a managed deployment platform, document the team or project account.
The client should know where the website actually runs.
CMS and Administrator Accounts
Create client-owned administrator accounts where appropriate.
Remove temporary development users that are no longer needed.
Explain roles and basic editing workflows.
Do not share one password among everyone simply for convenience.
Source Code and Repository
For custom development, document where the source code lives.
Give the client appropriate access to the repository or provide an agreed archive.
Include deployment instructions or build requirements where necessary.
Clarify ownership of custom code and any third-party licensed components according to the contract.
Analytics and Search Accounts
Make sure the client has access to website analytics, Google Search Console and tag-management tools used by the project.
Use business-controlled accounts rather than tying everything to the developer's personal login.
Document important conversion events and tracking assumptions.
Future marketing teams will need this context.
Third-Party Services
List services such as email delivery, forms, CRM, payment gateways, maps, booking tools, CDNs and automation platforms.
Record who owns each account and how billing works.
Document API keys securely without placing secrets inside public handover files.
A website often depends on more services than the visible CMS suggests.
Premium Licenses
Clarify which themes, plugins, fonts or software licenses are owned by the client and which depend on an agency plan.
Record renewal dates and expected recurring costs.
If functionality will stop receiving updates after a license expires, explain the impact.
A client should not discover hidden recurring costs months later.
Backups and Recovery
Explain how backups are created, where they are stored and how restoration works.
Confirm whether the maintenance provider or client is responsible for checking them.
Provide a fresh final backup or repository state at handover.
Recovery information should not depend entirely on the original developer.
Documentation and Training
Provide short documentation for recurring tasks such as editing pages, adding posts, managing products or reviewing forms.
Video walkthroughs can be useful when the editing workflow is visual.
Keep documentation focused on tasks the client will actually perform.
Do not overwhelm non-technical users with internal implementation details they do not need.
Support and Warranty Terms
State what support is included after launch, for how long and what counts as a bug versus new work.
Explain maintenance options and response expectations.
Document the process for requesting future changes.
A clean support boundary prevents misunderstandings after handover.
Frequently Asked Questions
Should clients receive source code? — It depends on the contract and platform, but ownership and access should be defined clearly before the project starts.
Who should own the hosting account? — The business should have clear ownership or recoverable control even if a developer manages the technical side.
Should passwords be emailed in a handover document? — Use a secure credential-sharing method instead of plain-text email or public documents.
Is training part of website handover? — It is highly useful for editable CMS sites and should be included or scoped explicitly.