SimpliGov |
October 8, 2026
When case management lives in inboxes and spreadsheets, the same failures repeat. No one can see where a case stands, the program cannot prove it followed required steps, and knowledge leaves when staff retire. Quality assurance, now mandated in states like North Carolina and Minnesota, runs on the same manual infrastructure it audits.
In this article
Teams running multi-step government programs see the same failures again and again. Cases move between departments by email and spreadsheet. No one can show how a decision was reached. When experienced staff retire, what they knew about the process leaves with them.
The cause is structural. Systems of record store what happened. The work that produces those records, the intake, approvals and handoffs between departments, lives in inboxes, spreadsheets and people’s heads. That gap has always cost time. Now it also carries audit and compliance exposure.
There is no single place to see where a case stands. When a program director needs a status update, someone has to ask. When a case moves from eligibility review to benefits determination, someone sends an email. When a document needs review by three departments, someone tracks it by hand.
The trouble often starts at intake. A paper or PDF form captures the information but can’t route the case to the next desk. From there, the work stays invisible until it stops moving.
When the steps between intake and decision happen outside a system, the program can’t prove it followed them.
A failed state audit is a common concern for program directors. Often the program did everything right. The evidence just lives in email threads, manual logs and staff memory.
State regulations set strict processing timelines. Manual workflows make them hard to hit consistently. Documentation becomes something staff reconstruct after the fact, from timestamps scattered across email and other systems.
New staff need to know which form goes to which department first, when a case needs a supervisor override, and who reviews the exceptions. In many programs, the system can’t tell them. The answers sit with someone who has done the work for 20 years.
When that person retires, the process goes with them, and the program has to relearn how to run consistently.
In ten states, counties carry the SNAP casework, according to the National Association of Counties: California, Colorado, Minnesota, New Jersey, New York, North Carolina, North Dakota, Ohio, Virginia and Wisconsin. That puts the coordination burden, and the compliance exposure, at the county level.
Quality assurance is a coordinated workflow of its own, layered on the casework it reviews: sampling cases, routing reviews, reporting results. In many programs it runs on the same email and spreadsheets. The process meant to verify compliance can’t document its own.
Minnesota allocated $50 million for social services quality assurance in 2026. North Carolina issued a county-wide social services quality assurance mandate. Ten states sit below federal thresholds for SNAP and Medicaid benefits processing. Policy is creating the requirement, and funding is following it. The operational infrastructure to meet it is not yet in place.
Staff care about the work, and leaders put service first. The failures come from running coordinated, multi-step programs on tools that were never built to move work between people and departments.
Fixing that starts when the program owns how its work moves: every handoff, decision and deadline recorded in one place, and the process documented in the system instead of in someone’s memory. The next step is building the operational infrastructure that can support the work.
See how program teams run case management in one place. Request a demo.
See how the workflows you're running by hand right now can run themselves.
