Software Escrow
An escrow is basically used whenever two parties have an agreement or transaction wherein a third party is needed to temporarily keep the payment or asset until the transaction or agreement comes into effect. There are several kinds of escrow businesses and one type of escrow business is that which has a focus on software escrow which can be a corporation that can hold the escrow or individual persons that can hold on to the escrow. It normally doesn’t matter what kind of incorporation is involved as the entity that takes care of the escrow will try to minimize it’s responsibilities as much as possible.
Basics for a Legal Escrow Agreement
The entity that is chosen (corporate or individual) to handle the software escrow will normally prepare an initial draft of the software escrow agreement which will be signed later on by both parties involved. Depending on the number of people involved with the software vendor, escrow agreements can vary between a one-to-one transaction, or a multi-customer-single-vendor or single-customer-multiple-vendors type of transaction. For a many-to-one agreement, this usually involves a very large software vendor with a huge business and therefore has to cater to a escrow agreement where many customers can be involved. For a large customer, this user can have multiple software escrow agreements with plenty of vendors.
The software escrow business will also participate in the agreement, giving free advice and assistance. These kinds of contracts will give the foundation for a basic legal framework around which the interests of both the software vendor and the user are fairly and justly considered, particularly in the usability of the asset that will be put in escrow.
Storage for the assets that will be put in escrow must be offered by the escrow business and it has to be secure and safe. In cases like this, think of the storage area as something similar to a bank vault or a safe deposit box.
The parties involved, including the escrow business can now also be offered an inspection of the assets that will be put in escrow. This does not have to be comprehensive, just a high-level inspection to make sure that the software that will be actually put in escrow will have some use and are what is expected.
The escrow verification then takes place to make sure that the source code of the software can be compiled and built into the application that was agreed to be put into escrow for. This may cause some problems becauase a complete compilation may not be possible to completely compile the actual application and the vendor may protest that secrets may be revealed.
The communication between all parties involved in the escrow agreement should be continuous and open. Any changes or additions in the assets that are in escrow or any movements in the contract has to be communicated in an open way.
Escrow fees are also part of the standard software escrow agreement, such as annual software escrow fees but you have to also have some lee way for some additional fees or disagreements that may trigger an arbitration process to fix the escrow agreement.