Short answer: a daily progress report (DPR) is a one-page record, made the same day, of what happened on a site: weather, manpower, machinery, work done against planned quantities, materials received and used, hindrances, instructions, safety events and photos. Fill it at the end of each shift, have the site engineer sign it, and have the project manager review it the next morning. A good DPR is short, uses the same headings every day, and ties each line of work to a BOQ item or work package, so the numbers can feed measurements, billing and delay claims later.
Most sites already write something daily. The problem is rarely that no report exists. It is that every engineer writes a different one, in a different notebook or WhatsApp group, and nobody can find Tuesday's entry when the client disputes a delay three months later. This guide gives you a format, a routine and the mistakes to avoid.
Why the DPR matters more than it looks
A DPR is not paperwork for its own sake. It is the cheapest evidence a contractor or project owner will ever have.
- Delays and extensions of time. Public-sector works manuals, such as the CPWD Works Manual and Coal India's civil works manual, provide for hindrances to be recorded at site in a hindrance register as they happen, and those records are used when an extension of time is considered.[1][2] A hindrance written down on the day carries far more weight than one reconstructed from memory.
- Measurements and bills. If the DPR records quantities against BOQ items, the running account bill becomes a check, not a fresh exercise. (See our guide to BOQ vs WBS and site measurements.)
- Cost control. Manpower and machine hours logged daily show where productivity is slipping long before the month-end cost report does.
- Handover between people. Engineers change shifts, go on leave and move to other sites. The DPR is how the next person knows what was promised and what is pending.
The DPR format: fields to include
Use the same headings every day, even when a section is "nil". A blank section tells the reader nothing; "nil" tells them someone checked.
| Section | What to record | Why it matters |
|---|---|---|
| Header | Project, site/block, date, shift, report number, prepared by | Makes every report findable and unique |
| Weather | Morning and afternoon conditions; rain start/stop times | Weather is a common, provable cause of lost hours |
| Manpower | Headcount by trade and by agency/subcontractor; own staff separately | Basis for productivity and subcontractor bill checks |
| Machinery | Each machine, hours worked, hours idle, reason for idle time | Idle hire time is a quiet cost; this is where you catch it |
| Work done | Activity, location (grid/floor), BOQ item or work package, quantity today, cumulative quantity, unit | Links progress to the schedule and to measurement |
| Planned vs actual | Today's planned quantity next to actual; short reason for any gap | Turns a diary into a control tool |
| Materials | Received (with GRN or challan number), issued, notable shortages | Feeds material reconciliation |
| Hindrances | What stopped or slowed work, start time, end time, who was informed | The evidence for delay discussions |
| Instructions | Drawings received, site instructions, RFIs raised or answered, client visits | Shows who asked for what, and when |
| Quality | Inspections done, tests taken (cube samples, slump), defects found | Lets you trace a later defect to a date |
| Safety | Toolbox talk held, near misses, incidents, PPE issues | Builds a safety record day by day |
| Photos | 3–6 dated photos of key work fronts, each with a caption | Proof that matches the words |
| Tomorrow | Planned activities, materials and manpower needed | Lets the office act before the gap appears |
| Sign-off | Site engineer signature; reviewer and review date | Makes it a record, not a draft |
Tip: keep descriptions short and factual. "Slab casting at Block B, 3rd floor, grid C–F, stopped 14:10–16:30 due to RMC delay; supplier informed 14:20" is better than "casting delayed due to supply issues".
How to run the DPR routine: step by step
- Agree one format for the whole company. Pick the headings above (or your own), freeze them, and use them on every site. Consistency is what makes reports comparable.
- Map work items to the BOQ or WBS before the job starts. Each activity in the DPR should point to a BOQ item or work package code. Without this, "work done" stays descriptive and cannot be added up.
- Assign one owner per site per shift. Usually the site engineer. Supervisors can feed manpower and machine numbers, but one person signs.
- Fill it the same day. Set a cut-off (for example, one hour after the shift ends). A report written days later is a reconstruction, and it reads like one.
- Attach photos and references, not just text. GRN or challan numbers for materials, RFI numbers for queries, photo captions with location.
- Review it the next morning. The project manager or planning engineer compares planned vs actual, flags gaps and asks one question per gap. Record that the review happened.
- Escalate hindrances in writing. If the DPR shows a hindrance that affects the client or another agency, inform them in writing the same day and note the reference in the DPR. Follow the notice and record-keeping clauses in your own contract.[1][2]
- Roll up weekly. Add the week's quantities, manpower-days and idle hours into a weekly progress report. If daily reports are consistent, this takes minutes.
- File it where everyone can find it. One place per project, searchable by date, not a phone gallery and a pile of notebooks.
A DPR is not your labour register
A DPR's manpower count is a management figure. It does not replace the registers and records that labour law requires employers and contractors to keep. India's four labour codes came into effect on 21 November 2025,[3] and the records they and the related state rules require are a separate compliance job. Keep them separately, and take advice on what applies to your site.
Common DPR mistakes (and what to do instead)
- Writing progress as percentages only. "Brickwork 60% done" cannot be measured or billed. Record quantities and units, then derive percentages.
- No planned figure. Without today's plan next to today's actual, the report cannot show slippage.
- Hindrances without times. "Rain" is weak. "Rain 11:15–13:40, concreting stopped" is useful.
- Photos without captions. A photo with no date, location or activity proves very little later.
- Different formats per engineer. Reports cannot be compared or rolled up, and new staff learn bad habits.
- Nobody reviews it. An unreviewed DPR is a diary. A reviewed one is a control.
- Copy-paste days. If Monday and Tuesday read the same, someone was not on site, or not looking.
Quick checklist before you sign a DPR
- ☐ Date, shift, site and report number filled
- ☐ Weather noted with times if work stopped
- ☐ Manpower by trade and agency; own staff separate
- ☐ Each machine with working and idle hours
- ☐ Every activity tied to a BOQ item or work package, with today's and cumulative quantity
- ☐ Planned vs actual shown, with a reason for each gap
- ☐ Materials received with GRN/challan numbers
- ☐ Hindrances with start/end times and who was informed
- ☐ Instructions, RFIs and visits recorded
- ☐ Tests, inspections and safety events noted (or "nil")
- ☐ Captioned photos attached
- ☐ Tomorrow's plan and needs listed
- ☐ Signed by the site engineer
Where software helps
A paper or spreadsheet DPR works if the routine is strict. It gets harder with several sites, subcontractors and a head office that needs one view. The main gains from putting daily records into a system are that the headings are fixed, work items are picked from the same BOQ and work packages used for measurement and billing, materials link to purchase orders and GRNs, and the history is searchable by date and location.
Woxox Construction OS keeps site records alongside the WBS and BOQ, work packages and measurements, schedule baseline and forecast, requisitions, POs and GRNs, RFIs, and quality and defects, so a daily report sits on the same project record as the bill it will later support. Construction AI works on the same records, and a person approves any action it proposes.
FAQ
What is a daily progress report in construction? It is a same-day record of site activity: weather, manpower, machinery, work done against plan, materials, hindrances, instructions, quality and safety events, and photos, signed by the site engineer and reviewed by the project manager.
Who should prepare the DPR? Usually the site engineer for that site and shift. Supervisors and subcontractor foremen can supply numbers, but one named person should sign each report.
What is the difference between a DPR and a hindrance register? The DPR records everything that happened in a day. A hindrance register, where the contract calls for one, is a dedicated record of events that obstructed work, with dates and durations, often used when deciding extensions of time. Record hindrances in the DPR and, where your contract requires it, in the register as well.
Should the DPR record quantities or percentages? Quantities with units, tied to BOQ items or work packages. Percentages can be calculated from quantities; the reverse is not possible.
How many photos should a DPR have? Enough to show each main work front, typically a handful, each captioned with date, location and activity. A few well-captioned photos are more useful than dozens without context.
Can a DPR replace labour registers? No. The manpower count in a DPR is for site management. Registers required under labour law are a separate record; take advice on what applies to your site.
See daily site records on your own projects
If your DPRs live in notebooks, spreadsheets and chat groups, it is worth seeing what they look like when they sit on the same record as your BOQ, measurements and purchases. Talk to Woxox and see it on your workflows.
By WOXOX Editorial Team
Sources
- CPWD Works Manual 2022 (Central Public Works Department), copy hosted by NDMC: https://www.ndmc.gov.in/departments/Departments/Finance/nodal_cell/CPWD Works Manual 2022.pdf
- Coal India Limited, Manual for Civil Engineering Works (updated till October 2023): https://bcclweb.in/HqrDepartment/Civil/Manual_for_Civil_Engineering_Works_updated_till_October_2023.pdf
- Ministry of Labour & Employment, PIB press release on the four labour codes coming into effect from 21 November 2025: https://labour.gov.in/sites/default/files/pib2192463.pdf