A business receives a source-code archive but the live site, phone number, and database remain in accounts controlled by the departing developer. Possessing files does not establish that the business can operate or maintain the product.
Use an asset-and-access checklist when discussing delivery terms and handover. Legal ownership and licence questions should be reviewed with an appropriately qualified adviser; this checklist addresses operational control.
Inventory the assets behind the running product
Include repositories, deployment projects, domains, database services, storage, phone numbers, provider integrations, analytics, and administrative email addresses.
| Asset | Practical question |
|---|---|
| Source repository | Which organisation owns it and who has appropriate access? |
| Hosting | Can the business deploy and inspect failures? |
| Domain | Who controls registration and DNS changes? |
| Data service | Can authorised staff export and recover records? |
| Third-party accounts | Who owns billing, permissions, and support contact? |
Do not record live secret values in the contract or public handover document. Record the account and controlled transfer process.
Separate permission from legal ownership
Repository access can permit collaboration without determining every right in the code or dependencies. Conversely, a contractual right is not a working login or a tested deployment path.
GitHub's repository transfer documentation describes its platform process. Verify the current requirements and effects for the actual repository before planning a move.
Use the provider's supported transfer or access procedures rather than sharing a former contributor's personal password.
Ask about dependencies and reusable components
Identify third-party packages, models, hosted services, and pre-existing components that affect ongoing use or transfer. Have the relevant agreement and licence questions reviewed rather than assuming everything in a folder carries identical terms.
Keep contributions and confidential customer material clearly separated where needed. An engineer should not provide another client's private code as proof of experience or as an undocumented shortcut.
Verify the handover through an authorised new operator
Have another authorised person follow the documented setup and deployment process in an appropriate environment. Confirm that monitoring, backups, and support contact details remain available.
Remove obsolete access through the agreed offboarding procedure after the transition is verified. Avoid disrupting a live service before replacement access works.
The technical-handover guide provides the related operating evidence.
Ownership-check questions
Is a ZIP file a complete operational handover?
Not when the running product depends on accounts and configuration outside it.
Does administrator access settle every licence question?
No. Have legal and dependency questions reviewed separately.
What should be written down early?
Document the asset inventory, intended account owners, and handover acceptance in the project brief.