Quick Answer: The CYFD case management system, New Mexico Impact, is still not the agency's only system of record. Officials say 205 critical items and about 30 years of data must be validated first. They expect it to become the system of record by the end of the year but won't commit to a specific date. Lawmakers say the project's cost has grown far beyond its original budget.

New Mexico's Children, Youth and Families Department (CYFD) was supposed to have a modern replacement for its foster care records system years ago. Instead, caseworkers are still working in the old tools. As The New Mexican reported, state lawmakers are now asking hard questions about the price and the timeline. Here's what's actually happening, and why a delay can be the responsible call even when it's frustrating.

Where the Project Started and Why It Went Off Track

CYFD began modernizing in 2017. The goal was to replace the Family Automated Client Tracking System, or FACTS, which the agency had run for years. The original plan was a $32 million project finished by October 2022.

That's not what happened. The project now carries a projected cost of at least $90.4 million, and the state has already spent more than $57.6 million. That's roughly 182% above the original budget, and the completion date has passed by more than four years.

Here's the thing most coverage skips: cost overruns like this are rarely about one bad decision. They build up from scope changes, delayed testing, and vendor work that gets extended month after month. Each extension looks reasonable on its own. Together, they turn a plan into a multi-year commitment nobody fully priced in.

What "System of Record" Actually Means

A system of record is the one place where authoritative data lives. For a child welfare agency, that means case notes, placement histories, and safety assessments. When caseworkers use a parallel system, you end up with two versions of the truth, and that's where children can fall through the cracks.

This is why CYFD's October target mattered. The agency had promised New Mexico Impact would become the only tool employees used on October 13. When that date passed, officials said software defects, data validation problems, and functionality gaps were still blocking the switch.

The reader question here is simple: if the software is already built, why not just switch? Because a system of record can't be half-live. Once caseworkers depend on it, every missing function becomes a safety issue.

The Work Still Left on the List

According to deputy director Joshua Fulkerson, the state and its contractor, RedMane Technology, are working through 205 "critical items," including bugs and functional gaps. They also have to validate roughly 30 years of historical data before the system can replace FACTS.

Here's what that work typically involves, based on how data migrations are usually staged in public-sector projects:

  1. Data mapping and cleanup: Old fields get matched to new ones, and bad or duplicate records get fixed.
  2. Validation testing: Samples of migrated records are checked against the originals to confirm nothing was dropped or altered.
  3. User acceptance testing (UAT): Caseworkers run real workflows, such as intake, placement, and court reporting, in the new system.
  4. Cutover and retirement: The old system goes read-only, and staff move fully to the new one.

The step most teams underestimate is validation. Migrating data is fast. Proving that 30 years of records came through intact is slow, and it's where many projects quietly lose months.

The January launch data suggests why this matters. Lawmakers were told that the mid-August launch was largely a data transfer from the legacy system, without promised features such as a mobile app for field workers. A transferred database is not the same as a working system.

Why Lawmakers Are Frustrated, and Why They're Also Stuck

Sen. Nicole Tobiassen, R-Albuquerque, said she was frustrated that children and families weren't being supported the way they should be, and that the program "should have been implemented a long time ago and for far less money." That criticism is fair. The state has already paid more than half the projected total without a working replacement.

Sen. Ant Thornton, R-Sandia Park, made the harder point: the state is "so far down this path now that there's no way we can back out." Walking away would leave the state paying for a dead system while still running on FACTS.

That's the sunk cost trap in its purest form. Money already spent shouldn't drive the decision. But abandoning a project also carries real costs: new procurement, a longer period on the old system, and a restart of the learning curve. The honest answer is that the decision should rest on whether the remaining work can be finished safely, not on what's already been spent.

Rep. Tara Lujan, D-Santa Fe, raised the other concern: protecting sensitive information about vulnerable children. That's why officials say they're going slowly. A rushed launch could expose data, and a failed launch could disrupt casework.

Why Officials Won't Name a Date (and Why That's Defensible)

Jason Habedank, deputy cabinet secretary for the New Mexico Department of Information Technology, said the team wouldn't announce a new date until it was confident it could hit it. "We don't want to mislead folks," he said, "give you a date and then be off by a week."

This is the counter-intuitive part. Most people assume a missing date is a red flag. In practice, public projects often lose trust because they announce dates, miss them, and announce new ones. Each miss erodes confidence more than a single honest delay would.

That said, there's a real catch. Withholding a date can also become a way to avoid accountability. Lawmakers need a schedule they can check against, and "by the end of the year" is a window, not a commitment. The fair test is whether the state reports measurable progress, such as the number of open critical items falling each month, rather than just repeating reassurances.

A Broader Pattern in Government Case Management Software

This isn't unique to New Mexico. Child welfare agencies across the United States have replaced case management systems in recent decades, often under federal frameworks administered by the Administration for Children and Families (ACF). The newer federal approach, the Comprehensive Child Welfare Information System (CCWIS), encourages modular designs so that agencies don't have to replace everything at once. You can read the program guidance on the ACF website.

Why do these projects run over budget so often? The common explanation is poor planning, but the more accurate one is that requirements change as caseworkers learn what they actually need. Legacy systems also hold rules that nobody wrote down. Discovering those rules during migration is expensive.

Here's a quick comparison of where the project stands on the metrics that matter:

MetricOriginal PlanCurrent Status (per source)
Budget$32 millionAt least $90.4 million projected
Spend to dateNot applicableMore than $57.6 million (about 64% of projection)
Completion targetOctober 2022Indefinitely delayed; end of the year expected
Open critical itemsNot specified205
Staff trainedNot specified1,836

Frequently Asked Questions

What is the CYFD case management system?

The CYFD case management system is the software New Mexico's Children, Youth and Families Department uses to track foster care cases. The current system is the Family Automated Client Tracking System (FACTS). The replacement, called New Mexico Impact, is being built to replace FACTS, and the project is developed with contractor RedMane Technology.

Why is the CYFD system taking so long to launch?

The system still has 205 critical items, including software bugs, and roughly 30 years of data must be validated. Officials say defects, data validation issues, and missing functionality caused the October rollout to be postponed. Caseworkers are not yet using New Mexico Impact for daily work.

When will New Mexico Impact become the system of record?

Officials say they expect New Mexico Impact to become the system of record by the end of the year. They have not announced a specific date. They say they'll share one only after they're confident they can meet it.

Why do government IT projects like this go over budget?

Most overruns come from changing requirements, underestimated data migration work, and extended vendor contracts. Hidden business rules in legacy systems also add time and cost. Projects tend to grow when testing starts late, so catching problems early is usually cheaper than fixing them at cutover.

The Takeaway for Anyone Watching a Public IT Project

If you're following this story or managing a similar migration, focus on one thing: the number of open critical items. That's the metric that tells you whether the project is converging on a launch or just stretching out. Track it monthly, and ask for the trend, not the reassurance. Try pulling the official status updates from your state's IT department this week and noting how the open-item count has changed since the last report. Pass this to someone who's wrestling with a similar CYFD case management system problem, and ask them what their open-item count looks like.