Contract Review for Insurance Implications in India: Indemnity, Waivers, and Requirements

Most commercial contracts in India contain clauses that directly affect insurance placement, pricing, and claims recovery, yet the insurance manager is rarely in the room when contracts are negotiated. Legal teams mark up liability caps and dispute resolution clauses; procurement teams chase price and delivery terms; and the risk manager receives the signed agreement weeks later, expected to arrange insurance coverage consistent with obligations already locked in.

This sequence creates structural problems. A contract can require insurance that IRDAI-filed policy wordings cannot provide. It can strip the insurer of its subrogation recovery before the insured has even obtained the insurer's agreement to waive that right. It can impose unlimited indemnity obligations that a liability policy with a INR 10 crore limit will not fully cover. Fixing these mismatches post-signing is expensive, sometimes impossible, and always slower than catching them at the contract review stage.

The practical answer is to build an insurance review step into the contract approval workflow for any agreement above a defined threshold. Typically contracts exceeding INR 1 crore in value, or any contract in sectors with elevated liability exposure such as construction, IT services, and manufacturing. The checklist below covers the six areas where contract language most frequently creates insurance problems in the Indian market.

An indemnity clause shifts loss from one party to another by contract. Section 124 of the Indian Contract Act, 1872 defines a contract of indemnity as one by which one party promises to save the other from loss caused by the conduct of the promisor or a third party. Indian courts have historically read Section 124 narrowly: indemnity is triggered only by actual loss, not by mere exposure to a claim, and the indemnified party must prove damage before recovering.

Commercial contracts use three forms of indemnity language. Under a broad form clause, Party A indemnifies Party B even against B's own negligence. Under an intermediate form, A indemnifies B except where B was solely negligent. Under a limited form, A indemnifies B only for losses caused by A's acts. Indian courts, including the Supreme Court in ONGC v. Modern Construction and later decisions, have been reluctant to enforce broad form indemnities in favour of the indemnitee's own negligence unless the language is unambiguous and the parties were of equal bargaining power. A clause that purports to hold a contractor responsible for losses attributable entirely to the project owner's design errors carries real enforceability risk in Indian courts.

From an insurance standpoint, the critical question is whether the liability assumed under the indemnity clause is covered by the indemnifying party's policy. Standard commercial general liability and public liability policies in India typically include a contractual liability exclusion that covers cover tort-based liability but not liability assumed by contract in excess of what would have existed at law. If a construction subcontractor signs a broad form indemnity promising to cover all losses the main contractor incurs on the project site regardless of fault, the subcontractor's public liability policy will likely not respond to the portion of liability it would not have borne without the contract. This gap is significant: in Indian EPC projects, subcontractors routinely sign indemnities pushed down from FIDIC-based main contracts without reviewing their own policy wordings.

For risk managers, the action is to read every indemnity clause in a material contract and ask two questions: (1) is this indemnity enforceable under Indian law as written, and (2) does the indemnifying party's liability policy cover this contractual assumption? Where the answer to either question is no, renegotiate the clause or obtain a specific contractual liability endorsement before the contract is signed.

Subrogation is the insurer's right to step into the insured's shoes after paying a claim and recover from the party that caused the loss. If a fire caused by an electrical contractor destroys the project owner's equipment, the project owner's property insurer pays the claim and then pursues the contractor for recovery. Subrogation is valuable to insurers: it allows them to recoup paid claims and, over time, to hold negligent third parties accountable rather than allowing them to benefit from their client's insurance.

Many construction contracts, IT service agreements, and infrastructure concession agreements contain a clause requiring the insured party to obtain a waiver of subrogation from its insurer, directing that the insurer will not pursue recovery against the contract counterparty. In a FIDIC Silver Book or Gold Book EPC contract, it is standard for both the employer and the contractor to require that the other party's insurers waive subrogation rights mutually. In an IT outsourcing agreement, the client may require that the vendor's professional indemnity insurer waive subrogation against the client even if the client's own acts contributed to the loss.

The challenge in India is that waiver of subrogation is not a standard feature of IRDAI-filed policy wordings. Public liability policies and fire policies under the Tariff Advisory Committee legacy structure, and even post-detariffication policies, are typically silent on waivers of subrogation or contain anti-subrogation-waiver language designed to protect the insurer's recovery rights. To obtain a waiver, the insured must request a specific endorsement and the insurer must agree to add it. Insurers generally agree, but the endorsement may attract an additional premium (commonly 1% to 3% of the relevant policy premium) and the underwriter must approve the specific counterparty identified in the waiver.

The operational risk for risk managers is signing a contract that requires a waiver of subrogation before confirming that the insurer will grant it. If the insurer declines, the insured is in breach of contract on day one. The correct sequence is: receive the contract draft, identify the subrogation waiver requirement, approach the insurer for written confirmation that the waiver endorsement is available and at what cost, and complete this step before the contract is finalised. For IT services companies in India that routinely sign master service agreements requiring these waivers across dozens of clients, maintaining a pre-approved form endorsement with the lead insurer saves significant time at each contract cycle.

