Industry Risk Profiles

Bulk Drug Park and API Manufacturing Risk Profile India 2026: Solvent Fire Load, Effluent Liability and Cluster Accumulation

As India's three bulk drug parks fill with API and KSM plants, brokers face a solvent-intensive risk with shared effluent and solvent-recovery infrastructure, reactor runaway exposure, pollution liability and a cluster accumulation problem that reshapes fire, liability and environmental cover.

Sarvada Editorial TeamInsurance Intelligence
9 min read

Listen to this article

Audio version • 9 min read

industry-risk-profilesapi-manufacturingbulk-drug-parksolvent-fire-loadpollution-liabilitycluster-accumulationpharmaceuticalsfire-insurance

Last reviewed: July 2026

Why bulk drug parks create a risk class distinct from general pharma

India's Bulk Drug Park scheme, backed by a central outlay of about INR 3,000 crore, has moved from paper to steel. Three parks, at Jambusar in Gujarat, Una in Himachal Pradesh and a site in Andhra Pradesh, had allotted land to roughly 194 manufacturers by September 2025, and the separate INR 6,940 crore Production Linked Incentive scheme for bulk drugs ran its sixth application round in November 2025. The policy intent is to cut import dependence on Chinese Active Pharmaceutical Ingredients (APIs) and Key Starting Materials (KSMs). For an underwriter, the intent matters less than what actually gets built: dense clusters of fermentation, chemical-synthesis and solvent-recovery units sharing fence lines, roads, effluent pipes and utilities.

This is not general pharma. A formulation plant that blends, granulates and blisters finished tablets carries a modest fire load and a benign effluent stream. An API or KSM synthesis unit runs multi-step organic chemistry at scale, storing and pumping tonnes of methanol, toluene, acetone, dichloromethane and similar solvents. The hazard signature sits far closer to a specialty chemicals plant than to a tablet line, yet risk managers and even some brokers still slot these accounts under a generic pharmaceutical rate.

The park model adds a second layer. Because tenants sit metres apart and lean on shared Common Effluent Treatment Plant (CETP) and common solvent-recovery assets, a single event can touch several insured balance sheets at once. Pricing each plant as an isolated island misreads the true exposure.

Class A flammable-solvent handling and reactor runaway

The defining physical hazard of an API plant is bulk flammable-solvent handling. Under the Petroleum Act, 1934 and the Petroleum Rules, 2002, solvents such as acetone, diethyl ether and many process alcohols fall in Class A (flash point below 23 degrees Celsius), the most volatile category, licensed and inspected by the Petroleum and Explosives Safety Organisation (PESO). A mid-size synthesis block can hold hundreds of kilolitres across solvent tank farms, day tanks and charging vessels. Vapour from a single failed flange or an over-pressured reactor vent can find an ignition source and produce a flash fire or vapour cloud deflagration.

Reactor runaway is the second signature peril. Exothermic reactions (nitration, hydrogenation, Grignard and diazotisation steps are common in KSM routes) release heat that, if cooling fails or a reagent is charged too fast, accelerates beyond control. The result is over-pressure, vessel rupture, solvent release and fire. Hydrogenation units carry their own hydrogen-handling exposure. These are the loss scenarios that drive Estimated Maximum Loss (EML) on the property slip, and they interact: a runaway breaches a reactor, the released solvent ignites, and the fire spreads through interconnected piping.

For placement, the Standard Fire and Special Perils wording and its large-risk market variants respond to fire and explosion, but the underwriter will scrutinise segregation distances, the dyking of tank farms, nitrogen blanketing, emergency relief systems and whether the plant is a Major Accident Hazard installation under the Factories Act, 1948 and the MSIHC Rules, 1989. Add-ons matter here: a Fire Loss of Profits section, machinery breakdown for reactors and compressors, and boiler-explosion cover for pressure vessels. Deductibles on solvent-intensive occupancies are set high deliberately, and warranties on hot-work permits and vapour-detection systems are routine conditions of cover, not optional extras.

Shared solvent recovery and effluent plant as a single point of failure

The economics of a bulk drug park depend on shared infrastructure, and that sharing is exactly what concentrates the risk. API synthesis consumes large solvent volumes, so most parks are built around common or clustered solvent recovery units that distil spent solvent back to reusable grade. A distillation column running flammable solvent at temperature is itself a high-hazard asset, and when several tenants pipe spent solvent into a shared recovery block, a fire or explosion there can halt production across many plants at once.

