Submitted and Forgotten: How Street Damage Reporting Apps Are Designed to Disappoint

When Maria Delgado photographed the same crater-sized pothole on her block in Columbus, Ohio, three times over eight months — each time submitting a report through the city's official mobile app — she expected at least an acknowledgment. What she received was a status update that read "Under Review" for 241 days before the ticket quietly closed without explanation or repair.

"I started keeping a spreadsheet," Delgado said. "Dates, ticket numbers, screenshots of the status. After the third one disappeared, I realized the app wasn't a reporting tool. It was a complaints folder no one was reading."

Delgado's experience is neither unusual nor accidental. Across the United States, municipal street-damage reporting platforms — many of them built on the same handful of vendor frameworks — exhibit strikingly similar patterns: low closure rates, unexplained status resets, duplicate-detection logic that discards legitimate follow-up reports, and geographic filtering that quietly deprioritizes requests from lower-income neighborhoods.

The Architecture of Inaction

Most residents assume that a city's reporting app is a direct pipeline to a public works dispatcher. In practice, the pathway is considerably more indirect. Submissions typically flow into a customer relationship management system — often a commercial platform like Salesforce Government Cloud or a proprietary vendor product — where they are sorted, scored, and queued according to criteria that are rarely disclosed to the public.

Those criteria can include the reported defect's proximity to a pre-designated "high-priority corridor," the volume of duplicate reports from the same location (which can paradoxically trigger automatic suppression rather than escalation), and the age of the complaint relative to available budget cycles.

Dr. Kevin Marsh, a public administration researcher at the University of Michigan who has studied 311-adjacent service request systems in 40 cities, describes the design philosophy as one of "managed demand."

"These platforms were not primarily engineered for responsiveness," Marsh explained. "They were engineered to give residents a sense of participation while managing the volume of actionable requests that actually reach operations staff. The user experience is the product. The repair is secondary."

That framing may sound cynical, but it aligns with findings from a 2023 analysis of service request data published by the Sunlight Foundation, which found that in 14 major cities, street-damage tickets submitted through official apps had a 60-day closure rate of just 22 percent — compared to a 47 percent closure rate for requests that originated through direct phone calls to public works departments.

How Duplicate Detection Becomes a Suppression Tool

One of the most consequential — and least discussed — design choices in modern reporting platforms is the duplicate-detection algorithm. Ostensibly, these systems exist to prevent the same pothole from generating hundreds of separate work orders. In practice, they can function as a mechanism to cap official complaint counts.

In several cities, residents have discovered that submitting a follow-up report on an unresolved defect triggers the new submission to be merged into the original ticket rather than logged as a separate request. The original ticket's timestamp does not update. Its priority score does not change. The follow-up effectively disappears.

Luis Herrera, a software engineer and civic technology advocate in Phoenix, reverse-engineered the submission flow of his city's reporting tool after noticing this pattern.

"The duplicate radius in Phoenix's system was set to 150 feet," Herrera said. "Any report submitted within that radius of an existing open ticket gets auto-merged, regardless of whether it's the same defect or a different one, regardless of how old the original ticket is. A ticket from 2021 was still eating new reports in 2024."

Herrera published his findings on a local civic technology forum. Within days, dozens of residents shared similar experiences, and a local television station picked up the story. The city subsequently confirmed the radius setting and announced a review — though no timeline for changes was provided.

Geographic Patterns in Request Processing

Beyond individual ticket suppression, researchers and resident advocates have documented broader geographic disparities in how street-damage reports are processed. In multiple cities, analysis of publicly available 311 data has revealed that requests originating in predominantly lower-income ZIP codes take measurably longer to close than those from wealthier areas, even after controlling for defect severity.

A 2022 study of Chicago's 311 data conducted by researchers at DePaul University found that pothole repair requests in the city's lowest-income quartile of census tracts took an average of 18.4 days longer to close than equivalent requests in the highest-income quartile. The disparity held even when researchers limited the comparison to requests categorized as "high severity."

City officials in Chicago and other cities where similar analyses have been conducted typically attribute such gaps to logistical factors: crew routing efficiency, the concentration of infrastructure deficits in historically underinvested areas, and the limitations of available maintenance budgets. Critics argue those explanations, while partially valid, do not account for the full gap — and that algorithmic prioritization frameworks may be encoding existing inequities rather than correcting them.

What Transparent Systems Look Like

Not every city operates an opaque reporting environment. Several municipalities have made meaningful commitments to system transparency that offer a useful contrast.

Boston's Commonwealth Connect platform publishes real-time data on all open service requests, including timestamps for every status change, the assigned crew or department, and estimated completion windows. Residents can view requests from their neighbors, which creates informal accountability pressure and allows community members to identify patterns of neglect.

San Jose, California, implemented a public-facing dashboard in 2021 that displays aggregate closure rates by neighborhood, average response times by defect category, and the percentage of requests that exceed their target resolution window. The dashboard is updated weekly and is accessible without requiring an account.

"Transparency doesn't fix every pothole," acknowledged a San Jose public works communications manager who spoke on background. "But it does change the internal culture. When supervisors know residents can see closure rates by district, the data stops being just a management metric and starts being a public commitment."

Practical Steps for Residents

For residents who want their reports to carry more weight within existing systems, several strategies have proven more effective than standard app submissions.

First, supplementing app reports with a direct email to the public works department — and copying your city council representative — creates a paper trail that is harder to administratively absorb than a ticket in a queue. Second, referencing specific city code provisions that establish maintenance obligations in your communication elevates the request from a preference to a compliance matter. Third, coordinating with neighbors to submit concurrent reports through multiple channels (app, phone, and email) reduces the likelihood that duplicate-detection logic will suppress the volume of concern.

Finally, requesting your city's 311 or service request data through a public records request — most states require its disclosure — allows you to examine your own ticket history alongside citywide patterns. That data, shared publicly or with local journalists, has proven to be among the most effective catalysts for system reform.

The pothole on Maria Delgado's block in Columbus was ultimately repaired — not after any of her three app submissions, but after she sent a documented complaint to her council member's constituent services office with her spreadsheet attached.

"The app is theater," she said. "The real system is still the phone call and the elected official. They just built something shiny to make you forget that."