The short answer: A daily progress report (DPR) in construction is a one-day record of what was done on site, by whom, with what materials and equipment, and what held work up. A good DPR shows today's quantities against the plan, flags hindrances with an owner, and reaches the project manager the same evening.
Every site produces a daily progress report in some form. On one project it is a neat PDF that the client reads every morning. On another it is a WhatsApp message typed at 9 pm from memory, with half the numbers missing. Both are called a DPR. Only one of them helps anyone make a decision.
This guide covers what a construction DPR should contain, a worked example from a typical building site, a format you can copy, the mistakes that make reports useless, and how teams are starting to automate the daily progress report so engineers stop rebuilding it every night.
What is a daily progress report in construction?
A daily progress report is a dated site record that captures the work completed, manpower and machinery deployed, materials received and used, hindrances, safety and quality events, and the plan for the next day, so the project team can compare actual progress with the schedule.
The DPR is usually prepared by the site engineer or project engineer and approved by the project manager. It goes to the developer's office, the client or project management consultant, and sometimes the lender's engineer. Over the life of a project, the stack of DPRs becomes the most detailed history of what happened on site: useful for billing, for explaining delays, and for settling disputes about what was done and when.
What goes into a construction DPR?
Formats differ between companies, but most useful DPRs cover the same ten sections.
| Section | What to record | Why it matters |
|---|---|---|
| Header | Project, block/tower, date, report number, weather, working hours | Makes each report traceable and explains weather-related stoppages |
| Work done today | Activity, location, unit, quantity today, cumulative quantity, % complete | The core of the report; feeds progress tracking and billing |
| Manpower | Headcount by trade and by contractor, present and absent | Links output to labour deployed; supports labour bills |
| Machinery | Equipment on site, hours worked, idle or breakdown time | Explains low output and supports hire bills |
| Materials | Received (with GRN or challan number), issued, and balance for key items | Catches shortages before they stop work |
| Hindrances | What stopped or slowed work, since when, who must act | Turns problems into actions with owners |
| Quality | Inspections, pour cards, cube samples taken, tests, non-conformities | Creates the quality trail the client and auditors ask for |
| Safety | Toolbox talk, incidents, near misses, permits issued | Shows the site is managing risk, not just reporting it |
| Instructions and visitors | Site instructions received, drawing revisions issued, visits | Records who said what, which matters later |
| Plan for tomorrow | Activities planned, resources needed, inputs awaited | Makes the next day's blockers visible today |
Add date-stamped photos for the main activities. A photo of the slab before and after the pour answers questions that no amount of text can.
How a DPR works on a real site: a worked example
Here is an illustrative example of a building project, Tower B, on a working day. The numbers are made up but realistic, so you can see how each section connects to the others.
- Work done: 7th floor slab cast, 142 m³ of concrete, 100% complete for that slab. Blockwork on the 6th floor advanced 15% today, reaching 70% cumulative.
- Manpower: 48 present out of 51 on the roll, including the bar-bending crew working on the 8th floor column cages.
- Materials: 4.2 t of 12 mm TMT bars received against a GRN. Cement stock at 12 bags; an indent for 50 bags of OPC 53 raised for the 8th floor columns.
- Quality: Cube samples taken during the pour and logged with sample IDs for 7-day and 28-day testing.
- Hindrance: 4th floor plumbing sleeves on hold because Revision 2 of the plumbing drawing has not reached site. Owner: MEP consultant. Raised: today, 8:55 am.
- Plan for tomorrow: 8th floor column reinforcement, needs the cement delivery before 8 am.
Read together, this report tells the project manager three things in under a minute: the slab is done, cement must arrive tomorrow morning or column work slips, and the plumbing drawing is now someone's job to chase. That is what a DPR is for.
How to prepare a daily progress report: step by step
1. Agree the format before work starts
Fix the sections, units and activity list with the project manager and the client at project start. Use the same activity names and locations as the schedule and the BOQ, so quantities can be compared without re-mapping every day.
2. Capture during the day, not at night
The most common reason DPRs are wrong is that they are written at 8 or 9 pm from memory and scattered messages. Note quantities, headcounts and deliveries as they happen, from the people who saw them: the supervisor, the storekeeper, the foreman.
3. Record quantities against locations
"Blockwork done" is not progress. "Blockwork, 6th floor, grid A–D, 38 m², cumulative 70%" is. Always give the location, the unit and the cumulative figure next to today's figure.
4. Split manpower by trade and contractor
A single headcount hides problems. Record carpenters, bar benders, masons and helpers separately, and note which contractor each crew belongs to. This is what makes the DPR useful for contractor billing and productivity checks.
5. Log materials with document numbers
For every delivery, note the GRN or delivery challan number. For critical items like cement, steel and ready-mix concrete, record the balance at the end of the day. This is what lets the store and the office reconcile later; see our guide to construction material management.
6. Write hindrances as actions
For each hindrance, record what is blocked, why, since when, and who must act. "Waiting for drawing" is a complaint. "L4 plumbing on hold, Rev 2 drawing awaited from MEP consultant since 8:55 am" is an action item.
7. Attach dated photos
Take photos of the main activities, deliveries and any hindrance. Name or tag them with location and date so they can be found later.
8. Compare against the plan
Show planned versus actual for the key activities. If the slab cycle is planned at a set number of days and today's work puts it behind, the DPR should say so plainly, with the reason. Our guide to construction scheduling and delay management covers how to track this over the week.
9. Review, sign and send at a fixed time
Set a deadline, for example 7 pm, and stick to it. The project manager reviews, corrects and approves. A DPR that arrives two days later is history, not a management tool.
10. File it so it can be searched
Store DPRs by project and date in one place. When a delay claim or a billing dispute comes up months later, you will need to find the report for one specific day in seconds.
DPR format you can copy
Use this as a starting template and adapt the activity list to your project.
| Field | Example entry |
|---|---|
| Project / block / date / DPR no. | Skyline Residency / Tower B / 02-11-2026 / DPR-0612 |
| Weather and working hours | Clear / 8:00 am – 6:30 pm |
| Activity, location, today, cumulative | Slab casting, L7, 142 m³, 100% |
| Manpower by trade / contractor | Masons 12, helpers 18, bar benders 9, carpenters 9 (48 of 51) |
| Machinery and hours | Concrete pump 7 h, tower crane 9 h |
| Materials received (GRN) / balance | TMT 12 mm 4.2 t (GRN-0388) / cement 12 bags |
| Hindrances, owner, since | L4 plumbing Rev 2 drawing awaited, MEP consultant, 8:55 am |
| Quality and safety | Pour card signed, cube samples taken, toolbox talk held |
| Plan for tomorrow and inputs needed | L8 column rebar; 50 bags OPC 53 by 8 am |
| Prepared / approved | Site engineer / project manager, with time |
DPR, DLR and weekly report: what is the difference?
| Report | Focus | Frequency |
|---|---|---|
| Daily progress report (DPR) | Work done, resources, hindrances, tomorrow's plan | Every working day |
| Daily labour report (DLR) | Attendance by trade and contractor, overtime, absentees | Every working day |
| Weekly progress report | Progress against the schedule, key risks, look-ahead | Weekly, built from the DPRs |
| Monthly progress report | Milestones, cost and schedule status, photos, issues for management | Monthly, built from weekly reports |
If the daily reports are accurate, the weekly and monthly reports become a summary job. If they are not, every higher-level report inherits the errors. For the seven updates every daily report should capture, see 7 construction site updates your team should track.
Common DPR mistakes to avoid
- Writing it from memory at night. Numbers drift, deliveries are missed and hindrances lose their timing.
- Percentages without quantities. "Blockwork 70%" means little unless the unit and the total are clear.
- One headcount for the whole site. It hides which contractor is under-manned.
- Hindrances with no owner. They get reported every day and resolved never.
- No link to the plan. Without planned versus actual, nobody can tell whether the day was good or bad.
- Copy-pasting yesterday's report. It saves time and destroys the report's value as a record.
- Different formats on different sites. The office cannot compare projects or roll them up.
Where software fits
Most of the effort in a DPR is not writing it. It is collecting the same facts that were already shared once during the day, in group chats, voice notes, store registers and phone calls, and typing them into a spreadsheet. Software helps when it captures those updates as they happen and assembles the report from them, instead of adding another form for the site team to fill in.
What to look for: capture from the phone in the language the site actually uses, quantities linked to activities and locations, attendance and material entries feeding the same report, photos attached automatically, and a review-and-approve step before anything is sent.
Automating the DPR with Brikito
Brikito, construction management software with Brik AI, turns the site's chat and voice updates into structured records: progress, attendance and material requests. From those, Brikito generates the DPR and the daily labour report as PDFs, with photos, ready for the project manager to review and approve. On higher plans, the DPR is linked to the weekly plan so planned versus actual sits in the same report.
BrikDocs, next on the Brikito roadmap, extends this to one-tap reports such as the DPR, DLR, GRN and stock statement, all built from what the team already logged. In every case, Brik AI drafts and a person approves; nothing is sent without review.
Frequently asked questions
Who prepares the daily progress report on a construction site?
Usually the site engineer or project engineer prepares it, with inputs from supervisors, the storekeeper and contractors. The project manager reviews and approves it before it goes to the office or client.
What is the difference between a DPR and a DLR?
A DPR records work done, resources, hindrances and the next day's plan. A DLR (daily labour report) focuses on attendance by trade and contractor, overtime and absentees. Many sites send both every day.
What time should a DPR be submitted?
Set a fixed cut-off, typically the same evening, so the project manager can act on hindrances before the next morning. The exact time should be agreed at project start and applied consistently.
Should a DPR include photos?
Yes. Date-stamped photos of key activities, deliveries and hindrances make the report verifiable and are often the fastest way to resolve later questions about what was done and when.
Can a daily progress report be automated?
Largely, yes. If site updates, attendance and material entries are captured digitally during the day, software can assemble the DPR from them. A person should still review and approve it before it is shared.
Make the DPR a decision tool, not a chore
A daily progress report earns its place when it is accurate, on time and connected to the plan. Capture facts as they happen, tie quantities to locations, turn hindrances into actions with owners, and send it at a fixed time every day.
Do that consistently and the DPR stops being something the site engineer dreads at 9 pm. It becomes the record the whole project runs on, from tomorrow's plan to next month's bill. For how this fits into the full sequence of work on a building project, read building construction process, step by step.