What a construction DPR must contain, a sample structure you can adopt this week, and how daily records become RA-bill and EOT-claim evidence.

Every construction contract in India — an NHAI package, CPWD works, a private developer's towers — assumes somebody is keeping a daily record of what happened on site. Most sites treat that record, the daily progress report, as an evening chore: a few lines typed into WhatsApp, a dozen photos, done. Then an RA bill gets questioned, or a delay turns into a liquidated-damages notice, and suddenly the DPR is the most important document the project never properly kept.

This guide covers what a daily progress report in construction must actually contain, a sample structure you can adopt this week, why DPRs die in WhatsApp groups, the claim value of weather and photo evidence, and how to automate the whole thing so your site engineers stop spending an hour every evening on compilation.

The Three Jobs of a DPR

A good DPR works for three different readers at once:

Operations. The project manager reads it to plan tomorrow — which gangs delivered, what is blocked, what needs material.
Commercial. The billing engineer reads it to build RA bill quantities and to log every hindrance that may later support an extension of time.
Management. Head office reads twenty of them, aggregated, to know which site is drifting before the drift becomes a crisis.

A DPR that serves only the first reader — "work going on, all okay" — is not a report. It is a formality that will cost you money in the third year of the project, in arbitration.

What a DPR Must Contain

Six sections. No more, and definitely no fewer.

1. Manpower

By category and by agency — skilled, semi-skilled, unskilled, staff — per subcontractor, against the planned deployment. Not "145 workers". Rather: shuttering carpenters 28 against 35 planned (M/s Sharma Enterprises), bar benders 22, masons 18, helpers 61, staff 9. The gap between planned and actual deployment, tracked daily, is the earliest predictor of schedule slippage you will ever get.

2. Materials

Three numbers for every A-class material: received today, consumed today, closing stock. Cement, reinforcement steel by diameter, diesel, and whatever else drives your cost — bitumen on a road job, aggregate ahead of a PQC pour. Closing stock reported daily makes pilferage visible in days instead of months.

3. Work Done — in Quantities, Against BOQ Items

The heart of the report. Not "slab work in progress" but: seventh-floor slab, east wing — 68 cum of M30 poured against BOQ item 5.3; reinforcement for eighth-floor columns — 4.2 MT tied. Location plus quantity plus BOQ reference means DPR entries roll straight into the next RA bill abstract instead of being re-measured from scratch.

4. Weather — With Times

Not "rain". Instead: "Rain 13:10 to 16:40. Concreting suspended; pour resumed 17:15, completed 21:30 under lights." On a project fighting a delay notice, three years of dated, timed weather entries are worth crores. More on this below.

5. Hindrances and Blockers

Drawing not released, front not available, client instruction awaited, DISCOM power shutdown, the adjacent-package contractor blocking access. Each with time, duration, and the activity affected. This is the raw hindrance register that your EOT claim will one day be built on.

6. Photos — Geo-Tagged and Time-Stamped

The minimum set: each active work front, any hindrance (a waterlogged foundation, a blocked haul road), every concrete pour, and anything unusual. A photo with GPS coordinates and an untouched timestamp is evidence. A photo forwarded on WhatsApp with its metadata stripped is just a picture.

A Sample DPR Structure

One page plus a photo annexure:

Header — project name (say, Metro Phase-II, Package CC-04), date, DPR number, weather with timings
Manpower summary — by category and agency, planned versus actual
Plant and machinery — deployed, working hours, idle hours with reason
Materials — received, consumed, closing stock for A-class items
Work executed — quantity, location, BOQ item reference
Hindrances — time, duration, activity affected, responsibility
Safety — toolbox talk done, incidents if any
Tomorrow's plan — gang-wise targets in quantities
Photo annexure — geo-tagged and captioned

An engineer working from structured data captured during the day fills this in fifteen minutes. An engineer starting from memory at 8 PM writes "work in progress as per schedule" — and that difference compounds into lakhs.

Why DPRs Die in WhatsApp Groups

WhatsApp is where Indian site reporting went to feel efficient — and where the record goes to die.

No structure. Quantities arrive as free text, photos without captions. Nothing can be aggregated, compared across days, or totalled into a bill.
No single version of truth. Was the 27 cum in Tuesday's message before or after the honeycombing repair? Which message was the correction? Nobody can say under cross-examination.
Unsearchable evidence. Proving the pour finished before the rain means scrolling months of messages — if the photo's metadata even survived WhatsApp's compression, which it did not.
History walks out the door. A site engineer resigns, the group gets cleaned up, a phone gets formatted — three years of records, gone.
Reporting theatre. Forty messages a day create the feeling of control while nothing usable is being recorded.

The pattern is always the same: WhatsApp works fine until the first serious dispute. Then the company discovers it owns thousands of messages and zero records.

The EOT Claim: Where DPRs Turn Into Money

Extension-of-time and prolongation claims on Indian public contracts — NHAI, PWD, CPWD, metro packages — live and die on contemporaneous records. Arbitrators and dispute boards consistently give more weight to records kept at the time than to analyses reconstructed years later by consultants.

Consider a realistic shape. A contractor on a highway package loses 47 working days across two monsoons to rain and to land handed over late. The prolongation cost — extended site establishment, idle machinery, staff salaries — comes to ₹3.1 crore. The claim succeeds or fails on questions only a DPR can answer:

On which specific dates did rain stop which specific activities, and for how long?
Was the affected activity on the critical path that day?
Which chainages were unavailable, and when was each front actually handed over?
Do photographs corroborate the waterlogging, the idle pavers, the blocked front?

Daily weather entries with times, hindrance logs naming activities, and geo-tagged photos answer all four. "Heavy rain this month" answers none of them. The contractor with structured DPRs recovers a substantial part of that ₹3.1 crore; the contractor with WhatsApp forwards writes it off against margin.

Automating the DPR

The fix is not a better template. It is removing evening compilation entirely — the DPR should assemble itself from entries made during the day:

Attendance captured at the morning muster flows into the manpower section automatically.
Store receipts and issues flow into the materials section, closing stock computed.
Engineers log quantities against BOQ items as work completes, taking the photo in the same screen — geo-tag and timestamp attached by the app, not by trust.
Weather windows and hindrances are entered when they happen, with durations.
At 6 PM the site management module compiles the day into a formatted DPR. The project manager reviews, signs off, and the report goes to the client and head office — while the same data updates schedule progress in project management and queues quantities for the next RA bill.

Compilation time drops from an hour to minutes, but that is the smaller win. The bigger one is that every DPR becomes claim-grade, because nothing in it was reconstructed after the fact. See the full daily flow on how it works.

The Bottom Line

A DPR is not paperwork. Kept properly, it is tomorrow's plan, next month's RA bill, and the evidence that wins a claim three years from now. The only sustainable way to keep it properly is to stop writing it at night and start capturing it during the day.

Book a ProjectSathi demo and watch a DPR assemble itself from a live site's daily entries.