The District of Columbia Policing Protection Act of 2025 rewrites parts of the D.C. Comprehensive Policing and Justice Reform Amendment Act of 2022 to change how and when officers may engage suspects in motor-vehicle pursuits.
It replaces detailed prohibitions in the existing statute with a permissive rule: officers may pursue unless they or a supervising officer reasonably conclude the pursuit would pose unacceptable risk, be futile, or a better alternative exists.
The bill also carves out sworn federal law-enforcement officers of covered federal agencies from the D.C. statute and requires the Department of Justice to evaluate PursuitAlert (or similar public-alert systems) for the Metropolitan Police Department within three years and report to four congressional committees. The practical impact: more operational discretion for D.C. officers, new jurisdictional complexity where federal agents operate, and a federal study that could steer adoption of public‑notification technology in pursuits.
At a Glance
What It Does
The bill amends D.C. law to allow vehicular pursuits unless an officer or supervisor reasonably believes the chase would (a) create an unacceptable risk to bystanders, (b) be futile, or (c) be less effective than another method of capture. It removes several specific prohibitions previously listed in the statute and excludes certain federal sworn officers from the statute’s definition of law enforcement officer.
Who It Affects
Primary targets are the Metropolitan Police Department and other officers operating in D.C.; covered federal law‑enforcement agencies gain an explicit exemption. Secondary targets include D.C. government officials responsible for training, civil‑liability carriers, and communities frequently exposed to police pursuits.
Why It Matters
The change shifts D.C. policy from a rules-heavy restriction model to a more discretionary, risk‑balanced test, altering accountability and after‑action review norms. The required DOJ evaluation of PursuitAlert could drive adoption of public notification tools and introduce new operational, privacy, and implementation considerations for local policing.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
Congress instructs a rewrite of specific sections of the D.C. policing reform statute so that officers in the District may engage vehicles they reasonably suspect are fleeing unless the officer—or a higher-ranking supervisor—concludes one of three things: the chase would pose an unacceptable risk to others, it would be futile, or there is a faster or safer way to catch the suspect. That replaces a set of enumerated prohibitions and clarifies who makes the call in real time: the on-scene officer or a supervising official.
Separately, the bill narrows who counts as a “law enforcement officer” under the D.C. statute by excluding sworn federal officers from covered federal agencies as defined elsewhere in federal law. Practically, that means federal agents working in the District operate under their own agency policies rather than the D.C. pursuit rule established in this statute, creating two overlapping standards in the same physical space.The Attorney General must, within three years of enactment, study PursuitAlert or similar technologies—systems that can notify nearby members of the public about an ongoing police pursuit—and deliver a written evaluation to four congressional committees.
The report must analyze costs and benefits; the bill does not mandate adoption, procurement, funding, or a timeline for the Metropolitan Police Department to implement such a system.Taken together, the measures increase tactical discretion for local officers, introduce jurisdictional fragmentation with federal officers exempted, and obligate a federal study that may shape technology-driven public-notification strategies. The statute leaves several operational questions to agency policies, training protocols, and post-incident review processes rather than prescribing granular rules in the text itself.
The Five Things You Need to Know
Section 2(a) replaces the existing pursuit rule (D.C. Code sec. 5–365.02) with a permissive standard: an officer may pursue unless an officer or supervising official reasonably believes the pursuit (A) would entail unacceptable risk to others, (B) would be futile, or (C) is less effective than another method.
The bill alters D.C. Code sec. 5–365.01(a) by striking multiple enumerated paragraphs and explicitly excluding "a sworn federal law enforcement officer of a covered federal law enforcement agency" as defined in 18 U.S.C. § 11712(d) (cited in D.C. law as 5–133.17(d)).
Congress requires the Attorney General to evaluate PursuitAlert or similar technology for the Metropolitan Police Department and to publish and submit that evaluation to four congressional committees not later than three years after enactment.
The operational decisionmaker named in the statute is the on-scene officer or a higher-ranking official with supervisory authority; the statute centers the supervisor’s reasonable belief as the legal trigger to stop or allow pursuit.
The amendment removes several named prohibitions from the 2022 D.C. law (striking paragraphs (1)–(5), (8)–(11) of sec. 5–365.01(a)), and redesignates remaining paragraphs, effectively shifting policy from prescriptive lists to a reasonableness‑based test.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Establishes the Act’s short title as the 'District of Columbia Policing Protection Act of 2025.' This is purely stylistic but signals the bill’s scope is limited to policing in the District and frames the subsequent amendments as changes to D.C. law enacted by Congress.
Definition edits and paragraph strikes
The bill strikes several enumerated paragraphs in the D.C. statute and redesignates remaining paragraphs, collapsing the prior list-based approach. Most operationally important, it inserts a carve-out: sworn federal law-enforcement officers of 'covered federal law enforcement agencies' (cross-referenced to federal law) do not fall within the D.C. statute’s definition of law-enforcement officer. That creates a statutory boundary: local pursuit rules apply to D.C. officers but not to certain federal agents operating in the same jurisdiction.
New standard for vehicular pursuits
This provision replaces prior subsections with a single permissive rule: encountering a fleeing motorist does not automatically bar a pursuit. The statute lists three factual predicates—unacceptable risk to others, futility, or existence of a better apprehension method—that, if reasonably believed by the officer or a supervising official, justify not pursuing. The text emphasizes a reasonableness evaluation rather than a fixed prohibition, which places weight on on‑scene judgment and supervisory oversight during dynamic incidents.
Mandated evaluation of pursuit‑alert technology
The Attorney General must evaluate the costs and benefits of the Metropolitan Police Department adopting PursuitAlert or similar public-notification systems and publish that report within three years. The report must be submitted to four congressional committees (Senate Homeland Security and Governmental Affairs; Senate Judiciary; House Oversight and Reform; House Judiciary). The statute requires the evaluation but does not require MPD to implement recommendations, fund the system, or adopt a specific procurement pathway.
This bill is one of many.
Codify tracks hundreds of bills on Justice across all five countries.
Explore Justice in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Metropolitan Police Department officers: The statutory change grants officers and their supervisors more operational discretion to initiate pursuits when they judge risk acceptable, reducing the need to navigate a prescriptive forbidden-list in high-pressure encounters.
- Federal law‑enforcement agencies and their sworn officers: By excluding certain federal officers from the D.C. definition, those agencies preserve prosecutorial and operational control under their own pursuit policies and training protocols.
- Police leadership and unions: Agencies can craft department-level pursuit policies aligned to the new reasonableness test; unions often prefer standards that emphasize officer judgment and supervisory decision‑making.
- Nearby residents and drivers (conditional): If DOJ’s evaluation favors PursuitAlert and MPD later implements it, people living or traveling in affected areas could receive real‑time warnings that reduce accidental exposures to high‑speed chases.
Who Bears the Cost
- D.C. residents and bystanders: The permissive standard may lead to more pursuits, raising the risk of property damage, injuries, and fatalities in public spaces.
- District government and MPD budget holders: Implementing new training, supervisory protocols, and potential civil‑liability exposure will create direct costs; the bill does not appropriate funds to cover those expenses.
- Oversight bodies, civil litigators, and internal affairs units: More discretionary standards increase the complexity of post‑incident reviews, litigation, and disciplinary decisions because resolving what was 'reasonable' requires detailed investigation and expert evidence.
- Department of Justice and congressional staff: DOJ must allocate analytical resources to conduct a three‑year evaluation and prepare a multi‑committee report, which diverts staff and may require interagency coordination; no dedicated appropriation is provided.
Key Issues
The Core Tension
The bill grapples with a common policing dilemma: grant officers the discretion needed to pursue and detain suspects effectively, or impose strict rules to minimize public harm and predictable risks. It solves one problem—rigid prohibitions that can hamper immediate policing decisions—by returning judgment to officers and supervisors, but in doing so it increases reliance on agency capacity, training, and post‑incident accountability to manage the heightened public‑safety risks.
The statute substitutes a reasonableness test for a set of bright‑line prohibitions. That makes on‑scene judgment the decisive factor, but it also pushes many implementation questions—how to measure 'unacceptable risk', what facts make a pursuit 'futile', and what counts as a 'more effective or expeditious' alternative—down to departmental policies, training curricula, and supervisory practices.
Expect litigation and administrative disputes to focus on those undefined terms rather than the statute’s text.
The federal‑officer exclusion creates a practical patchwork. In many D.C. incidents, local and federal officers operate simultaneously; divergent rules could cause coordination problems, conflicting commands, and uncertainty for bystanders and dispatchers.
The bill also orders a DOJ study of PursuitAlert but stops short of mandating funding, standards, or a pilot, leaving local politics and budgets as the decisive factors in whether and how any public‑alert technology is used. Finally, PursuitAlert raises privacy and civil‑liberties questions (geolocation tracking, false alarms, alert fatigue) that the evaluation must confront but the statute does not outline how to weigh or mitigate.
Absent further statutory guidance, Congress shifts the battleground from statutory prohibition to administrative rulemaking, training, and oversight. That makes the content and quality of MPD policies, supervisor training, data collection, and after‑action processes the primary levers for reducing risk—rather than text in the statute itself.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.