The project is complete, the final demonstration is approved and the source code has been shared. A week later, the client needs to update an email setting. Nobody is sure which account controls it.
This is a handover problem. A product has been delivered, but the knowledge needed to operate it remains scattered across conversations and personal accounts.
Begin the handover before the final week
Keep operational notes as the project develops. Record which services are used, who owns the accounts and how environments differ. Updating a working document is easier than reconstructing months of decisions immediately before launch.
Give the receiving team access early enough to try it. Access that has been invited but never tested can still fail at the moment someone needs to publish an urgent correction.
Transfer ownership deliberately
Domain registration, hosting, database access, storage, email delivery and analytics may belong to different providers. Identify the business owner and the technical contact for each one. Confirm that billing and renewal notices reach the right people.
Use appropriate account permissions and secure credential-sharing procedures. A private message containing a password is not a durable ownership plan. Explain how former collaborators lose access after their work ends.
Document the ordinary tasks
Show how to publish content, add a user, change a setting and investigate a failed submission. These are the tasks the receiving team will actually perform. Short instructions with clear starting points are often more useful than a long architecture document alone.
Include the boundaries. State which changes are safe through the admin interface and which require a developer. If publishing data also needs a site build for static pages, write down that dependency and the release command.
Walk through a release and a recovery
The next maintainer should know how to run the project, supply environment configuration, execute the relevant checks and release a build. Keep secrets out of the repository while documenting the names and purpose of required settings.
Explain how to restore a previous release and where backups can be found. A backup policy should include a way to verify restoration, rather than assuming that the existence of files proves recovery will work.
Ask the receiving team to demonstrate
- Sign in with the accounts they will use after handover.
- Publish a harmless content change in the appropriate environment.
- Run the documented checks and locate release output.
- Find the support route for an external service.
- Explain how they would respond to a failed release.
Use the questions from that session to improve the documentation. Finish with a clear list of outstanding items and the agreed support period. A successful handover leaves the next person able to operate the product with confidence and a known place to ask when something unusual happens.



