Weekly Progress Report Format for Construction: India-Specific Template, Sample & Compliance Guide [Free Download]

Bridge the gap between daily site execution and monthly billing with this CPWD/PWD-compliant weekly progress report format. Includes Earned Value snapshots, arbitration-ready hindrance registers, and RA bill linkage—specifically built for Indian construction projects.

Construction site engineer reviewing weekly progress reports and project documentation in a site office cabin with active construction work visible through the window

Weekly Progress Report Format for Construction: India-Specific Template, Sample & Compliance Guide

Your site engineer fills the DPR every evening. Your billing team chases Measurement Book entries at month-end. But between those two points, most contractors lose visibility—and money.

The Weekly Progress Report (WPR) is that bridge. Done right, it turns seven days of scattered site data into a billing-ready document that protects you in arbitration and gets your RA bills certified faster. Done wrong (or not at all), you're scrambling to reconstruct quantities from WhatsApp photos when the client disputes your claim.

This guide gives you a CPWD/PWD-compliant weekly progress report format for construction built for Indian contracting realities. It links your daily execution to RA bill processing, tracks earned value without the spreadsheet headaches, and documents delays as they happen—not three months later when you're preparing an EOT submission.


Why Most Weekly Reports Fail on Indian Sites

The reporting chain on a typical CPWD or state PWD project looks like this:

Reporting Level Frequency Primary Use Where It Breaks
DPR Daily Site execution, labour tracking Captured inconsistently on WhatsApp
WPR Weekly Client reviews, billing prep Ad-hoc emails or missing entirely
Monthly MIS Monthly Board reports, fund flow Aggregated too late for course correction
RA Bill Monthly Payment certification Reconciled against incomplete records

The gap is lethal. Project managers often paste DPR data into random Excel sheets Monday morning, missing:

  • BOQ line-item mapping that billing engineers need for Measurement Book entries
  • Earned Value snapshots (SPI/CPI) that tell you if you're bleeding money before month-end
  • Contemporaneous hindrance records that arbitrators weigh heavily in EOT claims
  • RA-ready quantity statements pre-validated for the client's QS

Without a structured WPR, you reach the billing cycle discovering that your concrete quantities don't match the pour cards, or worse—you've missed documenting a three-day client delay that now becomes your cost.


DPR vs WPR vs Monthly MIS: Which Report When?

Stop confusing your stakeholders with the wrong document at the wrong time.

Daily Progress Report (DPR)

Audience: Site engineers, subcontractors, project managers
Content: Task completion, headcount, machinery hours, weather, incidents
Timing: Same day or next morning
Purpose: Operational control—what happened today and what's blocking tomorrow

Weekly Progress Report (WPR)

Audience: Client/PMC, HO planning, billing engineers, contracts team
Content: Consolidated 7-day quantities, milestone status, hindrances, earned value, upcoming plan
Timing: Every Monday morning (previous week)
Purpose: Stakeholder management and billing readiness—this is your RA bill checkpoint

Monthly MIS Report

Audience: Directors, investors, lenders, corporate finance
Content: Portfolio cash flow, schedule variance, risk register
Timing: Within 5 days of month-end
Purpose: Strategic decisions—aggregated from WPRs, not DPRs

The rule: DPR tracks execution. WPR manages money and relationships. MIS drives investment.


When You Actually Need a Weekly Progress Report

Don't generate paperwork for the sake of it. Deploy your WPR in these specific scenarios:

1. Client Review Meetings

CPWD contracts and most developer agreements mandate weekly site reviews. Your WPR is the agenda and the official record. More importantly, it's your contemporaneous documentation of client-caused delays—critical when that "small drawing revision" becomes a 15-day EOT claim later.

2. HO Approval Checkpoints

Before head office releases subcontractor payments or approves material advances, they need consolidated visibility. A WPR with SPI/CPI metrics gives them confidence in project health without flying to site.

3. RA Bill Processing

Running Account bills require quantity verification against executed work. Your WPR's weekly quantity summary feeds directly into Measurement Book entries, reducing month-end reconciliation from days to hours.

4. EOT Claim Documentation

Arbitration panels under the Arbitration and Conciliation Act, 1996 give significant weight to contemporaneous records. A WPR with a maintained Hindrance Register creates an evidence chain that post-facto delay analysis cannot match. The Delhi High Court in Simplex Concrete Piles (India) Pvt. Ltd. v. Union of India (1989) emphasized contemporaneous site records over expert testimony compiled months later.

