Underwriters who provide insurance cover against loss of profits to corporate entities can improve their risk profile in this area by insisting that clients lodge mission-critical software source code in escrow. The key advantage of doing so is to ensure software applications which are vital to the profitable operation of the business could be recompiled and re-deployed quickly and completely, should the software supplier (for whatever reason) become unable to support or maintain their product(s).
Organisations that are reliant on computer technology, wholly or in part, for generating revenues and profits are at serious risk if their software supplier is liquidated, or merges with another business that is unable or unwilling to support the product (or wishes to do so only under commercially unacceptable terms), or otherwise stops servicing their product, says Andrew Stekhoven, Managing Director of Escrow Europe (South Africa), a leading provider of active software escrow and related services.
"The reason is that the vast majority of software procurement agreements involve a licence for, or use of, the software in object code format only. Object code is readable only by a machine (ie, the computer system), and cannot be debugged, corrected, maintained or updated in this format.
"The power of escrow is that, in the event of the supplier no longer being available, the escrow arrangement provides for access by the end-user to the source code of the product, which is human readable, can be debugged, corrected and updated, and thereafter compiled into object code for re-installation on the computer."
Escrow agreements are already common cause in Europe and the US (even SAP end-users are protected by source code escrow arrangements) but are still a little known component of good corporate governance in South Africa.
It should be obvious to players in the insurance underwriting arena that software escrow could be a significant risk reduction tool, if it were made mandatory for clients seeking cover against loss of profits, Stekhoven believes.
"Properly designed and managed escrow lowers the underwriter`s risk by ensuring the end-user has access to source code under specified future conditions. In particular, escrow ensures there is guaranteed access and legal right to the escrow material by the end-user; that the source code in escrow will be complete and recompilable in the event of such a release; and that the end-user, who has then had prior opportunity to ensure the availability of suitably qualified resources, will be able support and maintain the software in the absence of the supplier.
"Thus, in effect, the escrow agreement is a `technical insurance policy` that guarantees end-user business continuity in the event of the kind of problems as discussed above. As such, it should be attractive to all underwriters who seek to remove elements of doubt and uncertainty in framing agreements involving profit-loss cover," concludes Stekhoven.
Editorial contacts

