Police in the United States are not legally obligated to protect you as an individual. Courts, including the U.S. Supreme Court, have held that law enforcement’s duty runs to the public as a whole, not to any specific person who calls for help. A department can fail to respond, respond slowly, or decline to enforce an order you hold in your hand, and in most cases you cannot sue it for the harm that follows. The exceptions exist, but they are narrow and hard to win.
The Public Duty Doctrine
The rule has a name: the public duty doctrine. Under this principle, a police department’s protective duty is owed to the community at large rather than to any one resident. If you call 911, officers respond late or not at all, and you are harmed in the interim, the doctrine typically blocks a negligence suit against the department at the threshold. Because no duty to you personally exists, your claim fails at step one.
A handful of states have moved away from the doctrine through court rulings or legislation, but most still apply it.
What the Supreme Court Has Said
Two Supreme Court decisions have made this rule difficult to challenge on constitutional grounds, and an older appellate ruling reached the same result under common law.
DeShaney v. Winnebago County
Wisconsin caseworkers received repeated reports that a father was abusing his young son, Joshua DeShaney, and documented suspicious injuries during home visits, but never removed the child. The father eventually beat Joshua so severely that the boy suffered permanent brain damage.
The Supreme Court ruled that the Fourteenth Amendment’s Due Process Clause limits what the government can do to you but does not require the government to protect you from harm inflicted by private individuals. Because Joshua was in his father’s custody, not the state’s, no constitutional duty to intervene existed.1Justia. DeShaney v. Winnebago County DSS, 489 U.S. 189 (1989)
DeShaney did recognize one boundary. When the government takes someone into physical custody and restricts their ability to protect themselves, a duty to protect arises. Prisoners and people involuntarily committed to psychiatric facilities fall into this category. Outside of custody, though, the rule is that there is no constitutional duty to protect.1Justia. DeShaney v. Winnebago County DSS, 489 U.S. 189 (1989)
Town of Castle Rock v. Gonzales
Jessica Gonzales held a restraining order against her estranged husband. When he took their three daughters in violation of that order, she called police repeatedly over several hours. Officers did not act. Her husband murdered the children that night.
Colorado law said police “shall enforce” such orders, and Gonzales argued that this mandatory language gave her a personal right to police action. The Supreme Court disagreed. Even statutory language that sounds obligatory does not create a constitutionally protected property interest in enforcement, because police retain practical discretion in how and when they respond.2Justia. Castle Rock v. Gonzales, 545 U.S. 748 (2005)
Warren v. District of Columbia
Before either Supreme Court case, the D.C. Court of Appeals had reached a similar conclusion on common-law grounds. Two women heard their roommate being attacked by intruders downstairs and called police. Officers came, knocked briefly, got no answer, and left. A second call brought no return visit. All three women were held captive and assaulted for roughly fourteen hours.
The court held that police owed no specific legal duty to the individual women. Their duty to provide services belonged to the community at large, and absent a special relationship between the officers and the victims, no actionable claim existed.3Justia. Warren v. District of Columbia
When a Duty Can Arise: The Special Relationship Exception
The public duty doctrine is not absolute. The most widely recognized way around it is proving a “special relationship” between you and the officers, meaning they took on a specific duty to protect you that went beyond their general obligation to the public. Courts apply a demanding test, and most claims fail on it.
You generally need to show all four of the following:
- A direct and specific promise of protection from an officer. Vague assurances like “we’ll send someone” do not qualify. Courts have repeatedly held that a 911 dispatcher’s “help is on the way” is a promise to the public, not to the caller.
- Police awareness of a specific, identifiable danger to you personally. General knowledge that an area is dangerous is not enough. Knowledge that a named individual has threatened you at a known location is closer to what courts require.
- Your justifiable reliance on the promise, in a way that made your situation worse. A victim told an officer would be posted outside their home, who then stayed home instead of leaving for a shelter, has relied to their detriment.
- Direct contact between you and the officers, whether spoken or through conduct. A call placed by a bystander on your behalf, without officers ever communicating with you, may not satisfy this element.
Every element must be proven. Missing one sinks the claim. The bar is high by design; if a special relationship were easy to show, the public duty doctrine would have no practical force.
When Police Made Things Worse: State-Created Danger
A second, less common exception applies when officers do not merely fail to protect you but actively make your situation worse. Known as the state-created danger doctrine, it holds that the government can be liable under the Fourteenth Amendment when its own affirmative actions place you in greater danger than you faced before.
To succeed, you typically need to show three things: the government took affirmative steps that created or increased the danger, officials acted with deliberate indifference to your safety, and those actions directly caused your injury. The operative word is “affirmative.” Doing nothing is not enough; officers must have done something that left you worse off than if they had never arrived.
Nearly every federal appellate circuit recognizes some version of this doctrine, though the elements vary. The Supreme Court has never formally adopted or rejected it. The theory grew out of language in DeShaney suggesting that the state’s own conduct could trigger liability, and lower courts have built on that opening since 1989.1Justia. DeShaney v. Winnebago County DSS, 489 U.S. 189 (1989)
Suing Under Federal Civil Rights Law
The main federal vehicle for a case like this is 42 U.S.C. ยง 1983, which lets you sue anyone who, acting in an official government role, deprives you of a constitutional or federal right.4Office of the Law Revision Counsel. 42 USC 1983 – Civil Action for Deprivation of Rights
The hard part is proving a constitutional violation happened. After DeShaney and Castle Rock, failing to protect you from private violence is not, on its own, a due process violation. A Section 1983 claim built on police inaction almost always has to fit within one of the narrow exceptions above.
Suing the City Rather Than the Officer
A municipality can be sued directly under Monell v. Department of Social Services when the harm resulted from an official policy, a widespread custom, or a decision by someone with final policymaking authority.5Justia. Monell v. Department of Social Services, 436 U.S. 658 (1978)
If a department has an unwritten practice of ignoring certain kinds of calls, or a policy of deprioritizing protective order enforcement, the city itself can be held responsible. But a city is not liable simply because it employs someone who did something wrong. You have to tie the harm to a policy or entrenched custom, not to a single officer’s judgment call.5Justia. Monell v. Department of Social Services, 436 U.S. 658 (1978)
Qualified Immunity
If you sue an individual officer, expect a qualified immunity defense. This doctrine shields government officials from personal liability unless the officer’s conduct violated a constitutional right and that right was “clearly established” at the time. In practice, “clearly established” often means you need a prior court decision with nearly identical facts where an officer was found liable. Without such precedent, even conduct that looks plainly wrong can escape personal accountability.6Justia. Harlow v. Fitzgerald, 457 U.S. 800 (1982)
How State Law Can Change the Answer
Everything above is constitutional and common-law doctrine. State legislatures can and do adjust the picture through statutes that create specific duties, waive government immunity in defined situations, or impose procedural requirements before you sue.
Tort Claims Acts
Every state has a tort claims act defining when a government entity can be sued. Some waive sovereign immunity for certain kinds of police misconduct while capping damages. Others keep broad immunity but allow claims in narrow categories, such as vehicle accidents involving government employees. The details vary widely by state.
Mandatory Arrest Statutes
In some high-risk situations, state law removes police discretion. The most common example is domestic violence. Many states require an arrest when officers have probable cause to believe a protective order has been violated. Where a statute commands an arrest and an officer fails to make one, a victim may have a stronger footing for a claim than in a typical failure-to-protect scenario.
Notice of Claim Deadlines
Before you can sue a city or a police department, most jurisdictions require you to file a formal notice of claim with the government entity. The deadlines are short, often 90 days to a few years depending on the state, and missing one can end the case regardless of its merits. The notice typically has to describe what happened, when and where, and the damages you are claiming, and there is usually a mandatory waiting period before suit. If you believe police inaction caused you serious harm, talking to an attorney quickly is the single most important practical step.