The report that came back three times
The planning lead on a 420 crore NHAI HAM package in Maharashtra had submitted the April 2024 MPR on the 7th of May, which was on time. By the 14th, it was back from the resident engineer's office with a note: "incomplete, resubmit."
She revised it and resubmitted on the 18th. It came back again. "Resubmit with corrected EVM table and updated programme."
She submitted a third version on the 23rd. This one was accepted.
The data in all three versions was the same. The actual construction progress had not changed between May 7 and May 23. What changed was the way the data was presented, the sequence in which the sections appeared, and the specific format the resident engineer's office expected for the EVM table.
Three weeks of back-and-forth on a report that documented work already done.
What NHAI actually requires
The NHAI Monthly Progress Report is not a single standardized document. Each IE office has its own preferred format, and formats vary by project type (EPC, HAM, BOT) and by regional NHAI office. The starting point for any new package is to get the format the IE expects at the kickoff meeting, not to assume a format from a previous project.
That said, the core sections are consistent across packages. Every NHAI MPR is expected to contain:
Physical progress. Actual quantities executed in the reporting month, cumulative quantities from the start of construction, and percentage completion against the approved BOQ. This section requires the work to be broken down by major activity (earthwork, pavement layers, structures, drainage, safety measures) and by chainage where relevant. A summary table saying "65% complete" is not sufficient.
Financial progress. RA bills submitted, certified, and paid in the month. Cumulative billing and payment position. Outstanding RA bills with aging. Mobilization advance recovery status if applicable. This section is often underbuilt by contractors who treat the MPR as a progress document rather than a commercial document.
Programme vs. actual. A bar chart or table showing the planned versus actual position for each major activity, with variance explained. If the SPI is below 1.0, the IE expects to see the reason and the recovery plan. A bar chart that shows delay without explanation will come back.
EVM table. CPI, SPI, EV, PV, AC, EAC. The format varies but the requirement is consistent. The IE checks whether the numbers are internally consistent: CPI times AC should approximately equal EV. Tables where these numbers do not reconcile get flagged.
Issues and risks. Employer-caused issues affecting progress (land, utilities, design changes, delayed IE responses). Contractor-caused issues and mitigation actions. Upcoming risks. This section is where the contractor formally puts employer-caused delay on record. If it is not in the MPR, it is harder to prove it was communicated.
Labour and plant deployment. Peak and average strength for the month, by category. Plant position (what is on site, what is deployed, what is idle and why). IE offices use this to check whether the contractor is meeting the minimum resource commitments stated in the contract.
Where the data should come from
The MPR quality problem is usually a data sourcing problem. Teams that reconstruct MPR data at the end of the month from memory, site engineer calls, and incomplete measurement books produce reports that are inconsistent and sometimes internally contradictory.
Physical quantities should come from the measurement book, updated weekly. Measurement book entries that are reconstructed at month-end are less precise and harder to defend when the IE queries a specific chainage.
Financial data should come from the billing register, not from the accounts team's monthly close. The billing register tracks RA bill submission, certification, and payment dates. A contracts manager who does not maintain a current billing register will get the financial section wrong.
EVM numbers should be computed from the same source as physical quantities. Teams that run physical progress from one spreadsheet and EVM from another routinely produce MPRs where physical progress and EV do not reconcile.
Programme versus actual should be an update to the baseline programme, not a new document prepared each month. A baseline programme that is updated progressively gives you a traceable record of when delays started and what caused them. A programme that is redrawn monthly to show current status provides no historical record.
The four most common rejection reasons
Based on patterns from NHAI package MPRs, four issues come up most consistently.
EVM table inconsistency. CPI and SPI figures that are not derived from the same EV number, or EAC calculations that do not match the CPI. This is a calculation error that is easy to check before submission: multiply CPI by AC and confirm the result matches EV to within rounding.
Missing programme update. The bar chart shows current status without showing planned status from the baseline. The IE cannot determine whether the contractor is ahead or behind without seeing what was planned.
Issues section too vague. "Land acquisition issues continue to affect progress in certain sections" is not sufficient. The IE needs: which chainages, which survey numbers, what the status was as of the end of the reporting month, what NHAI action is pending. Vague issues sections read as the contractor not tracking the problem.
Labour and plant not reconciled with progress. If the physical progress section claims 85% earthwork completion and the labour section shows average daily deployment of 28 unskilled workers, the IE will question how that volume of earthwork was achieved with that resource level. The sections need to be checked for internal consistency before submission.
The preparation structure that works
The teams that produce consistent, accepted MPRs treat the monthly report as a continuous process rather than a month-end event.
By the 5th of each month, the measurement book entries for the previous month should be closed and verified. By the 10th, the RA bill for the month should be submitted or ready to submit. By the 15th, the EVM table should be computed from the closed measurement data. By the 25th, the draft MPR should be with the project director for review.
A report that is assembled in 2 days at the end of the month will have gaps. A report that is assembled progressively from real-time data takes the same total effort distributed over the month and produces a document that is substantially easier to defend.
The planning lead in Maharashtra implemented this structure in May 2024. Her June 2024 MPR was submitted on the 6th and accepted without revision on the 9th.
She told us the change was not about working more. It was about not doing the same work twice.