5. Subcontractor Payment Triggers

Many Work Orders link progress payments to weekly milestone achievement. Your WPR becomes the certification document triggering these releases.


Weekly Progress Report Format: Section-by-Section Breakdown

The following format is designed for CPWD/PWD compliance and Indian private development projects. It connects your daily site data to billing and claim outcomes.


Section 1: Project Header & Reporting Period

Field Purpose Example
Project Name Contract reference "Riverside Residences Tower A, Mumbai"
Contract Reference CPWD/PWD Agreement No. "CE(P)/Mum/2024/1847"
Reporting Period Clear week definition "Week 23: 03 June – 09 June 2024"
Report No. Sequential tracking "WPR-24-023"
Contractor/PMC Name Legal entity "Metro Builders Pvt. Ltd."
BOQ Reference Link to contract schedule "Schedule A – Civil Works, Item 1.1 to 4.7"

Compliance note: CPWD contracts require the Agreement No. on all formal submissions. State PWDs (Maharashtra, Karnataka, etc.) follow similar protocols. Include this header to ensure admissibility during audits or arbitration.


Section 2: Executive Summary – Earned Value Snapshot

This section separates professional contractors from those flying blind. Calculate these metrics weekly:

Metric Formula What It Tells You Target
SPI (Schedule Performance Index) EV ÷ PV >1 = Ahead, <1 = Behind >0.95
CPI (Cost Performance Index) EV ÷ AC >1 = Under budget, <1 = Over >0.95
Week's Earned Value Completed work × BOQ rates Cash-flow impact Track weekly
Cumulative Earned Value Total value to date Overall project position vs. Budget

Example:

"SPI: 0.94 (3 days behind baseline). CPI: 1.02 (2% under budget). Week's EV: ₹24.3 Lakhs. Primary delay: Foundation excavation in Zone B due to uncharted utilities per SI-2024-089."

Superwise's Estimation vs. Earned Value module auto-calculates these from progress entries and BOQ rates.


Section 3: Work Completion Summary (7-Day Consolidated)

Roll up your DPR entries into BOQ-line-item quantities. This is what your billing engineer needs for RA bill preparation.

BOQ Item Description Unit Planned Qty (Week) Achieved Qty (Week) Cumulative Qty % Complete
2.1 PCC M10 45 42 386 62%
2.2 RCC M25 (Columns) 28 28 124 38%
3.1 Brickwork 230mm 180 156 890 29%
4.5 Internal Plaster 320 340 1,240 41%

Critical practice: The "Achieved Qty" column must reconcile with your Measurement Sheets. This creates the audit trail: daily progress → weekly summary → RA bill. When the client's QS questions your quantities, you pull the WPR, not a shoebox of pour cards.


Section 4: Resource Deployment

Track productivity, not just presence. When your manday output drops, catch it here before it kills your schedule.

Resource Type Mon Tue Wed Thu Fri Sat Sun Weekly Total
Manpower
Skilled Masons 12 12 10 12 14 8 0 68
Bar Benders 4 4 4 4 4 4 0 24
General Labour 25 28 25 30 28 20 0 156
Machinery
Tower Crane (hrs) 10 10 10 10 10 6 0 56
Concrete Pump (hrs) 4 0 0 4 0 4 0 12
Material Receipts
Cement (MT) 12 0 18 0 15 0 0 45
TMT Steel (MT) 0 8 0 0 12 0 0 20

Red flag: If your masonry output drops from 2.5 m² per manday to 1.8 m² per manday, the table surfaces the productivity loss immediately—whether due to material shortages, rework, or weather.


Section 5: Hindrances & Delay Register (EOT Evidence)

This is your arbitration insurance. Document every impediment contemporaneously.

Date Hindrance Description Type Responsibility Impact (Days) Reference Document Status
05-Jun Delay in G+2 slab shuttering release by PMC Client-Caused PMC/Client 2 Site Instruction dated 04-Jun Resolved 07-Jun
06-Jun Non-availability of power from 14:00-18:00 External Discom 0.5 Complaint No. DES-240606-1 Ongoing
07-Jun Revised drawing for staircase landing received Design Change Client/Architect 1 Drawing Rev. B dated 06-Jun Resolved

Arbitration guidance: Indian arbitration panels evaluate delay claims based on contemporaneous documentation. Key fields: - Type: Client-caused, contractor-caused, force majeure, or neutral events - Reference Document: Links to Site Instructions, emails, drawing revisions, or formal notices - Impact: Quantified delay days—essential for EOT calculations and cost claims

