Child Welfare Case Management Should Fit Your Requirements — Not the Other Way Around

Child welfare case management operates in one of the most demanding environments in state and local government. Agencies must promote the safety, permanency, and well-being of children while coordinating services across providers, foster and kin caregivers, healthcare organizations, and schools — all while satisfying rigorous federal and state reporting requirements and protecting sensitive data. Too often, the technology meant to support that work makes it harder, because the software was never built to fit how the agency actually operates. For agencies managing complex child welfare case management requirements, technology should simplify daily practice rather than add another layer of administrative burden.

At Info-Matrix, we implement the Automated Child and Youth Services (ACYS) platform on a simple principle: the system should map to your requirements, not force your agency to bend to the system. Here is what that means in practice — and why it matters more as requirements keep changing.

Why generic child welfare case management systems fail child welfare agencies

Many states and counties run on general-purpose case management systems that don’t reflect child welfare processes and don’t capture the data needed for federal reporting and evidence-based decision-making. When a system forces an agency to change its workflows to fit the application, the result is predictable: manual workarounds, inconsistent practice, poor data quality, and reporting that feels like a second job.

The deeper problem is that no two child welfare jurisdictions are the same. Every state operates under its own statutes, court rules, forms, and funding structures; every county layers its own policies and practice models on top. A platform that treats them all identically can only ever be a compromise — and in child welfare, compromise shows up as audit risk, missed deadlines, and decisions that are harder to defend.

The federal government already settled the “one-size-fits-all” debate

Configuring a system to the agency rather than the agency to the system isn’t just good vendor practice — it’s the direction the federal government itself has set.

For more than two decades, agencies sought federal funding under the Statewide and Tribal Automated Child Welfare Information Systems (S/TACWIS) rule, which required a single, monolithic system supporting 51 federally mandated functions. In June 2016, the Administration for Children and Families replaced that model with the Comprehensive Child Welfare Information System (CCWIS) final rule.

CCWIS made a deliberate shift. Rather than dictating a fixed list of functions, it gives Title IV-E agencies the flexibility to determine the size, scope, and functionality of their own information systems, and it rewards modular, reusable design and bidirectional data exchange. In other words, the federal framework now encourages agencies to build systems tailored to their business needs — not to a one-size-fits-all federal template.

How ACYS maps to your child welfare requirements — by configuration, not workaround

Info-Matrix designed ACYS working directly with Pennsylvania county administrators and caseworkers, so the system reflects real practice rather than a theoretical business-process map. ACYS is designed by the caseworkers and for the caseworkers. That field-tested foundation shows up in four concrete ways. ACYS supports child welfare case management by aligning workflows, reporting requirements, and compliance checks with the way each agency operates.

A modular architecture you can adopt on your terms

As a CCWIS-aligned child welfare application, ACYS supports the full lifecycle of child welfare services — intake, assessment, case management, foster care, permanency(adoption and custodianship), engagement, fiscal management, provider oversight, and quality assurance — but it does not require you to take all of it at once. Because the platform is modular, agencies can pick and choose only the modules they need — deploying the complete system or implementing specific components and adding others over time — while ACYS maintains interoperability with the infrastructure you already have in place. One caveat worth naming: a few modules become essential once AFCARS reporting is in scope. To stay compliant, agencies need the modules that capture the required foster care and permanency data. In other words, modularity governs how you build towards your goals — federal reporting defines the minimum a compliance-ready deployment has to include.

A configurable workflow and business-rules layer

The operational logic of ACYS — case routing, task assignment, compliance validation, and automated notifications — lives in a configurable rules layer. That means workflows are set to your policies, procedures, and jurisdictional requirements, so the path a referral or a service plan takes through the system matches how your units and supervisors actually operate. Configuration replaces the brittle custom code and off-system spreadsheets that generic platforms force on staff.

Compliance embedded at the point of entry

