Buried Numbers: How Municipal Asset Records Conceal the True Cost of Neglected Infrastructure
Photo: Danielteolijr, CC BY-SA 4.0, via Wikimedia Commons
Every American city maintains some version of an asset management system—a database, spreadsheet, or software platform cataloging the condition of public infrastructure: roads, bridges, water mains, stormwater systems, municipal buildings, and everything in between. In theory, these systems exist to help city administrators prioritize spending and plan for the future. In practice, they frequently serve a second, less acknowledged purpose: managing appearances.
The gap between what a city's infrastructure actually costs to maintain and what officials are willing to publicly acknowledge has grown into one of the most consequential blind spots in local governance. Understanding how that gap is created—and how residents can close it—is essential civic work.
The Architecture of Underreporting
Municipal asset management systems are not inherently deceptive. The problem lies in how cities choose to populate, classify, and present the data they contain.
One of the most common techniques involves condition rating inflation. Most systems use a numerical scale to assess the state of a given asset—a bridge, for instance, might be rated on a scale from one to five, with one representing critical failure and five representing excellent condition. When budget cycles arrive, departments under fiscal pressure have strong incentives to rate assets slightly higher than their actual condition warrants. A bridge that engineers privately acknowledge as a three gets logged as a four. Multiplied across thousands of assets, these incremental adjustments can shave hundreds of millions of dollars off a city's reported maintenance backlog.
A related technique is selective asset enrollment—simply choosing not to include certain categories of infrastructure in the official database. Alleyways, smaller pedestrian bridges, aging municipal facilities, and secondary drainage infrastructure frequently fall into this gap. If an asset is not in the system, its deterioration generates no backlog figure, no budget pressure, and no public accountability.
Finally, cities frequently manipulate the definition of what constitutes a "maintenance" expense versus a "capital" expense. When a repair is reclassified as a capital project, it migrates off the maintenance backlog entirely—even if the underlying asset has been deteriorating for years and the reclassification was driven more by accounting convenience than engineering judgment.
Why This Matters Beyond the Balance Sheet
The consequences of hidden maintenance backlogs are not abstract. When deferred maintenance on a water main finally results in a rupture, the emergency repair cost is typically three to five times what preventive maintenance would have required. When a structurally deficient bridge requires emergency closure, the economic disruption to surrounding neighborhoods can persist for years. When a municipal building's roof is allowed to fail, the resulting interior damage cascades into costs that dwarf the original repair.
Beyond direct costs, concealed backlogs undermine the integrity of the budget process itself. City councils cannot make sound appropriations decisions when the maintenance picture presented to them is systematically optimistic. Residents cannot advocate for adequate infrastructure funding when they have no reliable baseline from which to argue. Bond rating agencies, which increasingly scrutinize infrastructure liability disclosures, are beginning to take notice—and some cities have faced credit downgrades partly attributable to the eventual surfacing of long-concealed deferred maintenance obligations.
What Transparent Asset Management Actually Looks Like
A handful of cities have moved toward genuinely transparent infrastructure accounting, and their approaches offer a useful benchmark for what residents should be demanding.
Charlotte, North Carolina, publishes a detailed infrastructure condition report as part of its annual budget documentation, breaking down backlog figures by asset category and explaining the methodology used to assign condition ratings. Denver has integrated its asset management data with its open data portal, allowing residents and journalists to query infrastructure records directly. Several cities participating in the Government Finance Officers Association's infrastructure transparency initiatives have adopted standardized condition rating methodologies that reduce the discretion available to individual departments.
These examples are instructive not because they represent perfection, but because they demonstrate that transparency is operationally feasible. The cities that resist it are not doing so because disclosure is technically difficult.
How Residents Can Access the Real Numbers
For residents in cities that have not voluntarily embraced infrastructure transparency, the path to accurate information runs primarily through public records law.
Request the underlying asset inventory, not the summary report. Most cities publish some version of an infrastructure condition summary—a glossy document with aggregate figures and reassuring language. The useful records are the raw asset inventory files: the actual database exports, inspection logs, and condition rating worksheets that underlie the summary. Submit a public records request specifically for these materials, naming the software platform your city uses if you can identify it (common systems include Cartegraph, IBM Maximo, and Cityworks).
Ask for the backlog calculation methodology. A maintenance backlog figure is only meaningful if you understand how it was derived. Request documentation explaining how your city defines a maintenance backlog, what condition threshold triggers inclusion, and how assets are enrolled in or excluded from the system. Discrepancies between the stated methodology and the actual data can be revealing.
Cross-reference against inspection records. Bridge inspection reports are federally mandated and publicly available through the National Bridge Inventory database maintained by the Federal Highway Administration. Comparing federal inspection ratings against a city's own reported condition ratings for the same structures can surface systematic inflation.
Engage the city auditor's office. Many municipal auditors have standing authority to examine asset management practices, and a formal request for an infrastructure audit—particularly if supported by multiple residents or a neighborhood organization—can carry significant weight. Audit findings are typically public documents and can generate press attention that accelerates corrective action.
Connect with local journalists and university researchers. Civil engineering faculty at regional universities often have both the technical expertise to interpret infrastructure records and the professional interest to do so. Investigative reporters at local news outlets are increasingly equipped to analyze data-heavy public records. Partnerships between engaged residents, technical experts, and journalists have produced some of the most consequential infrastructure accountability stories of the past decade.
The Broader Principle
Infrastructure maintenance is not a glamorous subject. It generates none of the political excitement of a new development project or a high-profile budget initiative. That relative obscurity is precisely what makes it vulnerable to the kind of quiet manipulation described here.
Cities that hide their maintenance backlogs are not simply managing optics. They are making a choice to defer costs onto future residents, future councils, and future budgets—while allowing the physical fabric of the community to deteriorate in ways that are invisible until they are catastrophic. Residents who treat infrastructure data as a legitimate object of civic scrutiny, and who use the legal tools available to them to demand accurate disclosure, are performing some of the most consequential accountability work available at the local level.
The numbers are there. They are just waiting to be asked for.