576 Workers and a Flooded Tunnel: EAR, DSU and Employer's Liability for Indian Contractors in the Himalaya

The Nepal Electricity Authority said 13 hydropower projects were damaged, including Rasuwagadhi, Chilime, Trishuli 3A, the Trishuli 3B 220 kV substation, Trishuli Hydropower Station and Devighat. The flood crippled a combined 281 MW of installed generation capacity, including a solar plant, and damaged four under-construction projects totalling 700 MW.

Around 900 people working on 12 hydropower projects were reported missing, with about 500 believed trapped in tunnels. At Upper Trishuli 1 alone, at least 576 workers were reported missing and roughly 300 were believed trapped inside the project tunnel.

Read the asset list again and note what is missing from it. Very little of this is buildings. It is headworks, diversion structures, penstocks, powerhouses, a high-voltage substation and tunnels with crews inside them. For an Indian EPC contractor, equipment lessor or manpower supplier working Himalayan hydro on either side of the border, that shape of loss tests three wordings at once, and each can fail independently of the other two.

Indian project placements run on two engineering wordings. Erection All Risks carries turbines, generators, gates and switchyard equipment. Contractors All Risks carries the civil works: coffer dams, intakes, headrace tunnels and the powerhouse cavern. Both cover physical loss or damage to the works from any cause not excluded, and both treat flood, inundation, storm, landslide, subsidence and avalanche as insured perils subject to a separate act of God deductible, usually the largest number on the schedule.

So on a plain reading a Himalayan outburst flood is covered. The difficulty is that a glacier or moraine collapse does not deliver clean water. It delivers a debris flow of ice, rock, moraine and mud moving fast enough to destroy structures by impact and abrasion before any inundation happens. That opens three arguments for an insurer, each a wording question rather than a facts question.

1. Is it a flood at all? Where the schedule defines flood as inundation from a watercourse overflowing its banks, a moraine dam breach fits reasonably well. Where flood is undefined, the surveyor characterisation in the preliminary report decides the peril, and that report is written before anyone has read the policy carefully.
2. Does it route into earth movement instead? Many schedules carry a higher deductible for landslide and subsidence, and some hill placements restrict cover for slope movement originating outside the site boundary. A debris flow that begins as a moraine failure above the works and ends as water at the intake can be pushed into the harsher treatment.
3. Does the design basis swallow it? If the diversion works were sized to a stated design flood and the event exceeded it, the surveyor has a route to a design inadequacy finding, and the faulty design exclusion then removes at least the cost of the defective item.

The fix is drafted at placement. Ask for a defined peril extension naming glacial lake outburst flood, moraine dam failure, debris flow and avalanche under one stated deductible, and keep the design basis on file: design flood return period, hydrology source, catchment definition and the approving authority's sign-off. This is a proximate cause fight, and the tender-stage file wins it far more often than the one assembled after the intake is in the river. The underwriting view of the peril is set out in our note on GLOF exposure for Himalayan hydropower and project cargo.

The flood hit both sides of the commissioning line on the same river within the same hour, which is why it reads as one disaster and settles as two unrelated books of claims.

The 281 MW of crippled installed capacity, including a solar plant, sits under operating covers: a fire or industrial all risks material damage section, a machinery breakdown section, and the business interruption or loss of profits sections measured off historic generation and tariff. The 700 MW across four under-construction projects sits under EAR or CAR plus delay in start-up cover, sold here as DSU or advance loss of profits. With no historic generation, that is a delay claim rather than a lost-output claim.

Delay in start-up is built for exactly this situation, works washed away before they ever generated a unit. Four mechanics decide whether it responds.

1. Whose policy it is. DSU insures the party that loses the revenue, the owner or, in a project-financed structure, the lenders through their assigned interest. An EPC contractor is not automatically covered for its own delay costs, which sit in extended overheads, idle plant and liquidated damages.
2. The trigger is the material damage claim. Standard wordings respond to delay caused by damage indemnifiable under the material damage section. If the flood is characterised into an exclusion or defeated by the faulty design carve-out, the DSU section pays nothing however long the delay runs.
3. The indemnity period must survive a Himalayan rebuild. A washed-out intake at altitude does not get rebuilt on a plains schedule. Access, working season, hydrology windows and plant lead times push a realistic rebuild well past a twelve month convention, while the time excess deducts only thirty to sixty days.
4. The sum insured comes off the financial model. Mongabay reported in September 2026 that the disaster puts Nepal's hydropower-first strategy and its power exports to the test. If the offtake route changes, so does the model behind the DSU sum insured, and an insurer measures the loss on the arrangement that existed at the date of damage.

At Upper Trishuli 1, at least 576 workers were reported missing and roughly 300 were believed trapped inside the project tunnel. That headcount is never a single employer's payroll. It is a stack of direct employees, subcontractor labour, tunnelling specialists, erection crews and manpower supplier gangs, each under a different policy.

Three covers get conflated and they are not substitutes.

• Statutory compensation. An employees' compensation policy indemnifies the employer's statutory liability on a formula of wages and age.
• Employer's liability. The extension covering damages beyond the statutory scale where negligence is proved. On a tunnel casualty with an alleged failure to evacuate, this is the exposure that grows.
• Group personal accident. A benefit policy paying a stated sum on death or disablement regardless of fault. It is the cheapest of the three and the fastest money to reach a family.