In child welfare case management, data accuracy is non-negotiable, and reporting requirements are exacting. Instead of treating compliance as a separate step before a deadline, ACYS builds federal and state rules directly into daily data entry — so information is validated as staff record it, and issues are caught and corrected in the moment rather than reconstructed under deadline pressure.

That same foundation lets ACYS meet both federal and state reporting obligations, including:

• AFCARS (federal) — ACYS produces federally compliant AFCARS reporting, in accordance with the governing bulletin.
• Title IV-E / OCYF reporting — ACYS populates the reporting template OCYF provides to the counties, including the required Title IV-E data.
• CY 28 — ACYS compiles the county-level funding and reporting that agencies submit to the state.

For Pennsylvania agencies, ACYS also provides deep CWIS integration, court documentation aligned to Administrative Office of Pennsylvania Courts (AOPC) standards, DOMREL exports, and native support for Commonwealth CY forms — including CY 47, CY 48, and CY 104 — under the Child Protective Services Law.

An integration layer that meets your ecosystem

ACYS exchanges data with CWIS/CCWIS environments, the state MCI client index, financial systems, and provider networks — including AFCARS and DOMREL exports. Rather than asking your partners and state systems to bend toward the software, the platform is built to connect to the environment you already operate in.

The difference between generic software and requirements-driven child welfare case management becomes clear when comparing how each approach handles workflows, reporting, and modernization. One-size-fits-all systems vs. the ACYS requirements-mapped approach

Built to adapt as requirements change

Mapping to today’s requirements is only half the job. Child welfare requirements don’t stand still — federal and state legislations are updated and amended on a constant basis and a system that can’t move with them becomes the next legacy modernization problem.

The evidence is in the federal record. AFCARS, the federal government’s primary source of foster care and adoption data, was significantly expanded under a 2020 final rule with new data collection beginning in federal fiscal year 2023, then revised again in a 2024 final rule effective February 2025. On the funding side, the Family First Prevention Services Act (FFPSA), enacted in 2018, restructured Title IV-E to fund evidence-based prevention services and now requires agencies to manage and report against new categories of spending. The reporting target moves on a regular cycle.

ACYS is designed for that reality. When requirements shift, agencies adapt through configuration and modular updates rather than rebuilding the system. And when an agency needs targeted improvement before it is ready for a broader transition, Info-Matrix add-on solutions integrate with existing child welfare systems to deliver value quickly — without disrupting current operations:

• CaseLink Mobile — real-time, two-way mobile access with voice-to-text notes, photo upload, and offline sync, so caseworkers document in the field and reduce after-hours work.
• AFCARS Insights — fast, readable error reports across all 186 AFCARS elements, for teams to proactively fix data and submit clean and accurate data reducing the risk of file rejections.
• Data Insights — a Power BI-enabled analytics layer that turns case data into trends, metrics, and oversight dashboards supervisors and administrators can personalize.
• Notes Insight — an AI-powered, HIPAA-aligned assistant that analyzes case notes and surfaces relevant information instantly, with a human-in-the-loop design that keeps professional judgment in control.
• ProviderCares — a secure gateway for agencies and providers to exchange licenses and certifications, initiate service requests, and streamline invoicing and payments.

What agency leaders gain from a system that fits

Modernization succeeds when it improves practice, strengthens oversight, and reduces administrative burden — not when it adds a new layer of process for staff to work around. A requirements-mapped platform delivers value from the field to the executive suite:

• Higher data quality and reporting accuracy, because validation happens at the point of practice rather than after submission.
• Less rework and greater submission confidence for AFCARS, FFPSA, OCYF, and Commonwealth-specific reporting.
• Lower modernization risk through a phased, add-on-first approach that keeps daily work running.
• Stronger oversight from dashboards and quality-assurance tools that give leadership real-time visibility into what is working and where attention is needed.
• Long-term adaptability from a modular, CCWIS-aligned architecture designed to evolve alongside changing policy, technology, and community needs.