Escrow set-up: stages and deadlines

Setting up a source-code escrow arrangement follows a fixed sequence: agreement, deposit, verification, and a release trigger. Each stage has its own deadline, and the sequence does not move to the next stage until the previous one is confirmed in writing. Miss one deadline and the arrangement resets to the point before it.

What escrow set-up covers

Escrow set-up is a contractual mechanism, not a filing with a public authority. Three parties sign: the licensor who deposits the material, the licensee who may later call for release, and an independent agent who holds the deposit and checks whether a release condition has occurred. No register records this step. The agreement itself is the only record that matters, and its wording decides everything that follows.

Set-up ends once the agent confirms that the first deposit matches the description agreed by the parties. Everything before that confirmation is negotiation. Everything after it is monitoring.

Practical consequence

Until the first deposit is verified, the licensee has no enforceable right to anything. A signed escrow agreement without a verified deposit is a promise, not a safeguard. This is the point most licensees overlook: the signature date and the protection date are rarely the same date.

Once verification is confirmed, a second clock starts. Every later release or patch covered by the agreement carries its own deposit deadline, usually tied to the licence term rather than to a fixed calendar date.

Typical stages and timing

Stage	Typical duration	Who acts
Agent selection and fee agreement	1–3 weeks	Licensee, with the licensor's consent to the chosen agent
Drafting and negotiating the escrow agreement	2–4 weeks	Both parties, agent provides the template
First deposit	Within the deadline set in the agreement, commonly 30 days from signature	Licensor
Verification of the deposit	1–2 weeks after deposit	Agent, sometimes with a technical reviewer
Update deposits	Recurring, tied to each new release	Licensor
Release on a trigger event	Set by the agreement, commonly 10–30 days after notice	Agent, following the licensee's notice and the licensor's right to object

What to do

Select an independent agent before drafting the agreement; the agent's own template shapes most of the later clauses.
Agree the definition of "deposit material" in writing, covering source code, build scripts, and supporting documentation.
Set a firm deadline for the first deposit and tie it to the licence's effective date, not to a separate calendar date.
Require written confirmation of verification from the agent before treating the arrangement as active.
If the arrangement covers work carried out by contractors, review Subprocessors, including local delivery partners overview and the deadline before signing.
Calendar every future release against its own deposit deadline; a missed update deposit weakens the arrangement even where the first deposit was verified.

Who decides

The agent decides whether a release trigger has occurred, based only on the wording the parties agreed. The agent does not rule on the merits of a wider contract dispute between the parties.

The party entitled to call for release is usually described in the agreement as the holder of the release right. For a wider explanation of that term, see Holder tokenised rights explained and the deadline.

If the licensor objects to release, the agreement's own dispute clause applies first, not a court. Courts become relevant only once the contractual objection period has expired without resolution.

If your situation differs

If you are the licensee and the licensor has entered insolvency proceedings, release usually still requires formal notice to the agent, not automatic release. Confirm the notice mechanism before assuming release is immediate.

If you are the licensor and support for the product is being discontinued, update the agreement's trigger list before discontinuation is announced publicly. A trigger added afterwards is unlikely to apply retroactively.

If no agent has been appointed yet and a dispute has already started, set-up cannot substitute for evidence already in dispute; treat the two tracks separately.

What this page does not cover

This page describes the set-up sequence only. It does not cover how much deposit material is adequate, and it does not cover how a court weighs a deposit once a dispute is already underway.

Where the arrangement needs to be assessed against the counterparty's financial standing before it is even signed, that question is covered separately: Counterparty report before extending credit and its limits in.

Where a dispute over release relies on the deposited material as evidence, the evidentiary question is addressed separately: Document report before relying on it in a dispute.

Verified

This overview was last reviewed in November 2025. It reflects standard three-party escrow structures used across technology licensing and does not rely on statutory citations, which fall outside the scope of a procedure page.

FAQ

How long does escrow set-up take in practice?

Agent selection and drafting typically take four to seven weeks combined. The first deposit follows within the deadline set in the agreement, commonly thirty days from signature, and verification adds one to two further weeks.

Which documents are needed to start?

You need the underlying licence agreement, a written description of the deposit material, the chosen agent's standard escrow template, and confirmation of who holds the release right.

What happens if the other side does not respond?

The agreement's notice clause sets a response deadline. If that deadline passes without a reply, the agreement usually lets the requesting party proceed to the next stage unilaterally, subject to the objection period still running.