On many Indian construction sites, the Daily Progress Report is treated like a late-night admin task. The supervisor sends a short WhatsApp update, someone in the office turns it into an email, and by the time the report is shared, half the important context is already missing.
That is why so many DPRs look complete on paper but fail in practice. They may show that "work is in progress," but they do not clearly capture what was finished, where it happened, how much labour was deployed, which material or equipment issue slowed the team down, and what support is needed tomorrow.
A strong DPR format should do three things at the same time:
- tell the site story of the day in a structured way
- help the office team act on blockers before the next shift starts
- create a record that is useful later for reviews, billing support, and disputes
This guide explains the DPR format for construction in India that actually works on live projects. You will see the exact fields to include, how to fill them without turning the report into a burden, common mistakes that make DPRs useless, and where a free Excel template is enough versus where software starts saving real time.
If you want the ready-to-use file first, download Site Setu's free DPR template. If you want to understand the format before rolling it out, start here.
What is a DPR in construction
In construction, a DPR usually means Daily Progress Report or Daily Progress Record. It is the daily log of what actually happened on site during that shift or day.
A practical DPR normally captures:
- activities planned and activities completed
- labour and staff deployment
- equipment or machinery used
- materials received or consumed
- weather, safety, inspection, and quality notes
- delays, decisions, and next-day actions
The DPR is not the same thing as a weekly progress report or a monthly client report. Those reports are summaries. The DPR is the raw daily operating record that those later summaries should draw from.
Is there one official DPR format in India
There is no single national DPR template that every project in India must use in the exact same layout. What usually happens instead is that the employer, PMC, architect, or contract conditions specify what information must be recorded and how often progress must be reported.
That is why you will see variations across residential, industrial, infra, and institutional projects. But the underlying logic stays similar.
Recent Indian contract documents still show the same pattern:
- An Indian Bank SCC tender requires contractors to submit daily, weekly, and monthly progress reports in approved formats.
- An SBI technical bid document calls for daily or monthly progress reports and explicitly mentions progress photographs and site records.
- A Cochin Port contract condition requires a daily site record form and weekly progress reporting.
The takeaway is simple: even when clients do not give you a perfect Excel sheet, they still expect a consistent daily record. Your DPR format should be designed around that expectation.
What a good DPR should help you answer by 6 PM
Before you design the format, ask what the report should make obvious to the reader.
By the end of the day, a good DPR should answer these questions:
- What work was planned today?
- What was actually completed, and in which location?
- How much labour and equipment was deployed?
- Did materials, drawings, approvals, or weather affect output?
- Were any safety, quality, or inspection issues raised?
- What is the immediate plan for tomorrow?
- What support is required from the office, client, PMC, or vendor?
If your current DPR cannot answer those questions in one read, the format needs work.
The best DPR format for Indian construction teams
The strongest format is usually one page for the summary plus a few structured sections below it. It should be short enough to finish on site, but detailed enough to support review later.
1. Header section
Start with the basics that make the record traceable:
- report date
- project name
- project code or client name if used internally
- zone, tower, floor, chainage, or work front
- contractor or package name
- prepared by
- reviewed by
This sounds simple, but missing header information is one of the easiest ways to make old DPRs hard to use later.
2. Planned vs completed work
This is the core of the report. Do not write only "good progress" or "shuttering work done." Write the actual activity and location.
Better examples:
- Tower B, 7th floor slab reinforcement completed
- Podium block retaining wall concreting completed, 42 cum
- Villa 18 to 24 internal plaster completed in living rooms
The more measurable the entry, the more useful the DPR becomes for PM review and billing support.
3. Manpower deployment
Track labour by trade or contractor, not only as one total number.
For example:
- masons: 12
- helpers: 18
- carpenters: 16
- bar benders: 10
- electricians: 4
- plumbing crew: 3
- site staff: 5
This gives context when progress is high or low. A delay means something different if RCC work had 38 workers versus 11.
4. Equipment and machinery used
Many DPRs skip this unless there is a breakdown. That is a mistake.
Record the major equipment actually used or standing idle:
- boom placer
- transit mixer
- hoist
- excavator
- concrete vibrator
- bar cutting machine
- DG set
If a machine failed, note the downtime and effect. One line such as "boom placer breakdown for 45 minutes; concreting sequence slowed" is far more useful than a generic delay remark.
5. Material receipt and consumption notes
You do not always need a full material ledger inside the DPR, but you should capture the material context that affected the day.
Typical examples:
- cement received: 120 bags
- TMT consumed: 1.8 MT
- block work held due to shortage of 150 mm AAC blocks
- waterproofing chemical received late at 3:30 PM
This is especially important when daily output depends on procurement or store response. If you later need to explain a delay, the DPR becomes your first supporting record.
6. Blockers, decisions, and deviations
This is the part most teams underwrite. They mention progress but hide the obstacle.
Good DPR formats force the site team to answer:
- what stopped or slowed work
- what decision is pending
- who needs to act
- by when
Examples:
- revised toilet sleeve drawing awaited from MEP consultant
- shuttering material shifted late from Tower C
- one transit mixer arrived 70 minutes behind slot
- rain stopped terrace waterproofing after 2 PM
7. Safety, quality, and inspection notes
Even if you run separate checklists, the DPR should note the events that matter for the day:
- cube samples cast
- consultant inspection done
- RFI closed
- NCR raised
- permit issued for height work
- unsafe scaffold rectified
This turns the DPR into a real operating document instead of just a productivity log.
8. Photo reference
You do not need to paste every photo into the Excel row, but the DPR should reference the photo set clearly.
Examples:
- photo folder: DPR-2026-04-22-Tower-B-Slab-7
- 8 progress photos attached
- before/after photos shared with PMC
On many sites, photos exist but are impossible to match back to the daily report. This one field solves that problem.
9. Next-day plan
A good DPR closes the loop by making tomorrow visible:
- start slab curing and column marking
- complete wall starter layout in grid C4-C8
- follow up revised drawing before 11 AM
- plan 2nd pour if pump availability is confirmed
Without this section, the DPR remains archival. With it, the DPR becomes operational.
Recommended DPR columns for an Excel format
If you are building the format in Excel, these columns work well for most building projects:
| Section | Suggested fields | |--------|------------------| | Report header | Date, project, zone/location, contractor/package, prepared by | | Planned work | Planned activity, target quantity, target location | | Completed work | Actual activity, quantity completed, location | | Manpower | Trade-wise labour count, staff count, subcontractor name | | Equipment | Equipment used, downtime, remarks | | Material context | Key material received, consumed, delayed, or short | | Issues | Drawing issue, approval issue, quality issue, safety issue, weather impact | | Photo record | Photo folder name, attachment count, reference link | | Tomorrow plan | Next activity, support needed, owner | | Sign-off | Prepared by, checked by, client/PMC review if applicable |
If your site runs multiple work fronts, do not force all details into one free-text paragraph. Use one row per work front or package where possible.
Sample DPR entry
Here is a simple example of what a filled DPR entry can look like:
| Field | Sample entry | |------|--------------| | Date | 22 April 2026 | | Project | Tower B Residential Block | | Location | 7th floor slab | | Planned work | Complete slab reinforcement and pour 180 cum concrete | | Completed work | Reinforcement completed; slab concreting completed 176 cum | | Manpower | 14 bar benders, 18 helpers, 9 carpenters, 5 staff | | Equipment | 1 boom placer, 4 transit mixers, 3 vibrators | | Material note | Cement received 90 bags; TMT consumed 1.7 MT | | Issues | One mixer delayed; pour finished 40 minutes late | | Quality/safety | Cube samples cast; edge protection checked before pour | | Photo reference | DPR-2026-04-22-TB7-SLAB, 12 photos | | Tomorrow plan | Start curing and column starter marking |
This is already enough for the project manager to understand the day without joining three phone calls.
How to fill the DPR in 10 minutes without making it a burden
The best DPR process is not "fill everything at night from memory." It is a short workflow:
1. Prepare the format once
Pre-fill static fields such as project name, zone, contractor names, common trades, and equipment lists. That saves time every day.
2. Capture rough notes during the shift
Use a pocket notebook, WhatsApp draft, or mobile form to note:
- work fronts
- labour count by trade
- material delays
- equipment breakdowns
- inspection events
Then convert those notes into the DPR before end of shift.
3. Write measurable completion, not vague summaries
Avoid entries like:
- site work in progress
- labour working
- concreting done
Replace them with:
- basement retaining wall reinforcement completed, grid A1-A6
- 68 labour deployed across RCC, masonry, and MEP
- PCC completed for utility trench, 18 cum
4. Make one person accountable
If three people "jointly own" the DPR, usually nobody owns it well. One site engineer or supervisor should compile it, even if inputs come from stores, QA/QC, or safety.
5. Share it while action is still possible
The real value comes when the DPR is sent before the next shift, not after the weekly review. That timing turns blockers into decisions.
Common mistakes in DPR formats
These are the errors that make daily reports almost useless:
Writing narrative without structure
A paragraph-style DPR looks polished but is hard to scan. Separate fields make it easier to compare days and identify recurring issues.
Tracking only total labour
If the DPR says "45 labour on site," nobody knows whether the shortage was in masonry, shuttering, or electrical work.
Skipping location details
Work done without tower, floor, grid, or zone is too vague for review and billing follow-up.
Hiding blockers
Many teams only report completed work because they do not want to highlight delay reasons. That defeats the purpose. The DPR is where you surface the blockage early.
No tomorrow plan
This turns the DPR into yesterday's archive instead of tomorrow's handoff.
No photo reference
Photos in WhatsApp without a matching DPR reference get lost very quickly.
DPR format in Excel vs WhatsApp vs software
This is the tradeoff most teams are actually deciding.
Good for:
- fast updates
- urgent coordination
- photo sharing
Weak for:
- structured history
- trade-wise manpower tracking
- consistent reporting across projects
- later review by management or client
Excel template
Good for:
- standardizing one format
- sending daily reports by email
- getting site teams disciplined
- starting quickly at low cost
Weak for:
- follow-up on blockers
- linking photos and attachments cleanly
- maintaining one version across teams
- searching old reports later
Connected DPR software
Good for:
- mobile capture from site
- photos, notes, and updates in one place
- linking DPR with tasks, drawings, materials, and issues
- same-day review across site and office teams
Weak for:
- teams that have not yet agreed on the basic reporting habit
That is why many Indian teams start with the Excel format first, then move into construction DPR software once the reporting discipline is stable.
When a free DPR template is enough
An Excel template is usually enough when:
- you have one or two active projects
- the client does not require a custom portal or reporting system
- the same engineer prepares the report every day
- photos are manageable without a large archive
- follow-up decisions still happen through a small team
If that sounds like you, start with Site Setu's free DPR template download.
When Excel starts breaking
Excel starts hurting when:
- multiple engineers fill different versions
- project managers need reports from many sites every evening
- material and drawing issues need traceable follow-up
- client and PMC comments need closure against the same record
- management wants searchable history, not folders full of files
That is where a connected workflow starts saving time. Site Setu's construction management app and DPR workflow page are built for that transition.
How Site Setu fits into daily reporting
Site Setu is useful when your team wants the DPR to connect with the rest of execution instead of staying as a standalone sheet.
That usually means:
- daily progress linked to planned tasks or work fronts
- materials and GRNs connected to the report context
- drawing issues visible inside the same workflow
- photos, remarks, and blockers tied to the date and location
- office review happening without waiting for a rewritten summary
The goal is not to make reporting longer. The goal is to make the same daily effort more useful.
FAQs
What is the difference between a DPR and a site diary?
They are closely related. On many projects, the DPR is the structured daily report shared with management or client, while the site diary is the broader running record of site events, instructions, and observations. Some teams combine them; others keep separate formats.
What should a construction DPR include every day?
At minimum, include project/date details, planned vs completed work, labour deployment, equipment used, material context, blockers, safety or quality notes, photo reference, and the next-day plan.
Should the DPR include quantities or only activity names?
Use quantities wherever practical. Quantity plus location is much more useful than a generic activity name, especially for review, billing support, and progress tracking.
Who should prepare the DPR on site?
Usually the site engineer, project engineer, or supervisor responsible for that work front. Inputs can come from stores, QA/QC, safety, or subcontractors, but one person should compile the final report.
Is there one universal DPR format for all projects?
No. The exact layout varies by employer and project type, but the core sections are usually the same: work done, resources used, issues, and next-step visibility.
Where can I download a DPR format in Excel?
You can download Site Setu's Daily Progress Report template and customize it with your logo, project naming, and approval fields.
Final takeaway
The best DPR format for construction is not the longest one. It is the one your site team can fill accurately every day and your office team can act on immediately.
If you keep the format focused on measurable work, trade-wise labour, equipment, material context, blockers, photos, and tomorrow's plan, the DPR becomes more than a status mail. It becomes the daily control point for execution.
Start with the free DPR template. When the reporting habit is stable and the spreadsheet starts getting in the way, move to a connected DPR software workflow.
References and Further Reading
Primary and supporting sources cited in this article.
Tags: