Hidden Clocks: How Cities Conceal Emergency Response Data—and What Residents Can Do About It

When a heart stops beating, the window for survival narrows with every passing minute. When a structure fire ignites, the difference between a contained incident and a total loss can be measured in seconds. Emergency response time is not an administrative abstraction—it is a matter of life and death. And yet, across hundreds of American cities, the data that would allow residents to evaluate how quickly help actually arrives remains buried, fragmented, or actively withheld.

This is not a fringe concern. It is a structural transparency problem embedded in the way municipal public safety agencies manage their own accountability.

What Response Time Data Actually Reveals

Emergency response time, in its most basic form, measures the interval between when a call is received by a dispatcher and when a first responder arrives on scene. Beneath that simple definition lies a web of metrics that cities can manipulate, selectively report, or decline to publish altogether.

Many municipalities report only average response times—a figure that can be dramatically skewed by fast responses in well-staffed, centrally located districts while masking dangerously slow arrival times in outlying or underserved neighborhoods. Others report median times, which tell a different story. Some agencies publish only fire response data while omitting emergency medical service (EMS) benchmarks. A few report only calls that meet their internal performance targets, quietly excluding the outliers that would alarm residents most.

The National Fire Protection Association recommends that fire departments reach 90 percent of incidents within four minutes of dispatch. The American Heart Association notes that survival rates from cardiac arrest drop roughly 10 percent for every minute without defibrillation. These benchmarks are widely cited in professional literature. What is far less common is a city government proactively publishing data showing whether it meets them—broken down by neighborhood, time of day, or call type.

Why Municipalities Resist Disclosure

Public safety agencies offer several explanations for limiting access to response time data. Some cite operational security concerns, arguing that detailed performance metrics could reveal staffing patterns or station coverage gaps that bad actors might exploit. Others point to data complexity, noting that raw dispatch records require significant context to interpret accurately. A smaller number raise privacy concerns related to individual incident records.

While each of these considerations has some legitimate basis, they are frequently used as blanket justifications for withholding data that would otherwise be releasable. The operational security argument, for instance, rarely holds up when the same information is routinely published by peer cities without incident. The complexity argument, meanwhile, places the interpretive burden on the agency rather than allowing residents and independent analysts to engage with the underlying records.

What is harder to articulate publicly—but often visible in practice—is institutional resistance to scrutiny. Departments that are understaffed, underfunded, or inequitably distributed across a city have strong incentives to avoid publishing granular data that would surface those disparities.

Using FOIA to Access What Cities Won't Volunteer

The Freedom of Information Act, and its state-level equivalents, provides residents with a legal pathway to obtain emergency response records that agencies decline to publish proactively. The process requires patience and precision, but it is accessible to any resident willing to invest the time.

Begin by identifying the correct agency. In most cities, emergency response data is held by the fire department, the EMS authority, or the city's 911 dispatch center—sometimes all three, depending on how services are organized. Each may maintain separate records systems.

When drafting your request, be specific. Ask for computer-aided dispatch (CAD) records, which are the timestamped logs generated automatically during emergency calls. Request a defined time period—one calendar year is a reasonable starting point—and specify that you want incident-level data rather than aggregate summaries. Key fields to request include: call received time, dispatch time, unit en route time, on-scene arrival time, incident type, and geographic identifier (address or census tract). Redaction of personally identifiable information is standard and appropriate; the timestamps and location data are what matter.

Submit your request in writing, retain a copy, and note the statutory deadline for response in your state. If the agency denies your request or fails to respond within the legal timeframe, most states have an appeals process through the relevant oversight body or attorney general's office.

Comparing Your City to Its Peers

Once you have obtained response time data, context is essential. A city that averages five minutes and thirty seconds for fire response may look adequate in isolation—but how does that compare to cities of similar size, density, and geographic character?

Several resources can help establish meaningful benchmarks. The International City/County Management Association (ICMA) publishes comparative performance data through its Center for Performance Analytics. Many state fire marshal offices compile annual response time summaries across jurisdictions. The U.S. Fire Administration, a division of FEMA, maintains national incident data through the National Fire Incident Reporting System (NFIRS), which participating departments submit to voluntarily.

Some cities have set a higher standard for proactive disclosure. Louisville, Kentucky, and Seattle, Washington, have at various points published detailed EMS and fire response dashboards that allow residents to filter data by neighborhood and time period. These examples demonstrate that granular transparency is operationally achievable—and politically possible when community demand is sufficient.

Turning Data Into Advocacy

Data without an audience changes nothing. Once you have obtained and analyzed response time records, the path from information to impact runs through the same civic channels that govern any municipal policy question.

Begin by mapping what you find. Visualizing response times by neighborhood—even with a simple spreadsheet and a publicly available mapping tool—can make disparities legible in a way that raw numbers cannot. If your data shows that residents in one district consistently wait two minutes longer for an ambulance than those in another, a map communicates that inequity more powerfully than a table.

Bring your findings to the appropriate oversight body. Most cities have a public safety committee within the city council, and many have civilian oversight boards for police and fire services. Requesting time on a public agenda to present your analysis is a formal mechanism for placing response time disparities on the record.

Partner with community organizations that have existing relationships with city hall. Neighborhood associations, tenant advocacy groups, and public health organizations often have standing in policy conversations that individual residents do not. Your data can strengthen their advocacy; their networks can amplify yours.

Finally, engage local journalists. A well-documented story about unequal emergency response times—grounded in records obtained through a public records request—is exactly the kind of accountability reporting that local newsrooms can pursue. Sharing your data with a reporter does not diminish your own advocacy; it multiplies the pressure on decision-makers to respond.

The Accountability Clock Is Running

Every resident pays for emergency services through property taxes, utility fees, and a dozen other municipal revenue streams. The implicit contract is straightforward: in exchange for that contribution, the city will dispatch trained personnel and equipment to a crisis as quickly as possible. What is less understood is that residents have both a right and a responsibility to verify whether that contract is being honored—and to demand correction when it is not.

The silence between sirens is not just the absence of sound. It is the absence of information that residents deserve to have. Filling that silence begins with a records request, a spreadsheet, and the civic conviction that public safety performance is a public matter.