twimco.Let’s talk ↗︎
Menu
Field notes / Buying software

CMS gave states until June 30 before work-rule denials begin, but January 1 still counts. Use the gap to rehearse

If your state takes CMS's optional delay, nobody loses Medicaid for missing a work requirement before July. That's not the same as the system having six months to get ready. Part of it has to work on January 1 anyway.

Editorial engraving of a caseworker pointing between two stacks of unlabeled file folders on a table while a developer with a laptop sits beside her.

On November 13, 2026, CMS offered states an optional hold harmless period through June 30, 2027 for the Medicaid work requirement that starts January 1. States that opt in must still check whether people meet the requirement or are excluded, but may not deny applications or end coverage solely for failing it. States must tell CMS by December 11. Treat the months as a rehearsal: measure how often automated checks find nothing, and fix notices before denials begin.

What CMS announced

On November 13, the Centers for Medicare & Medicaid Services announced an optional hold harmless period for the Medicaid work requirement that starts on January 1, 2027. It runs through and including June 30, 2027. A state that uses it will still assess whether each person meets the requirement or qualifies for an exclusion. What it won't do, during those months, is deny an application or end coverage for an otherwise eligible person solely because they didn't meet the requirement.

KFF's note on the announcement adds two details that matter to anyone building the systems. States have to tell CMS by December 11 if they plan to use the period. And CMS says plainly that states must keep working toward full compliance with the law. The delay is for fixing things, not for waiting.

CMS's release names the audience: states that are implementing on January 1 and can use the transition period "to improve their systems and processes." That's an invitation to treat the first six months as a working rehearsal, if a state chooses to.

Two calendars

It's tempting to say the date moved. It would be more accurate to say the program now runs on two calendars.

On the first calendar, nothing moves. From January 1, the state still has to look at each person and decide whether they meet the requirement or are excluded. That means the data matching, the notices and the case records all have to exist and work on day one. If the matching misses people, or the notices go out in a confusing form, the damage on that calendar is a bad record and a worried person, even if no one loses coverage yet.

On the second calendar, the consequences wait. Denials and disenrollments for people who can't show they meet the requirement can't happen until July 1, for a state that opts in. That calendar gives a state room to find out how often its data can't answer the question, and what happens to those people next.

The mistake to avoid is treating the second calendar as if it were the first. A system that's "ready" only on June 30 hasn't been rehearsed on anything.

Decision guide

Two calendars for the same program

ConsiderationStarts January 1, 2027 either wayCan wait until July 1 if the state opts in
Checking peopleAssess whether each person meets the requirement or is excludedDenying an application or ending coverage solely for failing the requirement
Data matchingUse data the state already has to verify activities and exclusionsAsking people to prove what the state could have checked
NoticesTell people what was verified, what is still needed and where to get helpConsequences attached to those notices
Compliance directionStates must keep moving toward full complianceFull enforcement
Decision framework built from CMS's Nov 13, 2026 announcement and KFF's summary; the rows are a reading aid, not CMS wording.
A date that moves still leaves a system that has to work on the old one.

What has to work on January 1

CMS lists four things it strongly encourages for every state implementing the requirement, and they read like a build checklist. Use reliable data the state already has to verify qualifying activities and identify exclusions before asking people for more. Give clear, timely notices that say what the state has verified, what it still needs and how to respond or get help. Test the whole path, so data matching, notices and eligibility decisions work together, including how the system treats missing, outdated or conflicting information. And coordinate with community partners who can connect people to work, education and training.

The June 2026 interim final rule lists what counts: for certain applicants and members aged 19 to 64, 80 hours a month of work, community service or a work program, half-time enrollment in school, a combination of those totaling 80 hours, or meeting a specified monthly income threshold, unless the person is excluded. That's a lot of different evidence from a lot of different sources. The first test of a system is what it does when the evidence is missing.

Use the months to measure

If a state takes the hold harmless period, the most valuable thing it has is a stretch of time in which a wrong answer doesn't cost anyone their coverage. Spend it learning.

Start by counting a single thing: how often the automated checks found nothing. Then read those cases. Was the person truly not working, or was the employer's data late, or filed under a different name, or a different month? Every pattern you find is a fix to the matching, or a line to add to a notice. Keep the count by reason, not just in total, because "no data" and "conflicting data" call for different fixes and different people.

Next, read the notices as the recipient. CMS wants them to say what was already verified. For example, a notice that says "we need more information" is a worse notice than one that says "we confirmed your wages for September and October; we still need November." Rewrite the worst ones and check whether the calls to the help line drop. We don't have any state's numbers to quote, and we won't make any up. The point is to collect your own.

Finally, test the ugly paths on purpose: two sources that disagree, a record that's two months out of date, a person who works for three employers. Do it with the caseworkers who will handle the exceptions, not just with the developers.

What to ask your vendor

If a vendor is building or extending your system, ask three questions this month. Which parts of the build are required on January 1, and which can wait? How will we see, case by case, why a person was marked verified or not verified? What does the report look like on the first day of February, and who reads it?

Ask, too, who at the vendor can change a notice's wording without a release, because the first drafts will need changing. If the answers are vague, that's useful to know now. You can ask for a different cut of the work while there's still time, or plan for the staff who'll cover the gap by hand.

A date that moves still leaves a system that has to work on the old one. One habit helps whichever dates you're working to. Keep a single written list of what has to be live on January 1, with a name and a date beside each item, and update it at every weekly check-in. A shared list that everyone reads is worth more than a perfect plan in someone's head.

Our government and public sector work starts from how a request really moves through an agency, then builds the intake, review and handover around it. If you're working out what has to be live on January 1 and what a rehearsal could prove, talk to us.

Related work: Sutton|Place

Sequence of work

A rehearsal plan for the months in between

  1. By December 11, 2026

    A state tells CMS whether it will use the hold harmless period (per KFF).

  2. January 1, 2027

    The requirement starts; the state assesses people and records what the data could and couldn't verify.

  3. January to March

    Read the cases where automated checks found nothing. Rewrite the notices those people received.

  4. April to June

    Test missing, outdated and conflicting data end to end, with staff and community partners.

  5. June 30, 2027

    The hold harmless period ends. Denials can begin for the people the system could not verify.

Illustrative plan; dates from CMS and KFF are marked, the steps are our suggestion.
twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Sutton Place ↗︎