State-side CCWIS oversight
The integrator owns its side of every interface. Someone has to own the state's.
EdgeTech puts a small senior team on the agency's side of the contract, led by a techno-functional architect and scaled to the build with integration, data, and test reviewers. We review designs, code, interfaces, converted data, and test results, then tell leadership in plain terms what is safe to accept and what isn't.
Salesforce, Microsoft Dynamics 365 and Azure, AWS, or a custom build. We review whatever the agency has chosen.
4 of 41 new CCWIS builds were fully operational as of February 2026. Median build time is about six years.
Ten years after the CCWIS rule, most new builds still aren't live
HHS reviewed every CCWIS project on record in June 2026. Only 23 of 75 were fully operational, and $2.28 billion has been claimed against $5.86 billion allocated.
Its explanation points at the agency's side of the contract: vendor costs rise where state oversight is limited, contract changes go unchecked, staff turnover weakens governance, and data migration is underestimated.
Source: HHS/ASPE, Child Welfare Technology System Implementation Shows Minimal Progress, June 2026.
Who covers what on a typical CCWIS program
IV&V, QA, and the PMO each do real work. None of them sits in the weekly design review on the state's behalf.
| Role | Reports to | Cadence | Built to catch |
|---|---|---|---|
| Systems integrator | Agency PM | Daily | Its own scope: design, build, test, deploy |
| IV&V | Agency executive and ACF | Monthly or quarterly | Program health, schedule, compliance, process risk |
| QA vendor | Agency PM | Per deliverable | Deliverables against acceptance criteria, UAT planning |
| PMO | Agency PM | Weekly | Schedule, risks, status reporting |
| EdgeTech state-side team | Agency program and IT leadership | Inside the build cadence | Design, code, interface, and data problems before they are built in |
What we review
- Design and architecture
- Solution designs, data models, and the decisions nobody wrote down.
- Integration code
- APIs, middleware, batch exchanges, error handling, and the integrator's own standards.
- Partner agency interfaces
- Medicaid, SSA, child support, courts, education, public health: contracts, mappings, test results.
- Data conversion
- Mappings, reconciliation reports, and defect trends before cutover.
- Sprint and release gates
- Sprint demos, defect triage, and SIT and UAT entry and exit criteria, Agile or waterfall.
- Federal alignment
- Deliverables mapped to 45 CFR 1355.52 and 1355.53, the approved APD, and ACF IM-26-03.
From an active CCWIS build
State-side technical review since January 2025 on a Salesforce and MuleSoft CCWIS heading into SIT in January 2027.
32
data exchanges with 14 trading partners, reviewed from the state's side
3
exchanges moved from nightly batch to real-time APIs, where caseworkers and families actually gain. 24 stayed on batch, where real-time would only add cost.
Pre-build
critical logic and architecture conflicts in a partner integration design were caught on paper, when they were cheap to fix
3 to 1
monthly credit bureau files replaced by a single aggregator API for foster youth credit checks
We know what the data is for
An interface review that stops at field formats misses the point. We review against how the agency reports, claims, and practices.
- Federal reporting
- AFCARS, NCANDS, and NYTD: extract logic, edit checks, and submission readiness traced back to the source data model, plus the inputs to CFSR, PIP, and APSR.
- Eligibility and claiming
- Title IV-E and IV-B: eligibility rules, funding source logic, and the Medicaid and court data they depend on.
- Assessments and practice tools
- CANS and SDM: how assessment inputs drive case decisions, and how that data moves through the CCWIS.
- Data quality
- The CCWIS data quality plan and the intake, reporting, and data quality self-assessments, checked against what the build actually produces (45 CFR 1355.52).
- Partners and agreements
- Interstate compact (ICPC and NEICE), courts, education, and public health exchanges, each tied to a data sharing agreement, a mapping, and a test.
- Case and provider operations
- Intake and investigation mapping, case management and placement processes, and provider management and payments, reviewed against the reengineered business process.
How an engagement runs
The agency keeps decision authority over its APD, procurement, and risk acceptance. The integrator keeps design and delivery. We review and report.
- Weeks 1 to 4
Baseline
Onboarding, access, document inventory, and a baseline risk register.
- During build
Review in cadence
Reviews timed to sprint demos and release planning, or to phase gates, with findings tracked to closure.
- Before release
Readiness gates
Entry and exit checks ahead of SIT, UAT, and go-live, then an M&O oversight plan or a clean handoff.
What we need from the agency: a named sponsor, access to design documents and repositories, and a standing meeting with the integrator's technical lead.
Put a state-side review team on your CCWIS build
Through state IT staffing and master contract programs, or by direct contract. Resumes, rates, and references on request.
- SBA
- 8(a) certified
- New Jersey
- SBE and MBE certified
- GSA MAS
- 47QTCA23D0041
- UEI
- LTJCEAFZUJA3
- CAGE
- 97JY0
- NAICS
- 541511, 541512, 541519