It is July 5, 2026. The federal enrollee-notice window for H.R.1 community-engagement requirements opened on June 30 and closes on August 31. That leaves roughly eight working weeks. For a Medicaid managed care organization that has not yet mailed its first notice — or has mailed but not yet layered a second channel — the remaining calendar is tight but workable, provided July is treated as an execution month, not a planning month.

The stakes are well documented. In Arkansas in 2018–19, roughly 18,000 people lost coverage under a similar requirement, most of them for procedural reasons rather than actual ineligibility. The lesson was not that outreach is impossible; it was that late, single-channel, English-only outreach fails predictably. CMS's interim final rule (CMS-2454-IFC, issued June 2026) reflects that lesson, and states are moving with the help of a $200 million federal implementation appropriation. Your plan's job in July is to make sure your members are not the ones who learn about the requirement in January 2027.

Week of July 6: lock the member file

Everything downstream depends on segmentation. This week, confirm three lists: subject enrollees (generally expansion adults ages 19–64), likely-exempt members based on data you already hold (pregnancy flags, disability indicators, SUD treatment claims, age), and members with stale contact data. Pull address updates from every source available to you — pharmacy fills, recent claims, call-center records, USPS NCOA. A perfect notice sent to a two-year-old address is a compliance artifact, not communication.

Week of July 13: finalize content and translations

By mid-July, notice content should be frozen. That means the four core elements are covered — what the requirement is, which exemptions exist and how to claim them, what happens if a member does nothing, and exactly how to report — and the plain-language review is documented. Spanish should be reviewed by a native speaker, not just machine-translated, and any additional threshold languages required by your state contract should be in final review. If translation is your bottleneck this week, escalate it now; it does not compress later.

Week of July 20: mail drop and channel two

Target the physical mail drop for the week of July 20 or earlier. Mailing in late July leaves August for the second channel and for remediation of returned mail. The second channel — SMS, IVR, email, or in-app messaging — should be scheduled to land seven to ten days after the mail piece, referencing it directly. Two channels that arrive months apart read as two unrelated messages; two channels that arrive a week apart read as a campaign.

Week of July 27: returned mail and non-responders

By the last week of July, returned mail starts coming back. Treat every returned envelope as a data point: that member did not get the notice, and the second channel just became the primary channel for them. Build a returned-mail queue with a defined owner and a defined action — phone outreach, alternate address lookup, or community-partner referral — rather than letting envelopes accumulate in a mailroom.

August: measure, remediate, document

August is for closing gaps, not starting work. Track delivery rates by channel, exemption-claim volume, and inbound call themes. Where comprehension looks weak — members calling to ask what the letter means is a signal, not noise — adjust scripts and follow-up messaging. And document everything: send dates, channel coverage, language coverage, and remediation steps. When your state or CMS asks how the window was executed, the answer should be a report, not a reconstruction.

The honest checkpoint

If your plan cannot check off segmentation, final content, and a scheduled mail drop by the end of July, the remaining window is no longer sufficient for a comfortable internal build. That is the point at which a rapid external build — production-ready, CMS-aligned, multilingual notice packages delivered in weeks — stops being a nice-to-have and becomes the difference between a documented, defensible campaign and a scramble. Either way, the calendar is the same for everyone: the window closes August 31, and enforcement begins January 1, 2027.