An additional insured endorsement adds a third party (the contract counterparty) as a named insured on the policy, giving that party direct rights against the insurer. In the US and UK markets, this is standard practice in construction, real estate, and service contracts. An owner requires the general contractor to name the owner as an additional insured on the contractor's general liability policy; subcontractors name both the general contractor and the owner. Each named party has direct standing to make a claim without routing through the contractor.

In the Indian market, additional insured endorsements are legally possible but practically constrained. IRDAI's product filing requirements mean that most commercial liability policies are filed with defined insured language. Adding a new named insured changes the risk profile and, in a strict reading, may require the endorsement to be separately filed with IRDAI. In practice, most commercial insurers operating in India have developed working procedures to add additional insureds by endorsement under existing filed products, but this requires the specific underwriter's agreement and may not be available across all policy types.

Public sector insurers: New India Assurance, United India, Oriental, and National Insurance are often less flexible on additional insured endorsements than private sector players. Their policy wordings tend to be more standardised, and underwriting officers may not have delegated authority to add parties not contemplated in the original filed wording without a reference to the regional or head office underwriting team. Private insurers such as ICICI Lombard, Bajaj Allianz, and HDFC Ergo generally have more developed endorsement libraries and can process additional insured requests faster.

For IT services companies responding to global client requirements, the additional insured question frequently arises in the context of professional indemnity policies. A US-headquartered client requiring its vendor to name it as an additional insured on the vendor's professional indemnity policy creates a documentation and underwriting problem: Indian professional indemnity policies are typically issued on a claims-made basis and the additional insured concept is less developed than in US E&O policy structures. The practical resolution in many cases is to provide a certificate of insurance confirming coverage rather than a true additional insured endorsement, and to negotiate contract language that accepts this substitute. Risk managers should not assume the contract requirement and the Indian insurance market reality will align without active broker intervention.

Commercial contracts drafted by US or UK counsel frequently specify minimum insurance requirements that reflect their home market norms. A US-drafted vendor agreement may require the Indian vendor to maintain: commercial general liability with limits of USD 5 million per occurrence and USD 10 million aggregate; professional liability (errors and omissions) of USD 5 million; workers' compensation as required by applicable law; and umbrella/excess liability of USD 10 million. Each of these requirements creates a translation problem in the Indian market.

Commercial general liability as a US product does not exist in India under that name. The nearest equivalent for a service vendor is public liability combined with a product liability endorsement, potentially supplemented by a contractual liability endorsement. The limits cited (USD 5 million is approximately INR 42 crore at current rates, are achievable but represent substantially higher cover than most mid-market Indian vendors carry as standard. Obtaining a quote for these limits requires accessing the facultative reinsurance market, which adds cost and lead time.

Professional liability or errors and omissions coverage at USD 5 million is available in India through professional indemnity policies, but the Indian market for mid-sized IT and consulting companies typically operates at limits between INR 5 crore and INR 25 crore. Scaling to USD 5 million requires specialist placement, and the insured should expect a premium increase of 3x to 5x relative to a standard INR 5 crore limit, depending on the nature of services, claims history, and the specific insurer.

Workers' compensation requirements under US contracts often assume a statutory scheme similar to US workers' compensation. India has the Employees' Compensation Act, 1923 (amended to this name from the Workmen's Compensation Act) and group personal accident policies typically serve the commercial insurance function. Neither is a direct equivalent, and contract language requiring 'statutory workers' compensation' may need negotiation to clarify that Indian equivalent coverage is acceptable.

Umbrella or excess liability policies are available in India but are less standardised than in the US market. Access to meaningful excess liability capacity (above INR 100 crore) often requires international placements or facultative reinsurance arrangements. For Indian companies signing contracts with US minimum requirements, the practical approach is to engage the broker to conduct a gap analysis against current coverage, obtain indicative quotes for the required limits, and present the commercial cost to the business before the contract is signed. In many cases, negotiating the requirements down to Indian-equivalent terms is faster and cheaper than arranging the full US-specification insurance programme.

Large Indian infrastructure and EPC projects frequently use FIDIC contract forms: the Red Book (construction), Yellow Book (plant and design-build), or Silver/Gold Books (EPC/turnkey). FIDIC contracts specify insurance obligations in Clause 18 (older editions) and Clause 19 (2017 FIDIC suite). The required insurances include: works all risks (covering the permanent and temporary works), construction equipment and plant, third party liability, and employer's liability/workers' accident coverage.

FIDIC Clause 18 typically requires that the works all risks policy cover both the employer and the contractor as co-insureds, and that the third party liability policy include a cross-liability clause. A cross-liability clause treats each insured party as if they held a separate policy, meaning that the employer and contractor can each make claims against the policy even where the loss involves the other. Without this clause, if the contractor's negligence damages the employer's adjacent property, the employer (as a co-insured on the same policy) has no recourse against the policy that covers the contractor.

