The Boundary in One Model: Administration, Verification, Disclosure

The subject remains the TANF Data system and the modified notice that describes how ACF may use and disclose it. The task here is to connect the system's contents to the proposed verification path without confusing a record category with a recipient, a retrieval key with a completed match, or an agency allegation with a court ruling. The useful judgment is simple but demanding: every claim about the system should be assigned to the part of the path it actually describes.

One record path, several different questions

The system can be represented as a path that begins with a TANF grantee and ends, potentially, with an outside entity involved in program-integrity work. The path is not a single permission and not a single event. It contains several transitions:

  1. A state, territory, or Tribal grantee reports information about a TANF family or individual to ACF.
  2. ACF maintains that information in System No. 09-80-0375, the TANF Data system.
  3. ACF locates a record using a case number or Social Security number, depending on the record stream.
  4. ACF obtains or uses verification information from the grantee, another HHS record, or another federal or state agency or entity assisting with a program-integrity review or project.
  5. If the stated conditions are met, the modified notice describes a possible disclosure to an engaged federal or grantee agency or entity, such as DHS or a TANF program administrator.

The first two steps describe the system's administrative foundation. The third describes an operating interface: how a record is found. The fourth introduces a second source of information. The fifth is a disclosure route. Treating all five as “sharing” erases the point at which a new question arises.

The difference is visible in the evidence. The modified SORN directly describes the categories, sources, retrieval methods, purpose, and routine use. It supports a statement that the agency has written a broader verification path into the system's public description. It does not support a statement that a particular family's record followed every step. The notice is evidence of design and stated authority; it is not a transfer log.

A second distinction concerns direction. A grantee's report flows to ACF because the federal system is built from information that grantees collect and submit. Verification information may come from another source into the federal system. Routine use 10 describes disclosure from the system to an entity engaged by ACF. Those directions are related but not interchangeable. An agency can be a source of information for one part of a project and a recipient of a disclosure in another, but the notice does not say that every agency occupies both roles or that every project uses the same fields.

flowchart LR A["TANF grantee report"] --> B["ACF/OFA TANF Data system"] B --> C["Retrieve by SSN or case number"] C --> D["Use or obtain verification information"] D --> E["Routine use 10 describes possible disclosure"] E --> F["Engaged federal or grantee entity"] B -.-> G["Security, access, and retention controls"] E -.-> H["Authority and procedure questions"] F -.-> I["Actual implementation not established by notice alone"]

The map is intentionally layered. Security controls sit around custody; they do not become a new recipient. A retrieval key makes information findable; it does not become a purpose.