Without this register, you're trying to prove a three-month-old delay from memory.


Section 6: Quality & Safety Observations

Date Observation Type Description Location Action Taken NCR Ref Status
04-Jun Quality Honeycombing in Column C-12, G+1 Grid C-12 Removed and re-cast NCR-2024-047 Closed
06-Jun Safety Missing guardrail at edge of slab G+3 South edge Installed immediately - Closed

For Superwise users, Quality Checklists and issue tracking populate this section automatically.


Section 7: Photo Evidence Grid

Compile geo-tagged, dated photographs from daily reports into a weekly grid:

Location/Activity Mon Tue Wed Thu Fri Sat
Foundation Zone A [Img] [Img] - - - -
Column Shuttering G+2 - [Img] [Img] - - -
Slab Casting G+1 - - - [Img] [Img] [Img]
Material Storage [Img] - [Img] - [Img] -

Compliance tip: CPWD and state PWDs require photographs as supporting evidence for Measurement Book entries. Your weekly photo grid satisfies this requirement while creating visual proof of progress for arbitration.


Section 8: Upcoming Week Plan (Look-Ahead Schedule)

Activity Target Quantity Dependencies Risk/Issue
Complete slab shuttering G+3 285 m² Column concrete curing complete (72 hrs) Crane availability confirmed
Start blockwork G+2 120 m² Slab shuttering release by PMC Await PMC inspection schedule
Foundation PCC Zone C 60 m³ Utility clearance from MCGM Approval pending, expedite

This look-ahead serves two purposes: it demonstrates proactive planning to clients, and it flags dependencies where you need external action—creating written record of what you're waiting for.


Section 9: Billing Impact Summary (RA-Ready Quantity Statement)

Transform your WPR from a status document into a billing tool.

BOQ Item Description Unit Rate (₹) This Week Qty This Week Value (₹) Cumulative Value (₹) Remarks
2.1 PCC M10 4,850 42 203,700 1,872,100 Ready for RA-6
2.2 RCC M25 (Columns) 8,200 28 229,600 1,016,800 Ready for RA-6
3.1 Brickwork 230mm 1,450 156 226,200 1,290,500 Hold – NCR open

Billing workflow: 1. Billing engineer extracts quantities from this section 2. Cross-checks with Measurement Sheets 3. Prepares RA Bill with pre-validated quantities 4. Reduces billing cycle from 5-7 days to 2-3 days


Sample Weekly Progress Report: Filled Example

Project: Riverside Residences, Tower A
Contractor: Metro Builders Pvt. Ltd.
Period: Week 23 (03 June – 09 June 2024)
Contract Ref: CE(P)/Mum/2024/1847

Executive Summary

  • Physical Progress: 62% of civil works (against 64% planned)
  • SPI: 0.97 (slight delay)
  • CPI: 1.01 (on budget)
  • Key Milestone: G+1 slab completed on schedule; G+2 columns in progress
  • Critical Issue: Uncharted sewer line in Zone B delayed foundation by 2 days; PMC instructed alignment change via SI-2024-089 (EOT claim documentation attached)

Work Completion Summary

Item Unit Planned Achieved Status
RCC Columns G+2 28 28 ✓ On Track
Slab Shuttering G+2 285 240 ⚠ Behind (crane breakdown)
Blockwork G+1 180 156 ⚠ Behind (manpower shortage)

Hindrance Register

Date Issue Type Impact Status
04-Jun Crane breakdown (Electrical fault) Contractor 1 day Resolved
05-Jun Revised architectural drawing for service duct Client 2 days Ongoing

Resource Deployment

  • Manpower: 248 mandays (target: 260)
  • Machinery: Tower Crane 56 hrs, Concrete Pump 12 hrs
  • Material: Cement 45 MT, Steel 20 MT

Billing Impact

  • RA Bill 6 Preparation: ₹8.45 Lakhs quantities verified and ready
  • Hold: Blockwork (Item 3.1) – NCR-2024-047 closure pending

Upcoming Week (24)

  • Complete slab G+2 shuttering
  • Cast slab G+2 concrete
  • Resolve utility conflict Zone B with MCGM

Weekly Report Best Practices for Indian Contractors

Timing and Distribution

Deadline: Every Monday by 10:00 AM (previous week data)
Distribution: Site Engineer → Project Manager → Client/PMC → HO Planning → Billing Team
Format: PDF for formal submission (tamper-evident), Excel for internal use

