Software acceptance, source-code handover and maintenance checklist
Launch is one milestone. Verify source code, deployment, accounts, data, licences, recovery and support so another team can take over.
Author:WeTech technical team · Updated: (Hong Kong time (GMT+8))
Accept both functional results and operational deliverables. Source-code handover needs more than a ZIP file: versions, build instructions, configuration, account control, data structure, licences and recovery procedures must be usable. Define maintenance separately, distinguishing defects, support, enhancements and incident response. Confirm ownership and licence terms in the agreement rather than assuming that repository access transfers every right.
When to use this guide
For businesses preparing to launch, change suppliers, take control of system administration or agree a maintenance contract.
Require evidence for handover
| Deliverable | Verification | Owner confirms |
|---|---|---|
| Source and version | Rebuild from the agreed version | Repository control, dependencies and licences |
| Deployment and configuration | Deploy to a test environment using the runbook | Environments, secret management and rollback |
| Data and backup | Reconcile and exercise a restore | Retention, deletion, backup access and recovery |
| Operations and support | Exercise alerts and incident handoff | Support channel, response scope and escalation |
Accept against the agreed scope
Record expected and actual results, defect severity and revisions against each acceptance condition. Cover normal and exception workflows. Assign owners and retest arrangements for open items and state whether they block launch. The business owner accepts the workflow while the technical owner reviews deployment and permissions. Supplier testing alone does not establish that users can complete the agreed business task.
Prove handover through rebuild and restore
Have the receiving team build in a separate test environment from the documentation. Verify dependency versions, database changes, scheduled jobs and external services. Transfer secrets through an appropriate channel and rotate them where needed; do not put them in source code or public documents. Repository transfer is only one step. Confirm control of domains, hosting, analytics and email accounts individually.
Make maintenance terms specific
Separate defects in agreed functionality, third-party changes, dependency updates, user support and new features. Specify support hours, incident levels, response and recovery targets, exclusions and escalation. A response target is not a guaranteed fix time. Assign backup ownership and verify restoration. Record maintenance changes against versions so the next handover includes an accurate operating history.
Frequently asked questions
Does receiving source code transfer all rights?
Confirm ownership and third-party licences in the agreement. Access to code does not replace those terms.
Why test restoration if a backup exists?
A backup may be incomplete or unusable within the required time. A restore exercise verifies data, files and dependencies.
Does maintenance include every new feature?
Check the contract scope. New workflows, integrations and substantial redesigns need separate estimation and agreement.
Brand and public case scope
WeTech Consulting, also called WeTech or WeTech AI HK, provides AI and IT consulting in Hong Kong. WeProperty HK and WeCredit HK are self-developed products. Their cases support the observable features listed: property, estate and transaction-reference entry points for WeProperty; submission, review and public-data masking for WeCredit. WeCredit is not a TU credit-rating service or a final determination of facts.
WeProperty HK · WeCredit HK (case studies in Traditional Chinese)
Reference sources
Official documents support the technical, risk and measurement concepts. Checklists, estimation methods and illustrative scenarios are WeTech planning recommendations, not official prices or client results. Check the supplier’s current plan and terms. Sources reviewed: (GMT+8)
Related guides
Discuss your project
Share your workflow, systems and goals. We will review scope before discussing deliverables, acceptance and a quotation.
Request an initial consultationExplore this service