Escrow arrangements: what the decision maker looks at
An escrow arrangement holds source code, documentation or other licensed materials with an independent agent until a defined trigger occurs. The agent does not decide who is right in a dispute. It checks whether the deposit is complete, whether the trigger is proven, and whether the release instruction matches the agreement. Everything beyond that sits with the parties themselves.
How the arrangement is structured
Three roles sit inside a typical arrangement: the depositor, usually the licensor who owns or controls the materials; the beneficiary, usually the licensee who needs access if support stops; and the agent, who holds the deposit and applies the release conditions written into the agreement. The agent is a checkpoint, not a judge of the underlying dispute.
The agreement itself sets the trigger events. Common triggers include insolvency of the depositor, cessation of support beyond a stated period, or a material breach that the beneficiary must evidence in a defined way. The wording of the trigger, not the general fairness of the situation, is what the agent applies.
What the agent checks before release
Before releasing anything, the agent runs a narrow verification. It is procedural, not substantive: the agent confirms form, not merits.
| Trigger claimed | What the agent verifies | Typical evidence required |
|---|---|---|
| Insolvency of the depositor | Formal status confirmed by an independent register or appointed officer | Court order, administrator's notice, or equivalent register extract |
| Cessation of support | Elapsed time against the period stated in the agreement | Correspondence log, support ticket history, notice sent to the depositor |
| Material breach | Whether the notice procedure in the agreement was followed | Breach notice, cure period expiry, depositor's response or silence |
| Deposit accuracy dispute | Whether the deposited material matches the verification report on file | Verification report, build log, hash comparison where available |
If any check fails, the agent does not release. It notifies both sides and, depending on the agreement, either waits for a joint instruction or refers the dispute to whatever forum the agreement names.
Documents needed to start
Opening an arrangement is faster when the depositor's ownership chain is already documented, rather than reconstructed after a dispute arises. For deposited software, this typically means proof of who created the code and under what terms, particularly where employees or contractors were involved rather than the licensor alone. Our page on Employee-created program in ownership of results sets out how that proof is usually assembled.
Beyond ownership evidence, the agent will ask for: the materials to be deposited, in the format agreed; a description sufficient to identify what has been deposited; the licence or transfer agreement that the escrow supports; and named contacts on both sides authorised to give or receive instructions.
What to do
- Depositor prepares the deposit package and a description of its contents before the agent will accept it.
- Depositor and beneficiary agree the trigger events in writing, inside the escrow agreement itself, not by side letter.
- Agent runs an initial verification of the deposit and issues a verification report to both sides.
- Where the deposit is delivered digitally rather than on physical media, the parties should confirm the accepted method of electronic delivery in advance; the approach used for other digital deposits is described in Electronic submission in tokenised rights: what changed and who.
- Beneficiary monitors for a trigger event and, if one occurs, sends a release request with supporting evidence to the agent.
- Agent verifies the request against the agreement and either releases the deposit or raises a query before proceeding.
Who decides
The escrow agent decides the narrow question of whether the release conditions on paper have been met. It does not decide whether the underlying breach actually occurred, whether the licence was validly terminated, or who owns the materials in the first place — those questions go to whatever forum the licence or transfer agreement names, typically arbitration or the courts agreed by the parties.
Where the agent itself uses a third party to store or process the deposit, that party sits in the same category as any other outsourced processing function; our general approach to such arrangements is set out in Subprocessors, including local delivery partners overview step by step.
If the depositor and beneficiary disagree about whether a trigger occurred, the agent typically pauses and asks for a joint instruction or a ruling from the named forum. It does not resolve the substantive dispute on its own authority.
Forks
If the depositor disputes the trigger. The agent does not release on the beneficiary's request alone. It waits for either a joint instruction or a decision from the forum named in the agreement, and the timeline extends accordingly.
If the depositor becomes insolvent. The agent looks for an independent confirmation of that status, such as an administrator's notice, rather than relying on the beneficiary's assertion. Once confirmed, release usually follows without further dispute.
If the deposit itself fails verification. The agent flags the gap at the verification stage, well before any trigger arises. The depositor is then asked to supplement or correct the deposit; an unresolved gap is a separate problem from the trigger dispute and should be closed early.
Practical consequence
Release of the deposit is only the operational half of the outcome. Where the underlying rights also sit on a public register — trade marks or design rights associated with the licensed product, for instance — a change of controller following release usually needs to be reflected there separately; the stages involved are described in Recordal of assignment. Escrow release does not itself update those registers.
Beneficiaries sometimes treat release as the end of the process. In practice it is the start of an integration task: the released materials need to be usable, and usability is not something the escrow agent certifies.
Limit
This page describes how a release decision is reached procedurally. It does not resolve whether a particular breach is material, whether a licence was validly terminated, or how a released deposit should be valued or used going forward. Those questions depend on the specific agreement and, where disputed, on the forum it names.
Verified
Checked and current as of the review date shown on this page. This description reflects common escrow practice used in licensing and transfer arrangements; agreements vary, and the trigger and verification wording in your own agreement always takes precedence over the general pattern described here.
Related publications
A comparable mechanism, used to secure a different kind of interest over rights rather than to hold materials for release, is covered in Registration of a pledge over rights step by step.
FAQ
How long does an escrow arrangement take in practice?
Setting up the arrangement, including the first verification of the deposit, usually takes longer than the release step itself. Release, once a trigger is confirmed and undisputed, is typically the fastest part of the whole process, because the agent's check at that stage is narrow.
Which documents are needed to start?
At minimum: the deposit itself with a description of its contents, the licence or transfer agreement the escrow supports, proof of the depositor's ownership chain where the materials were created by employees or contractors, and named authorised contacts on both sides.
What happens if the other side does not respond?
Non-response to a release request does not automatically trigger release. The agent applies whatever the agreement says about silence — commonly a defined waiting period after which the request is treated as unopposed, but this is set by the agreement itself, not assumed by the agent.