The agencies making real progress on the Comprehensive Child Welfare Information System (CCWIS) modernization have two practices in common:
- They buy modular SaaS instead of locking into custom big-bang builds.
- They prepare their people for the new system before any technology goes live.
Skipping either is what turns a modernization effort into a multi-year stall, with budgets running over, federal funding at risk, caseworkers stuck in the legacy systems they were promised would be replaced, and the children and families they serve waiting for changes that never arrive.
The 2016 final rule that replaced SACWIS sets the regulatory floor for CCWIS. The two practices below sit a level above the rule and determine whether modernization actually delivers what the rule contemplated.
This piece walks through both practices and how Binti’s approach reflects them.
Buy Modular SaaS Instead of Locking Into a Big-Bang Build
Modular SaaS reduces risk by limiting your exposure to any single vendor, getting working software in front of caseworkers in months rather than years, and offering a pricing structure that aligns the vendor’s incentives with yours.
The CCWIS work running over budget today shares one procurement decision in common. It’s a multi-year, single-vendor contract that committed the agency to a custom build before anyone could test how the vendor would actually deliver. Once that contract is signed and work has begun, the cost of switching is high enough that the agency stays in the relationship even when delivery is poor. That’s the lock-in problem, and many vendors price for it. Change orders on custom builds can exceed the original contract value by the time the system goes live, or doesn’t.
The federal CCWIS rule under 45 CFR 1355.53 explicitly allows, and in fact requires, a different path. Every automated function developed for CCWIS after July 31, 2018 must follow a modular design that separates business rules from core programming, with each function capable of being shared, leveraged, and reused as a separate component. The intent is procurement flexibility. States can buy what works for one workflow without committing to a single platform for everything.
Why SaaS Modules Are Lower-Risk Than Custom Builds
Pre-built SaaS modules have already worked for other agencies. The product exists, the vendor has implemented it before, and you can talk to the agencies using it. None of that’s true of a custom build, where every state is the first state to deploy a system designed specifically for them.
The deployment timeline reflects this. A SaaS module can go live in months. Caregiver Licensing has launched in roughly 12 weeks; Family Finding & Engagement in around two months. A custom-built CCWIS often takes years to deliver something workers can use. Every year that legacy systems stay in place is another year of workarounds, another year caseworkers spend on paperwork the new system was meant to take off their plate, and another year before the families they serve see the benefits modernization promised.
SaaS pricing also aligns the vendor’s incentives with the agency’s. A flat annual subscription comes up for renewal every year, and the vendor keeps the business only by continuing to earn it, so the commercial pressure points toward keeping the agency happy rather than billing more change orders. Custom-build vendors operate under different incentives.
The private sector made this shift decades ago. Government has been slower, partly because procurement rules historically favored large consulting contracts over commercial software. The CCWIS rule changed the federal posture. ACF may approve alternative designs, including commercial off-the-shelf and SaaS products, on a case-by-case basis under 45 CFR 1355.53(b). The lane is open.
What Modular Procurement Looks Like in Practice
The principle is to buy one module at a time. Pick a workflow where modernization will produce a visible early win for caseworkers, the community, and the families they serve. Run a contract for that module. If the vendor delivers on time and on budget, expand the relationship to the next module. If they don’t, you can switch without having committed your entire system to one platform.
Federal acquisition policy makes the same case for modular contracting in government technology. The argument is straightforward. Smaller contracts spread risk. They give the agency the ability to switch vendors when performance falls short. They let workflows go live in stages, so the people doing the work see progress before the entire project completes.
Rather than committing to a multi-year, multi-module monolith, some agencies have launched a single CCWIS module first, evaluated delivery, and expanded from there. That approach makes the implementation testable. The agency sees how the vendor delivers on a real piece of work before deciding whether to expand. And the workers, families, and children the system serves see the benefits of modernization in months rather than waiting through a multi-year build that may never reach them.
Prepare Your People Before the System Goes Live
The technology will only deliver better outcomes for children and families if the people using it are ready to work differently. Change management is the actual project, not a side workstream.
Software defects happen, and they can derail a project. But the failure pattern change management exists to prevent is a different one: the system goes live, the old workflows persist, and adoption stalls. New tools sit unused alongside the spreadsheets, paper forms, and tribal knowledge that workers actually rely on to do their jobs. Federal funds approved for the project go unspent because implementation milestones get missed. The promised improvements for families and children don’t show up.
Agencies that avoid this outcome treat change management as the project itself. They engage the people who will use the system, including caseworkers, supervisors, licensing workers, and people with lived experience in the foster care system, in designing the workflows before the technology is procured. Engagement starts in planning and continues through go-live and beyond.
What Engagement Looks Like in Practice
The practices below separate agencies that hit adoption targets from those that spend years managing workarounds alongside the new system. Each one requires deliberate effort before a vendor ever presents.
Map your existing workflows before any vendor presents. The point isn’t to digitize your current process. The point is to have a shared, documented understanding of what the work actually requires so you can evaluate whether a new system will support it.
Define baseline measures. Before anything goes live, capture the metrics that matter for the people the system serves. How long does it take to license a family? How long after a referral can a child be placed with kin? How many home visits can a caseworker complete in a month, and how many of those visits get fully documented in a way the supervisor can use? These numbers become the basis for evaluating whether the new system is producing the outcomes that justified the procurement.
Engage the people doing the work. Caseworkers and supervisors know which of the current workflows are functional, which are workarounds, and which exist because someone wrote a policy 15 years ago that nobody has revisited since. People with lived experience, including kinship caregivers and foster parents, know which of the agency’s interactions feel useful and which feel like compliance theater. The work also runs through the courts, service providers, and community partners whose own processes the system has to accommodate, and their constraints belong in the design from the start. So does youth voice and choice: the young people whose lives these decisions shape should help shape how the system works. Everyone here belongs in the room before the system gets configured, not after.
Train on the new processes, not just the new software. The hardest part of any CCWIS rollout isn’t learning the buttons; it’s learning the new workflow. If the project plan only budgets time for software training, the actual change management work, including supervisor coaching, practice changes, and policy updates, will compete with daily caseload demands and lose. Build the practice change time into the project schedule from the beginning.
Build review checkpoints into the schedule. A project plan that doesn’t allow for course-correction at defined milestones will produce a launch-day surprise rather than a successful go-live. Reviews at the end of each phase create moments where supervisors and project leads can flag what isn’t working before the issue compounds.
Agencies that build these practices into the project before go-live consistently reach adoption faster and produce the outcome data needed to defend continued investment at six and twelve months.
What Happens When Change Management Gets Skipped
Three patterns show up when change management isn’t budgeted as a real workstream.
The new system launches, but adoption stalls. Workers continue using the old workflows alongside the new tool. Data gets entered into both, or entered into one and not the other. The data quality problems the agency was trying to solve don’t get solved, because the workflows that produced them haven’t changed.
Federal funds sit unspent. ACF approves federal financial participation against an Advance Planning Document with milestones; if the agency can’t meet the milestones because the people side of the change isn’t ready, the federal share goes unclaimed. Money the agency was counting on doesn’t show up.
Old platforms stay in place because the agency can’t switch on top of everything else. Workers can’t migrate cases to the new system while still running the legacy one. The “transition period” extends. Hardware refreshes, license renewals, and security patches keep getting funded for systems that were supposed to be retired two years ago.
Each of these patterns hurts the people the agency is supposed to serve. Caseworkers stay on workarounds and stay on the documentation treadmill, while turnover pressure builds. Families wait longer for licensing decisions. Children stay in placements that were supposed to be temporary while the system that was supposed to support a faster path to permanency stays stuck in development.
How Binti Approaches CCWIS Modernization
We’ve designed our CCWIS approach around the two practices above. The platform is a set of modules that compose into a full CCWIS, deployed in phases that each produce a working system caseworkers can use while the next phase is in development.
The full path runs 24 months across four phases. Each phase delivers an operational module, and each phase produces metrics agencies can use to defend continued investment to their legislatures and to ACF.
- Phase 1, months 0–6. Caregiver Licensing and Family Finding & Engagement. Both launch first because the win is direct and visible. Licensing approval times can drop substantially in the first six months, returning weeks to caseworkers for the preparation and support families need before their first placement. Family Finding identifies kin connections that legacy systems miss, opening placement options that keep children connected to family rather than entering congregate care.
- Phase 2, months 6–12. Service Referral Management. Tracking services and providers in a structured system allows agencies to document FFPSA prevention service utilization in the form ACF accepts, which translates into more federal claiming for prevention work that was previously off the federal-funding ledger.
- Phase 3, months 12–18. Intake and Investigations. Once the agency has confidence in the platform and the configuration approach, the front-door modules come online. The data migration is heavier here than for licensing or family finding, which is why the work lands in the third phase rather than the first.
- Phase 4, months 18–24. Case Management, Eligibility & Payments, and integrations to existing court systems, Medicaid, and federal reporting endpoints. Case management is the data nucleus, and the integration work connects the platform to the rest of the agency’s environment. This is the heaviest data migration and the right work for the final phase, after the agency and the platform have been operating together for 18 months.
In our history of state and county deployments, we have never charged a change order. The flat-subscription pricing model and modular contracting structurally remove the change-order mechanism. Once an agency is in the subscription, scope changes are absorbed in the configuration, not priced as billable additions. Our incentives align with renewal. The agency’s incentives align with delivery. The contract reflects both.
Getting Started With Your CCWIS Project
You don’t have to replace everything at once, and the agencies making the most progress haven’t tried to. They start with one module, prove it works in their context with their workers and the families they serve, and expand from there.
Caregiver Licensing, Family Finding & Engagement, and Service Referral Management are all valid starting points. The choice depends on where modernization will produce the most visible early win for your agency. Pick licensing if approval timelines are slowing placement stability and keeping qualified families waiting longer than necessary. Pick family finding if workers are spending hours searching disconnected systems while children remain separated from relatives. Pick SRM if prevention referrals, provider coordination, and service tracking are fragmented across agencies and partners.
Whatever you start with, define baseline measures before launch. Track caseworker documentation time, licensing timelines, kinship placement rates, and placement stability metrics. Compare at six and twelve months. The numbers give your team the evidence it needs when the procurement conversation moves from “should we modernize” to “how fast can we expand.”
Share what you learn with peers and with ACF. Modernization is moving across the country, and the agencies further along can save those just starting hours of trial and error.
If you’d like to talk about how a modular SaaS approach could work for your agency, we’d be glad to walk you through it.
Frequently Asked Questions About CCWIS
How is CCWIS funded?
Title IV-E provides a 50 percent federal matching rate for CCWIS project costs. Training is matched at 75 percent. For ongoing operations, the federal share applies to costs allocable to Title IV-E, which means the actual federal contribution scales with the IV-E penetration rate, the percentage of children in your foster care caseload who are IV-E eligible. A higher penetration rate means more of your ongoing operations costs draw the 50 percent match.
How many states have completed CCWIS implementation?
No state has yet reached full operational CCWIS status. As of October 21, 2024, 45 states, the District of Columbia, and Puerto Rico had notified ACF of their intent to transition. A subset have reached a combined “Development and Operational” phase, where some functionality is live while other modules continue in development. Most remain in earlier stages, years after the 2016 final rule established the framework.
Can a state use SaaS for CCWIS?
Yes. Under 45 CFR 1355.53(b), ACF may approve alternative designs, including commercial off-the-shelf and SaaS products, on a case-by-case basis. The Title IV-E agency remains responsible for data quality and exchange regardless of the delivery model.
What’s the difference between modular procurement and a “big-bang” build?
A big-bang procurement commits the agency to a single, multi-year contract that delivers the entire system at the end. Modular procurement runs separate contracts for separate modules, with each module live and producing value before the next contract begins. Modular procurement is what 45 CFR 1355.53 contemplates, and it’s also what federal acquisition policy recommends for risk reduction in government technology projects.
