Software Escrow Agreement (Pakistan)

A Software Escrow Agreement in Pakistan records the bargain between the parties, fixing their respective rights, duties and remedies.

The Contract Act 1872 provides the legal foundation for the Software Escrow Agreement as an enforceable tripartite contract. Section 10 of the Contract Act 1872 requires that the agreement meet the standard requirements for a valid contract — lawful offer, acceptance, consideration, capacity, and free consent. The escrow arrangement creates obligations on all three parties: the depositor must deliver the deposit materials as specified; the escrow agent must store the materials securely and release them only in accordance with the agreement; and the beneficiary must pay the escrow fees and comply with the conditions precedent to release. Section 148 of the Contract Act 1872 defines bailment as the delivery of goods by one person to another for some purpose, upon a contract that they shall be returned or otherwise disposed of according to the directions of the person delivering them — the escrow agent's custody of the source code closely resembles a bailment, imposing on the agent the duty of a bailee under Sections 151–154 of the Contract Act 1872 to take as much care of the escrow materials as a person of ordinary prudence would take of their own goods.

The Copyright Ordinance 1962 is central to the Software Escrow Agreement because source code is a copyright-protected literary work under Section 2(c) of the Copyright Ordinance 1962. The escrow arrangement involves the depositor delivering a copy of the source code to the escrow agent — an act that would ordinarily constitute a breach of the developer's exclusive right of reproduction under Section 15 of the Copyright Ordinance 1962 if not authorised by the licence agreement. The Software Escrow Agreement must therefore include express provisions authorising the depositor to deposit the source code with the escrow agent without constituting a publication or transfer of copyright, and authorising the escrow agent to hold and — upon a trigger event — reproduce and deliver the source code to the beneficiary pursuant to a limited escrow licence.

In Pakistan's technology market, Software Escrow Agreements are most commonly used in enterprise software licensing transactions — where a large corporation, government ministry, or financial institution licences critical software from a mid-sized Pakistani software house or from a foreign software vendor. The beneficiary's concern is continuity of operations: if the developer becomes insolvent, is acquired by a competitor, or ceases to maintain the software, the beneficiary needs access to the source code to continue operating, maintain, and enhance the software using its own or third-party developers. Without escrow, the beneficiary may find itself unable to maintain mission-critical software and facing costly emergency replacement.

Escrow agents in Pakistan include law firms, chartered accountants, licensed banks approved by the State Bank of Pakistan (SBP), and specialist technology escrow service providers. The escrow agent's obligations and liability must be carefully drafted — the agent must maintain the deposit materials in secure, climate-controlled storage (or encrypted digital storage), maintain a current copy of the deposit materials (updated with each new software release), and have a clearly defined process for verifying release trigger events and notifying the parties before release.

The Software Escrow Agreement should be read alongside the main Software Licence Agreement and the Software Development Agreement — the three documents together constitute the complete contractual framework for a major software licensing relationship in Pakistan. The escrow agreement should expressly state that it is supplemental to and does not replace the primary licence agreement, and that the beneficiary's rights under the escrow are in addition to, not in substitution for, the beneficiary's rights under the licence agreement.

A Software Escrow Agreement in Pakistan is needed whenever a business or organisation licences software that is critical to its operations from a developer or vendor, and the licensee requires assurance that it will retain access to the software and its source code if the developer becomes unable to continue supporting it.

The agreement is needed when a bank, microfinance institution, or insurance company regulated by the State Bank of Pakistan (SBP) or the Securities and Exchange Commission of Pakistan (SECP) licences a core banking system, insurance management system, or financial technology (fintech) platform from a software vendor. SBP's IT Risk Management Guidelines and SECP's technology governance requirements for regulated financial institutions encourage or require software escrow arrangements for critical third-party software, recognising that vendor failure or cessation of support creates systemic operational risk.

A Software Escrow Agreement is needed when a government ministry, autonomous body, or public sector organisation — such as the National Database and Registration Authority (NADRA), the Federal Board of Revenue (FBR), or a provincial government department — procures a large-scale e-governance or enterprise software system under the Public Procurement Rules 2004. Government procuring entities require assurance that critical digital infrastructure will remain accessible to them in perpetuity, and escrow is a standard mitigation for vendor lock-in and continuity risk.

The agreement is required when a manufacturing company, retail chain, or logistics company licences an enterprise resource planning (ERP) or warehouse management system from a domestic Pakistani software company whose financial stability or long-term operational continuity is uncertain. If the software vendor is a small or medium-sized company, the risk of business failure or acquisition is real — escrow protects the licensee from losing access to mission-critical software.

