The Question Behind the Notice: Who Gets to Use TANF Data?

The subject of this series is a specific federal records system: the Office of Family Assistance system maintained within the Administration for Children and Families, System No. 09-80-0375, “Temporary Assistance for Needy Families (TANF) Data.” The immediate question is how far a 2026 modification to that system-of-records notice can extend the use of information collected through a welfare program. To answer it responsibly, a reader must keep four questions separate: what data the system contains, what the notice says the data may be used for, when a new use is scheduled to take effect, and whether the proposed use is lawful and has actually occurred.

That separation matters because the same document can be read in two very different ways. It can be an administrative description of how the Department of Health and Human Services wants to conduct program-integrity work. It can also be the focal point of a dispute over federal authority, state autonomy, privacy, and cross-agency data matching. The notice establishes the first kind of fact. It does not, by itself, settle the second.

A welfare data system with federal reach

TANF is a cash-welfare block grant. The official notice describes states, certain territories, and Tribal programs as receiving federal funds and flexibility to design and operate assistance programs. Those grantees also have statutory duties to collect core information about people receiving TANF assistance. The federal government therefore occupies an important but not exclusive position: local programs generate and report much of the information, while ACF maintains a system used for oversight, reporting to Congress, and research.

The system is broader than a list of current payment recipients. The notice covers members of families who received assistance in any month, as well as members of families who no longer receive TANF. For reporting purposes, the family can include a noncustodial parent where required, a parent or caretaker relative, minor siblings, and people whose income or resources count in determining eligibility or the amount of assistance. A record associated with a welfare case can therefore describe a household and its relationships, not only the person who received a payment last month.

The information is correspondingly varied. Grantees report family-level details such as location, household size, assistance, and case number. Adult and child records can include Social Security numbers, dates of birth, citizenship or immigration status, race, employment or education information, work-activity hours, and income. These examples are not an exhaustive database schema, but they show why a change in the system's sharing boundary has consequences beyond routine administration. The data can identify people, describe eligibility, and carry information about family circumstances and legal status.

The California Department of Justice, announcing the lawsuit, presented the program's scale as part of the stakes: the office said TANF distributes more than $16 billion in grants each year and serves about 350,000 California families each month. Those figures come from a party to the litigation, so they should be treated as an attributed description rather than an independently established count here. The broader point does not depend on accepting every figure. TANF is a large public program whose records are produced in the course of delivering assistance and then held for federal administrative purposes.

A notice that changes the boundary

A system-of-records notice, or SORN, is not just a press statement about privacy. It is a structured public description of a records system. It identifies the authority the agency invokes, the system's purposes, the people and records covered, the sources of information, the circumstances in which records may be disclosed, the way records are retrieved, and the procedures for access or correction. Those fields answer different questions. A stated purpose is not the same thing as a recipient category; a retrieval key is not the same thing as a legal permission; and a safeguard is not the same thing as a limit on agency authority.

The June 23, 2026 modified notice changes several of those fields together. It adds 42 U.S.C. 1320b-7 and 8 U.S.C. 1373 to the authority section. It describes a new purpose of confirming grantee compliance through program-integrity reviews, audits, fraud investigations, and monitoring. It also includes checking data accuracy, work participation and time limits, and the citizenship or immigration status recorded in Department of Homeland Security systems. The notice adds other HHS records and other government agencies or entities to the categories of possible verification sources.

The most consequential change is routine use 10. In the notice's language, records may be disclosed to another federal or grantee agency or entity engaged by ACF to assist with program-integrity reviews or projects. The notice gives DHS and TANF program administrators as examples and says the purpose can include verifying citizenship or immigration status. In plain terms, the document describes a path by which information held for TANF administration could be checked against information held elsewhere, with records disclosed to an entity participating in that integrity work.

That is an important expansion in the system's described architecture, but the wording must be handled precisely. The notice says routine uses set out circumstances in which ACF may release information without the individual's consent, and it also says each proposed disclosure will be evaluated to ensure that it is legally permissible. Thus, the notice records an intended disclosure framework. It does not prove that DHS received a particular file, that a matching project ran, or that every disclosure fitting the description would satisfy all other legal requirements.

flowchart LR A["TANF grantee reporting"] --> B["ACF/OFA TANF Data system 09-80-0375"] B --> C["Verification information from other HHS, federal, or state sources"] C --> D["Disclosure path described by modified routine use 10"] D --> E["Engaged federal or grantee entity, such as DHS or a TANF administrator"] B -.-> F["Multistate legal challenge"] D -.-> F F --> G["Questions of authority, procedure, and implementation"]

The diagram is deliberately a map of the notice's described path, not a claim that the path was completed. That distinction is the central discipline for reading this dispute. A SORN can disclose how an agency proposes to organize a system and the uses it believes are available. Whether Congress authorized those uses, whether the agency followed the required process, and whether the described activity took place are separate inquiries.

The timeline and the evidence problem

The effective date adds another layer. The June notice made the modification effective on publication except for subparagraph (a) under routine use 1 and the new routine use 10, which were assigned a later effective date. An August 7 Federal Register notice moved those provisions' effective date to September 1, 2026. A later first-party notice published August 20 moved them again, this time to September 30, 2026. As of September 13, the latest supplied notice therefore describes routine use 10 as scheduled for September 30, not as a provision that should automatically be treated as already operative.

The lawsuit developed alongside that administrative timeline. According to the public case record, twenty-three states and the District of Columbia filed State of New York v. Administration for Children and Families in the U.S. District Court for the District of Columbia on August 3. The plaintiffs sought declaratory and injunctive relief. An amended complaint filed August 17 added DHS and its Secretary as defendants and expanded the challenge to include a September 2025 data transfer and disclosure policy. A renewed motion for a preliminary injunction and a stay was filed August 25; the federal defendants filed an opposition on September 11; and a hearing was scheduled for September 24. The record identifies the case as ongoing and reports no prevailing party or relief granted.

The states' legal theories are also claims to be examined, not conclusions to repeat as fact. The California DOJ statement says the SORN exceeds statutory authority under the Administrative Procedure Act, is arbitrary and capricious, violates the Computer Matching Act because no matching agreement exists, and imposes an inadequately noticed condition on TANF funds under the Spending Clause. The case record summarizes related APA, Spending Clause, notice-and-comment, disclosure, and state-burden arguments. The supplied material does not include a merits ruling that accepts or rejects those theories.

This difference in source type is not a technical footnote. The Federal Register notices are the strongest sources for what the agency published, the fields it changed, and the dates it set. The California statement is useful for understanding how a plaintiff frames the stakes and the legal challenge, but it is advocacy by a party. The case record is useful for filing dates, motions, amendments, and the current docket posture, but a docket entry is not a judicial holding. None of these sources, alone or together, establishes the full history of actual data transfers, the contents of any matching agreement, the accuracy of verification results, or the eventual court decision.

The practical starting point, then, is neither “the government may share anything it wants” nor “the notice proves an unlawful transfer.” It is a more specific question: what does the TANF Data system contain, how is that information assembled, and which part of that structure would make the new verification path possible? Only after that data model is clear can the notice's proposed boundary—and the arguments over it—be evaluated without confusing administrative design with legal authority or implementation.

References