Community Safety Departments

A 911 dispatcher in Albuquerque pulls up a call: an intoxicated man slumped outside a gas station, unresponsive to passersby. Three years ago, that call went to police. Two officers would arrive, lights flashing, hands near holsters, and try to rouse a man who needed water and a ride, not a badge and a command voice. Now the dispatcher routes it to the city's Community Safety Department.¹ A trained community responder arrives in a branded vehicle, no weapon, no arrest authority. The responder sits with the man, checks for medical distress, connects him to a sobering center or shelter. No force. No arrest. No emergency room.

In cities around the country, 911 dispatchers face the same limitation every shift: three buttons. Police. Fire. EMS. A woman calls because her brother is having a psychotic episode in the backyard. Police. A business owner calls about a man slumped in the doorway, intoxicated and unresponsive. Police. A resident reports a neighbor screaming at no one on the sidewalk. Police. A school reports a student threatening self-harm. Police. Needles on the playground. Police.

Most American cities already have some version of non-police crisis response. Denver sends civilian crisis teams to mental health calls.¹ Portland dispatches civilian responders to behavioral health emergencies.² Harris County deploys crisis specialists across unincorporated areas.³ San Diego County fields 44 civilian crisis units across the region.¹⁶ The question a council member considering a Community Safety Department must answer is not whether to offer these services, but whether the institutional structure around them matters.

A mobile crisis team handles mental health emergencies. A violence intervention team handles retaliatory conflict. A clean team handles needle pickup. A Community Safety Department handles all of these and the calls that fall between them.

In cities around the country, 911 dispatchers face the same limitation every shift: three buttons. Police. Fire. EMS. A woman calls because her brother is having a psychotic episode in the backyard. Police. A business owner calls about a man slumped in the doorway, intoxicated and unresponsive. Police. A resident reports a neighbor screaming at no one on the sidewalk. Police. A school reports a student threatening self-harm. Police. Needles on the playground. Police.

Not many places yet. While more than 1,800 civilian crisis teams operate across the United States¹ and at least 14 of the 20 most populous cities host or are launching civilian crisis response programs,²⁹ the number of cities that have built a unified Community Safety Department, with its own director, budget, training infrastructure, and cabinet-level standing, can be counted on one hand. Several more are in development. National polling shows 82% public support,² but roughly five cities have built one.

Community Safety Departments poll with bipartisan margins that hold after voters hear opposition arguments. What makes the numbers actionable is that law enforcement leadership has landed in the same place as voters.

Every person in the room where a Community Safety Department is proposed, debated, funded, or evaluated experiences it through a different lens. The line officer wants calls off his plate. The union strategist wants headcount protected. The dispatcher worries about liability. The family calling 911 is afraid of what happens when police arrive. The budget director needs HR classifications. The council member needs quarterly metrics. A CSD that satisfies one of these constituencies at the expense of the others does not hold.

A leader who launches a Community Safety Department without understanding how these programs can fail is unprepared for the failure modes she will encounter. The risks below are not theoretical objections. They are documented patterns from cities that have tried, and in some cases failed, to build and sustain civilian response programs. Named failures with identified causes are more useful for implementation planning than success stories.

There are roughly ten design decisions every city faces when building a Community Safety Department, and they are sequential. Each one constrains the next. The institutional home determines the hiring pipeline. The hiring pipeline shapes team composition. Team composition dictates which calls the program can safely take. Call types drive the dispatch protocol. And the dispatch protocol determines whether anyone actually uses the department.

Community Safety Departments cost less per response than police handling the same calls, and when downstream savings are included, some programs generate a net fiscal gain. But the funding landscape is more complicated than any single cost comparison suggests. The type of funding matters as much as the amount, because different revenue sources carry different sustainability profiles, different political vulnerabilities, and different gaps in what they actually cover.

The language that works is operational, not ideological, and it has been tested. Three themes appear across every city that has successfully built a Community Safety Department, and the specific phrases that resonate share a common structure: they center public safety, clarify roles, and position the department as additional capacity rather than a replacement for anything.