13 Bridges in 18 Days: What Bihar's Collapse Crisis Teaches Every Project Manager

Between June and July 2024, Bihar witnessed 13 bridge collapses in 18 days. Not 13 near-misses. Not 13 structural warnings. Thirteen actual collapses - some mid-construction, some decades old, all captured on camera.

The government's response was quick: 15 engineers were suspended, a contractor was blacklisted, and an investigation was ordered. And then, in 2025, the Agwani-Sultanganj bridge, already infamous for collapsing in 2022 and again in 2023, collapsed a third time. The same contractor. The same river. The same reason about unexpected river surges.

This isn’t just Bihar’s tale. This is what happens when project management fails everywhere, all at once. The real question: how do you make sure your project doesn’t end up as the next cautionary tale?

Quality was never a control point - it was a conversation

Experts cited sub-standard materials, incorrect cement-to-steel ratios, and the absence of quality inspection at any stage. Locals blamed contractors and engineers for using low-quality materials. The government blamed Himalayan water surges. Both things can be true, and that is where the problem lies.

If your quality checks are 'we trust the contractor,' you don’t have quality assurance. You have wishful optimism with a signature at the bottom. Real project managers set up quality gates, actual checkpoints, with proof, not just a nod or a WhatsApp update. Evidence, or it didn’t happen.

Accountability was distributed so widely that it belonged to nobody

In Bihar, files vanished. Ministers shrugged and said they couldn’t find project records for months. An engineer got suspended for paying a blacklisted contractor. When pressed, officials blamed 'external factors' for the failures.

This is what happens when accountability is spread so thin, it disappears. The more names on the list, the less anyone actually owns the outcome. In project management, we call this a RACI breakdown. It’s the silent killer of projects. Never written in the post-mortem, because everyone’s too busy pointing fingers.

Risk was catalogued, not managed

Bihar is the most flood-prone state in India. 73% of its geographical area gets affected. Building bridges over the Ganga river during the monsoon is, by definition, a high-risk build. None of this was unknown; it was just background noise.

A risk register gets filled out once and is forgotten; it is just paperwork. Risks aren’t managed because they’re in a spreadsheet. They’re managed when someone owns them, has the power to act, and checks reality - again and again.

The project schedule was fictional

A bridge scheduled for completion in 2019 is still unfinished in 2025 and has collapsed three times. At what point should someone have escalated this? Should the project have been formally reviewed, replanned, or terminated?

Delays, when not formally acknowledged and replanned, compound silently. Teams slip on timelines. Stakeholders stop asking hard questions. The schedule becomes a document to satisfy reporting requirements rather than to guide execution.

This is evident in India's infrastructure at scale: according to the December 2023 report by India's Ministry of Statistics and Programme Implementation, 431 central government projects had a combined cost overrun of ₹4.82 lakh crore, with 36% of projects delayed by 25 to 60 months.

Lessons were never institutionalised

The same contractor. The same location. Three collapses. If a project review was made at any level, the second collapse would have triggered a root-cause review, making the third structurally impossible. Instead, each collapse was treated as an isolated incident, and the system learned nothing.

What this means for your projects

Bihar’s bridges are the headlines in project management.

Your project probably won’t collapse into a river. But the same patterns are seen at work:

• Quality checks exist on paper but not in practice

• Accountability spread thin enough that critical decisions fall through gaps

• Risk registers that become history within weeks of being written

• Schedules that are renegotiated quietly rather than formally managed

• Post-mortems that produce reports, not changes

Each of these failures is avoidable. Not with another tool or another meeting. But with real project management: clear ownership, actual checkpoints, honest reporting, and escalating when things go sideways.

Want to manage projects the way this should have been managed?

The Center of Applied Project Management's certification programs are built around real-world application - not just theory.

Start with the free Project Management Fundamentals course and see what rigorous practice actually looks like.