Medicaid After H.R. 1

Why Errors Will Rise Unless States Reduce Friction Before January 2027
By Jim Garrity, Chief Client Officer, SingleStone Consulting

Abstract

H.R. 1 significantly increases Medicaid verification workload at a time when state systems are already at capacity and budgets are flat. States must implement work requirements by January 2027, and outreach infrastructure must be in place by summer 2026. That leaves little runway.

When these systems are overloaded, the result is rarely tighter fraud detection. It is more procedural failures, more churn, and higher downstream costs.

What happens if states do nothing?

• Administrative errors rise as workload outpaces capacity
• Eligible people lose coverage and cycle back through re-enrollment, driving up costs
• Delayed care shifts to expensive settings like the emergency room
• Traditional cost controls like hiring freezes and rate cuts make the problem worse

What can states do about it?

• Reduce friction through real-time, two-way communication
• Adopt ex parte-first workflows that reserve manual effort for complex cases
• Design operations for surge conditions, not ideal ones

In this article, you will find the data behind these dynamics, why conventional responses fall short, and a practical framework for redesigning operations before the capacity gap becomes a coverage crisis. 

What H.R. 1 Changes Operationally

H.R. 1 introduces three changes that directly increase the volume and complexity of eligibility work for state Medicaid agencies.

First, adults aged 19 to 64 enrolled through the ACA Medicaid expansion must now meet community engagement requirements, documenting 80 hours per month of work, education, job training, or community service to maintain coverage.

Second, eligibility redeterminations move from once a year to every six months, doubling the processing volume for the largest segment of Medicaid enrollment.

Third, the law delays Biden-era rules that would have streamlined enrollment and renewal processes, freezing in place the paper-heavy, manual workflows states were already working to modernize.

These requirements arrive as systems are still recovering from the largest eligibility processing effort in Medicaid’s history. 

The Capacity Trap

H.R. 1 does not arrive in a recovered environment—it arrives in a depleted one.

The implementation timeline is compressed:

• Outreach infrastructure required by summer 2026
• Work requirements take effect by January 2027

At an operational level, strain shows up in three places:

• More touches per case
• Less tolerance for backlog
• No automatic capacity increase

The result is what we call the Capacity Trap: increased requirements applied to systems already running at their limits, producing more procedural failures than they prevent. 

Budget Pressure Is Constraining Capacity

Budget realities are tightening capacity even further.

For example, Virginia projects:

• $410.3M general fund shortfall in FY 2026
• $2.8B shortfall across FY 2026–2028

States nationwide face similar pressures: rising administrative workload, reduced federal matching support, and constrained budgets.

When systems must do more with less, timelines compress—and systems default to closure rather than resolution. 

Why More Verification Produces More Errors

More verification does not automatically mean better outcomes.

In Medicaid oversight, an “error” often reflects missing or incomplete documentation—not ineligible enrollment.

As verification workload rises:

• Friction turns routine work into rework
• Capacity constraints turn compliance into procedural failure

A typical pattern:

• A notice is sent to an outdated address
• The individual never receives it
• The system records “no response”
• The case closes
• The individual reapplies

The result is more work—not less. 

Why Traditional Cost Controls Miss the Problem

Common responses under pressure often make things worse:

Hiring freezes
Backlogs grow, timelines compress, and procedural errors increase.

Automation without guardrails
Systems may accelerate closures instead of correct outcomes.

Provider rate cuts
Access declines, shifting care to more expensive settings.

These approaches reduce cost in the short term but increase it over time. 

Administrative Friction Is the Hidden Cost

Procedural disenrollment creates churn—and churn is expensive.

When automated (ex parte) renewals fail due to data gaps, cases move into manual workflows:

• Mail cycles
• Delayed feedback
• Increased risk of termination

Each step adds cost, delay, and failure risk.

We’ve seen this pattern before in overwhelmed unemployment systems during the pandemic. Medicaid now faces a similar dynamic. 

What Actually Works Under Load

There is no single fix. Effective solutions operate at multiple levels:

1. Reduce friction inside renewal workflows

• Use real-time, two-way communication (e.g., text, secure uploads)
• Default to ex parte renewals; reserve manual effort for complex cases

2. Protect operational capacity

• Prioritize high-risk populations
• Create specialized queues
• Track resolution times and closure reasons
• Use surge “war room” models during peak periods

3. Address budget reality in parallel

• Focus integrity efforts on high-impact areas (e.g., provider payments)
• Reduce avoidable emergency and hospital use

Pushing eligible people off coverage shifts cost—it doesn’t reduce it. 

Design for the Reality States Are In

Verification requirements are rising. Workload is rising. Budget pressure is real. The January 2027 deadline is not moving.

If systems remain paper-heavy and delay-driven, the outcome is predictable:

• Backlogs
• Procedural terminations
• Rework
• Higher downstream costs

Reducing friction increases throughput. Increasing throughput keeps eligible people enrolled and preserves staff capacity for complex cases.

But friction reduction alone isn’t enough. Systems must be designed to operate under stress—not ideal conditions. 

Where to Start

The risk isn’t overcoverage—it’s systems exceeding capacity.

Three actions create immediate leverage:

1. Identify where the system is breaking

• Track procedural closure rates
• Monitor re-enrollment volume
• Compare backlog timelines to response windows

2. Reduce friction before adding capacity

• Prioritize ex parte workflows
• Implement digital communication
• Add guardrails to automation

3. Design for surge, not steady state

• Build outreach infrastructure by summer 2026
• Prepare for January 2027 compliance
• Use real-time monitoring and surge models

SingleStone works with state agencies to redesign systems that hold up under real conditions—not ideal ones. 

About the Author

Jim Garrity is Chief Client Officer at SingleStone Consulting. He works with state agencies and regulated organizations on modernizing high-volume systems where operational reliability, compliance, and human impact intersect.

About SingleStone

SingleStone is a data and technology consultancy that partners with public sector and highly regulated organizations to design resilient systems that operate reliably at scale—with a focus on workflow modernization, data-driven decision support, and capacity-aware system design.