Skip to content
Outrich Data

Glossary

Release conditions

Release conditions are the facts that must be true before an escrow holder pays out funds or hands over data. In a data sale the main condition is acceptance: the delivered dataset has passed the checks written into the license. Conditions should be objective, finite and tied to a named decision maker.

A release condition turns a commercial promise into something an escrow holder can act on. The holder cannot decide whether data is good. It can confirm that a named person has stated in writing that a listed check passed. Conditions are therefore written as events: receipt of an acceptance notice, expiry of a review period, receipt of a joint instruction, or a decision from the forum named in the license.

Three traits make a condition workable. It is objective, so two people applying it reach the same result. It is finite, so the escrow cannot stay open without limit. It names who decides. Many agreements add deemed acceptance, under which silence from the buyer through the review period counts as acceptance. Others split the release, paying part of the fee on acceptance of the first delivery and the remainder on a later refresh. Vague conditions, such as satisfactory delivery, are the usual cause of a frozen escrow.

Conditions should be tested before signing. For each one, the parties should be able to say who will confirm it, with what document and by what date. If no clear answer exists, the wording needs more work.

Find out if your data qualifies.

Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.

esc