Indian government contracts (those awarded by NHAI, CPWD, MoRTH, or state PWD bodies) frequently depart from FIDIC norms. Government tender documents specify insurance requirements in a schedule that may be several years old and reference limits in INR amounts that have not kept pace with project costs or inflation. A government road construction contract let in 2019 may specify a third party liability limit of INR 25 lakh per occurrence that is wholly inadequate for a highway project with public exposure, and the government client may have no mechanism to revise it without re-tendering. Contractors working on government projects must recognise that compliance with the tender's insurance schedule may not deliver adequate commercial protection, and they should carry supplemental coverage at their own cost.

For manufacturing sector EPC projects, FIDIC Silver Book structures are common for large plant construction. The employer-as-insured and contractor-as-co-insured model creates a claims management challenge: who reports losses, who manages the surveyor relationship, who controls reserve decisions? These questions must be answered in the project's insurance management protocol at the outset, not after a loss has occurred. Brokers managing large Indian EPC placements typically draft a project insurance protocol document as part of the placement, clarifying reporting lines, approval authorities, and communication with the co-insurers.

Indian manufacturing companies selling to retail chains, automotive OEMs, or export buyers routinely sign vendor agreements requiring product liability insurance. A tier-1 automotive supplier selling to Maruti Suzuki or Hyundai will receive a vendor code agreement specifying a minimum product liability limit, commonly INR 50 crore to INR 100 crore for components with safety implications, and requiring that the OEM be listed as an additional insured or loss payee on the supplier's policy.

Product liability insurance in India is available as an extension to public liability policies or as a standalone policy. Coverage under Indian product liability policies is typically on an occurrence basis for bodily injury and property damage caused by defective products. What Indian product liability policies generally do not cover, and what frequently appears in vendor agreements, is pure economic loss or recall costs. If a defective component causes the OEM to recall vehicles, the recall costs (collection, inspection, repair, and replacement of potentially millions of units) are not recoverable under a standard Indian product liability policy. The OEM's contract requirement for product recall insurance or recall expense coverage is a separate product that relatively few Indian suppliers maintain.

For IT services companies, the contractual liability gap is different in character but equally significant. An IT service agreement may include a clause under which the vendor accepts liability for data breaches caused by the vendor's systems, capped at 12 months of contract value or another defined amount. If the vendor's cyber insurance policy contains a contractual liability exclusion (common in older policy forms), the policy will not respond to a claim arising from this contractually assumed liability, even if the breach was caused by the vendor's own negligence. The distinction is subtle: the insurer will pay for tort-based liability arising from the breach (what the vendor would owe at common law) but not for any additional amount assumed by contract.

The solution in both manufacturing and IT services contexts is a contractual liability endorsement specifically extending coverage to the liability assumed under the identified contract. This endorsement must be requested, filed where required, and confirmed in writing before the contract commences. Risk managers should maintain a log of all contracts for which specific insurance endorsements have been obtained, with renewal reminder dates, so that coverage remains in place for the duration of the contractual obligation.

The most effective way to prevent insurance gaps from contractual obligations is to institutionalise a review process rather than rely on ad hoc expert judgment. For mid-market Indian companies (those with revenues between INR 100 crore and INR 2,000 crore), a practical workflow involves three steps.

First, identify trigger conditions: which contracts require an insurance review? At minimum, triggers should include: contracts above a defined value threshold (commonly INR 1 crore); contracts in high-liability sectors (construction, IT, manufacturing, logistics); contracts with foreign counterparties; and contracts containing any of the following terms: 'indemnify,' 'hold harmless,' 'waiver of subrogation,' 'additional insured,' 'minimum insurance,' or 'certificate of insurance.' A simple keyword search in the contract management system can flag documents requiring review.

Second, conduct the review using a structured checklist. The checklist should cover: (a) indemnity form (broad/intermediate/limited); (b) subrogation waiver requirement and endorsement status; (c) additional insured requirement and feasibility; (d) minimum insurance specifications and gap to current coverage; (e) cross-liability requirements for project contracts; (f) product liability or recall requirements for supply contracts; and (g) contractual liability assumed that may exceed policy coverage. Each item should produce either a 'compliant' finding or a 'gap' finding with a recommended action and owner.

Third, close the gaps before the contract is signed. Gap closure may involve negotiating revised contract language, obtaining endorsements from the insurer, arranging supplemental coverage, or accepting a retained risk with board-level sign-off. The risk manager should document the gap assessment and the resolution for every material contract. This documentation becomes valuable both for the annual insurance renewal briefing, where the broker needs to understand the insured's contractual exposure, and for any subsequent claim where coverage under a specific contract obligation is disputed.

For companies with a large volume of vendor or client contracts, a standard insurance exhibit, a pre-approved schedule of insurance requirements that the company can meet and that has been cleared with its insurer, reduces negotiation time significantly. When the counterparty presents its own insurance schedule, the company can counter with its standard exhibit and request acceptance. Most Indian insurers are willing to issue a form certificate of insurance or comfort letter confirming that a company's standard policy programme meets its standard exhibit requirements, which can then be used across multiple contracts without requiring individual insurer approvals.