How ShotSpotter Works in Baltimore and What Its Data Actually Shows

ShotSpotter, the automated gunshot detection system deployed across Baltimore since 2007, is a tool embedded in the city's public safety infrastructure that generates both operational responses and ongoing debate about surveillance, accuracy, and police resource allocation. This guide explains how the system functions in practice, what the data reveals about its use, and the questions it raises for residents and policymakers.

The System and Its Deployment

ShotSpotter uses networks of acoustic sensors installed on rooftops, utility poles, and other elevated structures throughout Baltimore to detect and locate gunshots. When sensors pick up sounds matching a gunshot's acoustic signature, the system triangulates the location and alerts Baltimore Police Department dispatch within 60 seconds. Officers then respond to the coordinates provided.

The city has expanded ShotSpotter coverage significantly over time. As of 2022, the system covered roughly 80 square miles of Baltimore, concentrating on neighborhoods where gun violence historically clusters: parts of West Baltimore including Sandtown-Winchester, Gwynn Oak, and Pimlico; sections of East Baltimore around Greenmount Avenue and near City Rec facilities; and corridors in Southwest Baltimore including Gwynn Oak and the areas around Catonsville Avenue. The coverage map is not uniform by neighborhood, which itself reflects historical resource allocation decisions.

The contract between Baltimore and ShotSpotter (operated by a California-based company of the same name) has been renewed multiple times. In 2020, the city allocated approximately $1.5 million annually for the system, a figure that has remained relatively stable through subsequent budget cycles, though the total cost including infrastructure maintenance varies year to year.

What the Data Shows

ShotSpotter's value depends on what you measure. The system detects a high volume of incidents: in 2019, before the pandemic, ShotSpotter registered over 8,000 incidents across the city. That number dropped to around 5,000 in 2021, tracking with broader trends in gun violence during COVID-era disruptions.

However, important caveats apply to interpretation. Police response rates to ShotSpotter alerts vary dramatically by neighborhood. In well-resourced districts with more available units, officers reach locations within minutes. In understaffed areas, response times stretch to 15 or 20 minutes, if units respond at all. A system alert without a police response generates no incident report and therefore no public record. This asymmetry means ShotSpotter's utility depends on police deployment capacity, not just sensor accuracy.

Accuracy is another layer. ShotSpotter acknowledges that its sensors can misidentify loud noises: fireworks, construction, vehicle backfires, or even amplified audio from events register as potential gunshots. The company reports a low false positive rate, typically citing figures in the 5 to 10 percent range, but Baltimore Police data on actual follow-up investigations (whether officers locate evidence of gunfire) is rarely published in detail. In 2021, the Baltimore Police Department released limited data suggesting that approximately 25 percent of ShotSpotter alerts resulted in an officer locating spent shell casings or other gunshot evidence, meaning roughly three-quarters of alerts did not confirm a shooting at the indicated location. This discrepancy does not necessarily indicate the system failed; it may reflect gunshots fired outside sensor range, misidentified sounds, or simple reporting lags. But it highlights that a ShotSpotter ping is not synonymous with a confirmed shooting.

Integration with Police Operations

ShotSpotter data feeds into the Baltimore Police Department's CompStat meetings and precinct-level accountability. Districts in the Northeast and Southeast rely heavily on ShotSpotter alerts for overtime deployment and focused patrols during high-alert periods. When cluster alerts occur, additional units may be assigned to a neighborhood for several hours.

The system also serves as a source for federal grant applications and community violence intervention programs. Organizations applying for Violent Crime Control funding often reference ShotSpotter coverage as evidence of comprehensive data collection infrastructure, even where the operational outcome remains contested.

Integration with broader crime analysis is inconsistent. ShotSpotter data is linked to CompStat but less routinely cross-referenced with victim reports, hospital gunshot wound admissions, or community-based violence interruption programs. This siloing limits opportunities to assess whether detection actually prevents injuries or simply documents incidents after they occur.

What Residents in Covered Areas Experience

In neighborhoods with active ShotSpotter coverage, residents notice increased police presence following alert clusters, though the visibility of this presence varies. Following a concentrated sequence of alerts in a specific block or corridor, officers may conduct enforcement stops or canvas for witnesses. The experience differs substantially between neighborhoods: in some areas, residents report feeling safer due to increased police visibility; in others, the same increased presence is experienced as surveillance and as a precursor to stops of pedestrians and drivers.

ShotSpotter's presence has also become part of local infrastructure literacy. Residents in covered neighborhoods often know roughly where the sensors are mounted. Some view the system as an accountability mechanism on police (documenting where violence occurs); others view it as an extension of surveillance targeting certain communities. Neither interpretation is universal, and both can coexist in the same neighborhood.

Ongoing Questions and Policy Tensions

The city has periodically reviewed ShotSpotter's contract. In 2020 and 2021, amid national scrutiny of police spending and effectiveness, Baltimore activists and some city council members raised questions about whether $1.5 million annually could be better spent on violence prevention, youth employment, or community health services. No formal cost-benefit analysis comparing ShotSpotter outcomes (incidents detected, subsequent arrests, lives saved) against alternative investments has been published by the city.

Coverage gaps persist in some high-violence areas due to infrastructure constraints, while some lower-violence neighborhoods receive coverage. The city has not published a detailed rationale for the current coverage map, which limits public understanding of how deployment priorities were set.

Police response data by ShotSpotter-triggered alert versus other call types is also sparse in public reporting, making it difficult to assess whether ShotSpotter alerts receive faster response than 911 calls for gunshots or whether the system actually changes response patterns.

Practical Takeaway

If you live or work in a ShotSpotter-covered neighborhood in Baltimore, understand that police may arrive in response to system alerts without a confirmed shooting being present, and response times can range from minutes to hours depending on precinct staffing. The system is a detection tool, not an immediate safety mechanism, and its effectiveness depends on police capacity, not sensor placement alone. For policymakers and community groups evaluating public safety investments, ShotSpotter represents a specific operational choice with measurable costs and debatable returns, not a comprehensive solution.