I did a poll on Patreon about cost issues to write about. This is a close second, with 11 votes; other people’s money won with 12, whereas neighborhood empowerment got 8 and will not be on my docket.
There are infrastructure investment programs defined around the specific projects funded: Crossrail, Second Avenue Subway, Grand Paris Express, Nya Tunnelbanan, the Toronto RER, Marmaray. Then there are programs defined around costs, where one constantly hears the project defined by its budget rather than what it produces; these are all in the United States, and include the entire slates of Los Angeles and Seattle rail extensions, and to some extent also California High-Speed Rail and Gateway. The latter appears like bad practice for cost minimization.
What’s the problem?
In isolation, I’d have expected cost-centric plans to be more prudent with the budget – there’s less room for overruns. This is related to Swiss practice, which is project-centric but also requires projects to go to referendum on the precise amount, which has disciplined cost overruns in most cases and also kept absolute costs low. However, the fact of the matter is that the only places that use cost-centric plans have high costs, having recently risen from levels that were not so bad 20 years ago. So why?
My suspicion is leakage. This is getting to be less general and more specific to the situation of California and its sales tax measures, but the way it works is, there is an amount that proponents think they can go to ballot on, and then they work the slate of projects backward. In theory, this is supposed to discipline the planners into better behavior: the amount of money is truly fixed, and if costs go up, it delays the entire program. In practice, there is no prior discipline about what infrastructure should be included, and thus the slate is decided politically on a place-based plan.
Further leakage occurs when buying off additional interest groups. Soon enough, one useful if very expensive subway line, like the Purple Line Extension in Los Angeles or the Ballard-West Seattle LRT, is bundled into a huge program alongside bus operating subsidies, road money, and low-usage lines to lower-density areas.
I can’t prove that this is the result of budget-centric planning. The comparison examples I have – all high-cost, politicized North American projects – exhibit leakage as well, but less of it. The Green Line Extension in Boston had extensive local leakage in the first iteration of the project, like the Somerville Community Path, but it wasn’t paired with less useful infrastructure elsewhere. Second Avenue Subway Phase 1 was paired with East Side Access and the Broadway subway in Vancouver is paired with a SkyTrain extension deeper into Surrey toward Langley; in both cases, the less useful projects are nonetheless more useful on a likely cost per rider basis than any of the American West Coast leakage and compete with the more useful projects. ESA is probably going to end up $60,000/rider, not much worse than GLX and probably about the same as the Purple Line Extension depending on how much transit-oriented development Los Angeles permits.
Place-based politics is a scourge and should be eradicated whenever possible. What it does wherever it is not suppressed is create political identification among local and regional power brokers not with the piece of infrastructure but its cost. The reason is that evaluating transportation needs is too technocratic for the attention span of a local politician, whereas the budget is a straightforward measure of one’s importance.
Once local actors are empowered, they make further demands for irrelevant extras (“betterments”), or construction techniques that spend too much money to avoid real or imagined negative local impact. People with a local identity don’t care about public transit much – public transit takes riders to other localities, especially city center, whereas the locally-empowered minority of people who work locally has little use for it and drives everywhere.
Local empowerment is not unique to budget-based infrastructure. It was a major drag on GLX and at least a moderate one on SAS Phase 1, neither of which is budget-based. The Central Subway and BART to San Jose projects are both place-based vanity, for Chinatown and San Jose respectively, but even these projects are smaller in scope than the Los Angeles or Seattle ST3 leakage. There’s just more surface area for it when advocates lead with a budget, because then every local hack sees an opportunity to make a claim.
The place-based politics in the Northeast is much broader and more regional: SAS, a city project championed by then-Assembly speaker Sheldon Silver (D-Lower East Side), was balanced with ESA, a suburban project serving the base of Governor George Pataki (R-Peekskill, but the state Republicans were based on Long Island). Metro Vancouver’s place-based extraction follows the same schema: if Vancouver gets a useful SkyTrain extension, Surrey must get an extension too regardless of usefulness. Massachusetts is likely to be in a similar situation with the TransitMatters Regional Rail program: RR serves the entire east of the state, and must be balanced with a Western Massachusetts project, for which we propose the still-useful East-West Rail program connecting Boston and Springfield.
In contrast, the situation in California and metropolitan Seattle is much worse – useful lines in Los Angeles are paired with many layers of leakage, as different groups make claims on the pot of money. This way, Los Angeles doesn’t build as much useful transit as New York and Boston even though its construction costs are comparable to Boston’s and much lower than those of New York, and even though it makes large amounts of money available for transportation by referendum.
Are jobs a cost or benefit?
Like place-based extraction, the use of infrastructure as a jobs program is terrible everywhere in a modern developed country where construction is not a labor-intensive zero-skill job, and should be eradicated. And like place-based extraction, I think – and am less certain than on the other points – there is more surface area for this when the program is about a budget and not a piece of infrastructure.
The mechanism is the same as before: once money becomes available, local labor groups descend on it to make claims. Promises of job creation are thus always local, including beggar-thy-neighboring-state demands for local rolling stock construction. These occur for both budget-based plans (like the Los Angeles light rail fleet) and project-based ones (like the new Red and Orange Line cars for Boston, built in Springfield due to place-based extraction). However, it’s easier to make a claim when the political discussion is about how to spend $X and not how to optimally produce a desired piece of infrastructure.
The way forward
The American West Coast’s problem of budget-based planning is, thankfully, easy to solve, because it’s been solved in other parts of the same country. The Bay Area has less of it than Southern California and the Pacific Northwest (but it’s not free of it – many of the specifics of California High-Speed Rail’s failure come from Bay Area power brokers hoping to use it as a slush fund). The Northeast doesn’t have it at all. Los Angeles is likely to be forced in that direction anyway, because it’s running out of sales tax capacity – the already-approved measures are spoken for through the 2050s.
The impact is likely not a matter of straight construction costs in dollars per kilometer. Rather, it’s about leakage. Los Angeles and Seattle do not have unusually higher per-km costs by American standards; in the 2000s Los Angeles looked like the good part of America and in the 2010s Seattle did, but since both have converged to much higher figures. The problem is that a smaller share of the Los Angeles Measures R and M spending goes to useful expansion than the capital budget in places that have project-based planning. This is what needs to be fixed through transitioning to project-based planning, costs aside.