Rs 978 Crore of the Rs 1,001 Crore Was Roads and Water Works: Himachal's Bill Is a Contractor's Problem

The Tribune reported on 18 August 2026 that Himachal Pradesh's monsoon losses for the season had reached Rs 1,001.71 crore. The department split is the part worth reading twice. The Public Works Department accounted for Rs 750.9 crore, Jal Shakti Vibhag for Rs 227.46 crore, and the Power Department for Rs 5.3 crore. Two departments carry roughly Rs 978 crore of the bill.

The same report counted 88 roads blocked across the state, including 32 in Mandi and 25 in Kullu, and 85 houses completely destroyed. Heavy rainfall was forecast through 21 August with orange and yellow alerts across several districts, so the season was still running when the tally was published.

Strip the departmental labels away and the loss is a physical inventory: hill roads, retaining walls, culverts and bridge approaches on the PWD side, and intake structures, diversion channels, rising mains and gravity water schemes on the Jal Shakti side. Almost none of it is a building. Almost all of it is linear or hydraulic infrastructure sitting in a drainage line, which is the asset class a monsoon takes out.

That matters because departmental assets are not built by departments. They are built, and for a defined period maintained, by contractors working to a contract that allocates monsoon risk between the two parties. A very large share of the Rs 978 crore is therefore not a state loss at all. It is a contractor loss wearing a state department's accounting code.

Whether a washed-out road is the state's problem or the contractor's turns on one question: what stage of the contract was the asset in when the water arrived?

1. Under construction, not yet handed over. The works are at the contractor's risk. If a slope fails and takes out 200 metres of formation and a retaining wall, the contractor rebuilds and claims on the project policy. The department's loss figure records the damage; its balance sheet does not necessarily absorb it.
2. Completed but inside the maintenance or defect liability period. The contractor stays liable for making good defects, often with specified maintenance obligations, while retention money and performance security are still held. Whether monsoon damage counts as a defect or as an insured peril event is the argument that follows a season like this one.
3. Handed over, out of maintenance. The asset is the state's, and restoration is funded budgetally rather than by insurance.

With typical defect liability periods running one to two years past completion, a large share of the works in any district falls into buckets one and two. In Mandi and Kullu, where the closure counts were highest at 32 and 25 roads, that share is higher still, because these are the districts carrying the most restoration work from prior monsoon seasons.

Indian project placements use two engineering wordings. Erection All Risks is the plant-led wording, written for erection and testing of machinery, and it carries a Jal Shakti pumping station, an intake gate assembly or a lift scheme's pump house. Contractors All Risks is the civil-led wording, and it carries road formation, retaining walls, culverts, bridge substructures and channel works. Larger packages are placed on a combined basis, and the boundary between the two sections is drawn in the schedule.

Both are project-period policies covering physical loss or damage to the contract works from any cause not excluded. Flood, inundation, storm, landslide and subsidence are covered perils in the standard Indian market wordings, subject to the schedule's separate deductibles for what insurers call AOG perils, set materially higher than the general deductible. On a hill road package the AOG deductible is often the largest single number on the schedule and the one nobody checks until a claim.

Neither wording pays for the consequences of the works being unavailable. Delay costs, extended overheads, idle plant beyond the sub-limit, liquidated damages and lost margin sit outside the material damage section. Advance loss of profits attaches to the principal, and a state road contract usually carries none because there is no revenue stream to insure. A washout on a hill package routinely produces a material damage claim in the tens of lakhs and a delay exposure several times larger, so a contractor who misses the contractual extension of time notice window can win the insurance claim and still absorb the bigger loss through liquidated damages.

The exclusion that decides hill infrastructure claims is faulty design, not flood.

Standard CAR and EAR wordings carry a design exclusion removing loss or damage arising from faulty design. Narrower market forms extend cover to resulting damage to correctly executed parts of the works while still excluding the cost of putting right the faulty item. The widest forms cover improved reinstatement of the defective item too. Which version sits in the schedule is worth more than the premium difference, and hill packages usually carry the narrow default.

The reason this bites in Himachal is causation. When a retaining wall fails during a cloudburst, the surveyor's report rarely says the wall was destroyed by water. It says the drainage provision was inadequate for the observed intensity, or the weep holes silted, or the toe was founded above the scour line. Each is a design finding, and each moves the claim from covered peril to excluded cause. The same applies to an intake washed out because the diversion structure was sized for a lower return-period flow than the event delivered.

Three defences are worth building into the file before the season, not after:

• Keep the design basis with the policy. Return-period assumptions, hydrological data source, catchment area and the approving authority's sign-off. A design executed to the department's approved parameters is a departmental design rather than the contractor's faulty design, and that changes the exclusion analysis.
• Buy the wider design cover explicitly. Ask in writing for the wording to extend to resultant damage and, where available, to the defective item on an improvement basis, and get it endorsed on the schedule.
• Separate maintenance failure from design failure. Silted weep holes and blocked catch drains are maintenance findings. If the maintenance obligation had already passed to the department, that failure is not the contractor's to fund even where the wall was the contractor's to build.

This is a proximate cause argument, and the file that documented the design basis at tender stage wins it far more often than the one assembled after the wall is already in the river.

The maintenance period section is the single most misunderstood part of an engineering policy, and after a season like 2026 it is the section that decides whether a contractor rebuilds at his own cost.

