This bill restricts the circumstances under which Federal law enforcement officers and members of the Armed Forces may perform crowd-control, riot-control, or arrest functions in the United States. It requires visible identifying information for deployed federal personnel, prohibits concealing that information and bars use of unmarked vehicles for apprehensions in those operations.
It also confines federal crowd-control authority to Federal property and its immediate vicinity unless a state and local government jointly request assistance or the Insurrection Act is invoked.
The measure adds a near-real-time transparency requirement: agencies must publish specified deployment details on their public websites within 24 hours. For compliance officers and agency lawyers, the bill creates new operational limits, recordkeeping and coordination obligations, and potential legal exposure where federal arrests occur while identification or location rules are violated.
At a Glance
What It Does
The bill defines who counts as a Federal law enforcement officer (including contractor personnel), requires officers and service members engaged in crowd or riot operations to display agency and last name or unique identifier (and rank for service members), bans concealing that identification, and forbids using unmarked vehicles to apprehend civilians during such activity. It limits federal crowd-control actions to Federal property and immediately adjacent public space, subject to two narrow exceptions, and mandates public disclosure within 24 hours of deployments.
Who It Affects
Federal law enforcement agencies and components of the Department of Defense, contractors and subcontractors performing law-enforcement functions, state governors and local chief executives who may request assistance, protest participants and bystanders near federal property, and journalists and civil-rights groups who monitor deployments.
Why It Matters
The bill redraws boundaries between federal and local roles in public-order policing, forces agencies to operationalize identification and reporting practices, and creates a statutory basis to challenge federal arrests that occur in violation of its limits. That changes how federal deployments will be authorized, documented, and scrutinized during demonstrations.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill starts by defining key terms narrowly but inclusively. “Federal law enforcement officer” covers not only agency employees but also contractor and subcontractor personnel authorized by law or contract to perform law-enforcement functions; “member of an armed force” explicitly covers active duty and National Guard under title 32/10 definitions. Those definitions matter because the bill’s limits and duties apply across agency staff, military members, and contracted individuals doing the same work.
For any federal personnel engaged in crowd control, the bill requires clear, visible identification: the agency name plus the officer’s last name or a unique identifier; service members must also display rank. The text forbids taping over, obscuring, or otherwise concealing that identification while engaged in the relevant law-enforcement activities.
It further prohibits using unmarked vehicles to apprehend, detain, or arrest civilians during these operations, a constraint aimed at preventing covert-style detentions in public-order responses.On geography and authorization, the bill sharply narrows federal authority: federal officers and service members may only perform crowd-control functions on Federal property and the immediate adjacent sidewalks and streets. Two exceptions exist: a joint written request by a State Governor and the head of a unit of local government authorizes federal action beyond that footprint; and invoking the Insurrection Act overrides the restriction.
The bill makes an arrest unlawful if it occurs while the arresting federal personnel are acting in violation of the identification or geographic limits.Finally, the bill imposes a transparency duty: within 24 hours of any deployment for crowd control, the responsible agency or armed force must post on its public-facing website the deployment date, the number of federal personnel in each locality, a description of the mission, locations where civilians are being detained and who holds custody, and a copy of any written request for assistance. That combination of operational limits, identification rules, and rapid public reporting aims to change both how and when agencies send federal personnel into public-order situations and to make those actions discoverable quickly.
The Five Things You Need to Know
The bill’s definition of “Federal law enforcement officer” explicitly includes contractors and subcontractors authorized by law or contract to perform law-enforcement functions.
It requires personnel engaged in crowd or riot control to display agency and last name or unique identifier, and for service members to also display rank, and it bans taping over or otherwise obscuring that identification.
Federal crowd-control authority is limited to Federal property and the immediate sidewalk and street adjacent to it; operating beyond that requires a joint written request from the State Governor and the head of a local unit of government or the invocation of the Insurrection Act.
The bill makes it unlawful for federal personnel to arrest anyone if the personnel were conducting activities in violation of the identification or geographic limits.
Agencies must publish specified deployment information on their public websites within 24 hours, including personnel counts by locality, mission description, detention locations, custody holders, and any written state/local request.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Designates the act as the “Preventing Authoritarian Policing Tactics on America’s Streets Act.” This is purely nominative but flags the bill’s policy focus on crowd-control limits and transparency.
Who counts as a covered officer or service member
This subsection sets the scope: a covered ‘Federal law enforcement officer’ includes civilian agency employees and contractor or subcontractor staff authorized by law or contract to perform law-enforcement functions; ‘member of an armed force’ tracks the title 10 and 32 statutory definitions. For practitioners, the practical implication is that contracts and statements of work will need review to determine which contractor roles trigger the statute’s operational restrictions and reporting duties.
Visible identification; bans on concealment and covert vehicle arrests
Agencies and units must ensure deployed personnel display identifying information (agency and last name or unique identifier; rank for service members). Subsection (b)(2) forbids taping over or otherwise obscuring those identifiers and bars using unmarked vehicles to arrest, detain, or apprehend civilians during the covered activities. Compliance will demand uniform updates, new gear standards, and supervisory monitoring; contractors will have to be issued and maintain comparable identifiers.
Geographic limits with narrow exceptions
Federal personnel may exercise crowd-control, riot-control, and arrest authority only on federal property and the immediately adjacent sidewalk and street. The statute creates two explicit exceptions: a joint written request from the State Governor and head of a unit of local government, or an invocation of the Insurrection Act. Agencies must implement processes for capturing and retaining any written state/local request and for documenting when Insurrection Act authority is relied upon.
Unlawful arrests and 24‑hour public reporting
Subsection (d) makes arrests unlawful if carried out while an officer or service member is violating the identification or geographic rules. Subsection (e) requires the deploying agency to publish, within 24 hours, specified information on its public website: deployment date, number of personnel by city/town/locality, mission description, detention locations and custody holders, and any written request for assistance. This creates a near-real-time public record that agencies and legal teams must be prepared to produce and defend.
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
- Protesters and demonstrators near federal buildings: the geographic limits and ID rules reduce the likelihood of surprise federal interventions and make it easier to identify and document personnel conduct.
- Civil-rights organizations and journalists: the 24-hour publication requirement provides rapid, official data for monitoring deployments and alleging unlawful activity.
- Local and state officials asserting control over public-order responses: the bill requires a clear joint written request before federal forces operate beyond federal property, strengthening local input into federal assistance decisions.
Who Bears the Cost
- Federal law enforcement agencies and DOD components (including mission planners and legal teams): they must change deployment doctrine, implement identification and vehicle policies, and create processes to satisfy the 24-hour reporting requirement.
- Contractors and subcontractors that perform law-enforcement functions: they will fall within the statute’s scope and need to comply with new uniform and identification rules, contract changes, and reporting expectations.
- Governors and local chief executives: when they request federal help, they must provide a joint written request (procedural burden and political risk) and will be publicly tied to any subsequent federal deployments.
Key Issues
The Core Tension
The central dilemma is between protecting civil liberties and public transparency on one hand, and preserving federal officers’ and commanders’ operational flexibility and safety on the other: rules that make federal deployments more visible and geographically constrained reduce the risk of overreach but also limit rapid, covert, or force-protected responses that federal agencies argue are sometimes necessary to protect life and property.
The bill leaves several operational and legal questions unresolved. It says arrests are “unlawful” when made while personnel violate the identification or geographic rules but does not create a private right of action, specify criminal penalties, or spell out administrative remedies; courts will have to decide what “unlawful” means in practice and who can enforce it.
Agencies will need to draft implementing policies quickly: what counts as a qualifying unique identifier, how to handle safety-based concealment claims, and how to inventory contractor roles are all implementation necessities left to agency guidance or litigation.
The geographic limitation—federal property plus the “immediate vicinity” including the sidewalk and adjacent street—sounds precise but invites dispute. Events frequently spill beyond that footprint, and small differences in how “immediate vicinity” is measured could create operational gaps or litigation points.
The requirement to post deployment details within 24 hours is transparent in intent but operationally heavy: tracking personnel by locality, detention locations and custody holders, and publishing copies of written requests will demand rapid interagency and intergovernmental information flows that most agencies do not currently maintain.
Finally, the contractor inclusion creates command-and-control complexity: contractor employees may wear different uniforms, operate under different rules of engagement, and be subject to both contract and this statute. Integrating contractors into ID, vehicle, and reporting systems will require contract amendments and closer oversight, and it raises procurement and liability questions the bill does not address.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.