The dual deadline
§71119 of H.R. 1, the One Big Beautiful Bill Act (signed July 4, 2025) requires states to implement community engagement requirements for ACA Medicaid expansion adults ages 19–64, plus individuals enrolled through a waiver providing equivalent coverage. Those individuals must complete at least 80 hours per month of qualifying activities — work, community service, a SNAP work program, half-time educational enrollment, or a combination — or demonstrate an exemption. Qualifying income (monthly earnings at or above the federal minimum wage times 80 hours, roughly $580 at $7.25/hour) is also a compliance pathway. When data cannot confirm compliance, the state sends a noncompliance notice; the individual has 30 calendar days from receipt to demonstrate compliance or a qualifying exclusion, with coverage continuing during that period; if no showing is made the state must consider other eligibility bases, then deny or disenroll by the end of the following month, after advance notice and fair-hearing rights (§1902(xx)(6)).
§71107 of H.R. 1 is a separate provision that requires six-month eligibility redeterminations for ACA expansion adults, also effective January 1, 2027. H.R. 1 provides no good-faith exemption for it; the §1902(xx)(11) exemption covers community engagement only.
The two mandates impose operationally distinct system requirements that happen to share a deadline. Work requirement verification is a new data integration problem: confirming monthly activity hours against workforce records most Medicaid eligibility platforms were not built to query. The six-month redetermination cycle is a throughput scaling problem: processing twice as many renewals in the same time with the same staffing. Solving one doesn't help with the other.
CMS issued initial guidance on December 8, 2025, followed by State Medicaid Director Letter #26-001 on redeterminations on March 6, 2026. On June 3, 2026, CMS published an Interim Final Rule (91 FR 33348, effective July 31) with the most detailed implementation requirements yet. That rule narrowed the definition of medical frailty, requiring a condition that "significantly impairs the individual's ability to comply," which Manatt Health found "sharply narrows who qualifies for the exemption." States that had planned to use self-declaration to verify work hours in 2027 can still do so: the rule allows self-declaration through December 31, 2027, but beginning January 1, 2028, documentation is required wherever it is reasonably available, and medical-frailty attestations shift to once per enrollment period. States leaning on self-declaration in 2027 face a second implementation cliff a year later.
The ex parte verification problem
H.R. 1 requires states to use available data before requesting documentation from beneficiaries. CHCS describes this as a data matching requirement: states must query payroll records, Medicaid payment and encounter data, and other existing sources to verify compliance before asking the individual to prove it. This is the same ex parte logic that governs standard eligibility renewals, applied to a new data type.
State Medicaid agencies are already required by regulation (42 CFR 435.948) to request wage and income data from the state workforce agency and unemployment insurance administrator, and to access SNAP and TANF data. But those feeds were built for income verification, not activity verification. Quarterly wage records carry earnings totals, not monthly hours. Community service, work-program participation, and educational enrollment are not in those feeds at all. The income pathway (monthly earnings at or above the federal minimum wage times 80 hours) is where wage data becomes directly usable — but verifying the activity-based pathways requires a different integration. Many states will need new data-use agreements and query logic, and records from education agencies or community organizations may arrive through a manual or batch process rather than real-time lookups.
This is an integration project, not a configuration change. States that haven't completed that integration by January 1 face a choice between two operationally expensive fallbacks:
- Manual documentation requests: Ask every potentially-subject individual to submit pay stubs, employer letters, or enrollment verifications. This replaces an automated query with a case manager review for a population that may number in the hundreds of thousands. At Montana's scale, the Department of Public Health and Human Services explicitly used its hold-harmless period to help beneficiaries understand how to comply before facing denials. Without that runway, manual processing creates backlogs immediately.
- Default to non-compliance: Treat individuals whose status cannot be ex parte confirmed as non-compliant, generating 30-day notices for many who are actually meeting the requirement. This produces both erroneous coverage losses and an appeals volume that most state Medicaid agencies are not staffed to absorb.
The structure adds another dimension. Qualifying activities and activity-based exceptions are assessed for the look-back months (one to three months before the application or renewal date). Specified-excluded status — medical frailty, caregiver of a child 13 and under, veteran with total disability, and others — is assessed at the time of application or renewal using current information (42 CFR 435.556–435.557). The IFR requires checking exclusions before compliance, so the system must first run a current-status exclusion check and only proceed to the activity-data query if no exclusion applies. A system that applies the same data extract to both checks, or assesses current exclusion status against look-back-period data, risks the wrong result for individuals whose status changed during the look-back window.
The redetermination throughput problem
The shift from annual to six-month redeterminations isn't just about volume — it's about the composition of the caseload. The expansion population that will face this requirement on January 1 has been on annual redeterminations. States have calibrated their ex parte success rates, staffing ratios, and processing timelines against that cadence.
Doubling the redetermination cycle doubles workload while timelines and staffing stay fixed. To use a hypothetical: a case management team processing 10,000 annual renewals would need to process 20,000 within the same calendar year, in the same staffing structure, with the same system throughput constraints. States that have invested in improving ex parte success rates — where the system automatically renews without requiring the beneficiary to respond — can absorb more of this through automation. States whose ex parte rates are low face a staffing problem that a system fix cannot resolve by January 1.
CBPP's analysis of the January 2027 deadline is worth reading in full. In CBPP's scenario for a state implementing community engagement on January 1, 2027, the first work-requirement coverage loss could be effective as early as April 1, 2027 — when the state applies the requirement to its March 2027 renewal cohort. That provides a brief diagnostic window, but only if the state can distinguish which system generated a coverage loss. If work requirement denials and redetermination disenrollments are running simultaneously in overlapping cohorts, attribution becomes difficult.
What Montana and Nebraska are showing
Montana implemented on July 1, 2026 through a State Plan Amendment under federal law. Montana's community engagement statute is MCA 53-6-1308; the federal requirement governs the federal ACA expansion population. DPHHS built in a hold-harmless period: individuals found non-compliant during July, August, and September received notices and outreach but were not disenrolled. DPHHS ended the hold-harmless period September 30 and began enforcing denial and disenrollment in October 2026. The agency described the hold-harmless period as time for beneficiaries to understand the requirements; it also served — as Spartan X reads the sequence — as a period for identifying workflow gaps before those gaps produced irreversible coverage terminations.
Nebraska implemented on May 1, 2026 through a state plan amendment, following an announcement in December 2025. KFF's early insights brief reports Nebraska's September 17, 2026 Medicaid Advisory Committee data: of the 7,280 renewals processed July through August 2026 that required a work-requirement determination, 57% of renewing individuals qualified for an exclusion. Nebraska's verification approach combines automated data matching with self-declaration forms that carry a 30-day return deadline. Montana's choice to build a hold-harmless period before enforcement is itself an implementation signal — states that go live on January 1, 2027 without one are doing their system learning in production, with coverage terminations running in real time.
Decision framework for the next 62 days
State eligibility system directors with January 1 deadlines have a short but workable decision window:
Request a good-faith exemption if your ex parte pipeline isn't validated. §1902(xx)(11), added by §71119, lets the Secretary exempt a state "demonstrating a good faith effort to comply" — weighing actions taken, significant barriers (including those related to "funding, design, development, procurement, or installation of necessary systems or resources"), and a detailed plan and timeline. The CMS IFR preamble describes the threshold as "extraordinary, severe, or unexpected issues that hinder their progress." CMS approves initial exemptions for no more than six months (42 CFR 435.560(c)(1)), with quarterly reporting and possible early termination for lack of continued progress; no exemption extends beyond December 31, 2028. A well-documented gap in the activity-data integration — with a credible remediation timeline — is a reasonable basis for a request. An exemption is not a failure; it is the correct risk management decision when the alternative is erroneous coverage terminations at scale.
Understand what can and cannot be deferred. The community engagement exemption under §1902(xx)(11) covers work requirements only. Six-month redeterminations under §71107 have no exemption mechanism — they proceed on January 1, 2027 regardless. A state with a credible exemption request for community engagement still must execute six-month renewals on schedule. Plan the two tracks separately.
Prioritize ex parte architecture over manual processes. If January 1 is fixed, the most valuable hours between now and then are spent validating the ex parte query logic against real workforce data samples — not training case managers on manual review procedures. Manual workarounds can absorb the residual cases that ex parte doesn't resolve; they cannot absorb the primary verification burden at scale.
Test the notice generation system before it runs. The outreach notices that must go out before implementation (§1902(xx)(8)) require regular mail plus at least one additional contact method. The noncompliance notices that trigger the 30-day response period (§1902(xx)(6); 42 CFR 435.558) have their own content and accessibility requirements. Both notice streams are recurring sources of legal challenge in Medicaid. Verify that the notice logic, address data, contact method records, and fair-hearing rights language are current and accurate before the first batch goes out.
Calibrate staffing for the first 90 days. Work requirement appeals are a new case category. Staff need to know which exclusions apply, how to evaluate submitted documentation, and where to route cases that involve borderline medical-frailty determinations under the IFR's tightened definition (the "significantly impairs the individual's ability to comply" standard). Nebraska's data showed 57% of renewing individuals qualified for an exclusion — understanding which exclusion categories will dominate in your population matters for staffing the review queue. Montana's hold-harmless period served this function; states without one need to build it into the training plan before January 1.
What's the right next action
For a state Medicaid IT director reviewing this on October 31, the most valuable immediate action is an ex parte validation run: take a sample of the expansion population that would be subject to work requirements, attempt to verify compliance using the current data pipeline, and measure the failure rate. If the failure rate is high enough that manual review would be required at scale, that is the technical basis for a good-faith exemption request — and documenting it now, rather than in February, is what enables a credible conversation with CMS. Nebraska's data (57% exclusion rate) suggests that most of the verification burden may fall on the exclusion-check side, not the activity-verification side, which is relevant to both the staffing plan and the data integration priority list.
Spartan X has served as a trusted advisor to state executive leadership — including CDLE, OIT, and the Governor's office in Colorado — and has designed and delivered major state technology platforms involving systems integration across multiple agencies. The questions that determine whether a work requirement verification system holds together at scale — how to design queries against heterogeneous agency data, how to structure the audit trail for federal compliance reporting, how to make a system adaptable to the next policy change — are the same ones that arise in any state platform where eligibility, verification, and cross-agency data exchange intersect.
Sources and further reading
- H.R. 1, One Big Beautiful Bill Act, 119th Congress (Public Law 119-21, signed July 4, 2025) — §71119 (community engagement), §71107 (six-month redeterminations)
- CMS Interim Final Rule, 91 FR 33348 (June 3, 2026) — regulatory text at 42 CFR 435.550–435.563; effective July 31, 2026
- CMS CMCS Informational Bulletin, December 8, 2025 — initial implementation guidance
- State Medicaid Director Letter #26-001, March 6, 2026 — six-month redetermination transition guidance
- KFF Medicaid Work Requirements Tracker Overview — 44-jurisdiction count and state-level implementation decisions
- CHCS: A Summary of Federal Medicaid Work Requirements — including look-back requirements and data matching obligations
- Manatt Health: CMS' Medicaid Work Requirements Rule: A 50-State Analysis of Additional Coverage Losses (July 2026) — narrowed medical frailty definition, self-attestation rules, and 50-state coverage-loss estimates under IFR vs. plain-language H.R. 1
- Montana DPHHS: Medicaid Community Engagement Requirements Begin July 1 (June 30, 2026) — state announcement of implementation and qualifying activities
- KFF: Early Medicaid Work Requirement Insights from Nebraska — September 2026 data from Nebraska's Medicaid Advisory Committee
- CBPP: Timing of State Implementation of H.R. 1's Medicaid Policies — implementation timeline scenarios, coverage-loss timing
- Kaufman Dolowich: New Medicaid Work Requirements Under the One Big Beautiful Bill Act — legal summary of state implementation obligations including notice requirements
- National Rural Health Association: H.R. 1 Medicaid Work Requirements Summary — provision-by-provision analysis including effective dates
