The federal enrollee-notice window for H.R.1 community-engagement (work) requirements runs June 30 through August 31, 2026. For a Medicaid managed care organization, this is not a grace period — it is a compliance deadline with direct revenue consequences. Every member who reaches January 1, 2027 without understanding what is required of them, and without claiming any exemption they qualify for, is a procedural disenrollment risk that shows up as lost capitation in the first quarter of 2027.
What the federal window requires
CMS's Interim Final Rule (CMS-2454-IFC, effective June 1, 2026) requires that states and their contracted MCOs reach subject enrollees — generally Medicaid expansion adults ages 19–64 — through mail plus at least one additional channel before August 31, 2026. The two-channel minimum exists because no single channel reliably reaches a mobile, lower-income population. A mailed notice sent to a six-month-old address, with no follow-up, does not satisfy the spirit or the letter of the rule.
Required content in each notice includes: (1) a plain-language explanation of the community-engagement requirement — what counts, how many hours, and how to report; (2) the full list of exemption categories and how a member can claim one; (3) the consequences of non-compliance, stated clearly and without bureaucratic softening; and (4) reporting instructions, including the specific portal, phone number, or paper form the member must use. A notice that omits any of these four elements is incomplete.
Plain language and multilingual access are not optional
The Arkansas 2018–19 program experience is the field's most-cited cautionary data point: roughly 18,000 people — about one in four subject enrollees — lost coverage, with no measurable employment gain. Post-implementation analyses consistently found that a large share of those members never understood the requirement applied to them. The notices existed. The comprehension did not.
Plain language means an eighth-grade reading level or below, active voice, and a single clear call to action in the first paragraph. Multilingual access means Spanish at minimum for most state markets, and additional languages wherever the plan's enrollment data shows a meaningful limited-English-proficient population. Translating the English notice word-for-word and calling it done is not sufficient — a notice that is grammatically correct but culturally flat still gets ignored. Native-language reviewers, not machine translation alone, are the standard.
The checklist: eight things to confirm before August 31
Before the window closes, MCO compliance and communications teams should verify: (1) Member file is segmented — subject enrollees are identified separately from exempt and excluded populations. (2) Mail notices are printed and in queue, with updated address data pulled as close to send date as possible. (3) A second channel — SMS, IVR, email, or in-app — is scheduled and technically tested. (4) Notice content covers all four required elements (requirement, exemptions, consequences, reporting). (5) Plain-language and eighth-grade-level review is documented. (6) Spanish-language version is ready and reviewed by a native speaker. (7) Other threshold languages are covered per state contract and CMS guidance. (8) Exemption claims can be processed — the back-end workflow exists before the outreach triggers demand.
For most MCOs, the limiting constraint is not willingness — it is the time required to build, review, translate, and stage materials that have never existed before. Plans that treat the August 31 window as a production deadline, not a policy milestone, are the ones that will enter 2027 with retention intact. If your plan needs a rapid-build partner for CMS-compliant, multilingual notices inside the federal window, the Aug 31 Notice & Outreach Rapid Pack is designed to deliver in two to three weeks. Start with our Coverage-Loss & Retention ROI Calculator to size what your plan has at risk — then schedule a readiness audit before the window closes.