Two variants are standard in the Indian market, and they are not close substitutes.

Visits maintenance

Covers loss or damage caused by the contractor while carrying out maintenance obligations, plus damage from a cause arising before the maintenance period but discovered during it. It does not cover fresh damage to the completed works from a new event. A road handed over in May 2026 and washed out in August has no cover under a visits maintenance section.

Extended maintenance

Adds cover for damage during the maintenance period from a cause originating in the construction period, and in wider forms from any insured cause during the maintenance period itself. That is the version a hill contractor needs, and it is the version placements drop when the project premium is negotiated down at the end of a tender cycle.

Two mechanical points follow. The policy maintenance period must match the contractual defect liability period, because a twelve month policy period under a twenty four month liability leaves a full monsoon uninsured, and in Himachal every twelve month window contains one. And the maintenance period starts only on the taking-over certificate date. Partial handovers, sectional completions and packages taken into use without formal certification break the date chain, and insurers read the schedule dates rather than site reality.

On plains projects debris removal is a small line item. On hill infrastructure it can exceed the cost of the permanent works it uncovers.

When 88 roads are blocked across a state, including 32 in Mandi and 25 in Kullu, the blocking material is slope debris: soil, boulders, felled trees, failed retaining structure and sometimes an entire hillside. Clearing it means excavators walked in over broken access, muck disposal to designated sites at a lead because tipping into the nallah is not permitted, and night working under rain alerts.

Engineering policies cover debris removal as a separate item with its own sum insured, not as an automatic addition to the works value. Three failure modes recur:

1. The item is left blank or nominal. A token debris removal item on a multi-crore road package is exhausted by a single slope failure.
2. The sub-limit is a percentage of the claim rather than of the sum insured. That formulation collapses when the physical damage is modest and the clearance is large, which is the characteristic shape of a landslide blockage.
3. Only debris on the site is covered. Material that slid onto the works from outside the contract limits falls outside a narrowly drafted site definition, and on a hill alignment most debris crosses that boundary.

The fix is dull. Set the debris removal item from a quantity estimate for a credible worst-case slope failure on the alignment rather than a percentage rule of thumb, and get the site definition drafted to include material originating outside the site that comes to rest on the works. Both are cheap at placement and unbuyable after the event.

Public works contracts allocate monsoon risk in three places, and a contractor reading only the EAR wording sees a third of the picture.

• The insurance clause. Most state and central works contracts require the contractor to insure the works, plant, materials, third party liability and workmen for the contract period plus the defect liability period, with the employer as joint insured or named interest. That status makes cross liability drafting matter and gives the department standing in the claim.
• The excepted risks clause. Typically carves out war, nuclear risk and, in many forms, forces of nature beyond what an experienced contractor could reasonably have foreseen and provided against. That phrase does real work in hill contracts: a cloudburst well outside the design return period can qualify where a routine heavy monsoon does not, and where it qualifies the employer bears the restoration cost even inside the contract period.
• The extension of time clause. It decides whether the contractor absorbs the delay, and it runs on notice periods shorter than most claim cycles.

So after an event the contractor runs two files: an insurance claim against the project policy, and a contractual claim against the employer under the excepted risks and extension of time provisions. Where the insurer accepts the loss, the contractual claim reduces to the deductible, the uninsured heads and time. Where the insurer declines on design defect, the excepted risks argument becomes the primary recovery route, resting on the same design basis documentation.

Subrogation shapes both files. Where the employer is a joint insured, the insurer's ability to recover from the department is limited, which is one reason insurers test the design defect route harder on jointly insured public works than on private projects.

Himachal's Rs 1,001.71 crore tally was published on 18 August with rainfall forecast through 21 August, so post-event work overlaps with live exposure and the sequencing matters.

1. Notify every event, including those below the deductible. A minor slope movement cleared in July becomes evidence of a pre-existing cause when the same slope takes the wall out in August. Unnotified small events are the cheapest way to lose an expensive claim.
2. Photograph with survey reference. Chainage markers, a date-stamped level or total station reading at the failure, and the rain gauge record for the nearest observatory. Intensity data separates a design-exceedance event from a design-inadequacy finding.
3. Get the surveyor appointed before clearance starts, or document the emergency. Hill clearance often cannot wait, because the road is a lifeline. Where clearance precedes survey, record the pre-clearance state fully and obtain the department's written instruction to proceed.
4. Log quantities daily. Muck volume, machine hours, lead distance and disposal site. Debris removal claims settle on quantity records, and reconstructed quantities get discounted heavily.
5. File the contractual notices in parallel. Extension of time, excepted risks and any site condition notice, each inside its own window and referencing the same event log as the insurance intimation.

For the next placement cycle, four schedule entries matter most on hill packages: the AOG deductible, the design defect wording variant, the maintenance period variant and its end date, and the debris removal item. The rest of the engineering insurance schedule is standard. Those four decide how the Rs 750.9 crore of PWD damage and the Rs 227.46 crore of Jal Shakti damage gets allocated between the state, the contractors and the insurers.

The same season's non-damage exposure, the closures and utility failures that hit manufacturers rather than builders, is covered in our note on denial of access cover in Himachal, and the wording structure in the construction all risks policy guide.