The Transparency of Migration Act directs the Secretary of Homeland Security and the Secretary of Health and Human Services to publish specified information about individuals unlawfully present in the United States who are apprehended by U.S. Customs and Border Protection (CBP) or processed through HHS facilities. The statute requires weekly updates on daily counts, countries of origin, ages and genders, the States to which people are released or transferred, and the number and types of criminal convictions, if any.
This is a narrow, operational statute rather than a standalone immigration-policy change: it compels public reporting. That shifts decision-making from internal agency reporting to continuous public visibility, with predictable consequences for privacy, agency workload, intergovernmental coordination, and how data are used by journalists, researchers, and policymakers.
The bill is silent on data format, aggregation level, definitions for key terms, funding, and privacy protections — all of which will determine how the requirement actually plays out in practice.
At a Glance
What It Does
The bill requires DHS and HHS to make specified migration-related information available to the public on their departmental websites and to update that information weekly. Covered information includes daily counts, country of origin, age and gender breakdowns, destination States, and criminal-conviction counts and types for people processed by CBP or HHS facilities.
Who It Affects
Primary obligations fall on DHS (including CBP) and HHS (including ORR and HHS-run facilities). Secondary audiences and users include state and local governments receiving released individuals, researchers, journalists, immigration advocates, and law enforcement entities that rely on public data.
Why It Matters
Public, frequent reporting creates a new transparency precedent for operational migration data and can influence policy and public debate in near-real time. How agencies implement the requirement — aggregation level, definitions, redactions, and update processes — will determine privacy risks, administrative costs, and the usefulness of the data for planning and oversight.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill imposes a simple statutory duty: both the Secretary of Homeland Security and the Secretary of Health and Human Services must publish certain information about people unlawfully present in the United States who are processed by CBP or HHS facilities. ‘‘Processed’’ is drawn broadly by the bill to include individuals apprehended and either detained or released by CBP and people who pass through HHS facilities. The law does not alter immigration statuses, detention authorities, or release rules; it only prescribes public reporting of a set list of data points.
The required data elements are fivefold: a daily headcount, country of origin, age and gender breakdowns, the State to which each person was released or transferred, and whether individuals have criminal convictions — including counts and types. The statute mandates weekly updates to these data on the agencies’ public websites.
The bill does not require posting personally identifying information, nor does it specify whether the data should be published as aggregate tables, machine-readable files, or narrative summaries.Several practical gaps stand out in the text. The measure does not define ‘‘types of criminal convictions’’ (for example, whether convictions are U.S. federal, state, foreign, or pre-conviction charges), it does not instruct agencies how to classify ‘‘country of origin’’ when records contain multiple countries or missing data, and it does not say whether reported ‘‘daily numbers’’ are snapshots, cumulative totals, or net changes.
The absence of definitions forces agencies to create operational standards or risk inconsistent public releases between DHS and HHS.Because the bill requires public publication but allocates no funding or enforcement mechanism, agencies will need to absorb the administrative and IT costs into existing budgets. That includes building or repurposing web pages, establishing data pipelines from detention and intake systems, applying privacy reviews, and coordinating with states that receive released individuals.
The combination of mandatory public reporting and minimal statutory guidance means the real-world impact will hinge on choices agencies make during implementation.
The Five Things You Need to Know
The bill mandates weekly public posting on DHS and HHS websites of specified migration data—no other agencies are named.
It applies to individuals ‘‘unlawfully present’’ who are apprehended by CBP and detained or released, and to those processed through HHS facilities; the term remains undefined in the text.
Required data elements are: daily counts, country of origin, ages and genders, States to which individuals are released or sent, and the number and types of criminal convictions, if any.
The statute is silent about whether data must be published in aggregate only, whether individual identifiers are permitted, or how to treat missing or ambiguous records.
The bill includes no funding provision, enforcement mechanism, or specification of definitions (for example, what counts as a ‘‘type’’ of criminal conviction).
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
This section provides the Act’s short name, the ‘‘Transparency of Migration Act.’
Who must publish and which populations are covered
Section 2(a) creates the core obligation: the Secretary of Homeland Security and the Secretary of Health and Human Services must make certain information available on their departmental websites. The provision applies to ‘‘individuals unlawfully present’’ who are either apprehended by CBP and detained or released, or who are processed through HHS facilities. Practically, this places responsibility on agency components that run or receive people at the border (CBP) and on HHS units that house or process vulnerable populations (for example, ORR).
Specified data elements to be published
This subsection lists five categories of information the agencies must publish: (1) the daily number of affected individuals; (2) countries of origin; (3) ages and genders; (4) States where individuals were released or sent; and (5) counts and types of criminal convictions, if any. The section is prescriptive about content but not about format, granularity, or definitions—leaving agencies to decide classification rules and presentation formats.
Update frequency
Section 2(c) requires weekly updates to the posted information. The text does not define ‘‘weekly’’ (for example, which day of the week or a rolling 7‑day window), nor does it require historical archives or machine-readable releases. Those operational choices will determine the usability of the data for trend analysis and oversight.
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 and policymakers—gain more frequent, centralized public data useful for monitoring enforcement trends and crafting legislative responses.
- Researchers, journalists, and advocacy organizations—obtain faster access to operational migration statistics that support analysis, reporting, and evidence-based advocacy.
- State and local planners—receive regular information about inflows and transfers to help allocate shelter, health, and social services resources.
Who Bears the Cost
- DHS (including CBP) and HHS (including ORR)—must build or adapt data pipelines, web pages, and privacy reviews with no appropriations provided, increasing staff and IT workloads.
- Migrants and asylum seekers—face elevated privacy and safety risks if data reveal locations, small-group movements, or criminal histories without appropriate redactions; vulnerable populations (including minors) could be exposed.
- State and local agencies—may face public scrutiny, political pressure, and additional administrative burdens when named as destinations in publicly released data.
Key Issues
The Core Tension
The central tension is between a public interest in near-real-time transparency about migration operations and the competing need to protect individual privacy, safety, and operational integrity; the bill forces agencies to choose how much clarity to give the public at the expense of confidentiality and administrative capacity.
The bill’s promise of transparency collides with several practical and legal constraints. First, privacy and safety risks are acute: publishing destination States and criminal-conviction information can reveal patterns that identify facilities, operators, or small populations, which raises statutory Privacy Act concerns and risks to individuals (including trafficking or retaliation).
The statute contains no guidance on redaction, aggregation thresholds, or protections for minors; agencies will need to reconcile publication obligations with existing confidentiality duties and child-protection norms.
Second, the measure leaves key operational definitions and formats unspecified. Without definitions for ‘‘unlawfully present,’’ ‘‘types of criminal convictions,’’ or how to count ‘‘daily numbers,’’ agencies can reach different conclusions about scope and counting rules.
Those choices affect comparability across DHS and HHS releases and across time. The absence of funding or enforcement language increases the chance of uneven implementation: one agency could produce detailed machine-readable tables while the other posts cursory summaries, undermining the bill’s stated goal of transparent, usable public data.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.