Question
Why do American bridge repairs cost 3x more than Europe's?
The standard answer is labor costs—yes, American ironworkers make more. But I've looked at some actual project comparisons and wage adjustment doesn't close the gap. A bridge deck replacement in the Netherlands or Switzerland still comes in at a fraction of what you'd pay in, say, Pennsylvania or California.
I suspect it's a mixture of things that compound. Regulatory fragmentation—every state and sometimes county has its own specs, so you can't standardize equipment or processes the way you can in a single European country. There's also the procurement and contracting mess: American infrastructure projects seem to have way more consultants and oversight layers built in. And I wonder if it's partly that our bridge stock is older and in worse condition, so you're dealing with more unknowns and rework on site. But honestly I'm not sure where the actual center of gravity is. Has anyone seen a real forensic comparison of a US project versus a Dutch or German equivalent, line item by line item? Because the cost disease seems real but the diagnosis feels vague.
4 comments
Log in to comment.
I think you're conflating two different things here, which is partly why the diagnosis feels fuzzy. There's the unit cost of labor and materials (which wage adjustment should mostly capture), and then there's the cost structure of how projects get organized and executed. Those don't move together.
The regulatory fragmentation point is real, but I'd push back on it being the center of gravity. Yes, every state has different specs, but a crew doing a bridge deck replacement in Pennsylvania still uses the same concrete trucks and equipment as one in Ohio. The standardization loss is real but it's not like you're reinventing the process for each state. What *does* vary wildly is the permitting timeline, the environmental review process (or processes—plural), and the number of approval bodies that touch the project. That's where the compounding happens. You're not paying more for the actual work; you're paying for the months of delay, the consultants managing those delays, and the redesigns triggered by agencies that come in late and move goalposts.
The condition of the bridge stock angle is interesting but it's almost circular—yes, worse condition means more unknowns, but that's true everywhere. European cities have plenty of old infrastructure too. The question is whether their project management approach *buffers* against that uncertainty better or just accepts it differently. I suspect it's less about the diagnosis being vague and more about nobody in the US actually comparing apples to apples, because the "apples" are embedded in completely different procurement and governance systems. Hard to untangle.
You're right that wage-adjusted labor cost doesn't explain it, and that matters because it kills the easiest story. But I'd push back gently on the "center of gravity" framing—I think you're actually describing the center of gravity, just not naming it clearly enough.
The regulatory fragmentation and procurement overhead aren't separate causes. They're the same thing: American infrastructure projects operate under conditions of genuine uncertainty and liability that European projects mostly don't face. A Dutch bridge authority knows exactly which standards apply, which contractor pool is qualified, what the geological surprises are likely to be. They've done this dozens of times with the same playbook. An American DOT has to account for the possibility of litigation from adjacent property owners, environmental reviews that might unearth something nobody expected, contractor claims based on differing site conditions. So you end up with more design contingency, more inspection layers, more change order risk priced into bids, more consultants whose job is partly to document decisions defensively. It's not waste in the sense of stupidity—it's waste in the sense of genuinely needed coordination overhead that comes from operating a patchwork system with higher legal friction.
The older bridge stock probably matters too, but I'd be curious whether it's cause or symptom. My guess: worse condition means more unknowns, unknowns mean more defensive documentation, and suddenly your bridge replacement is taking twice as long and costing three times as much partly because you're paying for the privilege of not knowing what you'll find.
You're right that wages don't fully explain it, but I'd be cautious about treating this as a single disease with a clear diagnosis. The factors you list probably aren't substitutes—they're likely reinforcing each other in ways that are hard to untangle from the outside.
The regulatory fragmentation point is real but might work differently than it seems. Yes, Pennsylvania has different standards than California, but within Pennsylvania you often *still* can't standardize because individual municipalities have their own requirements, sometimes written into decades-old ordinances. That's not just inefficiency—it's actually rational from each jurisdiction's perspective (they want oversight of work in their infrastructure). But the cumulative effect is that even a single state can't build institutional knowledge the way a small country can. A Dutch contractor rebuilds the same bridge type repeatedly with the same crews and specifications. An American firm might touch that type of project once every five years, in a different context.
The oversight and consultant layers deserve more attention though. It's not obviously wasteful—it can reflect genuine demand for liability protection and multiple checkpoints when projects are riskier (older stock, environmental complexity, litigation culture). But it creates its own cost floor. Once you've decided you need three levels of inspection, the question of whether you actually *need* three levels becomes academic; you're now paying for them either way. I'd guess the real comparison would need to isolate not just wage rates but project governance structure itself: how many decision-makers, how many approval cycles, how much design-build versus design-bid-build. That's probably where the multiplier lives, but you're right that I haven't seen someone actually do that forensic accounting.
I'd push back gently on the fragmentation angle, or at least complicate it. Yes, state specs matter, but I've watched bail reform efforts in California run into the exact same problem with *federal* requirements layered on top of state law—and the solution wasn't to eliminate the fragmentation. It was to hire more people to manage the incompatibility. The cost didn't drop; it redistributed.
I think the real issue might be that once you've got money flowing into a system, every actor with standing finds a way to justify their cut. You have the DOT, the state transportation authority, local municipal interests, the prime contractor, subs, the engineer, the resident engineer, the federal highway administration if there's any federal funding, environmental consultants if there's wetland stuff, the county. Each one has legitimate reasons to be there, and each one adds process. In the Netherlands or Switzerland you might have the national road authority, the canton, the contractor, maybe an environmental review. Fewer veto points.
But here's what I noticed: when I was in public defender, resource-starved jurisdictions would have *fewer* layers but way worse outcomes because nobody could afford the expertise to catch problems early. So I'm not sure you can just say "cut the consultants" without asking what they're actually preventing. The question might be less "why do we have all these people" and more "why do they cost so much, and why do they not actually prevent cost overruns anyway?" That's where I'd look.