BOQ Builder·Auto-BOQ from dimensions, DSR ratesNEWBidEasy·Government tenders, searchableLIVEInfraLens App·Free on Play Store, offline-readyNEW
PMC📊 Reports — Daily / Weekly / MonthlyWeekly Progress Report (WPR)

Weekly Progress Report (WPR)

report
PMC-RPT-RPT-009·v1.0-beta·⚠ Beta — review before use

Bridges the daily site reports and monthly MPR. Summarizes a calendar week's progress, resource use, issues, photos, and look-ahead — submitted to PMC / client on Monday for previous week.

ReferencesFIDIC Sub-clause 4.21 (Progress Reports)CPWD Works Manual 2019Project Specific Reporting Schedule
Download
📍 When to use this template
  • Every Monday for the previous calendar week (Mon-Sun).
  • Input to weekly progress review meeting.
  • Cumulative input to MPR + S-curve update.
  • Reference document for delay / claim discussions.
Sections & fields
Preview of the template structure. Download Excel to fill on site.
1Header6 fields
Project Name
_____________
Reporting Week (e.g., Week 23: 5-11 Jun 2026)
_____________
Week-end Date
_____________
Prepared By (Site Engineer)
_____________
Reviewed By (PM)
_____________
Submitted to (PMC / Client)
_____________
2Executive Summary5 fields
Week's Highlight (1-2 lines)
_____________
Overall Progress % (Cumulative)
_____________
Schedule Status (On Track / Behind / Ahead)
_____________
Major Achievements
_____________
Key Issues / Roadblocks
_____________
3Activity Progress7 fields
Activity Code (WBS)
_____________
Description
_____________
Planned Quantity (Week)
_____________
Actual Quantity (Week)
_____________
Cumulative Quantity
_____________
Cumulative % Complete
_____________
Remarks / Variance Reason
_____________
4Resource Deployment (Average / Day)5 fields
Skilled Labour (Nos)
_____________
Unskilled Labour (Nos)
_____________
Engineering Staff
_____________
Supervisory Staff
_____________
Equipment (by category)
_____________
5Material Receipts (Week)6 fields
Material
_____________
Unit
_____________
Planned
_____________
Received
_____________
Cumulative Received
_____________
Pending Orders
_____________
6Issues + Mitigation5 fields
Issue Description
_____________
Impact (Schedule / Cost / Quality / Safety)
_____________
Owner
_____________
Target Resolution Date
_____________
Status
_____________
7Look-ahead (Next Week Plan)4 fields
Activity
_____________
Target Quantity
_____________
Resource Requirement
_____________
Pre-requisites / Approvals Required
_____________
8Site Photographs4 fields
Photo Caption
_____________
Location
_____________
Date Taken
_____________
Reference to Activity
_____________
💡 Sample filled excerpt
Week 23 highlight: Slab L+5 cast (1240 cum); 3-day rain delay handled by RMC + accelerator. Overall progress: 41 % (Plan 45 %). Manpower: 245 avg/day. 1 NCR (closed). Look-ahead: L+6 column starter + L+5 walls.
⚖ Compliance notes
  • WPR is contemporaneous record; cited in claims under FIDIC Sub-clause 20.1.
  • Photos timestamped + geo-tagged if smartphone-captured — enhances evidentiary value.
  • Progress %s computed by both physical (work done) + financial (value earned) methods for cross-check.
  • Issues escalated weekly that aren't closed within 2-3 weeks should auto-escalate to PMR / client review.

Engineer's Notes — Weekly Progress Report (WPR)

Why the Weekly Progress Report matters

On any project with a structured PMC + client review cadence, the Weekly Progress Report (WPR) sits between two other documents: it summarises seven Daily Progress Reports (DPRs) and feeds into the Monthly Progress Report (MPR). It is the most-read project document during construction — PMC, owner, lender, consultants all scan WPRs to track schedule + cost + risk.

FIDIC Sub-clause 4.21 explicitly requires the contractor to submit progress reports at stipulated intervals; on most contracts that interval is weekly. The WPR is also the contemporaneous record cited under FIDIC Sub-clause 20.1 when filing claims for extension of time or additional cost — without disciplined WPRs, claims fail for lack of evidence of when issues arose and what was their impact.

For non-FIDIC contracts (CPWD / state PWD / private), the WPR is still industry standard — typically agreed in the Programme Management Plan or Contract Management Plan.

How the WPR is structured + circulated

Standard WPR structure (8 sections): 1. Header — project + reporting week (Mon-Sun) + author + reviewer 2. Executive summary — 3-5 lines; cumulative % progress + planned vs actual + week's highlight + key issues 3. Activity progress — WBS-level: planned qty / actual qty / cumulative / variance with explanation 4. Resource deployment — average per day: skilled + unskilled labour + engineers + supervisors + equipment by category 5. Material receipts — week's receipts + cumulative + pending POs 6. Issues + mitigation — owner, target date, status (typically tracks 5-15 open issues weekly) 7. Look-ahead — next week plan: target activities + quantities + resource requirements + pre-requisites (drawings / approvals / materials) 8. Photographs — 6-12 site photos with captions + dates + activity references

Circulation (typical): - Monday morning: PM finalises WPR for prior week (data from Friday-Sunday DPRs included) - Monday by 12 noon: WPR emailed to PMC + Owner + lender's engineer (if any) - Monday afternoon: weekly progress review meeting; WPR is the agenda document - Tuesday: minutes circulated; WPR archived to project records + uploaded to project management software (Procore / Aconex / SharePoint)

Common WPR weaknesses

1. Cut-paste from previous week — content barely changes; no real reflection of week's work; reviewers stop reading.

2. Cumulative % only, no weekly delta — "38% complete" — but was that 35% last week or 37%? Always show weekly delta.

3. No variance explanation — actual differs from plan; report doesn't say why. Reviewer must ask in meeting; wastes time.

4. Photos undated / un-captioned — can't tell what's being shown or when. Evidentiary value zero.

5. Resource numbers fictional — "245 avg labour/day" but biometric attendance shows 180. Damages credibility.

6. Issues parked, not escalated — same 12 issues every week, same target dates that keep slipping; reviewer fatigue.

7. Look-ahead too vague — "continue concreting" vs "L+6 columns + beams + L+5 slab pour 1240 cum". Latter is plannable.

8. No cross-reference to RFIs / approvals pending — work blocked because design / material approval pending; report doesn't surface this, owner not pushed.

9. Submitted late — Monday deadline becomes Thursday; loses currency; meeting can't happen.

10. No physical-financial cross-check — physical % done shows 45% but billed value shows 32%; signals quantity over-claim or under-billing; report should flag.

Cross-references

Companion PMC formats: - Daily Progress Report — Site (FMT-SIT-016) — daily input - Monthly Progress Report (PMC-RPT-RPT-011) — monthly roll-up - Weekly Progress Report Site format (FMT-SIT-017) — contractor's site-level version - Look-ahead Schedule (PMC-PLN-LOG-002) — detailed forward planning - Issues Log (PMC-MGT-LOG-001) — issue tracker

Contracts + standards: - FIDIC Red/Yellow/Silver Book 1999 — Sub-clauses 4.21, 8.3, 20.1 (progress, programme, claims) - CPWD Works Manual 2019 — Chapter on monitoring + reporting - NHAI / MoRT&H Manuals — Project monitoring formats - NITI Aayog PRAGATI dashboard — for centrally-funded projects