When states and federal officials talk about implementing Medicaid work requirements, most of the conversation — and most of the money — focuses on eligibility systems: the software platforms that will verify whether a member has met the 80-hours-per-month community-engagement requirement, process exemption documentation, and trigger disenrollment when a member falls out of compliance. These are complex, expensive systems, and the ten largest Medicaid technology vendors pledged a combined $600 million or more to build and upgrade them.
What that conversation almost entirely omits is what happens between the eligibility system and the member. Who tells the member what the requirement is? Who explains, in language the member can understand, that they may already qualify for an exemption? Who sends the notice in Spanish to the member whose primary language is not English? Who follows up when the first notice goes unanswered? That gap — between the eligibility system and the member — is the member-engagement layer, and it is effectively unowned.
What does the eligibility layer actually do?
The eligibility and verification layer is the back-end infrastructure of Medicaid administration. It determines whether a member meets the income, residency, and categorical requirements to be enrolled. Under H.R.1, the community-engagement requirement adds a new input to that calculation: did this member report 80 hours of qualifying activity this month, or do they have a documented exemption? The eligibility system processes that input, updates the member's status, and generates the administrative action — continued enrollment, a notice of non-compliance, or disenrollment.
What the eligibility system does not do is communicate with the member in human terms. It does not explain what qualifies as community engagement. It does not proactively identify members who appear to meet an exemption and prompt them to document it. It does not send a plain-language letter in the member's language explaining what will happen on a specific date if no action is taken. Those functions sit outside the eligibility platform — and in the current implementation landscape, largely outside any contracted scope of work.
What is the member-engagement layer?
The member-engagement layer is the set of communications and assistance functions that connect the administrative mandate to the human being it affects. It includes: CMS-compliant plain-language notices explaining the requirement and the deadline; multilingual outreach in the member's primary language; exemption education that proactively surfaces the exemption categories a member may qualify for; member assistance tools like an 'Am I exempt?' navigator that helps a member self-identify; omnichannel delivery across mail, SMS, and IVR to reach members wherever they are; and reporting that lets the MCO or state agency track who has been reached, who has responded, and where members are falling through.
None of these functions are embedded in the eligibility platforms that the major vendors are building. The eligibility system generates a trigger; the engagement layer is what acts on that trigger in a way the member can understand and respond to.
Why is this layer suddenly essential — and why is it unowned?
The dominant failure mode in prior Medicaid work-requirement programs was not members refusing to comply. It was eligible members losing coverage because they never understood what was being asked of them, or because they qualified for an exemption they did not know existed, or because a notice sent to a stale address was never received. In Arkansas's 2018-2019 program, roughly 18,000 people lost coverage — approximately one in four subject enrollees — with no measurable gain in employment. Analyses attributed the coverage loss overwhelmingly to procedural and communication failures, not to members who were actually ineligible.
H.R.1 scales that risk nationally. The community-engagement requirement will apply to many Medicaid expansion adults ages 19 through 64. OBBBA also shortens the eligibility redetermination cycle for expansion adults from annually to every six months, doubling the administrative touchpoints where an eligible member can fall off coverage through confusion or missed paperwork. A federally-mandated enrollee-notice window runs June 30 through August 31, 2026, with enforcement beginning January 1, 2027.
The combined $600 million or more that major eligibility-system vendors pledged was concentrated on the back-end systems. That investment was necessary — states cannot process work-requirement reporting without upgraded eligibility infrastructure. But it left the member-facing layer without a priced product, a named contractor, or a funded scope of work at most MCOs and state agencies. The engagement layer is unowned not because it is unimportant, but because it falls between the eligibility-system scope and the member's front door.
What does this mean for MCOs?
For a Medicaid managed care organization, procedural disenrollment is not a policy problem — it is a revenue problem. Every procedurally disenrolled member is lost capitation premium each month. A plan with 100,000 members subject to the work requirement at a $450 per-member-per-month capitation rate and an 18% procedural disenrollment rate has roughly $100 million in annual premium revenue at risk. The members who are most likely to be procedurally disenrolled — those with low literacy, primary languages other than English, or unstable housing — are also the members most likely to re-enroll within months once the confusion is resolved, producing churn costs on top of the premium loss.
An MCO that invests in the engagement layer before January 2027 is not spending on charity. It is protecting its member base. The Coverage-Loss and Retention ROI Calculator at medicaid.atypical.global/calculator.html lets a plan estimate its specific premium-at-risk and the return on a retention engagement.
What does this mean for state agencies and primes?
State Medicaid agencies face the August 31, 2026 federal notice-window obligation regardless of where their eligibility-system implementation stands. CMS requires mail plus at least one additional channel for every subject enrollee before that date. For state agencies currently contracting with eligibility-system primes, the notice window may fall inside an implementation schedule that has not yet built or procured a member-communications capability. A member-communications vendor that can be added to the prime's scope as a subcontractor — and that has a pre-built, CMS-compliant notice pack deployable within the window — solves that gap without requiring a separate procurement.
For primes, a member-communications subcontractor also strengthens the bid. The engagement-layer gap is visible to state procurement officials who read the H.R.1 implementation guidance. A prime that can demonstrate a member-facing capability in its proposal — rather than leaving the engagement layer as an open question — presents a more complete implementation picture. If the subcontractor is a minority-owned firm, it may also help the prime meet Business Enterprise Program or diversity participation requirements embedded in the state contract.
The 59-page 2027 Medicaid Coverage Retention Report, the 50-state procurement tracker, and the Aug 31 Notice Pack are available at medicaid.atypical.global/resources.html. To discuss the engagement layer for your plan or state, use the contact form at medicaid.atypical.global/#contact.