Escrow clause (source code and software continuity) template clause
Updated: 17 November 2026
Please note: these example clauses are intended as a starting point, not as legal advice. Always adapt the text to your specific situation and have important contracts reviewed by a legal professional.
Clause text
1. Within [number, e.g. 30] days of signing this agreement, Supplier shall deposit with [name of escrow agent] ("the Escrow Agent") the source code of [name of the software] ("the Software"), together with the technical documentation, build instructions, the development tools and libraries used with their versions, and the scripts and configuration needed to install the Software and put it into production (together, "the Deposit"). For this purpose the parties shall enter into a three-party agreement with the Escrow Agent based on the model in Annex [X].
2. Supplier shall update the Deposit within [number, e.g. 30] days of each new major version of the Software and in any event once every [number, e.g. 6] months. The Deposit shall at all times match the version Customer is using.
3. Once per contract year, Customer may have the Escrow Agent carry out a verification in which an independent expert checks whether the Software can be built and installed from the contents of the Deposit. If the Deposit proves incomplete, Supplier shall complete it free of charge within [number, e.g. 20] working days and shall bear the cost of a repeat verification.
4. The Escrow Agent shall release the Deposit to Customer if:
a. Supplier is declared bankrupt or applies for a suspension of payments;
b. Supplier ceases its business or its support of the Software, without a third party taking over that support on the same terms;
c. Supplier fails to resolve a priority [1] incident within [number, e.g. 10] working days of a written notice of default; or
d. Supplier fails to update or complete the Deposit under paragraph 2 or 3 and does not remedy this within [number, e.g. 20] working days of a written reminder.
5. Supplier hereby grants Customer a non-exclusive, non-transferable and perpetual right to use and modify the source code in the Deposit, and to have it modified by third parties, solely for maintaining and continuing Customer's own use of the Software. Customer may exercise this right only after the Deposit has been released to it under paragraph 4.
6. Where the Software is provided as a service, the Deposit shall also include a description of the hosting environment and the access credentials needed to take over the production environment. Supplier shall ensure that the hosting environment remains available for at least [number, e.g. 3] months after a release event under paragraph 4, provided that Customer bears the hosting costs from that moment.
7. The Escrow Agent's fees shall be borne by [Customer / Supplier / the parties in equal shares]. A verification under paragraph 3 is at Customer's expense, except in the case described in the last sentence of that paragraph.
8. The confidentiality obligations in this agreement apply in full to any source code Customer receives on release.
What does this clause mean?
With custom software or a niche product you usually receive a right to use it, nothing more. The source code, which a developer needs to fix bugs or make changes, stays with the supplier. If that supplier disappears, nobody can work on the system any longer. An escrow arrangement solves this: the source code is held by an independent party, the escrow agent, and released to you in agreed situations. Legally it is a three-party deposit agreement. This clause puts the supplier's obligation to take part in your main contract and spells out what must actually be in the vault.
Paragraphs 1 and 3 are the difference between a usable deposit and an empty one. Source code without build instructions, library versions or installation scripts is a puzzle without the picture on the box for a new developer. Verification has an expert try to build the software from the deposit. That is not excess caution. According to Ironclad (2025), 92% of contract management errors are human errors, and a deposit that was never updated after the first delivery is a textbook case.
Paragraph 5 grants the licence now rather than on release, for a reason. In a bankruptcy the trustee controls the supplier's assets, and a right the supplier would still have to grant after being declared bankrupt is then out of reach. A right that already exists and only waits for the deposit to be released is in a far stronger position.
When should you use this clause?
Use the clause for software your operations run on and that you could not replace with another product within a few weeks: custom builds, an industry package from a small supplier, a scheduling system in healthcare, or a till or booking system in hospitality. For mainstream software with thousands of customers, escrow is rarely worth it; a data portability clause that lets you take your data to an alternative does more.
In a SaaS agreement, source code on its own is not enough. Without the servers, the database and the configuration nothing runs, which is why paragraph 6 also asks for the hosting details and a period in which the environment stays up. Place the clause next to your intellectual property clause and an exit clause, which covers the handover when the contract ends in the normal way.
Customize these elements
- 1Weigh the cost against the risk. An escrow agent charges an annual fee plus the cost of each verification. For a package costing a few thousand a year that is often too much; for the system your whole schedule depends on it is not.
- 2Run the first verification straight after the first deposit, not when something has gone wrong. Schedule the next one in the same quarter as the contract's notice deadline, so you know whether the deposit is in order when the renewal decision comes up.
- 3If you have no developers of your own, agree in advance with another software firm that it can take over the deposit after release. A deposit nobody can read does not help much.
- 4Record against the contract when the deposit was last updated and verified. If an update is missing, paragraph 4(d) lets you act on it, but only if someone notices.
- 5If the supplier uses open source components, ask for a list with their licences. Some licences attach conditions to modifying and distributing the code.
Sources
Manage all your contract deadlines automatically
Tracking Contracts alerts you well before every notice period. No spreadsheets, no missed renewals.
Start free month