The cross-border question sits on top of all three. An Indian compensation or employer's liability policy is written with a territorial scope, and a schedule that says India does not cover a fitter deputed to a Nepali site. This is the most common gap in a manpower supplier's book, because the placement renews on last year's schedule while the deployment moved across the border. The same applies to group medical and evacuation cover.

Nepali labour law requires employers to carry accident and medical cover for workers engaged in Nepal, so an Indian contractor there typically runs two stacks over the same headcount: a locally admitted policy for the local workforce, and an Indian policy with an extended territory for deputed staff. Reconcile them by name and by site, because the overlap is where double recovery arguments and denials live.

Fix the joint insured schedule as well, naming the principal, the EPC contractor, every subcontractor, the manpower suppliers and the lessors, with a cross liability clause. Without it the principal's insurer pursues the tunnelling subcontractor, and that subcontractor's third party liability cover becomes the real answer to a claim everyone assumed the project policy had absorbed.

Compensation and personal accident policies pay on death or disablement. A worker reported missing is neither, in policy terms, until a death is established, and that is the obstacle standing between about 900 families and any payment. Indian law presumes death after seven years of unexplained absence, which is a useless timeline for a dependant who lost the household wage in August. Disaster administrations normally shorten it by issuing death certificates against an official list of missing persons, and in a cross-border casualty that certificate issues under the law of the country where the event occurred. The Indian side of the file then needs it recognised for the compensation and personal accident claims, provident fund and gratuity settlement, and the family's succession process.

Some group personal accident wordings carry a disappearance clause paying the death benefit after a stated period where the insured has not been found. Read it before relying on it, because many restrict it to disappearance following the wrecking or sinking of a conveyance, which does not describe a flooded tunnel.

The evidence that decides these claims is generated at the portal, not in the claims department.

• The tag board or access control record for the shift. Primary proof of who was underground when the water arrived. On a project running three shifts and several subcontractors, a tag board kept by one party for its own crews proves nothing about the others.
• Daily manpower returns and wage registers for every layer of the labour chain, with names, identity document numbers and dates of birth. Statutory compensation runs on wages and an age factor, so a missing date of birth stalls the calculation even after death is established. Manpower suppliers are the weakest link here, and the principal employer inherits the problem.
• Next of kin and nominee records, documented at induction rather than reconstructed afterwards.

Equipment lessors carry a distinct and often unhedged exposure. A drill jumbo, shotcrete robot, muck loader or gantry inside a flooded headrace tunnel is neither recovered nor written off for months, and the hire contract keeps running meanwhile. Four points decide how that resolves.

1. Is underground working declared? Contractors plant and machinery cover prices and restricts plant working in tunnels and shafts differently from surface plant. A schedule that lists the fleet without declaring the underground deployment invites a non-disclosure argument on its largest machines.
2. Whose loss is it under the hire contract? Standard hire terms make the hirer responsible for loss on a new replacement basis, plus continuing hire charges until settlement or return. The lessor's protection is that the hirer's policy names the lessor's interest and covers continuing hire charges as a separate head, because an insurer that pays the machine value and nothing else leaves the lessor absorbing months of unpaid hire.
3. Recoverable in principle, uneconomic in practice. A machine that could be extracted after dewatering is not a total loss on a strict reading, and the argument over constructive total loss, salvage ownership and dewatering cost is where these claims stall, so fix that position in the hire agreement.
4. Replacement plant has to cross a border. Moving a transformer or tunnelling machine from India to a Nepali site is a project cargo exposure with its own transit, customs and last-mile risk on damaged hill roads, and a delayed replacement extends the DSU claim it was meant to shorten.

The discipline applied after a washout season on the Indian side of the border, set out in our note on Himachal's monsoon losses and hill contractor exposure, applies here with the plant, the insurer and the salvage in three jurisdictions.

The Nepal Insurance Authority had received 583 flood-related claims worth NPR 25.87 billion as of 31 August 2026. A market absorbing that volume at once will be slow on survey appointment and on interim payments, and unforgiving on documentation gaps. The work that improves an outcome is done before the next bid.

1. Name the peril in the schedule. Glacial lake outburst flood, moraine dam failure, debris flow and avalanche, insured under one act of God deductible rather than left to the surveyor's characterisation.
2. File the design basis with the placement. Design flood return period, hydrology source, catchment area and the approving authority's sign-off. This cannot be created after the loss.
3. Reconcile territory on every people policy. Compensation, employer's liability, personal accident and medical schedules should each name the country of the site, and check the manpower suppliers' policies too.
4. Set the DSU indemnity period against a real rebuild programme, including access seasons and plant lead times.
5. Fix the joint insured schedule and cross liability across principal, contractor, subcontractors, manpower suppliers and lessors, and write the evidence obligations (tag board discipline, manpower returns, wage registers, nominee records) into each subcontract.
6. Decide the admitted placement structure early, including which risks must be insured locally, how the reinsurance sits behind the local policy, and who controls the claim.

An AP report of 31 August 2026, Nepal floods expose risks to hydropower in a warming Himalayas, treated this as a warming-driven exposure rather than an isolated event. Underwriters read that report too, so the extensions described here get harder and dearer at each renewal after this loss. The engineering insurance schedule negotiated on the next award is likely to be the last one placed on pre-event terms.