Want to reduce SNAP errors? Start by reducing churn

Most state administrators of the Supplemental Nutritional Assistance Program (SNAP), which provides food security for more than 40 million Americans, don’t need to be told why churn is a problem. When beneficiaries repeatedly move in and out of the program, SNAP leaders witness the impact firsthand—not just on families but on their own work. It’s call queues that never quite come down, reapplications that pile up, and staff who spend more time reopening cases than moving work forward. 

Churn results in more than just a gap in benefits. It causes the same eligibility decision to be processed twice. When an otherwise eligible household exits SNAP for administrative reasons and then returns weeks or months later, the system doesn’t resume where it left off; it restarts. That restart generates a new application, another interview, additional documentation, more notices, and more staff handling time—none of which meaningfully improves program integrity. With recent staffing constraints, increased oversight, and rising expectations around accuracy, the cost of that rework has become harder for agencies to absorb. 

What’s more, repeated transactions fragment documentation, compress timelines, and increase handoffs. Staff members lose context. Cases move quickly, then stall, then restart again. Under such conditions, even experienced, well-trained workers are more likely to struggle to reconcile information or catch subtle inconsistencies. Inevitably, the payment error rate (PER) suffers.  

Given that new federal rules attach a potentially huge price tag to such errors, reducing churn and its operational impact needs to be an urgent priority for state SNAP and HHS leaders. 

How churn undermines accuracy 

PER is often treated purely as a compliance concern, addressed through quality control reviews, corrective action plans, and targeted training. Those solutions play an important role. But at its core, PER reflects whether staff have the information they need when they need it to make the right eligibility decision. Most errors aren’t the result of fraud or intentional misrepresentation. The majority stem from missing information, inconsistent data, a loss of context due to repeated handoffs, or timing issues such as documents that arrive too late or changes that aren’t acted on promptly. 

Churn exacerbates all of those challenges. When households cycle in and out of the program, documentation becomes harder to track and maintain. Information that was previously verified must be collected all over again or reevaluated. Staff are forced to work reactively, often under tighter time pressure and with less continuity. Each additional touchpoint becomes another opportunity for something to be missed. Over time, churn quietly becomes a structural contributor to error risk. 

This dynamic is easy to overlook because churn often shows up as a series of smaller problems: higher call volume, more interviews, more notices, more follow-up. But collectively, those problems shape the operating environment in which accuracy is maintained or breaks down. Put simply, churn—and the rework it triggers—makes accuracy harder to sustain. 

The accuracy trap 

In periods of heightened focus on PER, many agencies respond by adding safeguards. Documentation requirements expand. Verification becomes more conservative. Manual checks are layered into workflows. These responses are understandable as leaders try to protect the program and avoid future findings. 

But added controls can eventually worsen the problem they’re intended to solve. Each additional requirement increases the likelihood that a household will miss a step, submit incomplete information, or fail to meet a deadline. Missed steps often result in procedural closures, which drive churn, which in turn increases workload pressure and destabilizes documentation quality. 

This is the accuracy trap. Well-intended efforts to reduce error risk end up increasing the volume of rework the system has to absorb. Staff spend more time reopening cases, chasing documentation, and responding to confusion. Time pressure increases. Context is lost. The risk of error rises again, reinforcing the impulse to add even more controls. Over time, this cycle erodes staff confidence as workers spend more energy undoing work than completing it. 

Breaking this cycle requires a new approach to reducing PER. Instead of focusing primarily on compliance after the fact, agencies need to reduce the amount of preventable work flowing through the system in the first place. 

One useful starting point is to limit the number of calls, visits, and follow-ups that agencies have to handle. Some of these are dictated by policy requirements and thus unavoidable. But others are discretionary, such as calls to check whether documents were received or follow-ups triggered by incomplete interviews. Such interactions often create confusion rather than clarity. By designing processes that provide clearer signals, earlier resolution, and fewer opportunities for cases to fall out of the pipeline, leaders can minimize that confusion without lowering standards. 

Reduce rework first—accuracy will follow 

Reducing churn is rooted in better operational design rather than changes to policies or standards. Better design starts with four essential moves that agencies can implement within existing policy frameworks. 

1. Design interviews to resolve issues, not defer them. The eligibility interview is one of the most consequential moments in the SNAP lifecycle—and one of the most common sources of downstream rework. When interviews conclude without resolving missing or inconsistent information, follow-up is all but inevitable. Additional document requests, pended actions, layered notices, and repeat contacts typically follow. Agencies that are serious about reducing churn are increasingly treating interviews as a resolution point rather than a precursor to follow-up. 
   
   This shift doesn’t require longer or more burdensome interviews. It requires better support at the point of interaction so that gaps are surfaced while the household member is still engaged. Some agencies are experimenting with tools that help flag missing or conflicting information during the interview itself, allowing workers to address issues before the conversation concludes. Addressing potential issues upfront reduces the need to chase documentation later and limits the number of cases drifting into the pend-and-close cycles that ultimately drive churn. 
   
   
2. Enforce simplified reporting through system behavior, not policy reminders. Simplified reporting is a powerful policy lever, but its operational impact depends on how it’s implemented. In many agencies, systems still behave as though all households are subject to full change reporting. Portals, forms, and notices prompt household members to report changes they’re not required to report. Staff are obligated to act on reported information, triggering verification and documentation requirements that add work—often worsening churn but not improving accuracy.  
   
   Getting results from simplified reporting requires smarter system design—including limiting prompts and setting narrower guidelines for when action is needed. For example, when a household member selects “report a change” in a self-service portal, the system can first identify that household’s reporting status. If the household is on simplified reporting, the portal can present a short, clear prompt such as, “Do you have one of the following changes to report?” followed by the specific required triggers. If the person selects “no,” the system can clearly instruct them that no reporting is required at this time. If they select “yes,” only then does the system proceed to the reporting screens. This approach prevents optional disclosures from entering the system, reducing unnecessary case actions and follow-up. 
   
   The same filtering logic can apply to phone interactions. Before capturing details, workers can be trained to use short, standardized questions to confirm whether a household is required to report a change. This prevents optional disclosures from becoming mandatory work, protecting both staff and households from unnecessary follow-up.  
   
   For multiprogram households, this filtering should be applied at the program level to ensure that SNAP reporting rules are enforced without preventing required reporting for other programs that the household is enrolled in. 
   
   
3. Improve self-service portals to eliminate status-check calls. Too often, self-service portals prompt people to upload documents without indicating whether further action is needed. From their perspective, this lack of visibility creates uncertainty. Was the document received? Is it under review? Do I need to do anything else? Without clear and timely answers, they often call or visit offices to check on their status.  
   
   A well-designed portal plainly shows case status notations such as “documents received,” “under review,” “processed,” and “awaiting additional information.” When household members can see where their case stands, they’re less likely to reach out for confirmation. 
   
   
4. Stabilize the pipeline with proactive communication. Missed interviews and deadlines are two of the most common drivers of churn. Well-timed reminders—especially for interviews, verification deadlines, and recertification milestones—can significantly reduce no-shows and late submissions.  

Taken together, these moves point to a simple operational truth: Accuracy is easier to achieve in a system that generates less rework. When churn declines, a virtuous cycle is created. Agencies process fewer repeat transactions, and when repeat transactions fall, staff regain time and focus. When they have more time per case, documentation quality improves and PER risk eases. Lowering that risk prevents disruption and ultimately empowers SNAP workers and HHS leaders to reduce churn further. The result: Households stay enrolled and keep getting the critical food assistance benefits they’re eligible for.