H.R.5007 directs the Director of U.S. Immigration and Customs Enforcement to produce a public report within 30 days of enactment and every quarter thereafter listing three core aggregates for the prior quarter: arrests, detainees in DHS custody, and deportations. For each aggregate the report must include the share of those individuals who were convicted of a state or federal criminal offense and the share in four internal categories labeled ICE Threat Level 1, 2, 3, or not designated.
The bill matters because it converts routinely collected operational figures into a mandated, published oversight dataset and attaches categorical crime‑threshold definitions to those figures. That creates a predictable flow of data for Congress, advocates, researchers, and journalists — while also raising implementation questions about data definitions, denominators, classification consistency, and privacy safeguards that agencies will need to resolve quickly.
At a Glance
What It Does
The bill requires ICE to publish, on its website, a quarterly report (first report due within 30 days of enactment) listing total arrests, detainee counts, and deportations from the prior quarter, with percentages of convicted individuals and breakdowns by four ICE threat‑level categories. It defines the threat categories by conviction type and sentence length.
Who It Affects
Directly affects U.S. Immigration and Customs Enforcement and the Department of Homeland Security’s data and public‑affairs offices; it also impacts local agencies and courts that supply conviction and custody information to ICE. Secondary audiences include congressional oversight staff, civil‑society organizations, journalists, and researchers who use immigration enforcement data.
Why It Matters
By tying public reporting to internal threat‑level labels and conviction thresholds, the bill standardizes a metric set that has previously been unevenly disclosed; that can change oversight dynamics and media narratives about enforcement priorities. It also places an operational burden on ICE to reconcile conviction records with custody and removal workflows on a recurring timetable.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill sets a simple deliverable: a publicly accessible report about ICE enforcement activity for the immediately preceding quarter. ICE must deliver the first report within 30 days of the law taking effect and then produce the same report every quarter.
Each report must contain three headline counts — arrests, number of individuals in DHS custody, and deportations — and for each count the report must show the percentage who had criminal convictions and the percentage falling into four internal threat categories.
Those threat categories are not generic labels; the statute defines them by conviction type and punishment length. A Threat Level 1 offender is someone convicted of an aggravated felony or convicted of two or more offenses punishable by more than one year.
Threat Level 2 covers either a single offense punishable by more than one year or three or more offenses punishable by less than one year. Threat Level 3 is intended to cover offenses punishable by less than one year, though the statutory text contains a drafting error that misnames that definition (see below).The bill also requires ICE to post the report on its public website.
It does not require line‑level datasets, individual identifiers, or case‑by‑case narratives; the deliverable is aggregate percentages and totals. Because the statute attaches specific legal definitions to the threat levels, ICE will need to map conviction records to those definitions on a recurring schedule, which intersects with state court records, federal convictions, and ICE’s internal classification processes.Operationally, ICE will have to determine which custody and removal actions map to the statutory aggregates (for example, whether administrative arrests by officers in the field, transfers from local jails, or re‑arrests during removal proceedings all flow into the same 'arrests' count).
The law is silent on some of those details, so ICE will need to adopt internal reporting rules or guidance to ensure the quarterly figures are consistent and defensible. Finally, the statute mandates public posting but does not create a separate inspection or audit mechanism; enforcement relies on transparency and legislative oversight rather than private rights of action.
The Five Things You Need to Know
The bill requires ICE to publish a report on its website within 30 days of enactment and quarterly thereafter covering the immediately previous quarter.
Each report must include three totals — arrests, detainees in DHS custody, and deportations — and for each total the percentage convicted of a state or federal crime.
For each aggregate, ICE must also report the percentage of individuals in four categories: ICE Threat Level 1, 2, 3, and 'not designated', with statutory definitions tied to conviction type and sentence length.
Threat Level 1 is statutorily defined to include aggravated felonies or two or more offenses punishable by more than one year; Threat Level 2 and 3 are tied to single offenses punishable by more than one year, or offenses punishable by less than one year with numeric thresholds.
The statutory text contains a drafting inconsistency: the provision intended to define Threat Level 3 repeats the label 'ICE Threat Level 2 Offender,' creating ambiguity that ICE or Congress will need to resolve.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Quarterly reporting requirement and timing
This subsection sets the cadence: the first report is due within 30 days of enactment and subsequent reports are due every quarter, each covering the immediately preceding quarter. Practically, that forces ICE to stand up a quarterly production pipeline and schedule for collating counts and conviction mappings, not a one‑off disclosure.
Required aggregates: arrests, detainees, deportations
The bill mandates three headline counts—total arrests, total detainees in DHS custody, and total deportations—for the prior quarter. Agencies must decide how to reconcile different operational definitions (for example, field arrests versus transfers from state jails) to produce consistent quarterly totals and to document those choices for transparency.
Percentage breakdowns by conviction and ICE threat levels
For each aggregate, ICE must report the percentage of individuals with criminal convictions and the percentage in four ICE threat categories. That requires matching custody and removal records to conviction data, including conviction dates and statutory offense classifications, and then applying the statute’s sentence‑length thresholds to classify defendants.
Public publication on ICE website
The report must be posted on ICE’s public internet site. The statute does not require a data download or machine‑readable format, nor does it require archival retention beyond the publication mandate; ICE will set the format and location unless further guidance is issued.
Statutory definitions of ICE Threat Levels (with drafting error)
This subsection defines the three threat levels by conviction type and sentence length—aggravated felonies and multi‑offense thresholds for Level 1, single >1‑year offenses and multi‑misdemeanor thresholds for Level 2, and <1‑year offenses for Level 3. The text, however, mislabels the Level 3 definition as 'ICE Threat Level 2 Offender' (a drafting mistake). That naming error creates legal ambiguity about which label controls and will likely require corrective amendment or administrative interpretation.
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
- Congressional oversight committees — gain a standardized, recurring data feed that supports oversight, hearings, and comparative analysis of enforcement activity.
- Civil‑society and legal aid organizations — receive regular, publicized aggregates they can use to monitor enforcement trends and prioritize advocacy, litigation, or client outreach.
- Researchers and journalists — obtain a predictable, government‑published dataset that can be tracked over time to analyze enforcement patterns and geographic or policy impacts.
Who Bears the Cost
- U.S. Immigration and Customs Enforcement — must develop and maintain the data‑collection, classification, and publication processes on a recurring schedule, creating an operational and compliance burden.
- Department of Homeland Security components and state/local record providers — will need to deliver reliable conviction and custody data to ICE on time, which may require staff time or system changes.
- Detainees and counsel — face potential privacy risks from more granular public characterization of enforcement cohorts if ICE expands disclosure beyond aggregates, and may see shifting classification practices affecting case narratives.
Key Issues
The Core Tension
The bill pits the value of routine public transparency against the practical and privacy costs of producing standardized enforcement statistics: increased disclosure improves oversight and public understanding but forces ICE and partner agencies to make difficult classification choices, creates the risk of data‑driven gaming of categories, and raises concerns about how much enforcement detail should be publicly linked to individual cases.
The bill creates transparency but leaves key technical choices unresolved. It prescribes aggregates and categorical definitions but does not define fundamental operational mapping rules: what counts as an 'arrest' for quarterly totals, how to handle convictions entered after custody begins, how to treat plea agreements or sealed convictions, or how to reconcile federal and state sentencing calculations.
Those gaps matter because small definitional choices can materially change the reported percentages and the resulting public narrative.
The statute ties its categories to conviction‑based thresholds but does not specify the denominator (for example, whether the 'percentage convicted' is of those arrested, those detained, or those deported) beyond saying 'for paragraph (1) through (3)' — an ambiguity that could produce inconsistent reporting across the three aggregates. The drafting error in the Threat Level 3 label compounds interpretive risk: absent correction, ICE may need to issue an administrative interpretation or Congress may have to pass a technical fix to prevent litigation or confusion.
Finally, the law mandates publication but does not require machine‑readable releases, independent validation, or data retention standards — all of which affect the usefulness of the reporting to oversight actors.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.