AFCARS and NCANDS: federal child welfare data reporting

Reference article · 6 min read

Every title IV-E agency feeds two federal data streams out of the same case management system. AFCARS carries foster care, adoption, and guardianship assistance records, is required by statute and regulation, and has financial penalties attached to poor data quality. NCANDS carries child maltreatment report and investigation records and is voluntary in form, though the consequences of submitting late, partial, or unexplainable data are real. Both are assembled from fields caseworkers enter during ordinary daily work, which makes data quality a casework and training problem at least as much as a technical one.

Program managers usually confront this material at one of two moments: a federal error or assessment report comes back with problems to correct, or a new system is being procured and a vendor asks which version of the file specification to build to. What follows covers what each stream requires, how the elements trace back to screens, and what to fix first.

AFCARS: scope, periods, and penalty exposure

AFCARS is administered by the Children's Bureau within the Administration for Children and Families. Title IV-E agencies, including states, the District of Columbia, Puerto Rico, and tribes operating approved title IV-E plans, submit case-level records on children in out-of-home care under the agency's placement and care responsibility, and on children with title IV-E adoption or guardianship assistance agreements.

• Report periods. The federal fiscal year is split into two report periods, October through March and April through September, with submissions due a set number of days after each period closes. The regulations also govern how and when a corrected resubmission may be filed. Confirm current deadlines against the Children's Bureau's published guidance rather than institutional memory.
• Error standards. Compliance is expressed as error rates on specified elements, plus internal consistency checks that compare elements against one another within a record. A file that exceeds the threshold on the identified elements is out of compliance for that period.
• Penalties and correction. Penalties are assessed against title IV-E funds. The regulations provide a correction period, and an agency that repairs and resubmits within it can generally avoid or reduce a penalty. Missing the correction window, rather than the original error, is usually what costs money.
• Which version. The AFCARS element set has been revised more than once in recent years, including changes affecting elements related to the Indian Child Welfare Act, and further rulemaking is possible. Do not let a procurement document say "current AFCARS" without naming the effective rule.

NCANDS: voluntary in name only

NCANDS collects data on maltreatment reports, screening decisions, investigation or assessment dispositions, maltreatment types, victim and perpetrator characteristics, risk factors, and services provided. Most agencies submit a case-level child file plus an agency-level file covering counts the case-level file cannot carry.

Submission is not compelled by a fiscal penalty the way AFCARS is. It matters anyway. NCANDS is the source for the national child maltreatment reporting the Children's Bureau publishes, it sits alongside CAPTA state grant reporting expectations, and it supplies safety measures used to assess agency performance. An agency that does not submit clean data is declining to put its own evidence on the record.

Mapping elements to the screens caseworkers use

The single most useful artifact a program office can maintain is a living crosswalk from each federal element to the exact screen, field, and code value that populates it, plus the business rule that derives it when no field maps directly. Keep the derivation logic in the crosswalk, not only in code.

Removal date, removal reasons, placement setting and placement history, permanency goal, caretaker family structure, parental rights termination dates, discharge reason and date, and adoption or guardianship finalization are the recurring trouble spots on the AFCARS side. On the NCANDS side, report source, response time, disposition, and the relationship between victim and perpetrator generate the most inconsistency. Most of these are entered by a worker under time pressure, often in a free-text or optional field that the system permits to be blank. Where an element is federally required, the entry screen should require it, validate it against the federal code list, and explain in plain language why it is being asked.

Generating, testing, and correcting files

Treat file generation as a routine operational process rather than a semiannual event.

1. Run the extract monthly against production data, not only before the deadline, so error trends surface while the period is still open.
2. Validate locally before submission, using the federal edit checks and your own additional rules, and produce an error report broken out by county, office, and worker so correction can be assigned.
3. Track each error to its cause: missing entry, wrong code, a conversion defect from a prior system, or a genuine policy question about how a situation should be coded.
4. Correct historical records deliberately. Fixing a case record today does not change a file already submitted, so identify which prior periods are still eligible for resubmission and which corrections change only future extracts.
5. Keep a written record of coding decisions, because the same ambiguous scenario will recur and inconsistent answers produce inconsistency errors.

How CFSR and the CFSP draw on the same data

The Child and Family Services Review statewide data indicators are calculated from these submissions. Measures of maltreatment recurrence draw on NCANDS. Measures of maltreatment in foster care combine NCANDS victim data with AFCARS foster care records. Permanency, re-entry, and placement stability measures come from AFCARS. The Child and Family Services Plan and its annual progress report describe improvement work against those same numbers.

The practical consequence is that data quality work is performance work. A removal date entered late or a discharge reason coded loosely does not only create an error line, it moves a measure the agency will be held to, and it may push the agency into a program improvement plan on the strength of a recording problem rather than a practice problem.

What to ask vendors and require in the contract

• Name the specific federal rule and file specification version the system must meet, with the effective date, and state who bears the cost of adapting to a future revision.
• Require the crosswalk as a deliverable: element to screen to field to code list to derivation logic, maintained as the system changes.
• Require configurable validation, so new edit checks can be added without a code release.
• Require an error report usable by supervisors, showing the case, the element, and the reason, routed to the office responsible.
• Ask how historical data will be handled during conversion, and what the vendor's approach is to resubmission for prior periods.
• Align expectations with CCWIS requirements, including the data quality plan and automated support for federal reporting, if the system is being built or modernized under that framework.

Requirements in this area change through rulemaking and guidance. Confirm current elements, thresholds, deadlines, and penalty provisions with the Children's Bureau, and involve agency counsel before relying on any specific figure.

HQT works with state and local agencies on data engineering, reporting pipelines, and systems integration for regulated program reporting.

Frequently asked questions