What Cities Actually Say When You Ask Them About Crash Response

After the sirens fade, the system starts to break down.

Strong Towns has been talking with cities across the country about the Crash Analysis Studio and what we’re hearing is illuminating.

When a fatal crash happens on a city street, the official response is almost always the same. First responders arrive. The scene is cleared. A police report is filed. The road reopens.

From the outside, this can look like the full response. It isn’t. In most cities, what follows is a slower, more deliberate process: a study is commissioned, a plan is developed, and a project is added to compete in a future funding cycle.

None of that is inherently wrong. In fact, many cities are doing serious, thoughtful work to improve safety. But after months of conversations with city staff across the country that included engineers, planners, public works directors and Vision Zero coordinators, it’s become clear that the core problem isn’t what happens immediately after a crash.

It’s what happens next.

Almost Every Conversation Starts the Same Way

“We already do this. We’ve been doing this for quite some time.”

That’s not defensiveness, it’s accurate. Cities pointed to annual hazard reports, high-injury network analyses, signal upgrades, pedestrian refuge islands, and a growing list of safety interventions. In Fort Smith, Arkansas, a public works director described a proactive program addressing dangerous intersections. In Columbus, Ohio, staff highlighted a well-developed Vision Zero effort. In Ann Arbor, Michigan, monthly interdepartmental crash reviews have contributed to measurable safety improvements.

These are not cities ignoring the problem. They are cities investing real time, money, and expertise into addressing it.

But as those same conversations continued, a different pattern began to emerge.

Cities Are Generally Good at Handling the Very Small and the Very Large

Cities can respond quickly to 311 calls, routine maintenance requests, and signal timing adjustments. At the other end of the spectrum, they can deliver major capital projects: corridor reconstructions, federally funded safety improvements, and long-range plans.

What they struggle with is everything in between.

A fatal crash that doesn’t occur on a designated high-injury network. A dangerous intersection that doesn’t meet signal warrants. A street that residents know is unsafe, but where the data hasn’t yet reached a threshold that justifies a capital project.

These situations fall into a kind of operational gap. They are too serious to ignore, but they don’t fit neatly into the systems cities have built to respond.

This is the missing middle of city operations and it’s where crash response often breaks down.

Inside That Gap, Failure Doesn’t Look Like Neglect. It Looks Like Fragmentation.

After a serious crash, no single department is clearly responsible for what happens next. Police have reports and data. Engineers have design authority. Public works has materials and crews. But there is often no shared process to bring those pieces together.

Instead, departments operate independently, generally without access to all the tools or information they need.

One planner described a moment after a pedestrian fatality at a busy crosswalk. The engineering team’s response was that they “didn’t want to have a knee-jerk reaction to every single crash.”

From the outside, that can sound callous. But inside a system with limited staff, constrained budgets, and no clear way to triage these events, it’s a rational response. It reflects a deeper problem: not a lack of concern, but a lack of structure for acting.

When no shared process exists, even serious events struggle to produce coordinated action.

A Fatal Crash Should Function as a Clear Signal

I fatal crash is a moment when the system reveals something important about how it is performing. But in many cities, there is no mechanism to translate that signal into a timely response.

Instead, the signal gets absorbed into existing workflows in the form of studies, plans, and future capital projects, operating on timelines measured in months or years.

Meanwhile, the public is operating on a different clock. After a fatal crash, people expect acknowledgment, visible action, and evidence that the city is learning from what happened within days, not years.

When that doesn’t happen, trust erodes. And it erodes even in places where meaningful work is underway but not visible.

This is what institutional fragility looks like: not the absence of effort, but the inability to adapt in real time when conditions demand it.

What These Conversations Make Clear Is That Cities Do Not Lack Knowledge

Cities know where many of their dangerous locations are. They understand the contributing factors behind crashes. They have staff with deep expertise and, in many cases, access to materials and tools that could be deployed quickly.

What they lack is a shared way to act on what they already know.

Specifically, they lack a defined, cross-departmental process for responding to serious crashes in the space between immediate emergency response and long-term capital planning.

Without that, each event becomes an exception to be managed rather than a signal to be acted on.

Some cities are beginning to address this gap by creating more structured, immediate responses.

One example is the Crash Analysis Studio, which brings together staff from across departments to examine a crash site, identify contributing conditions, and develop near-term actions using existing resources. The specifics vary by community, but the underlying shift is the same: treating a crash not as an isolated incident, but as a trigger for coordinated, timely response.

The important point is not the program itself. It’s the recognition that this middle layer of response needs to exist. If there is one thing these conversations have clarified, it’s this: the issue is not whether cities care about safety or are doing work to improve it. The issue is that they are missing an operational layer.

They have systems for small problems. They have systems for big projects. But when something serious happens that doesn’t fit either category, they often have no clear way to respond.

And that is where some of the most important opportunities to prevent the next crash are being lost.