What Happens After a QA Finding in County Human Services

Over the past year, we’ve spent a lot of time with quality assurance teams in county social services and human services agencies, often while they walked us through their own review process on a shared screen. Within a few minutes, the conversation almost always moved past the review itself to what happens afterward: the correction that hasn’t come back, the rebuttal waiting on a supervisor, the trend someone means to pull from the spreadsheet, and the report due at the end of the quarter.

The agencies went by different names, including Department of Social Services, Health and Human Services, Human Services, and Job and Family Services. Their teams reviewed SNAP, Medicaid, TANF and child care cases. The follow-up work looked much the same in all of them.

Those conversations are the basis for this post. County QA teams know policy well, read cases closely, and catch the errors that matter. The work that follows each finding takes a large share of their time, and in most agencies it was never designed as a process at all. It grew out of email, shared spreadsheets and the habits of whoever set it up first.

QA corrections that depend on someone’s inbox

In most county social services and human services agencies, a QA finding still travels the way it did 10 years ago. The reviewer completes a spreadsheet or a printed form and sends it by email, sometimes as a scan. Whether the correction happens depends on someone noticing the message, opening the attachment, finding the right item and replying.

Each of those steps is a chance for the finding to stall. Messages get buried under the rest of the day’s email, and when a reviewer goes on leave, her open findings wait in an inbox nobody else checks. Due dates tend to live in someone’s memory or in a spreadsheet column that rarely gets filtered, so following up means opening the log, checking case by case and sending another round of email.

Because the review itself was done correctly, none of this registers as an error. The QA team still spends hours closing out its own work, one reminder at a time.

When a second-party review score depends on the reviewer

QA works only when staff trust the results, and that trust wears thin when the same case could score differently depending on who reviewed it.

This happens more often than most teams would like. One reviewer deducts points for an item that another lets pass, or a single mistake gets counted in several places because it touched several parts of the case. Weighted questions often rely on a formula someone built years ago, and few people are sure it still matches the current state tool.

Rebuttals add more uncertainty. When a caseworker disputes a finding, it may go to her supervisor and then to the QA supervisor, often by a different route than the original review took. The reasoning behind an upheld rebuttal can be hard to find later, and a run of rebuttals upheld against the same reviewer can go unnoticed for months.

Many teams also work to keep reviews impersonal, so that staff respond to the finding itself without wondering who wrote it. That is difficult to sustain when every review arrives in an email with the reviewer’s name at the top.

Finding error trends takes time QA teams don’t have

The most useful thing a county QA program produces is what a month of findings shows when you look at them together: the program that keeps missing an income verification, the unit that struggles with redeterminations, or the error that only two caseworkers keep making.

That picture decides what happens next. If two people are making the same mistake, a supervisor can coach those two people, and if most of the staff is making it, a refresher training makes sense. A wrong read either costs a full training day or leaves the people who needed help without it.

Most QA teams have the skill to find these patterns, but they rarely have the time. Findings are spread across monthly spreadsheets, often one tab per program, and pulling a trend means copying, filtering and counting by hand. The analysis gets pushed back, and the same errors show up again the following month.

New staff are affected by the same gap. Trainees often move through review in stages, with every case checked until they are ready to work independently, and experienced workers sometimes need closer review for a stretch after a pattern appears. Today, seeing how any one person is progressing usually takes an afternoon with a spreadsheet.

Rebuilding the quarterly QA report by hand

At the end of each quarter, the same findings have to become a report, whether that means error trends for the state, dollar error amounts, progress on a corrective action plan or a summary for county leadership.

The numbers already exist across logs and spreadsheets, so someone on the QA team rebuilds them by hand, reconciles totals that don’t quite match and formats everything again. It is careful and necessary work, and it repeats every quarter because the data was never kept in one place to begin with.

The monthly sample often starts the same way. Someone exports cases, runs a random selector, checks that every action type is represented and copies the list into the log. The method is sound, and it still takes hours from the same small team.

Following one QA finding through a better process

Here is a single finding moving through a process designed around the work that follows it.

1. The reviewer completes the review on a digital checklist with the county’s weighted scoring built in, so the same case earns the same score from any reviewer.
2. The finding goes directly to the caseworker with a due date attached, and opening it takes her straight to the item that needs correcting.
3. She corrects the item or disputes it. A dispute routes to the right person under the county’s own rebuttal rules, and the outcome is recorded either way.
4. The supervisor can see what is open, what is overdue and who it is waiting on without asking anyone, and reminders go out automatically.
5. When the case closes, its full history stays with it, including the finding, the correction, any rebuttal, and every date and name along the way.
6. Each closed review adds to a dashboard organized by program, unit and worker, so patterns are visible as the month goes on.
7. When the state changes its review criteria, the QA lead updates the checklist herself on the same day.

The reviewer brings the same knowledge and judgment she always has. The work after the finding now runs through a process the QA team designed and controls, the record keeps itself, and the hours that used to go to follow-up can go to coaching and training.

Why human services quality assurance matters more now

QA teams are small, and they are being asked to do more. Changes under H.R. 1 are putting new attention on payment accuracy in SNAP and Medicaid, and much of that attention lands on county quality assurance and quality control reviews. Many agencies are also short-staffed and bringing new workers up to speed faster than usual.

A process held together by email and one person’s spreadsheet is fragile under that kind of pressure. When the person who built the log leaves, much of what the team knows about its own process leaves with her, and a tool that needs IT for every change soon stops matching how the team actually works.

The counties that come through this period well will be the ones whose findings close reliably, whose patterns surface early, and whose QA staff have time to help caseworkers improve.

Five questions to ask about your QA process

If you run quality review for a county agency, try answering these without opening your inbox.

1. How many corrections are open right now, and which ones are past due?
2. If a reviewer were out for two weeks, who would see her open findings?
3. Would the same case get the same score from any reviewer on your team?
4. Which errors are coming from two people, and which are coming from most of the staff?
5. How long does your quarterly report take to build?

If any of these would take more than a minute to answer, the follow-up work after each review is a good place to start looking.

See what happens after a case is flagged

Our webinar, Inside the Workflow, walks through what happens after a QA finding, from review to correction to trend, using the same kind of process county teams run today. Watch Inside the Workflow.

For the research behind this post, The Documentation Gap white paper covers how county quality review processes break down and what a structured corrective action process looks like.