SSA Foster Care Data Exchange Faces State Adoption and Legacy IT Gaps

What happened

The Government Accountability Office (GAO) has found that the Social Security Administration (SSA) still has outreach work to do on its foster care data exchange, which has not been able to bring new states on board for two years. The finding, reported by FedScoop, puts the agency's adoption challenge at the centre of the review rather than the platform's core function.

The watchdog also identified what it described as "cumbersome IT systems" supporting the exchange. Taken together, the findings point to two related constraints: slow uptake among states, and legacy technology that makes participation harder than it should be.

The reporting does not present these as a single cause. Rather, it frames state onboarding and the underlying systems as separate areas where the agency needs to act if the exchange is to widen its reach.

Why it matters

For public-sector digital transformation, this is a useful reminder that a shared data platform succeeds or fails on adoption as much as on engineering. An exchange only delivers value when partner agencies connect, validate and keep using it. When new participants stop arriving, the platform can be technically sound and still fall short of its purpose. That makes partner enablement, documentation, support and onboarding part of the product, not an afterthought.

The cumbersome-systems finding also matters for operating-model change. Legacy architecture raises the effort required of every state that wants to join, and each extra step in that process lengthens the path between a record being updated and the people who rely on it. For a programme serving foster care beneficiaries, that friction is ultimately felt by the individuals and the caseworkers who depend on accurate, timely information.

The Renascence take

Most coverage of government data initiatives asks whether the technology works. The more revealing question is whether anyone is treating the state agencies as customers with a journey to complete.

A platform can be built correctly and still stall, because the people who must adopt it have not been given a clear, low-effort path to do so. Stalled onboarding is usually a service-design failure: too much friction, unclear value and too little hand-holding at the moment of decision. Operators in this space should map the state onboarding journey end to end, measure where participants drop out, and fix the experience before adding features. Legacy systems deserve attention too, but they are easier to prioritise once you can see which steps are costing adoption the most.