Abigail Spanberger took the oath of office as Virginia’s 74th governor on January 17, 2026, becoming the first woman to lead the Commonwealth. Within hours, she signed Executive Order One, establishing the Economic Resiliency Task Force charged with implementing “changes to Medicaid and SNAP resulting from H.R. 1 while protecting access for eligible Virginians.” The careful phrasing captured the posture of a state that did not want work requirements but recognized they were coming regardless. Spanberger’s order also created an Interagency Health Financing Task Force to maximize federal funding during the transition, a tacit acknowledgment that Virginia’s fiscal exposure extended well beyond the compliance challenge itself.
The November 2025 elections had given Democrats a sweep of statewide offices and expanded their legislative majorities. Spanberger defeated Republican Winsome Earle-Sears by roughly 15 points, carrying the mandate of voters who had also returned Democratic control of both legislative chambers. The political context could not have been more favorable for resisting work requirements. But H.R.1 left no room for resistance. Virginia could choose how to implement, but not whether.
The scale of the task is substantial. Virginia’s Medicaid expansion, which began in January 2019 under a Republican legislature that negotiated a bipartisan deal with Democratic Governor Ralph Northam, covers approximately 600,000 adults. The Department of Medical Assistance Services, known as DMAS, must build verification infrastructure for this population using a decentralized network of 120 local Departments of Social Services that operate with significant independence from the state agency. Only 11 percent of local agencies complete applications within the 45-day federal timeline. Adding semi-annual work requirement verification to this system will test whether decentralized administration can be made to function at the speed federal law demands.
Virginia’s Expansion History#
Virginia was the 33rd state to expand Medicaid, arriving relatively late after years of legislative deadlock. Republican control of the House of Delegates blocked expansion from 2014 through 2017, despite Democratic governors pushing for adoption. The breakthrough came in 2018 when a sufficient number of suburban Republicans, responding to constituent pressure after the 2017 Democratic wave elections, joined Democrats to pass expansion with conditions.
Those conditions included a requirement that the state seek a Section 1115 waiver to impose work and community engagement requirements. Virginia submitted its waiver application in November 2018, proposing the COMPASS program: Complex Patient Assessment, Screening, and Services. COMPASS would have required 80 hours monthly of work, education, training, job search, or community service for non-exempt expansion adults, with a 90-day ramp-up period for new enrollees.
CMS approved Virginia’s waiver in March 2019, but the state never implemented it. Legal challenges to Arkansas’s work requirements, combined with the change in federal administration in 2021, led to withdrawal of the waiver. Governor Northam formally withdrew the COMPASS application, and the Biden administration revoked the underlying approval. Virginia enrolled 600,000 expansion adults over five years without ever requiring work documentation.
The COMPASS waiver is relevant to the current moment not because Virginia built implementation infrastructure, as it did not, but because the policy design work was completed. DMAS developed exemption categories, reporting frameworks, and compliance timelines that partially overlap with H.R.1’s requirements. Whether that institutional memory accelerates current planning depends on how much the agency’s composition has changed in the intervening years and whether the COMPASS design is compatible with federal specifications that differ in important details.
H.R.1 and Federal Requirements#
H.R.1 requires 80 hours monthly of work, education, job training, job search, community service, or caregiving for expansion adults aged 19 to 64. Virginia must verify compliance at application and at semi-annual redetermination. CMS issued initial guidance on December 8, 2025, with detailed regulations expected by June 1, 2026. The compliance deadline is December 31, 2026, with good-faith extensions available through December 31, 2028.
Exemptions cover pregnancy through 60 days postpartum, medical frailty, disability, full-time students, caregivers of dependents under 14 or incapacitated individuals, unemployment benefit recipients, and substance use disorder treatment participants. The mandatory outreach period from June 30 through August 31, 2026, requires Virginia to communicate requirements to its entire expansion population before enforcement begins.
DMAS Director Cheryl Roberts has indicated the department is in planning mode, awaiting the June 2026 detailed guidance before finalizing its approach. Roberts noted that Virginia has not submitted a state implementation plan and will not do so until federal specifications are complete. This cautious posture is consistent with a state that wants to implement the minimum federal requirements without volunteering for additional enforcement mechanisms.
The 120-Agency Problem#
Virginia’s most distinctive implementation challenge is structural. Unlike states that administer Medicaid through a centralized state agency, Virginia delegates eligibility determination to 120 local Departments of Social Services. Each is governed by a local board of social services, typically appointed by the county board of supervisors or city council. State policy flows through DMAS and the Department of Social Services at the state level, but execution depends on local agencies with varying staffing levels, technology adoption, and institutional capacity.
This structure served Virginia adequately when eligibility determination meant income verification at annual intervals. Work requirement compliance demands ongoing documentation, exemption adjudication, and appeals processing at a pace and complexity that magnifies local variation. A well-staffed agency in Fairfax County with broadband infrastructure and a population accustomed to digital interaction will process work verifications differently than a two-person office in Lee County serving an Appalachian community where internet access is unreliable and employment is largely informal.
The 11 percent on-time application completion rate among local agencies reflects this variation at its most consequential. Federal law requires Medicaid applications to be processed within 45 days. Virginia’s local agencies miss that deadline 89 percent of the time. Semi-annual work requirement verification imposes a faster cadence with higher stakes, since failure to verify means coverage termination rather than delayed enrollment.
Virginia’s IT infrastructure compounds the challenge. The Virginia Case Management System, or VaCMS, handles eligibility processing but was not designed for ongoing activity verification. Upgrading VaCMS to support work requirement documentation, exemption tracking, and automated data matching will require investment that the state has not yet budgeted. The Spanberger administration’s Economic Resiliency Task Force is charged with identifying these needs, but the gap between planning and deployment narrows as the December 2026 deadline approaches.
Regional Contrasts#
Virginia’s geography creates at least three distinct implementation environments, each with its own challenges.
Northern Virginia, anchored by Fairfax, Loudoun, and Prince William counties, is among the wealthiest and most educated regions in the country. Expansion adult enrollment is lower as a share of population, and those enrolled tend to have higher labor force participation and better access to digital verification tools. The challenge here is different: federal workforce disruptions from DOGE-related reductions in force at agencies headquartered in Northern Virginia may push previously stable federal employees and contractors onto Medicaid precisely as work requirements take effect. Virginia has an estimated 178,000 federal civilian employees, the second-largest concentration after the District of Columbia. Reductions in force, hiring freezes, and contract terminations ripple through the regional economy in ways that create new Medicaid applicants who must immediately demonstrate work compliance.
Hampton Roads and Richmond represent mid-range urban environments with significant military presence, healthcare systems, and service economies. Expansion enrollment is substantial, and the MCO infrastructure is relatively developed. Compliance challenges will center on populations in transitional employment, those working multiple part-time jobs, and communities where documentation literacy varies.
Southwest Virginia and the Southside present challenges that resemble those of Appalachian Kentucky or West Virginia more than the rest of the Commonwealth. Lee, Scott, Dickenson, Wise, and Buchanan counties have poverty rates exceeding 20 percent, limited broadband penetration, and healthcare provider shortages. The coal economy’s decline left communities dependent on disability benefits, seasonal employment, and informal economic activity that does not generate the wage records automated verification systems require. Ballad Health, the dominant hospital system in the region, operates under a cooperative agreement with the Commonwealth that requires it to maintain services in exchange for its effective monopoly. Coverage losses among the expansion population would stress Ballad’s financial model and the cooperative agreement’s sustainability.
The MCO Landscape#
Virginia completed its Cardinal Care managed care consolidation in July 2025, reorganizing its Medicaid managed care program into six regions served by five MCOs: Aetna Better Health of Virginia, Anthem HealthKeepers Plus, Molina Healthcare, Sentara Health Plans, and Virginia Premier Health Plan. Each expansion adult is enrolled in one of these plans, which serve as the primary point of contact for healthcare services and, increasingly, for member communication about eligibility requirements.
The Cardinal Care restructuring was designed to improve care coordination and reduce administrative fragmentation. It may inadvertently position Virginia’s MCOs to play a more active role in work requirement navigation than in states with more fragmented managed care landscapes. MCOs already have member engagement infrastructure, care coordination staff, and data systems that track utilization patterns indicating whether members are likely working, caregiving, or medically exempt.
The conflict-of-interest provisions in H.R.1 complicate MCO participation in compliance determination. MCOs have direct financial interest in member retention, which theoretically conflicts with objective compliance assessment. But the same financial interest motivates investment in navigation services that help members document existing compliance. Virginia’s approach to defining the boundary between prohibited compliance determination and permitted navigation support will significantly affect MCO operational strategy.
Coverage loss projections for Virginia range from 130,000 to 210,000 over the coming decade, depending on methodology and assumptions about exemption rates. KFF’s central estimate of approximately 210,000 losses reflects both direct work requirement terminations and the compounding effect of semi-annual redetermination on populations that experience intermittent eligibility.
Federal Workforce Disruption#
Virginia faces a dimension of work requirement implementation that no other state shares at equivalent scale. The federal government employs approximately 178,000 civilian workers in Virginia, concentrated in Northern Virginia but present across the state at military installations, VA hospitals, and federal offices. The Department of Government Efficiency’s workforce reduction initiatives, combined with agency reorganizations and hiring freezes, have created economic uncertainty that intersects with Medicaid eligibility in complex ways.
A GS-7 federal employee earning $48,000 annually is not Medicaid-eligible. But a contract worker whose position is eliminated may qualify for Medicaid expansion coverage if their income drops below 138 percent of the federal poverty level. That newly eligible person must immediately demonstrate 80 hours of monthly work activity, which may be complicated if they are between jobs, pursuing job search activities, or managing severance and unemployment transitions. The timing of federal workforce disruptions and work requirement implementation creates a population of newly eligible Virginians encountering the compliance system at its most nascent.
The defense contracting sector adds another layer. Northern Virginia’s economy depends heavily on contracts with the Department of Defense, intelligence community, and civilian agencies. Contract modifications, delays, and cancellations affect employment patterns in ways that standard wage data may not capture in real time. A contractor working reduced hours pending contract renewal is still employed, but their hourly verification may fall below thresholds if the reporting window misaligns with contract cycles.
What Virginia Will Likely Do#
Virginia under Spanberger will implement work requirements with maximum use of exemptions, automated verification, and administrative streamlining. The Economic Resiliency Task Force signals an approach that treats implementation as an exercise in harm reduction rather than enforcement. Democratic control of both legislative chambers ensures that any state legislation needed to support implementation will reflect this philosophy.
Specific policy choices likely include broad interpretation of medical frailty exemptions, use of Virginia Employment Commission wage data for automated work verification, maximum use of the good-faith extension if systems are not ready by December 2026, and investment in the outreach period to ensure expansion adults understand requirements and exemption pathways before enforcement begins.
The structural challenge of 120 local agencies will not be solved by policy preferences alone. Virginia will need to either centralize work requirement processing at the state level, which would require significant system changes and potentially legislative action, or provide local agencies with standardized tools, training, and staffing that reduce variation in execution quality. Neither path is quick.
Virginia’s most likely outcome is a state that implements work requirements reluctantly, interprets flexibility generously, invests in automated verification to minimize individual reporting burden, and uses every available extension and transition period to phase in enforcement gradually. Coverage losses will be lower than in enforcement-oriented states but higher than policy designers intend, because administrative infrastructure cannot be wished into existence and 120 local agencies cannot be brought to uniform competence on the timeline federal law provides.