Escrow arrangements: documents to prepare
An escrow arrangement holds source code, keys or other licensed material with a neutral third party until a release event occurs. The documents that matter fall into three groups: the deposit material itself, the escrow agreement between depositor, beneficiary and agent, and the underlying licence that the escrow is meant to protect. Missing any one of the three delays the deposit and, in a dispute, weakens the beneficiary's position.
What changes in practice
Without a signed escrow agreement, an agent will not accept material, however complete it is. Without a current deposit description matched to the licence, a release request can be refused on the ground that the deposit does not correspond to what was licensed. Timing therefore runs on two tracks: preparing the paperwork and preparing the technical deposit, and the slower of the two sets the date the arrangement actually starts.
Documents to prepare
| Document | Purpose | Prepared by |
|---|---|---|
| Escrow agreement | Sets deposit, verification and release terms between depositor, beneficiary and agent | Depositor and beneficiary, jointly drafted |
| Underlying licence or supply contract | Defines what the escrow is meant to secure and cross-references release triggers | Licensor and licensee, already in force |
| Deposit description | Lists exact contents, version, format and build instructions of the material deposited | Depositor, technical team |
| Verification report | Confirms the deposit is complete, buildable and matches the description | Escrow agent or independent verifier |
| Release notice | Formal trigger document invoking a release event under the agreement | Beneficiary, at the time of the event |
| Update schedule | Records each subsequent deposit as the licensed product changes | Depositor, on an agreed cycle |
What to do
- Confirm the underlying licence contains an escrow clause with named triggers before drafting anything else.
- Select an escrow agent and agree its standard terms, verification scope and fee structure.
- Prepare the deposit description together with the technical team responsible for the product.
- Sign the three-party escrow agreement and deliver the first deposit within the agreed window.
- Request an independent verification of the first deposit before relying on it.
- Set a recurring schedule for updates so the deposit never falls behind the licensed version.
Who decides
The escrow agent decides whether a deposit meets the agreed description and whether a release notice satisfies the trigger conditions written into the agreement. The agent does not decide whether the underlying contract has actually been breached; that question sits with the parties or, if they disagree, with whichever forum the licence itself designates. Where the agreement is silent on a release request, the agent typically holds the material and asks both sides to confirm their position in writing before acting.
Forks
If the licence already names an escrow agent and a set of triggers, the agreement can often be signed within days once the deposit is ready. If it does not, drafting the escrow terms from scratch adds a separate negotiation before any deposit takes place. If the deposit is source code tied to a wider product, questions about who owns underlying contributions can surface at the same time; see AI products and models a contractor claims ownership of before finalising the deposit description. If the release also requires transferring registered rights rather than only releasing code, the separate step of Recordal of assignment follows a different timetable and should not be assumed to happen automatically.
Point of no return
Once the escrow agent has verified a deposit and issued a verification report, the deposit is treated as accepted for the version described. Correcting an error after that point means a new deposit and a new verification cycle, not a silent amendment. Depositors who skip verification to save time carry that risk into the release stage, when there is no longer an opportunity to check the material before it matters.
Limit
This page covers the documents needed to set up and maintain an escrow arrangement for licensed material. It does not cover how a specific escrow provider prices its service, how a court would assess a disputed release, or how a security interest over the same rights is registered; a pledge follows its own paperwork, described in Registration of a pledge over rights step by step. It also does not cover escrow for tokenised or blockchain-based rights, where control can be lost in a different way; that situation is addressed separately.
Verified
Reviewed against current escrow agent practice and standard licensing precedent as of this publication. This page does not cite statutory provisions: the escrow mechanism is contractual, and the applicable rules come from the agreement the parties sign, not from a specific enactment. Our approach to collecting and dating source material is set out in Methodology: collection, cross-checking and dating and the evidence.
FAQ
How long does escrow arrangements take in practice?
Signing the escrow agreement itself can take a few days once terms are agreed. The overall timeline usually depends on how quickly the deposit description and the first build are ready on the depositor's side.
Which documents are needed to start?
At minimum: the underlying licence with an escrow clause, the three-party escrow agreement, and a deposit description matching the licensed version. Everything else follows from those three.
What happens if the other side does not respond?
The escrow agent will typically hold the deposit and wait for a response within the period set in the agreement before treating silence as acceptance or refusal of a release request.
If control of a related arrangement has already slipped, When the issuer loses control of the contract in sets out the first steps to take. For a wider view of where escrow fits among licensing tools, What to do first in this situation covers a related deadline scenario worth checking against your own file.