Federal and state claims, 2016–February 28, 2026 · USD millions
Source: HHS ASPE, June 1, 2026, Table 1. Reported claims may undercount spending. This comparison does not show total allocated funding or project success rates.
Read the project numbers with the right denominator
HHS published a June 2026 issue brief on Comprehensive Child Welfare Information System (CCWIS) implementation using project data through February 28, 2026. The ASPE summary reports 75 projects across 49 states and territories: 41 new CCWIS builds and 34 transitional systems. Twenty-three projects were fully operational; eight closed without becoming operational. Only about 10 percent of new builds were operational at the snapshot date. Federal and state claims totaled approximately $2.28 billion, with another $5.86 billion allocated or approved to spend. Claimed amounts are not the same as total costs, and most claims went to transitional systems.
These figures show slow progress. They do not establish that nine in ten projects failed: active projects may be unfinished, project ages differ, and new builds should not be conflated with transitional systems. HHS ASPE: CCWIS implementation findings.
Governance is part of the delivery system
The brief identifies organizational barriers alongside the technical work: planning, leadership, workforce capacity, funding, and alignment between program and IT governance. This supports a practical interpretation: buying software cannot substitute for the ability to make and sustain program decisions. It does not prove that technology is irrelevant or establish a controlled ranking of which factor caused each delay. Child welfare delivery includes difficult AFCARS reporting, Title IV-E eligibility, court interfaces, and data conversion. A strong governance model makes those dependencies visible and assigns someone authority to resolve them.
A weak one leaves requirements disputes to contract correspondence and repeated escalation. Program directors should therefore treat governance as something to design and test—not a steering committee name on a slide.
California: evaluate readiness, not just the calendar
California's CWS-CARES remains an important implementation case. The March 2025 Legislative Analyst's Office review describes a project approved in January 2013 to replace the federally noncompliant CWS/CMS. It records an approved baseline of approximately $1.7 billion, excluding additional project-related costs—not a newly measured September 2026 total. LAO budget analysis.
The state's August 3, 2026 bulletin continued to identify October 26, 2026 as the planned Version 1 go-live. The delivery approach had changed: April 2026 Senate materials state that a production simulation for users in all counties replaced the proposed county pilot. It is therefore inaccurate to describe a five-county live pilot as having launched in August. CWDS bulletin archive, Senate budget review.
Those facts sharpen the readiness question: can simulation results demonstrate realistic caseworker operations, reconciled interfaces and converted records, and a safe continuity plan? A target date is not an accomplished rollout. Iterative delivery should be judged through working releases and user evidence rather than its methodology label.
Why this matters beyond child welfare
The coordination problem extends beyond child welfare. Medicaid eligibility modernization, unemployment insurance replacement, and benefits interoperability all connect program rules to software and interagency data exchange. These programs should not be assumed to have identical causes of delay, but they share dependencies that procurement alone cannot resolve. Federal reporting defines part of the scope; agencies and courts control interfaces; budget and solicitation calendars constrain delivery. The SNAP director or child welfare administrator may not control the technology team, while the CIO may not be authorized to interpret a program rule.
Every unresolved requirement, scope decision, and release acceptance then crosses that boundary. Our assessment is that explicit joint decision rights reduce avoidable rework. States should test that proposition by measuring decision turnaround and requirement churn, not by assuming a particular organizational chart guarantees success.
Iowa and the value of early program involvement
Iowa's VISION program offers a useful example of early collaboration. Iowa HHS describes a contract with Google to replace the long-serving FACS mainframe, with direct input from child protection workers, and links its partnership announcement with ACF. This is evidence of a delivery approach and stated goals—not yet proof of improved outcomes or a guaranteed schedule. Minnesota DCYF separately describes 2025–26 planning for replacement of SSIS and phased implementation beginning in 2027, with county and Tribal involvement. That is a published plan, not evidence that it has adopted Iowa's model. Minnesota project timeline. The same readiness questions apply: who owns the program decisions, when do workers validate the design, and how will federal technical assistance be integrated with state accountability?
Partnership announcements establish an approach; status reports and user evidence show whether it is working. Maintaining that alignment across administration, staff, and vendor changes is as important as establishing it at kickoff.
Turn the lessons into procurement conditions
For program directors and CIOs, the operational projects in the federal record are an opportunity to learn, not a promise that copying a vendor or delivery method produces the same result. Ask peer states what was validated before procurement, which requirements changed, who resolved disagreements, and how they retained staff through implementation. Planning quality means a reliable starting point and controlled learning, not a demand that every requirement remain frozen for years. Governance maturity means shared authority where scope and resource conflicts actually occur. Workforce continuity means retaining institutional knowledge rather than expecting it to reappear in vendor deliverables.
Program-IT alignment means shared service outcomes, not separate budget presentations to the same oversight committee. Those conditions are investments states can make before a solicitation opens and continue to improve after launch.
Five decisions to settle before award
Before committing to the next delivery phase, program and technology leaders should be able to answer these questions together.
- Name joint decision owners. Give program and IT leaders documented authority over scope, funding, data definitions, and release decisions; set a deadline for escalating unresolved conflicts.
- Validate work with caseworkers. Walk through placement, eligibility, court reporting, and emergency access using realistic cases, including exceptions—not only a vendor demonstration.
- Demand evidence at each release gate. Review migrated-data reconciliation, integration testing, training completion, open defects by severity, and a rehearsed continuity plan.
- Protect institutional knowledge. Fund state product owners and subject-matter experts through implementation and operations, with an explicit handover plan when staff or vendors change.
- Track outcomes after launch. Compare time spent entering a case, duplicate records, reporting corrections, unresolved tickets, and worker confidence against a pre-launch baseline.
Sources and further reading
- California LAO: March 2025 baseline
- Minnesota DCYF: modernization phases
- California Senate: April 2026 production simulation change
- HHS ASPE: CCWIS implementation findings
- California: CWS-CARES user resources
- California Senate: May 2026 child welfare budget review
- Iowa HHS: VISION program
For Spartan X, this is where program execution and engineering meet: translating child welfare requirements into a delivery plan with clear ownership, testable milestones, and systems that caseworkers can use.
