Child Welfare Technology System Implementation Shows Minimal Progress: After 10 years and $2 Billion, Modern Information Systems Are Still Out of Reach

Issue Brief - June 2026

This summary highlights key findings from this study. Readers are encouraged to download the full report for complete details and analysis.

KEY POINTS

• Comprehensive Child Welfare Information System (CCWIS) is the federal framework intended to modernize child welfare systems, but implementation across jurisdictions has been slow and uneven.
• Less than a third of CCWIS projects are operational, with 15 states not yet declaring any new CCWIS projects.
• CCWIS projects have run for six years on average, with wide variation across states. Most projects are still not fully operational after eight years of implementation.
• Total federal and state spending on CCWIS has reached over $2.2 billion since 2016. This excludes projects that have not yet submitted claims to ACF. Total allocated funding - the amount that projects are approved to spend - was over $5.8 billion.
• Transitional projects - legacy systems maintained while CCWIS projects are being completed - represent 85 percent of total claims, at $1.9 billion. New CCWIS builds totaled $313 million in claims.
• The median claim amount for CCWIS projects is $11.2 million, relative to $27.4 million for transitional systems.
• Factors that affect CCWIS project progress include the complexity of technological requirements, organizational readiness for modernization, reliance on transitional systems, and federal processes and requirements. State constraints such as procurement processes, staff capacity, and legal issues, also affect progress.
• There are opportunities to reshape the federal role to better support implementation, including repositioning ACF as an active partner, redefining metrics of success, and modernizing federal guidance.

BACKGROUND

The Comprehensive Child Welfare Information System (CCWIS) is the federal regulatory framework governing how states design and operate child welfare information systems, in place since 2016. It replaced the prior Statewide Automated Child Welfare Information System model, shifting from large monolithic builds to modular, interoperable development. CCWIS is intended to serve as the system of record for child safety, family engagement, service delivery, placement history, and outcomes. It also supports caseworkers, agency accountability, and federal reporting. Despite the potential of CCWIS, data in many states remain fragmented, difficult to access in real time, and underutilized.

States transitioning to CCWIS may continue operating legacy systems - known as transitional systems - which serve as a bridge between the prior models and new CCWIS builds. Federal funds under CCWIS regulations may support both transitional systems and new CCWIS development simultaneously, allowing resources to flow to legacy environments even while modernization is underway.

DATA AND METHODS

The analysis draws on data collected as of February 28, 2026 by an independent contractor, based on formal Advance Planning Document (APD) submissions, status updates, and claims data (form CB-496). Data may undercount actual spending and progress, as some states had not submitted all claims or received APD approvals for completed activities. Findings on barriers to CCWIS implementation are drawn from existing research, author expertise, and input from federal experts overseeing CCWIS at state and federal levels.

LESS THAN A THIRD OF PROJECTS ARE OPERATIONAL, WITH 15 STATES NOTYET DECLARING ANY NEW CCWIS PROJECTS

Since 2016, 49 states and territories have worked on 75 total projects - 41 new CCWIS builds and 34 transitional systems. Three states (Alaska, Massachusetts, Nebraska) have no active projects; 12 have only transitional systems with no new CCWIS build underway. Of all 75 projects, only 23 (30 percent) are fully operational, and eight were closed without ever becoming operational. Among new CCWIS builds specifically, only 10 percent are fully operational. See Figure 1 for project status breakdown.

Note: Status as of February 28, 2026. Data include 41 CCWIS and 34 transitional projects. Closed projects were ended early before becoming fully operational.

CCWIS PROJECTS HAVE RUN FOR SIX YEARS ON AVERAGE, WITH WIDE VARIATION ACROSS STATES

The median project duration for new CCWIS builds is approximately six years. Among states that have reached operational status, the average time from declaration to operational status is 61 months (five years). States still in active development have averaged 93.8 months (nearly eight years) since declaration. Seventy-five percent of all projects are not fully operational after eight years, and 32 states/territories have exceeded five years without an operational project. Idaho and Arizona are the two notable successes, completing their builds in approximately three and six years, respectively.

