Why Most Indian Construction Projects Go Over Budget — Five Specific Causes, What Earned Value Management Catches Early, and Why By Month Three the Overrun Is Already Predictable
Key facts at a glance
- 60–80% of Indian construction projects experience cost overruns (McKinsey 2017, CAG audit reports, KPMG India surveys)
- The Cost Performance Index set by 20% of project duration predicts the final overrun within 10% — this is PMI's most validated EVM finding
- The top cause: scope changes verbally approved on site but never priced as formal variation orders
- Material price escalation accounts for 15–25% of infrastructure project overruns on multi-year contracts
- A ₹20 Cr project running at Cost Performance Index 0.93 in month 4 = ₹1.4 Cr overrun already in progress
- VentureVitals calculates Cost Performance Index per project continuously from live procurement and progress data
In this guide
Cost overruns in Indian construction are not random. They are not bad luck. They are not the result of uniquely difficult conditions in India — though India has plenty of those. They are the predictable output of five specific failure patterns that repeat across projects worth ₹5 Cr and ₹500 Cr with remarkable consistency. The difference between the projects that finish on budget and the ones that do not is almost never what happened on site. It is what was known and acted on in month 2 versus what was discovered in month 18.
I want to be specific about the data before the analysis, because "construction projects go over budget" is a claim that gets made loosely. Let me ground it properly.
How common are cost overruns in Indian construction?
Multiple independent assessments consistently find that 60–80% of Indian construction and infrastructure projects experience cost overruns. The McKinsey Global Institute's 2017 global infrastructure analysis found 80% of large infrastructure projects come in over budget globally, with India performing worse on government infrastructure. The Comptroller and Auditor General of India's audit reports on Central Public Works Department and National Highways Authority of India projects document systematic overruns of 20% to 100% above original values. The KPMG India Project Management Survey places the figure at 60–70% for commercial and industrial projects. The range — 60% to 80% — reflects different project types: infrastructure and government projects sit at the higher end; well-managed private sector commercial projects can be lower.
Sources: McKinsey Global Institute "Reinventing Construction" (2017); CAG Reports on NHAI and CPWD (2018–2023); KPMG India Project Management Surveys (2016–2022).
What the aggregate statistic obscures is the distribution. A 20% cost overrun on a ₹5 Cr residential project is ₹1 Cr — painful but survivable for a developer. A 20% cost overrun on a ₹200 Cr infrastructure contract is ₹40 Cr — potentially company-ending for an MSME contractor whose entire working capital position is that project. The Indian construction MSME sector is dominated by companies in the ₹30–300 Cr annual turnover range, for whom a single significant cost overrun can destroy several years of margin and often does.
The Comptroller and Auditor General's reports on Central Public Works Department institutional projects (hospitals, universities, government buildings) routinely document overruns of 30–60% above original contract values. The causes named in those reports are identical to the causes named in this guide — they are the same failure patterns, documented by a government auditor across hundreds of projects over decades. They are not new, and they are not unavoidable.
The five specific causes of construction cost overruns in India
The five most common causes: (1) Scope creep without timely pricing — design changes and variations added after the Bill of Quantities is signed, unpriced until project end, becoming disputes; (2) Bill of Quantities errors discovered after mobilisation — quantities prove wrong after work begins, requiring additional procurement not in original budget; (3) Material price escalation — cement, steel, and bitumen volatility during the project, particularly on contracts without adequate price variation clauses; (4) Procurement inefficiency — sub-optimal purchase order timing and quantity, emergency procurement at premium rates when materials run short; (5) Contractor underperformance requiring acceleration — contractor delay forces injection of additional resources, overtime, and multiple-shift working at rates above the original programme. Each of these is detectable in advance. All five show up in the Cost Performance Index before they show up in the project accounts. Sources: PMBOK 7th Edition; CPWD GCC clauses 7 and 14; IS 15883 Part 1.
Sources: PMBOK 7th Edition (Risk Management Domains, Cost Control); CPWD GCC clauses 7 and 14; CAG infrastructure audit reports; IS 15883 Part 1.
-
Scope creep without timely pricing
The most common cause by volume. An architect changes the flooring specification from vitrified tiles to natural stone. The structural engineer adds a retaining wall to the drawings that was not in the original Bill of Quantities. The client verbally approves a partition layout change on a site visit. Each change is implemented because the project needs to move forward. The formal variation order with an agreed price is not raised because it takes time and creates a conversation nobody wants to have. By the time the project is 80% complete, there are ₹2–4 Cr of unpriced variations on a ₹25 Cr project — and the contractor and client both have different views of what those variations are worth. This is not a dispute. It is a cost overrun that was preventable at the point of each change.
-
Bill of Quantities errors discovered after mobilisation
The Bill of Quantities was prepared in 4–5 days from drawings that turned out to have been revised the previous week. The reinforcement steel quantities were measured from the architectural drawings rather than the structural drawings. The MEP scope was not captured at all because the MEP drawings were not issued at tender stage. None of this is discovered until the contractor begins procurement and realises the quantities on order will not cover the actual scope of work. The additional procurement is unbudgeted. The cost overrun is already 8% of contract value before foundation work is complete.
-
Material price escalation on multi-year contracts
A ₹80 Cr infrastructure project with a 3-year programme signed in January 2022 used cement and steel rates from the 2022 base date. By mid-2022, cement prices had risen 15% and steel had risen 25% in many markets. On contracts without a price variation clause, or where the clause applied only above a 20% escalation threshold (when actual escalation was 15%), the contractor absorbed the difference. On a ₹80 Cr project with 40% material content, a 15% escalation = ₹4.8 Cr additional cost not in the contract budget.
-
Procurement inefficiency — emergency buying at premium rates
A contractor running a ₹45 Cr institutional building discovers at the 60% completion stage that the aluminium windows and glazing package — which represents ₹3.5 Cr of the contract value — was never properly tendered. The site programme requires delivery in 6 weeks. The tender process that would have produced competitive pricing takes 8–10 weeks. The contractor buys from the only vendor who can deliver in 6 weeks, at a 12–18% premium. The procurement failure that caused this was visible 4 months earlier in the purchase order status report — no PO raised for a major package with a 16-week lead time.
-
Contractor underperformance requiring acceleration
The structural contractor for a ₹60 Cr residential complex is running 3 months behind programme by the time the developer notices — because the only progress tracking mechanism is a monthly site visit and a verbal update. The developer has a Real Estate Regulatory Authority (RERA) possession date commitment to 200 buyers. Acceleration requires running three shifts, Saturday overtime, and a second structural contractor brought in to work in parallel. The additional cost is ₹1.8 Cr. None of it was in the original programme. All of it was predictable from the Schedule Performance Index data that was never calculated.
How Bill of Quantities variations cause cost overruns in Indian construction contracts
Under CPWD General Conditions of Contract clause 14 and FIDIC Silver Book clause 13, contractors are entitled to additional payment for variations — extra work not in the original scope. The cost overrun risk arises when: variations are verbally instructed and implemented before a formal order is issued with an agreed price; cumulative variations exceed the Bill of Quantities contingency (typically 5–10% of contract value); the contractor prices variations using original Bill of Quantities rates which may not reflect the actual cost of changed scope; or disputes arise over whether an item is a variation or part of original scope. On a ₹30 Cr project, variations totalling 15–20% of original Bill of Quantities value — ₹4.5 to ₹6 Cr — are common when design development continues during construction. Managing each change with a contemporaneous written instruction and agreed variation order converts a potential overrun into a managed cost increase. Sources: CPWD GCC clause 14; FIDIC Silver Book clause 13; IS 15883 Part 1.
Sources: CPWD GCC clause 14 (Additions and Alterations to the Work); FIDIC Silver Book (2017) clause 13 (Variations and Adjustments); IS 15883 Part 1 (Project Management Guidelines for Construction).
How Earned Value Management detects cost overruns before they become irreversible
Earned Value Management integrates scope, schedule, and cost into one measurement: Cost Performance Index = Earned Value ÷ Actual Cost. A Cost Performance Index of 0.93 means the project is spending ₹100 to complete ₹93 of work — a 7% overrun already running. On a ₹20 Cr project this is ₹1.4 Cr overrun visible in month 4. The critical PMI research finding: a Cost Performance Index established by the end of 20% of project duration rarely changes by more than 10% at completion. A project with a Cost Performance Index of 0.88 in month 4 of a 20-month programme will almost certainly finish between 10% and 20% over budget. This is the early warning signal that most Indian MSME contractors never calculate — because cost tracking and progress tracking live in different systems, different teams, and different update cycles. VentureVitals connects procurement purchase order data (Actual Cost proxy) and site progress tracking (percentage complete) in the same system, calculating the Cost Performance Index continuously. Sources: PMBOK 7th Edition (section 4.5); PMI Practice Standard for Earned Value Management (2011); IS 15883 Part 1.
Sources: PMBOK 7th Edition (Section 4.5 — Earned Value Management); PMI Practice Standard for Earned Value Management, 2nd Edition (2011); IS 15883 Part 1.
The power of the Cost Performance Index is not that it tells you something you don't know. A site manager who has been running a project for 4 months knows something is not right. The Cost Performance Index tells you precisely how not right — in rupees, with a projection of where the project is heading if nothing changes.
Consider two scenarios on the same ₹20 Cr project at month 4:
Scenario A (no data): The site manager says things are "a bit behind but we'll catch up." The project director says costs are "running a little over but it'll even out." Nobody has a number. Month 8 arrives, the client requests a cost-to-complete estimate, and the contractor prepares one for the first time — showing a ₹3 Cr overrun. The client is angry. The options are limited.
Scenario B (Cost Performance Index = 0.93 in month 4): The Estimate at Completion = ₹20 Cr ÷ 0.93 = ₹21.5 Cr. The project director knows today that the project is heading for a ₹1.5 Cr overrun unless corrective action is taken. Three actions are possible right now that reduce the overrun: formalise all uninstructed variations (potentially recovering ₹80–100 lakh), rebid the remaining materials packages where prices have softened (potentially recovering ₹40–60 lakh), and issue a formal performance notice to the underperforming subcontractor while there is still time to correct performance without premium acceleration costs. The decision window is open. In Scenario A, it closed in month 6 without anyone noticing.
Can a construction project recover from a cost overrun once it has started?
Recovery is possible but becomes progressively harder as the project advances. The Cost Performance Index established by 20% of project duration defines the window: early in the project, corrections are still possible. The recovery levers: (1) scope reduction — removing or deferring non-critical scope with client agreement; (2) procurement renegotiation — rebidding key material packages where prices have softened; (3) productivity improvement — correcting contractor underperformance through formal performance notices and subcontractor changes; (4) variation recovery — formalising and pricing unpriced variations already performed, recovering cost through legitimate contract mechanism rather than absorbing it as a loss. The last lever is most valuable and most neglected: a ₹30 Cr project with ₹3 Cr of verbally approved, unpriced variations has a legitimate contract claim that can recover most of the apparent overrun — if the variations were documented contemporaneously. Sources: PMBOK 7th Edition; CPWD GCC clause 14; FIDIC Silver Book clause 13.
Sources: PMBOK 7th Edition (Cost Control, Integrated Change Control); CPWD GCC clause 14; FIDIC Silver Book (2017) clause 13; IS 15883 Part 1.
See your project's current Cost Performance Index and Estimate at Completion in 20 minutes. Bring your contract value, current completion percentage, and actual expenditure to date.
Book a 20-minute project cost health walkthrough →Or calculate it yourself now: Free Cost Performance Index and Schedule Performance Index Calculator →
Related reading
For construction company CEOs: managing cost overrun exposure across a 5–50 project portfolio