A monsoon playbook for Indian contractors — site preparation, rain-day documentation, hindrance registers, and turning weather logs into EOT claim evidence.

Every Indian contractor plans for the monsoon and is somehow still surprised by it. Between June and September — earlier on the west coast, later in the northeast — productive days drop, waterlogged fronts multiply, and the schedule quietly absorbs a delay that someone, three years later, will have to explain to an arbitrator. The contractors who come out of the season with margins and claims intact are not the ones with the best luck; they are the ones with the best records. This is a practical monsoon playbook: preparing the site, documenting rain days properly, running a hindrance register that stands up to scrutiny, and converting weather logs into extension-of-time evidence.

What the Monsoon Actually Costs

Put numbers on it before the season starts, because the costs hide in different ledgers:

Lost working days. A site in central or western India can lose 25 to 45 working days across a monsoon between rain itself, waterlogged fronts, and unworkable moisture conditions for earthwork and concreting.
Prolongation costs. Site establishment, staff salaries, hired plant on monthly rentals, and idle machinery continue at full rate through every lost day. A mid-size site with ₹18–25 lakh of monthly fixed cost bleeds ₹60,000–80,000 for each unproductive day.
Rework. Slushed haul roads, collapsed trench edges, cement set in leaking stores, rain-damaged brickwork — work paid for twice.
Liquidated damages exposure. If the delay lands on you because you cannot prove it landed on the weather, LD clauses at half to one percent of contract value per week of delay concentrate the whole season's cost into one deduction.

The first three are partly controllable with preparation. The fourth is controllable entirely with documentation.

Preparing the Site Before the Rain

The pre-monsoon checklist is well known and still routinely skipped. The essentials, four to six weeks before onset:

Drainage first. Cut and maintain site drains, desilt existing ones, grade haul roads with camber, and stock metal or milling waste for road repairs. Most monsoon downtime is not rain — it is the three days of slush after the rain.
Dewatering readiness. Pumps serviced and staged at excavations, standby fuel, and a named operator per shift. An open foundation that floods for want of a working pump can cost a week.
Material protection. Cement on dunnage, double-covered; steel on sleepers with drainage beneath to limit scaling; electrical items and finishing materials moved to sealed stores. Verify stock levels — monsoon supply chains slow down too.
Front sequencing. Re-plan the three monsoon months around covered and monsoon-tolerant work: interiors, finishing, fabrication, precasting, plant maintenance. Pull indoor work into the wet window and push earthwork out of it.
Safety systems. Earth-leakage protection on all temporary power, lightning protection on tower cranes and batching plants, slope protection on deep excavations, and a written stop-work threshold for wind and lightning.

Rain-Day Documentation: The Records That Matter

Here is the discipline that separates a paid EOT claim from a rejected one: the monsoon must be recorded the way a lawyer will one day want to read it, not the way a site diary usually keeps it.

"Heavy rain today, work affected" is worthless as evidence. Three years later it proves nothing — not which activity stopped, not for how long, not whether that activity was critical. The record that works looks like this:

Weather log with times. Rainfall start and stop times, and where possible a site rain gauge reading in millimetres — a ₹1,500 gauge read at 8 AM daily produces data an arbitrator can compare against IMD records. Note ground conditions separately: "no rain, but cutting area waterlogged from overnight rain, unworkable till 14:00."
Activity-level impact. Which specific activities stopped and which continued: "PQC pour at km 42.6 suspended 11:20; reinforcement fabrication in covered yard continued." Blanket claims that the whole site stopped for 40 days get discounted; precise partial claims get paid.
Geo-tagged photographs. The flooded excavation, the standing water on the subgrade, the anemometer reading that stopped the crane — time-stamped, location-stamped, and captioned against the affected activity in the daily record kept in site management.
The DPR as the carrier. All of this belongs inside the daily progress report, entered the same day, because contemporaneous entries carry evidentiary weight that reconstructed statements never will.

The Hindrance Register

The hindrance register is the spine of any delay claim, monsoon or otherwise. It records every event that obstructed work: rain and its after-effects, fronts not handed over, drawings pending, client instructions awaited, utility shifting, third-party stoppages. For each entry, capture:

Hindrance number, date raised, and date closed
Description and cause, with responsibility — client, contractor, or neither
Activities and locations affected, with BOQ or schedule references
Duration in days, updated as the hindrance continues
Supporting evidence — photos, letters, DPR references
Whether the affected activity was on the critical path at the time

Two rules make the register credible. First, entries are made when the hindrance starts — a register produced in one handwriting, one ink, at claim time convinces nobody. Second, hindrances are notified to the client in writing within the contract's notice period; most standard forms, including FIDIC-based and government conditions, make timely notice a condition precedent to any claim. A hindrance recorded but never notified is a claim already half lost.

Turning Weather Logs Into an EOT Claim

When the season ends, the claim assembles from records that already exist — never from memory:

Establish the baseline. The approved programme showing planned activity dates and the critical path before the delay window.
Map hindrances to activities. Each rain event and after-effect linked to the specific activities it stopped, from the DPRs and hindrance register.
Demonstrate criticality. Delay matters only where it hits the critical path — the schedule in project management shows which stoppages actually pushed the completion date and which were absorbed by float.
Compute the entitlement. Days of critical delay, net of concurrent contractor delays, with the arithmetic shown — and, where rainfall exceeded the norms assumed in the contract, IMD data alongside your gauge readings to prove exceptionality.
Claim prolongation costs where the contract allows: establishment, staff, and idle plant for the extended period, at rates supported by your own cost records.

An EOT file built this way runs to a few hundred pages of dated, corroborated evidence. Industry experience is blunt about the difference it makes: claims backed by contemporaneous DPRs, hindrance registers, and photographs settle at a large fraction of their value; claims reconstructed from correspondence settle for coins on the rupee, if at all.

Working Through the Season

Documentation protects the claim; management protects the margin. Run the monsoon months on a tighter rhythm — daily review of tomorrow's weather against tomorrow's plan, gangs pre-assigned to covered fallback work so a rain call at 7 AM redirects labour instead of dismissing it, and dewatering and road-repair crews treated as first-priority deployments rather than leftovers. Sites that plan the pivot lose hours where unprepared sites lose days.

The monsoon is the most predictable risk in Indian construction. It arrives on schedule, does what it always does, and rewards the contractor who wrote everything down.

Book a ProjectSathi demo at /contact to see weather logs, hindrance registers, and DPRs come together into claim-ready records.