TOTAL CLAIMS FOR CCWIS AND TRANSITIONAL PROJECTS HAS REACHED OVER $2.2 BILLION SINCE 2016

Total federal and state claims since 2016 reached $2.28 billion, with an additional $5.86 billion allocated (approved to spend). The overwhelming majority of claims - 85 percent - have gone to transitional systems rather than new builds.

Table 1. Total Claimed and Allocated Funding for CCWIS and Transitional Projects, 2016 through February 2026 (Dollar values in millions; Percentages reflect percent of total funding in each column.

At the per-project level, the median claimed amount for new CCWIS builds is $11.2 million, compared to $27.4 million for transitional systems. When accounting for project duration, transitional projects cost approximately 20 times more per year than new builds ($4.9M vs. $250K per year). Fifteen states with active CCWIS projects had submitted no claims as of the analysis date.

FACTORS AFFECTING CCWIS PROJECT PROGRESS

The brief identifies four major categories of barriers:

• Complexity of technological requirements. Large, enterprise-wide scopes, complex legacy architectures, and data migration demands (particularly in county-administered systems) increase cost and duration.
• Organizational readiness. Successful implementation requires stable leadership, aligned program and IT governance, adequate workforce capacity, and sustained funding. Many states begin development before these foundations are in place, leading to evolving requirements, rework, and delays. Inconsistent state budget commitments - required to cover half of implementation costs - are a particular risk.
• Reliance on transitional systems. Federal policy allows simultaneous funding of legacy and new systems without firm transition deadlines, diverting resources from modernization and reducing incentives to complete new builds. Eighty-five percent of claims support legacy systems.
• Federal processes and requirements. Multi-layered federal approval requirements can be burdensome and encourage risk-averse approaches. Evolving compliance requirements slow implementation, limit flexibility, and reinforce reliance on slower, monolithic system approaches.
• State procurement, capacity, and legal constraints. State procurement timelines of one to two years cause delays, and large bundled contracts undermine the modular approach CCWIS envisions. Staff turnover, weak contract oversight, and legal issues such as consent decrees further complicate progress.

RETHINKING THE FEDERAL ROLE IN SUPPORTING CCWIS IMPLEMENTATION

Current federal funding and approval processes do not consistently ensure that states are prepared to begin system development, contributing to uneven progress across the CCWIS landscape. There are several areas where federal policy and support can better position states for success.

• Position ACF as an active partner, rather than primarily overseeing compliance. ACF can engage earlier and more substantively in state planning, establish standardized readiness criteria, and require demonstrated planning maturity before approving implementation funding.
• Redefine metrics of success towards outcomes and impact. ACF can move beyond on-time/on-budget measures toward outcomes such as system usability, data quality, deployment progress, and improvements in child welfare practice.
• Modernize federal guidance to keep pace with technological change. Clarify expectations around modularity, emerging technologies (AI, SaaS), and iterative system improvement. Frame CCWIS modernization as an ongoing lifecycle rather than a one-time transition. Many of these changes can be made under existing regulatory authority without new rulemaking.

CONCLUSION

After a decade and over $2.2 billion in spending, CCWIS implementation remains slow and uneven, with most resources flowing to legacy systems rather than modernization. These outcomes stem from persistent gaps in planning, governance, and readiness, not a lack of available technology or funding. CCWIS is not simply a technology investment. It is the primary infrastructure through which child welfare agencies capture and act on critical information supporting eligibility determinations, safety assessments, placement decisions, and payments to providers. Implementation delays therefore carry direct programmatic consequences: prolonged reliance on legacy systems limits data quality, restricts interoperability, and increases caseworker burden, with downstream effects on the timeliness of services, child safety, placement stability, and permanency.

Adapting federal processes does not require updating regulations, which is a lengthy process. ACF and states can take steps immediately to align planning, funding, and oversight with the goals of CCWIS modernization. This offers a clear path to improving implementation outcomes and ensuring that these investments more effectively support child welfare practice and outcomes.

Read the issue brief: Child Welfare Technology System Implementation Shows Minimal Progress: After 10 years and $2 Billion, Modern Information Systems Are Still Out of Reach