The CMS-2454-IFC Interim Final Rule, effective June 1, 2026, makes clear that every state implementing H.R.1 community-engagement requirements must give written notice to affected Medicaid members with at least one additional outreach channel between June 30 and August 31, 2026. That window is now inside 90 days. For most state procurement offices, that means the award needs to be in place before July is over. The sequence is unforgiving: competitive solicitation, evaluation, award, and onboarding all have to clear before a vendor can produce a single compliant notice.

Scope what the mandate actually requires

A common mistake is to treat the member-notice obligation as a print job. It is not. CMS requires plain-language, culturally appropriate notices that explain the requirement, the exemption pathways, how to report, and the consequence of non-reporting. That scope encompasses notice redesign and content authoring, multilingual translation and quality review (including threshold languages under your state’s Title VI LEP plan), an SMS or IVR script for the additional outreach channel, an exemption education insert, comprehension testing with member panels, and a reporting and delivery-confirmation mechanism. Each of those is a statement of work element. Omitting any of them from the solicitation creates compliance risk that lands back on the agency after the vendor departs.

Build your procurement around deliverables, not hours. A deliverable-based scope—notice package delivered by July 25, SMS script by July 28, comprehension-testing summary by August 5—creates a schedule the vendor and the agency can both hold. An hours-based engagement stretches to fill whatever time is available, which is exactly the time you do not have.

Use existing contract vehicles wherever possible

A full competitive RFP process takes 60 to 90 days in most states. That is longer than the time between now and August 31. State procurement offices should first check whether an existing MMIS or health-IT contract vehicle, a master services agreement, or a cooperative purchasing arrangement can be used to bring a vendor on board in two to three weeks rather than two to three months. Many states have statewide IT or communication-services vehicles that cover member-communications work. If yours does, a task order off that vehicle is the fastest legally defensible path.

If no existing vehicle applies, a streamlined sole-source or emergency procurement may be defensible given the federally-imposed deadline, but document the justification carefully. CMS does not excuse a non-compliant notice window because procurement took longer than expected.

The risk buried in bureaucratic language

Agencies that hand a notice template to a print vendor without content rework often produce legally complete but behaviorally useless notices. The language reads like a regulatory citation because it was written by regulatory staff. Members read at a sixth-grade level on average; Medicaid populations skew lower. A notice that opens with “Pursuant to 42 CFR § 435.916 and the requirements of the One Big Beautiful Bill Act, enrollees subject to community-engagement requirements must demonstrate…” will not produce the action rates the state needs. The dominant failure mode in prior work-requirement programs—including Arkansas—was not member non-compliance. It was member non-comprehension. Arkansas saw roughly 18,000 people lose coverage, with analyses finding about one in four affected enrollees never understood the requirement applied to them. That is a notice failure, not a compliance failure.

Diversity and Business Enterprise Program participation

Most state procurement offices have Business Enterprise Program (BEP) or MWBE participation goals for contracts of this size. Vendors who already have BEP-certified teaming partners or subcontractor relationships in communications, translation, or outreach can satisfy those goals faster than vendors who have to build those relationships after award. When evaluating proposals, give weight to the specificity of the diversity plan: a named certified subcontractor for translation services is stronger evidence than a commitment to “identify diverse partners.” Subcontracting to a certified firm for the multilingual component is a natural fit and a common way to meet participation goals on this type of work.

The timeline math

Working backward from August 31: allow two weeks for CMS review and any state legal review before the notice mails, one week for print production and mailing logistics, one week for comprehension-testing revisions, two weeks for translation and review, and two weeks for draft development. That puts the vendor start date at approximately July 1. Which means award by June 28. Which means you needed to issue the solicitation by the end of this week. Every day of delay compresses a timeline that has no slack. Agencies that move now preserve options. Agencies that wait until mid-July will be choosing between a rushed competitive process and a sole-source emergency justification—neither of which is comfortable to defend.

If your agency has not yet opened a procurement for member-notice work, the first step is a readiness audit that maps your current notice inventory, your threshold-language obligations, your existing contract vehicles, and the gap between where you are and what August 31 requires. Our 2027 Readiness Checklist and the 50-State Procurement Tracker at medicaid.atypical.global/states/ are built for exactly that assessment. Start there, then move.