Why construction projects go over budget in India — and the three causes you can actually control

Cost overruns are the default outcome in construction, not the exception. India's own Ministry of Statistics and Programme Implementation (MoSPI) tracks central-sector infrastructure projects and has for years reported a large share of them running over their original cost — overruns that, across the monitored portfolio, run into lakhs of crores of rupees. Academic studies of Indian building and infrastructure projects echo the pattern: most projects, most of the time, finish for more than they were budgeted, and later than they were promised. The two overruns are usually the same event wearing two costumes, because time is money on a site running daily-wage labour and rented equipment.

The useful question isn't whether projects go over — it's why, and which of those causes a builder can actually put a system around. Researchers who survey Indian contractors, consultants and clients keep surfacing the same short list of dominant causes. Here is what the evidence consistently says, and then the three you can control.

What the research keeps finding

Study after study of construction cost and time overruns in India converges on a familiar set of top-ranked causes. Rankings differ by author and by project type, but the leaders barely move:

• Material price escalation and material delays. The rising cost of materials — steel and cement above all — and their late or short delivery is, in a large body of Indian research, the single most-cited driver of both cost and schedule overrun. A slab that can't pour because the TMT hasn't arrived costs twice: the idle day and, often, the premium paid to buy in a hurry.
• Slow decision-making and slow deployment of labour and resources. Crews that arrive late or in the wrong number, approvals that sit, and mobilisation that lags the plan repeatedly rank near the top. Labour on a site is a running meter; when it's idle or mis-sequenced, the money leaks whether or not anything gets built.
• Poor coordination between the parties. Owner, contractor, consultant and vendors working from different information — a stale drawing, an unanswered query, a change nobody logged — produces rework, and rework is pure overrun. Much of what looks like “bad luck” on a project is really a coordination failure that had a paper trail nobody was keeping.

Other causes recur too — design changes and scope creep, optimistic initial estimates, financing and payment delays, weather, and regulatory or land holdups. Some of those a small builder genuinely cannot control (a monsoon, a policy change, a client who keeps redesigning the kitchen). The list below is deliberately the opposite: the causes that are within reach.

You cannot control the price of steel. You can control whether you find out you're short of it four days before the pour or four minutes after the pump arrives. Most “overruns” are really late information.

Control #1 — Live material tracking against commitments

If material is the number-one cause, material visibility is the number-one lever. That means three numbers a builder should be able to see at any moment for a key material: what's on hand, what's committed (ordered but not delivered), and what upcoming work will consume. When those live on a system instead of in a storekeeper's head, a shortfall shows up days ahead as a purchase order, not on pour morning as a panic buy — and the early warning is also what lets you buy competitively instead of at a distress premium. Just as important, counting committed costs (open POs), not just paid ones, keeps the budget honest: it shows the real remaining headroom rather than a flattering number that ignores everything you've already promised to spend.

Control #2 — Attendance and labour deployment you can see

Idle or mis-timed labour is the overrun nobody photographs. The control is unglamorous: know who is actually on each work-front each day, verified rather than remembered, and match it against what the schedule said should be happening. Attendance that is captured on site — rather than reconstructed from a photographed register at month-end — does two things at once. It stops wage leakage (you pay for the crew that worked, not the crew that was claimed), and it tells you, while there's still time to act, whether a work-front is being starved of the hands it needs to stay on the critical path.

Control #3 — One system of record so coordination stops failing

Coordination failures are, at root, information failures: the drawing was stale, the query went unanswered, the change was never logged. The antidote is a single system of record where the current drawing, the tracked RFI, the logged change order and the daily site log all live in one place that every party reads from — instead of a dozen WhatsApp groups where the latest revision is buried above a hundred “ok sir” messages. When there is one version of the truth, rework from working off the wrong information simply has fewer places to hide. It also settles disputes later, because who-decided-what-and-when is on the record rather than in an argument.

There is a fourth control that sits underneath all three: knowing which delay actually threatens your handover date and which one has slack. That is the critical path, and it is worth understanding on its own — we walk through it on a real villa schedule.

The through-line

Notice that all three controllable causes reduce to the same thing: timely, shared information. Material shortfalls hurt when you learn of them late; labour leaks when attendance is a memory; coordination fails when everyone reads a different copy of the truth. A builder can't change the price of cement or the weather, but can decide to run the project on one live system of record instead of on lagging, scattered fragments — and that single decision touches the three causes that show up at the top of nearly every study of why Indian projects go over budget.

That's the whole case for putting a project on one system: what a construction ERP does for an Indian builder, in plain terms.