The CETP carries a parallel concentration. Multiple units discharge process effluent into common collection, primary treatment, and often a shared zero-liquid-discharge (ZLD) train mandated by state pollution boards. If the CETP trips, is damaged, or breaches its consent limits, every connected tenant may be forced to stop production, because discharging untreated effluent invites closure orders from the Central Pollution Control Board (CPCB) and its state boards under the Water (Prevention and Control of Pollution) Act, 1974.

This creates a business-interruption exposure that a standalone property policy does not naturally capture. A plant can be physically undamaged yet fully idled because a shared asset it does not own has failed. Two mechanisms address this:

  • Customers and suppliers extensions (also called denial of access and public utilities extensions) on the Fire Loss of Profits section, which respond when a named external asset stops the insured operating.
  • Contingent business interruption wording that names the specific shared solvent-recovery or effluent asset as an insured dependency.

Brokers should map, plant by plant, which shared assets are single points of failure, then confirm the FLOP wording actually names them. A generic indemnity period bought without this mapping will leave a real and recurring gap, because in a park the most likely cause of a long shutdown is often not a fire in the insured's own shed.

Effluent, pollution and environmental liability

API manufacturing generates hazardous liquid effluent, spent solvent, process residues and off-gases, which makes environmental liability a first-order exposure rather than an afterthought. The Environment (Protection) Act, 1986, the Water Act, 1974 and the Air (Prevention and Control of Pollution) Act, 1981 frame the compliance regime, and enforcement has hardened: the National Green Tribunal has repeatedly ordered closures and levied restitution costs on chemical and pharma clusters for effluent breaches.

Two distinct insurance instruments come into play. First, the Public Liability Insurance Act, 1991 makes cover compulsory for any unit handling notified hazardous substances above threshold quantities. The Public Liability (Act) Policy provides no-fault relief to third parties for death, injury or property damage from an accident involving those substances, funding relief on a defined scale and contributing to the Environment Relief Fund. It is a statutory minimum, not a genuine indemnity for the operator.

Second, and more important commercially, is Environmental Impairment Liability (EIL), sometimes placed as pollution legal liability. A standard Commercial General Liability or public liability wording typically excludes gradual pollution and often limits even sudden and accidental pollution. Slow effluent seepage into groundwater, soil contamination discovered years later, or a CETP overflow that damages neighbouring land can fall outside CGL entirely. A dedicated EIL policy responds to on-site and off-site clean-up costs, third-party bodily injury and property damage from pollution conditions, and often defence costs for regulatory proceedings.

Brokers should also test the product liability position: APIs shipped to formulators and export markets carry recall and downstream contamination exposure that a property-led programme ignores.

Cluster accumulation: the underwriter's park-level problem

The feature that makes a bulk drug park attractive to policymakers (density) is the feature that makes it hard to insure at portfolio level. When 30 or 60 high-hazard units sit inside one boundary, sharing roads, pipe racks, solvent storage and effluent lines, an insurer or reinsurer that writes several of them holds a correlated, not a diversified, book. A vapour cloud explosion, a solvent-recovery fire that jumps units, or a park-wide toxic release can trigger multiple property and liability claims from a single event.

This is an accumulation problem of the same family that catastrophe teams manage for flood zones or industrial estates. A fire in one shed that spreads across shared infrastructure produces a loss that is not independent across the insured plants. Reinsurance treaties respond to it through event limits and per-location aggregation, and treaty reinsurers increasingly ask cedants to identify same-park exposures so the accumulation can be modelled rather than discovered after a loss.

For the broker, three practical consequences follow. Capacity for a given park can tighten once one or two insurers reach their internal aggregation cap for that location, so early placement matters. Pricing may carry a cluster loading that a standalone plant of identical construction elsewhere would not attract. And co-insurance or layered placements become more common, because no single insurer wants full exposure to a park-wide event.

Risk managers can improve terms by giving underwriters the data that lets them separate their plant from its neighbours: firewall ratings, segregation distances to adjacent tenants, independent solvent storage where it exists, and the plant's own emergency response capability. The park's master risk assessment and its off-site emergency plan under the MSIHC Rules, 1989 are underwriting documents in this context, and presenting them well can move a plant from a blanket cluster loading toward terms that reflect its actual, better-than-average protection.

Structuring the programme: fire, BI, liability and EIL together

A defensible insurance programme for a bulk-drug-park API unit is built as a coordinated set of covers, not a single fire policy with add-ons bolted on late. The property spine is a large-risk fire and special perils placement with reactors, columns and utilities correctly valued on reinstatement value, plus machinery breakdown and boiler-explosion sections for pressure vessels and rotating equipment. Under-insurance here bites hard, because the average clause applies and API plant is capital-intensive.