A Software Escrow Agreement is needed when a software development agreement contains a staged delivery structure and the client wants assurance that intermediate source code deliverables — which the developer retains until full payment — will be accessible if the developer becomes insolvent before full delivery and payment. The escrow allows the partial deliverables to be preserved independently of the developer's financial stability.

The agreement is also needed when a multinational company entering Pakistan's market licences software from a local Pakistani developer and the head office risk management team requires an escrow arrangement as part of the standard vendor management due diligence process. International business partners commonly include software escrow as a contractual requirement in their vendor qualification procedures.

A valid Software Escrow Agreement in Pakistan under the Contract Act 1872 and the Copyright Ordinance 1962 must contain the following essential elements.

Parties: Full legal names and addresses of the three parties — the depositor (software developer or licensor), the beneficiary (software licensee or client), and the escrow agent — together with their respective SECP registration numbers (for companies under the Companies Act 2017) and NTN numbers with the Federal Board of Revenue (FBR). The escrow agent must be identified by name and its qualification to act as escrow agent should be stated — whether it is a law firm, chartered accountant, licensed bank under the State Bank of Pakistan, or specialist technology escrow provider.

Deposit Materials: A precise description of the materials to be deposited with the escrow agent, including: the complete source code in the programming language(s) used; all build scripts, compilation instructions, and development environment specifications needed to compile the source code into executable software; database schemas, data migration scripts, and configuration files; technical documentation, system design documents, and code comments; third-party libraries and components incorporated in the software (with licence details); and any cryptographic keys, certificates, or access credentials necessary to run the software. The deposit materials must be sufficiently complete that a competent developer who has never worked on the software can, using only the deposit materials, compile, deploy, and maintain it.

Deposit and Update Obligations: The frequency with which the depositor must deliver updated deposit materials to the escrow agent — typically upon each major software release, version update, or at minimum annually. The escrow agent must maintain records of all deposit versions and their delivery dates. The beneficiary should have the right to request periodic verification of the deposit materials to confirm they are current, complete, and compilable.

Release Trigger Events: The specific events that entitle the beneficiary to request release of the deposit materials from the escrow agent. Standard trigger events under a Software Escrow Agreement in Pakistan include: the depositor becoming insolvent or having a winding-up petition presented against it under the Companies Act 2017; the depositor ceasing to carry on business in the field of software development; the depositor's material breach of the main software licence agreement that remains unremedied after the notice period; and the depositor's failure to provide contracted maintenance and support services for a specified consecutive period.

Release Procedure: The procedure the beneficiary must follow to request release — typically a written notice to the escrow agent specifying the trigger event with supporting evidence. The escrow agent must notify the depositor of the release request and allow the depositor a specified period (typically 15–30 days) to dispute the claim. If the depositor disputes the release claim, the agreement should provide a fast-track dispute resolution mechanism, such as expert determination by a neutral technical expert, to avoid prolonged litigation that would defeat the purpose of the escrow.

Escrow Fees: The initial setup fee, annual maintenance fee, and any per-release fee payable by the beneficiary (or shared between the parties) to the escrow agent for its services. The fees must represent fair compensation for the escrow agent's secure storage, version management, and release processing obligations. The escrow agent's liability for loss or damage to the deposit materials should be addressed — under Section 152 of the Contract Act 1872, the bailee's standard of care requires reasonable diligence.

Confidentiality: The escrow agent's obligation to keep the deposit materials strictly confidential and not disclose or copy them except as required by the agreement. This obligation is reinforced by the Prevention of Electronic Crimes Act 2016 (PECA), which criminalises unauthorised access to or copying of data.

Forms-legal.com provides this Software Escrow Agreement (Pakistan) template as a practical reference document for software licensors and licensees seeking to manage continuity risk. The template reflects the requirements of the Contract Act 1872 and Copyright Ordinance 1962. Parties should engage an IT lawyer enrolled at a provincial Bar Council and, for major financial sector implementations, confirm alignment with State Bank of Pakistan IT Risk Management Guidelines.

Under the Companies Act 2017, the Securities and Exchange Commission of Pakistan (SECP) maintains the register of Pakistani companies. Section 16 of the Companies Act 2017 governs company incorporation. The Contract Act 1872 governs general contractual obligations. The Federal Board of Revenue (FBR) administers corporate tax under the Income Tax Ordinance 2001. The High Courts (Lahore, Sindh, Peshawar, Balochistan, Islamabad) have original and appellate jurisdiction.