Sign-Off Requirements

  • Prepared by: Site Engineer
  • Reviewed by: Project Manager
  • Approved by: Project Director (for client submission)

Digital vs. Excel: Tool Comparison

Capability Excel WPR Superwise Digital Reports
DPR auto-consolidation Manual copy-paste Automatic from daily entries
EVM calculation (SPI/CPI) Manual formula Auto-calculated from schedule
Photo geo-tagging Manual organization Auto-compiled from site photos
Measurement Book linkage Manual cross-reference Direct integration
RA bill generation Separate process One-click from weekly data
Hindrance Register Static table Linked to EOT claim workflow
Multi-project roll-up Complex Portfolio dashboard built-in

Recommendation: For projects under ₹10 Crores or single-site operations, Excel templates work. For multi-project portfolios, PMCs, or contractors with monthly RA bills exceeding ₹50 Lakhs, digital tools pay for themselves through reduced billing cycle time and improved claim documentation.


How Weekly Reports Protect You in Arbitration

Indian construction arbitration turns on contemporaneous documentation. Your WPR becomes evidence in three scenarios:

1. Extension of Time Claims

CPWD Clause 5 (and equivalent state PWD clauses) entitle contractors to EOT for delays not attributable to them. Your Hindrance Register with dated entries, reference documents, and impact quantification provides the evidence chain arbitrators require.

2. Disruption Claims

Even without time extension, claim costs for disruption (reduced productivity due to client-caused interruptions). Resource deployment tables showing declining productivity per manday support these claims.

3. Variation Valuation

Your weekly quantity summaries establish baseline quantities before and after variations, supporting your valuation of additional works.

Documentation standard: Maintain WPRs with: - Sequential numbering (WPR-24-023, etc.) - Consistent reporting periods (Monday-Sunday) - Cross-references to Site Instructions and drawings - Quantified impacts in days or cost - Acknowledgment receipts from client/PMC


FAQ: Weekly Progress Reports for Indian Construction

Q1: Is a WPR mandatory under CPWD contracts?

While CPWD contracts don't explicitly mandate a "Weekly Progress Report," most Agreement conditions require weekly site meetings with documented minutes. Your WPR serves as those minutes and becomes the official record of progress and hindrances.

Q2: How is WPR different from the Daily Progress Report (DPR)?

DPR captures task-level execution data daily. WPR consolidates 7 days of DPR data into stakeholder-ready summaries with earned value metrics, hindrance registers, and billing linkages. Think of DPR as operational and WPR as managerial.

Q3: Who should prepare the WPR?

Site Engineers compile the data. Project Managers review and approve. Billing Engineers validate the quantity summaries. For client submission, the Project Director typically signs off.

Q4: Can WPR data be used directly for RA bills?

Yes, if your WPR includes a Billing Impact Summary with BOQ-mapped quantities. This section should reconcile with your Measurement Book entries before RA bill preparation.

Q5: How do I document hindrances for EOT claims?

Record: (1) Date of hindrance, (2) Description, (3) Type (client/contractor/external), (4) Responsible party, (5) Quantified impact in days, (6) Reference document (SI, email, drawing), and (7) Resolution status. This structured record supports arbitration evidence requirements.

Q6: How long should WPRs be retained?

Retain for the contract period plus the limitation period under the Arbitration and Conciliation Act, 1996 (typically 12 years from cause of action). For government contracts, follow document retention schedules specified in the contract.


Takeaway Template: Free Weekly Progress Report Format

Download our India-compliant Weekly Progress Report Template in Excel and PDF formats. This template includes:

  • Pre-formatted sections matching CPWD/PWD requirements
  • Built-in formulas for EVM calculations (SPI/CPI)
  • Hindrance Register with EOT evidence fields
  • Billing Impact Summary linked to BOQ structure
  • Photo evidence grid
  • Sample data from a residential high-rise project

Download the ready-to-use files for this article:

CPWD/PWD-compliant weekly progress report workbook with built-in Earned Value calculations (SPI/CPI), hindrance register for EOT claims, BOQ-linked quantity summaries, and RA bill-ready billing impact section. Best format: Excel, because this asset is meant to be edited and reused on-site. - Download Excel template

Related Resources: - Construction Reporting Pack for India - Daily Progress Report Format - RA Bill Certification Guide - Digital Measurement Book - Earned Value Management


For contractors, PMCs, and project managers handling CPWD, state PWD, NHAI, and private development projects—this weekly progress report format bridges your daily execution to monthly billing success.

Read more