This bill amends section 287 of the Immigration and Nationality Act to add new identification and verification obligations for officers and employees of U.S. Immigration and Customs Enforcement (ICE) and U.S. Customs and Border Protection (CBP) when they are engaged in law enforcement or immigration enforcement activities. It sets statutory standards for on-duty identification that link to an official Department of Homeland Security (DHS) webpage with specified verification data and a public complaint mechanism.
The measure is designed to increase public accountability and accessibility of information about enforcement personnel, while also creating operational and technical obligations for the agencies that deploy and maintain the required identification and intake systems. Compliance, privacy, and officer-safety questions will drive implementation choices at DHS and its components.
At a Glance
What It Does
The bill requires DHS to set a timeframe for officers and employees of ICE and CBP engaged in enforcement to display a scannable quick response (QR) code on their uniform that links to an official DHS webpage. That webpage must present identity and operational verification details and provide a secure way for the public to submit complaints, plus aggregated complaint counts that are non-personally identifiable.
Who It Affects
The requirement applies to ICE and CBP officers and employees engaged in law-enforcement or immigration-enforcement activities; DHS operational units must build and maintain the linked public webpages and complaint infrastructure; members of the public interacting with enforcement personnel gain a direct route for verification and reporting.
Why It Matters
The statute creates a routine, technology-enabled transparency tool for front-line enforcement interactions, shifting some oversight access to publicly available digital channels and obliging DHS to operationalize identity verification, complaint intake, and public data publication in ways agencies historically handled internally.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill adds a new subsection to the INA's section 287 that directs the Secretary of Homeland Security to require visible, scannable identification for ICE and CBP personnel performing enforcement duties. Congress frames the new requirement as a combination of on-person hardware (the scannable code on the uniform) and an online verification endpoint maintained by DHS.
The statute specifies what the DHS page must surface (identity, badge, unit, active status timestamp) and what it must not (home address, personal phone), and it mandates user-facing complaint submission and publication of aggregated, non-identifiable complaint counts.
Operationally, the law pairs a modest physical mandate—wear a scannable code, visible and not obscured—with a substantive IT obligation: DHS must host and secure a publicly accessible verification site that authenticates an officer's active status in real time or near-real time. The bill leaves implementation mechanics to DHS (it does not prescribe specific QR standards, encryption, authentication protocols, or hosting arrangements), but it imposes a hard deadline: implementation must begin within 180 days of enactment.Because the statute does not create explicit exemptions for undercover, covert, or certain tactical operations, agencies will need to craft internal policies addressing officer safety and operational security while still meeting the statute’s visibility requirement.
Similarly, the law requires a “secure mechanism” for complaints without specifying the intake workflow, investigation timeline, or how complaints will map to existing internal affairs or inspector general processes—leaving significant procedural design to DHS and component offices.Finally, the bill contains a rule of construction clarifying it does not preempt any Federal, State, or local law that provides additional transparency or accountability. That language preserves the ability of other jurisdictions or agencies to layer on stricter requirements, but it also leaves open coordination questions where local policies differ from DHS decisions on display formats, data publication, or complaint handling.
The Five Things You Need to Know
The bill inserts a new subsection (i) into 8 U.S.C. §1357 (section 287 of the INA) establishing the identification and verification requirements.
DHS must implement the requirement no later than 180 days after the statute’s enactment.
The on-uniform QR code must be clearly visible and unobscured by other clothing or equipment while an officer is engaged in enforcement activities.
The DHS-hosted page the QR links to must display the officer’s full name, badge number, agency and operational unit, and an active-status verification that includes a timestamp; it may include a photograph but may not display home address, telephone number, or other personal contact information.
The DHS page must include a secure mechanism for the public to submit complaints about officer conduct and must publish aggregated, non‑personally identifiable data on how many complaints were received for each officer who drew a complaint.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Declares the statute the “Quick Recognition Act” or “QR Act.” This is a naming provision only and has no operational effect beyond labeling the amendment for reference in statutes and agency materials.
New statutory subsection establishing identification and verification duties
Adds a standalone subsection (i) that becomes part of the authorities governing immigration enforcement. By placing the requirement directly in section 287, the bill integrates the identification obligation into the code provision that already governs arrest, inspection, and enforcement powers for ICE and CBP personnel, making the requirement statutory rather than purely regulatory or administrative.
Physical QR code mandate and required content for the linked DHS webpage
Requires officers engaged in enforcement to wear a scannable QR code on their uniform, positioned to remain visible and not obscured, and to link to an official DHS public webpage. The statute specifies exactly which data elements the page must present (full name, badge number, agency/operational unit, and an active-status verification with timestamp), permits a photograph, and expressly bars posting officers’ home addresses or personal phone numbers. Practically, that creates both a badge-hardware requirement (durable, tamper-resistant QR medium) and an external-facing IT obligation (authenticated, reliable verification that reflects 'active status').
Mandatory complaint intake and public complaint counts
Commands DHS to provide a secure method on the linked page for individuals to submit complaints about an officer’s conduct. It also requires DHS to make available aggregated, non‑personally identifiable counts of complaints per officer when complaints are filed. The statute does not define the complaint intake workflow, how complaints map to investigations, or data retention/retirement standards—those procedural choices will be made in agency policy and technical design.
Does not preempt more stringent transparency or accountability laws
Contains a rule of construction that the new subsection does not limit or preempt other Federal, State, or local laws or policies that provide additional transparency or accountability. This preserves the authority of other jurisdictions or agencies to impose further requirements, but it also creates a potential need for DHS to reconcile differing local rules with a national implementation approach.
This bill is one of many.
Codify tracks hundreds of bills on Immigration across all five countries.
Explore Immigration 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
- People interacting with ICE/CBP in the field — The public gains a quick, standardized way to verify an officer’s identity and active status and a direct channel to submit complaints when they believe misconduct occurred.
- Civil‑rights and oversight organizations — Easier public verification and a formalized complaint intake point create a richer evidentiary trail and publicly available aggregated complaint counts that can inform advocacy, audits, and research.
- DHS internal oversight offices and inspectors general — Standardized complaint routing and identification data can streamline case intake and link reports more reliably to specific officers and duty assignments.
Who Bears the Cost
- DHS and component budgets — DHS must design, build, host, secure, and operate the verification webpages and complaint intake systems and supply durable scannable identifiers for personnel, creating implementation and ongoing maintenance costs.
- Operational units (ICE/CBP) — Units will need to change uniform/equipment protocols, train personnel, and craft safety and operational-exemption policies; units with frequent covert or tactical operations will face harder trade-offs.
- Field officers — While the statute limits publication of personal contact data, officers may face increased exposure during public encounters and potential safety risks if adversaries misuse published verification details; they also must comply with a visible-identification rule that may complicate some deployments.
Key Issues
The Core Tension
The central dilemma is between public transparency and accountability on one hand, and officer safety, operational effectiveness, and administrative capacity on the other: the statute advances routine, public verification and complaint access, but doing so in a way that protects covert operations, prevents misuse of verification data, and provides meaningful complaint resolution will require careful—and potentially costly—policy and technical trade-offs by DHS.
The bill sets a clear transparency objective but leaves critical design choices to DHS. It requires an 'active status' verification with a timestamp, but the statute does not define the technical or procedural standard for that verification (for example, whether it requires online authentication against live rosters, the latency tolerance for 'active' status, or the anti‑tampering controls for badges).
Those gaps create implementation variability: agencies might adopt robust, real‑time authentication for urban checkpoints but choose slower or batched verification for remote operations, producing uneven public experience.
Officer safety and operational-security risks are the other major unresolved area. The statute lacks an explicit exemption for undercover work, consensual-monitoring operations, or other sensitive deployments.
Agencies must reconcile the visibility mandate with existing operational practices or face either compliance failures or increased operational risk. The complaint mechanism requirement also omits critical procedural details: it does not set standards for triage, linkage to internal affairs processes, timelines for acknowledgment or resolution, or protections against frivolous or abusive complaints.
Without clear procedural requirements, agencies could end up with a public-facing intake that raises expectations but fails to deliver consistent investigative follow-through.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.