India’s central infrastructure pipeline has grown nearly fourfold since 2014, and MoSPI’s PAIMANA portal now tracks close to 2,000 projects worth over Rs 42 lakh crore. On paper, that’s a monitoring success story: monthly flash reports, sector-wise breakdowns, physical and financial progress percentages, all publicly available.
But there’s a quiet shift buried in the reporting. Older versions of this data explicitly flagged how many projects were “delayed” and by how many months. The current reports have moved away from that framing, choosing instead to highlight completion percentages — how far along a project is, not whether it’s behind schedule. A project sitting at 60% physical progress can look healthy in a dashboard even if it was supposed to be finished two years ago.
The cost side tells its own story. Sanctioned costs have risen by lakhs of crores against original estimates, standard territory for what used to be called “cost overruns” before that language quietly dropped out too. Progress by rupees spent doesn’t always match progress on the ground — a project can show high financial completion while physical construction lags, which is often a sign of front-loaded spending rather than actual execution speed.
Why projects actually slip — and it’s rarely one thing:
- Land acquisition — still the single most cited delay driver in infrastructure reporting, year after year.
- Forest and environmental clearances — sequential approvals that stall execution long before a shovel hits the ground.
- Financing gaps — delays in tying up project funding or in releasing sanctioned funds.
- Engineering and design delays — detailed engineering finalized after construction has technically “started.”
- Tendering and procurement — slow ordering and equipment supply cycles.
- Contractual and scope issues — change in scope mid-project, contractor disputes, geological surprises.
None of these are exotic. They’re the same handful of causes that have shown up in project monitoring reports for over a decade. What’s changed is not the reasons projects fall behind — it’s how visible that fact is in the data the public sees.
Why this matters for anyone running a project, not just the government’s. The instinct to report “percentage complete” instead of “days behind schedule” isn’t unique to ministries — it’s a common failure mode in construction reporting everywhere. Progress metrics that don’t reference the original timeline aren’t progress metrics; they’re vanity metrics. A project can be 80% complete and still be a failure if it was supposed to be 100% complete eight months ago.
At Greywork, this is exactly the gap we build for: decision-making that’s tied to real schedules and real cost baselines, not just stage-of-completion snapshots. Construction decisions at the speed of compute means catching the slip while it’s still a few weeks, not a few years.
Note: The data in Flash Reports now often lags slightly behind data on the PAIMANA portal, which is updated in real time by many ministries, which explains why some recent media reports based on the live portal cite 1,981 projects with a revised cost of Rs 42.78 lakh crore. The PAIMANA archive of older Flash Reports, maintained separately for reasons unknown, is here.
Leave a comment