Information technology
Software project handover template (US)
A general template under US law. Laws differ from state to state, so check it against your state's law or with a lawyer licensed there. We are not a law firm and do not give legal advice.
Fill in this template- Written for US law, with your state left to fill in
- Fill the blanks in your browser
- Print or save as PDF; Word is 15 points
- Start right away, sign in to download
Preview — US standard
Software Project Handover Certificate
Project: Project Name
Contract or statement of work: Contract or SOW Reference and Date
Client: Client Name
Developer: Developer Name
Handover date: Handover Date
1. Items Delivered
| Item | Location or Format | Delivered |
| Complete source code, with full commit history | Repository URL or Archive | Yes or No 1 |
| Build and deployment scripts | Location 2 | Yes or No 2 |
| Database schema and migrations | Location 3 | Yes or No 3 |
| Technical documentation and architecture diagrams | Location 4 | Yes or No 4 |
| User and administrator guides | Location 5 | Yes or No 5 |
| Test cases and test results | Location 6 | Yes or No 6 |
| List of third-party and open-source components with licenses | Location 7 | Yes or No 7 |
2. Accounts and Credentials
The following accounts have been transferred to the client, with ownership and administrator rights in the client's name: Accounts, such as Cloud Hosting, Domain Registrar, App Store, Code Repository, Email and Payment Services.
All credentials were delivered through Secure Method, such as a Password Manager Share, not by plain email. The developer has removed or will remove its own access by Access Removal Date, except: Retained Access for Warranty Support, or None.
3. Environments
Production URL: Production URL
Staging URL: Staging URL
Hosting provider: Hosting Provider
4. Intellectual Property
On full payment, ownership of the deliverables and the custom code passes to the client as provided in the contract. Open-source components remain under their own licenses. The developer keeps its pre-existing tools as licensed in the contract.
5. Known Issues
Known Issues and Limitations, or None
6. Warranty and Support
The warranty period of Warranty Period begins on the handover date. Support after that is Support Arrangement, or Not Included.
7. Data and Security
The developer confirms it has deleted or returned all client personal data and production data in its possession, except: Retained Data and Reason, or None.
8. Acceptance
The client confirms receipt of the items above. This certificate does not waive the client's rights for defects not apparent at handover.
| Developer | Client |
| Signature: Developer Signature | Signature: Client Signature |
| Name and title: Developer Signer Name and Title | Name and title: Client Signer Name and Title |
| Date: Developer Signing Date | Date: Client Signing Date |
Frequently asked questions
Do I need an account to use this template?
Start right away and fill it in in your browser; signing in is needed to download or print. It takes seconds, and every new account gets free points.
How do I save it once filled in?
Fill in the blanks online, then print it or save it as PDF. An editable Word file is 15 points.
Are my files private?
Your files are kept in private storage no one else can reach, and are deleted from the servers automatically within two days at most.