The business-interruption layer needs an indemnity period long enough to reflect the real recovery time of a synthesis line, which can run 18 to 24 months once you account for re-qualification, regulatory re-inspection and, for export product, re-audit by overseas regulators. The FLOP section should name shared solvent-recovery and effluent assets as insured dependencies, and should carry customers/suppliers and denial-of-access extensions sized to the park's actual interdependencies.

On liability, the stack is layered:

  1. The compulsory Public Liability (Act) Policy for the statutory no-fault relief.
  2. A broad-form Commercial General Liability or public liability policy for third-party bodily injury and property damage.
  3. A standalone Environmental Impairment Liability policy for gradual and sudden pollution, clean-up and remediation.
  4. Product liability, structured for domestic and export exposure, on API supplied to downstream formulators.

The most common structural failure is buying property well and liability thinly. At an API site the pollution and product-recall losses can exceed a shed fire, and they are the covers most often left generic or under-limited. Every layer should be read against the others for gaps and overlaps: pollution wording in the CGL versus the EIL, the BI trigger versus the property peril list, the deductible ladder across sections. That reading is where placements are won or lost, and it is exactly the wording-level work that separates a programme that pays from one that argues.

How Sarvada helps brokers place API-park risk on the right wordings

The through-line of an API and KSM risk profile is that outcomes turn on wording detail: whether the FLOP section names the shared solvent-recovery plant, whether the CGL pollution exclusion is bridged by a real EIL policy, whether the indemnity period matches an 18-to-24-month synthesis recovery, and whether cluster accumulation is being priced or merely assumed. Those answers live inside insurer policy wordings that differ, clause by clause, across the market.

Sarvada makes those wordings searchable. Brokers and risk managers can compare how different insurers handle solvent fire load, contingent business interruption on shared park infrastructure, gradual pollution, and product-recall triggers, then match a specific API or KSM plant to the wordings that actually respond to its exposures rather than to a generic pharma template. That comparison is difficult to do by hand, because the relevant clauses sit deep inside each insurer's fire, liability and environmental wordings and rarely line up section for section.

For an occupancy this exposed to pollution and cluster accumulation, the wording gap is where claims are lost, so the placement work is worth doing before a loss rather than during one. If you place or advise on bulk-drug-park risk and want to compare insurer wordings on these clauses side by side, Request Access to Sarvada.

Frequently Asked Questions

Why can't an API plant use the same fire rate as a formulation unit?
Because the hazard is fundamentally different. A formulation unit blends and packs finished dosage forms with a modest fire load. An API or KSM synthesis plant stores and pumps tonnes of Class A flammable solvents and runs exothermic reactions in reactors, so its fire and explosion exposure sits closer to a specialty chemicals plant. Rating it on a formulation benchmark understates the Estimated Maximum Loss and typically mis-prices the account.
Does a standard CGL policy cover pollution and effluent liability at an API site?
Usually not adequately. A standard Commercial General Liability or public liability wording generally excludes gradual pollution and often restricts even sudden and accidental pollution. Slow effluent seepage, groundwater or soil contamination, and remediation orders from pollution boards or the National Green Tribunal can fall outside it. These sites need a dedicated Environmental Impairment Liability policy that responds to on-site and off-site clean-up, third-party pollution damage and regulatory defence costs.
How does a shared effluent or solvent-recovery plant affect business interruption cover?
It creates exposure a standalone property policy misses. A tenant plant can be physically undamaged yet fully idled because a shared CETP or solvent-recovery unit it does not own has failed or been shut by regulators. The Fire Loss of Profits section must therefore name those shared assets as insured dependencies and carry contingent business interruption plus denial-of-access and public-utilities extensions, sized to the park's real interdependencies.
What is cluster accumulation and why does it change my premium?
Cluster accumulation is the correlated exposure an insurer holds when it writes several high-hazard plants inside one park that share roads, pipe racks and utilities. A single event, such as a solvent-recovery fire that spreads, can trigger multiple claims at once, so the losses are not independent. Insurers manage this with event limits and per-location aggregation caps, which can tighten capacity and add a cluster loading to your premium.

Related Glossary Terms

Related Insurance Types

Related Industries

Related Articles

Sarvada Intelligence

Ready to see Sarvada in action?

Explore the platform workflow or start a product conversation with our underwriting automation team.

Explore the platform