The handover is part of the product. Treat it that way.
What the next person needs to run, understand and maintain the work you receive.

Make the system understandable
A useful handover explains the purpose of the system, the main workflows and the providers it depends on. It does not need to reproduce every line of code. A small, accurate map of the moving parts can save the next owner from guessing which account, environment or service is important.
Record how to run and release it
List the supported runtime, dependencies and setup steps relevant to the accepted project. Describe the release route and any checks that must happen before production changes. Keep production secrets out of documentation. Explain how an authorised owner obtains the required access through an appropriate secure channel.
Name the responsibility
Domain registration, hosting, email, application code and third-party subscriptions may have different owners. Record who approves changes and renewals. A project handover does not automatically include ongoing monitoring, on-call support or the cost of a platform subscription. Make those boundaries understandable before the engagement ends.
Keep a useful record of the result
The acceptance notes should reference the agreed requirements and the evidence used to check them. Record known limits and provider dependencies rather than presenting a broad guarantee of permanent security or availability. Distinguish a defect in the agreed work from a new requirement discovered after delivery.
Remove temporary access
When delivery work is complete, review the access that was granted for the engagement. Transfer the agreed files and operational notes, remove temporary accounts where appropriate and record any retained materials under the relevant agreement and privacy policy. The goal is for the customer to understand the next step and retain the authority needed to take it.