From June to September: The SORN's Effective-Date Lifecycle

The TANF Data system has two timelines that must be read together but not merged: the administrative lifecycle of the modified system-of-records notice and the procedural lifecycle of the lawsuit challenging it. This chapter traces both through the supplied record so the reader can say which provisions were scheduled to operate, what the states and federal defendants had filed by September 13, 2026, and what remains unknown. The central discipline is to treat a date, a filing, and a court result as different kinds of events.

The notice changed state more than once

The June 23 modified Federal Register notice set a general effective date of publication for the changes to System No. 09-80-0375. It carved out two items for a later date: subparagraph (a) under routine use 1 and the new routine use 10. The notice said that the new routine use would become effective thirty days after publication, subject to the notice's stated timing and comment process. In other words, the system description changed on June 23, but the disclosure-related provisions did not enter the same effective-date state as every other modification.

That carve-out matters because routine use 10 is the provision that describes disclosure to another federal or grantee agency or entity engaged by ACF to assist with a program-integrity review or project. If the new route is not yet effective, the fact that it appears in the published document does not by itself make it an operative basis for a disclosure on an earlier date. The notice's text and the date attached to that text must be read together.

The first later transition came in the August 7 delay notice. It said the modified system had been effective June 23 except for subparagraph (a) under routine use 1 and routine use 10, and moved the effective date of those provisions to September 1, 2026. The notice did not erase the provisions or announce a final decision about their legality. It changed the schedule on which the provisions were to take effect.

A second transition came in the August 20 notice. That notice delayed the effective date of the same provisions again, this time to September 30, 2026. It says the comment period closed August 11. The later notice is the more current first-party statement in the supplied material, so it supersedes the earlier September 1 schedule for purposes of describing the record as of September 13.

This sequence should not be overinterpreted. The supplied notices do not explain why the second delay occurred. They show an administrative decision to move the date, not the reason for it. It would be a mistake to infer from the delay alone that the agency abandoned routine use 10, admitted that it was unlawful, or had already begun using it before the new date. The evidence supports a narrower conclusion: the relevant provisions were published, repeatedly delayed, and most recently scheduled for September 30.