A daily progress report (DPR) is the single page that tells the office what happened on site today: the work done, who did it, what material was used and what is holding things up. Done well, it is the most useful record a project keeps. Done badly, it is a photo dump in a chat group that nobody can find a month later. This guide gives you a practical DPR format and the habits that make it stick.
What is a daily progress report in construction?
A DPR is a dated record, prepared by the site engineer or supervisor, of the work carried out on a project during one shift or day. It is reviewed by the project manager and kept as part of the project file. Clients, consultants and auditors rely on it when they need to know what was done, when, and with what resources.
On Indian sites the DPR also settles practical questions: how many workers each contractor sent, how much cement was used for a pour, and why a slab was delayed. That is why it pays to keep the same format every day.
What to include in a DPR: the essential fields
| Section | What to record | Why it matters |
|---|---|---|
| Header | Project, location or work front, date, shift, weather | Ties every entry to a place and a day |
| Work done | Each activity with quantity and unit (e.g. 99 sqm shuttering) | Measures real progress against the plan |
| Labour | Count by trade and by contractor | Supports wages and contractor bills later |
| Material | Received, used and short, by material | Catches shortages before they stop work |
| Equipment | Machines on site and hours used | Shows idle time and hire cost |
| Hindrances | Anything that stopped or slowed work | Explains delays with evidence |
| Safety and quality | Incidents, checks done, tests taken | Keeps a record you may need later |
| Photos | Before and after shots of each activity | The proof clients and auditors ask for |
| Tomorrow | Planned activities and material needed | Lets the office prepare in time |
| Sign-off | Prepared by, reviewed and approved by | Makes the report accountable |
Run your project management on CivilPilot
Projects, tasks, schedules, locations and issues for every site, in the same place your team reports progress.
A sample DPR entry
Here is what one day might look like for a residential building. The format matters more than the numbers, which are for illustration only.
| Activity | Quantity | Unit | Labour | Remarks |
|---|---|---|---|---|
| 3rd floor slab shuttering | 99 | sqm | 14 | Props checked by engineer |
| 3rd floor column concreting | 15 | cum | 11 | Cube samples taken |
| 1st floor block masonry | 64 | sqm | 9 | — |
| Ground floor conduit laying | 141 | rmt | 4 | Waiting for junction boxes |
Who prepares and who approves the DPR?
The site engineer or supervisor prepares it at the end of the shift, while details are fresh. The project manager reviews it the same evening or next morning and either approves it or sends it back with a reason. Approved reports should not be edited quietly afterwards; if something was wrong, record a correction.
Common DPR mistakes
- Filled at month-end from memory. The report becomes a guess. Make it a same-day habit.
- Photos without context. A photo needs the activity, location and date attached to it.
- Labour counted as one number. Split it by trade and contractor, or it is useless for billing.
- No hindrance column. Delays without a recorded reason turn into disputes.
- Different format on every site. The owner cannot compare sites if each one reports differently.
Paper, Excel or software?
Paper registers work until someone needs to search them. Excel sheets are better, but they live on one laptop and photos sit somewhere else. Site management software keeps the report, its photos and its approval in one place, searchable by project and date.
In CivilPilot, the site engineer files the DPR from a phone browser: work items with quantity, unit and labour, photos stamped with where they were taken, and notes. The project manager approves it or asks for changes, and anyone can download it as a PDF for the client.
Make the DPR a daily habit
- 1Agree one format for every site and stop accepting reports in chat.
- 2Set a deadline, such as 7 pm, for each day’s report.
- 3Review and approve every report within a day, so engineers see it matters.
- 4Use the reports in your weekly meeting; people fill in what gets used.
