AI Esquire
Menu
Plans from $497/monthBuy Intake AI
Immigration · Government information

DOJ Wants the Whole State to Report. Who Decides What It Knows?

A reporting obligation has two boundaries: who must report, and what they must know before reporting. Change both, and the result is much larger than a revised mailing list. The Justice Department's September 2 announcement concerns the first boundary. Its Office of Legal Counsel says participation in specified federal benefit programs subjects all agencies within a state to immigration-reporting duties, not merely the agencies administering those benefits. But a footnote in the underlying opinion deserves equal attention. It challenges the longstanding threshold for deciding when a government entity actually knows that someone is not lawfully present.

The word Congress used was State

Start with the statutory text. Section 404 of the 1996 welfare-reform law created the reporting framework. Under 42 U.S.C. § 611a, a state receiving the specified Temporary Assistance for Needy Families grant must provide names, addresses, and other identifying information at least four times annually and upon request for individuals the state knows are unlawfully in the United States. The related definition in § 619(5) identifies the states, the District of Columbia, and specified territories. It does not say that State means only the benefits office.

That gives the broad reading a real textual argument. A state accepts the grant; the statute then refers to what the state knows. Reading the same noun to mean the whole sovereign at the beginning of the sentence and one department at the end requires an explanation. Opposition to an administration's immigration policies is not a substitute for supplying one.

The earlier explanation is available. OLC's August 18, 1998 opinion favored the narrower reading based on context, structure, and legislative history. Among its concerns: Congress had specified particular benefit programs, and a government-wide reading would make other reporting provisions largely redundant in practice. It also questioned whether Congress had spoken clearly enough to impose such extensive obligations on grant recipients. That was an interpretive position, not an exemption written into the statute.

The footnote changes the harder boundary

The September 1 opinion withdraws that earlier advice. Its footnote 2 also rejects the view that knowledge requires a formal determination supported by immigration authorities. OLC gives examples including affirmative DHS notice, an admission of unlawful entry and no basis for lawful presence, and immigration records establishing expired or terminated status. It also invokes willful blindness. Those are the opinion's legal positions, not findings about any individual.

The distinction matters because a duty can become dramatically broader without changing its reporting schedule or the information transmitted. Expanding the set of offices covered by a rule increases the number of potential reporters. Lowering the threshold those offices use increases the number of people potentially reported. Lawyers should analyze the two changes separately, even when they appear in the same document.

The historical comparison is concrete. A September 28, 2000 interagency notice required a formal determination subject to administrative review, supported by an INS or EOIR determination. It expressly said that a SAVE response showing no agency record, or a status that made someone ineligible for a benefit, did not itself establish unlawful presence. It also explained that benefits agencies were not being directed to decide lawful presence when that inquiry was unnecessary to determine eligibility.

That notice was doing more than limiting paperwork. It separated possession of immigration-related information from an adequately supported conclusion about that information. The new opinion attacks the threshold, but the underlying distinction remains a serious implementation problem: a record can be authentic and still fail to answer the question for which someone wants to use it.

A data field cannot resolve its own meaning

My concern is not that government agencies must be forbidden to share accurate information. It is that the instruction to report can travel farther and faster than the capacity to evaluate what is being reported. An employee may see an old document, a database result, or a statement recorded by another office. Before that becomes the state's asserted knowledge, somebody must decide whether it is current, complete, and legally sufficient.

A sound implementation would preserve the difference between a missing record, an adverse record, and an unresolved conflict between records. It would not use foreign birth, language, or inability to produce a particular document as a substitute for the statutory conclusion. Nor should a software system silently convert uncertainty into a yes-or-no immigration classification merely because its reporting form requires a binary answer.

These are recommendations for accuracy, not claims that the new opinion expressly mandates a particular software design. They follow from the stakes of the decision. If information is to trigger enforcement attention, the organization should be able to explain its source, the inference drawn from it, the person responsible for that inference, and the route for correction. Otherwise, responsibility becomes dispersed while the consequences remain concentrated on the person named.

There is an uncomfortable incentive problem here. An institution worried about losing funds may prefer an unnecessary report to a missed one. But the person evaluating compliance and the person suffering a mistaken report do not bear the same costs. A reporting system should be designed with that asymmetry in mind, rather than assuming that a larger volume of reports proves better compliance.

Funding conditions need more than a confident announcement

The Spending Clause issue should not be reduced to the assertion that accepting money means accepting anything Washington later demands. In Pennhurst, the Supreme Court explained that conditions on federal funds must be stated unambiguously so a state can knowingly accept them. That principle does not decide this dispute, but it identifies the question: what obligation did Congress actually communicate?

OLC argues that the statutory definition and structure supply adequate notice, and that the condition satisfies constitutional limits concerning coercion and relatedness. That is its conclusion, not a court's resolution of this September opinion. A persuasive challenge would need to engage the statute and funding arrangement, not merely count the years during which the executive branch read the law differently.

DOJ's announcement says the interpretation applies prospectively, protects past reliance on the 1998 position from retroactive penalties, and permits federal agencies to update grant agreements and compliance processes. It also warns that noncompliance could result in loss of program funding. These are consequential signals, but they are not evidence that a particular state's funding has already been terminated.

For counsel advising a government entity, the operative documents matter as much as the press release: the relevant award or agreement, its timing, the implementing agency's instructions, and any applicable judicial orders. The distinction between a legal interpretation and a completed implementation is not an excuse to ignore the opinion. It is how one determines what action is actually required and what can be challenged.

The person at the counter needs a narrower answer

An individual asking whether to approach a public agency is not asking for a seminar on statutory interpretation. They want to know what that office may do with their information. Counsel should resist both categorical reassurance and categorical alarm. This opinion does not support telling every noncitizen to avoid every government service. Nor is its executive-branch form a reason to dismiss it as legally irrelevant.

The useful advice begins with the particular person, program, agency, and record. What information would be supplied? What does it actually establish? Which current instruction governs its use? That inquiry may be slower than repeating a headline, but it avoids turning a broad policy development into an unsupported personal prediction.

The larger lesson is institutional. Government-wide responsibility does not automatically produce government-wide expertise. If the state is going to say that it knows something consequential about a person, it should be able to show how it reached that conclusion.

General legal analysis, not individualized immigration advice. AI Esquire is an attorney-led publication, not an immigration news service. The documents discussed here have different legal roles; implementation and any subsequent judicial review require current, matter-specific research.

Sources and further reading

Primary and industry sources used to support this page. External guidance should be reviewed in context and for your jurisdiction.

  1. DOJ Office of Legal Counsel, reconsideration opinionSeptember 1, 2026. Executive-branch legal advice, including footnote 2 on knowledge; not a judicial holding.
  2. DOJ announcementSeptember 2, 2026. Scope, implementation, prospective application, and potential funding consequences.
  3. 42 U.S.C. § 611aTANF-linked state reporting requirement.
  4. 42 U.S.C. § 619(5)Statutory definition of State.
  5. 1998 OLC opinionAugust 18, 1998, 22 Op. O.L.C. 204. Historical reasoning, now withdrawn.
  6. 2000 interagency implementation noticeSeptember 28, 2000, 65 FR 58301–58303. Historical knowledge threshold challenged by the new opinion.
  7. Pennhurst State School & Hospital v. Halderman451 U.S. 1 (1981), especially page 17. Supreme Court clear-notice principle for federal funding conditions.
The AI Esquire Journal

Read beyond the announcement.

Attorney-led analysis of institutions, technology, and the changing practice of law.

Read the journalAbout AI Esquire