Most coverage notices are written to be legally defensible, not to be understood. The result is a document that satisfies a compliance reviewer and loses the member. With community-engagement requirements enforced from January 1, 2027, that tradeoff is dangerous: a notice the member cannot parse is a notice that ends in procedural disenrollment.
What the typical notice says
A common opening reads: 'Pursuant to applicable regulations, certain enrollees may be subject to community engagement requirements and must satisfy reporting obligations to maintain eligibility for medical assistance benefits.' Every word is accurate. None of it tells the reader what to do. It does not say who is affected, what counts, by when, or what happens if they do nothing. A member skims it, sees no clear demand, and files it away.
This is exactly the dynamic behind Arkansas, where roughly 18,000 people lost coverage and about one in four never understood the requirement applied to them. The notices were not lies. They were unreadable to the people who most needed to read them.
The rewrite
A plain-language version: 'You need to do one thing to keep your Medicaid. Report 80 hours a month of work, school, or volunteering, OR tell us why you qualify for an exemption. Do this by [date]. The easiest way: reply YES to this text or call [number]. If you do nothing, your Medicaid may stop on [date].' Same legal substance, radically different outcome.
The principles are repeatable. State the single action first. Use 'you' and short sentences. Name a concrete date, not a relative period. Make the consequence explicit but not threatening. Offer the lowest-friction path to comply. And read it aloud; if it sounds like a contract, rewrite it until it sounds like a person explaining something to a neighbor.
Plain language is not dumbing down. It is the discipline of moving the burden of comprehension off the member and onto the writer, which is exactly where it belongs when coverage is on the line.