Same Federal Rule, Different Evidence Architecture

POST-PUBLICATION UPDATE — OCTOBER 13, 2026

After the initial publication, Indiana FSSA official materials were added to the comparison. Indiana uses a three-month lookback for applicants and existing HIP members and quarterly compliance checks, extending the evidence-architecture spectrum from Missouri/Nebraska one-month designs and Iowa's two-month design to an Indiana three-month design. Indiana's estimate of more than 58,000 members not currently in compliance is treated only as a preliminary readiness signal, not projected coverage loss or a PERM result. The article's conclusion did not change; the new evidence strengthens the state-variation thesis.

The federal requirement is national.

The evidence architecture is not.

CMS’s 2026 community-engagement rule establishes a common Medicaid framework: certain adults must demonstrate qualifying work, education, training, community service, or sufficient monthly earnings as a condition of eligibility. States must verify compliance at application and renewal, and they may choose more frequent verification between renewals.

But CMS also leaves states meaningful implementation choices.

Those choices are already producing different operating models.

Missouri says an adult subject to the requirement can satisfy it at renewal by meeting the requirement in at least one month since the last renewal. Nebraska’s approved state-plan amendment similarly requires one month during the eligibility period. Iowa, by contrast, says current members must meet the requirement for any two months during the review period since the last eligibility determination or renewal.

Same federal rule.

Different evidence architecture.

That difference is more than a policy detail. It changes what information a state must find, what exceptions it must evaluate, how many months it must reconstruct, how often a case can fail automated verification, how much manual work may follow, and what evidence must still be available if the eligibility decision is later reviewed.

CMS’s interim final rule requires affected applicants and beneficiaries to satisfy community-engagement requirements but gives states choices about the review period.

For applicants, states may require one, two, or three months of qualifying activity before application. For enrolled beneficiaries, states determine how many months must be demonstrated between renewals. States may also elect more frequent checks between renewals.

That flexibility is important.

It also means “community engagement” is not one national transaction.

It is a family of state-specific eligibility processes operating under one federal framework.

For PERM, MEQC, internal quality review, systems testing, and appeals, that distinction matters. An auditor cannot reconstruct a determination simply by asking whether a person worked 80 hours. The state must be able to show which rule applied, which months were in scope, whether an exclusion or exception applied, what data sources were checked, whether the state could verify compliance without contacting the individual, and what happened when automated verification was unsuccessful.

The evidence path is part of the eligibility decision.

CMS’s own beneficiary-facing implementation now reinforces that point. Medicaid.gov has state-specific eligibility-change pages for Delaware Medicaid, MO HealthNet, ARHOME, and other state programs. The pages use common federal language about the new community-engagement requirement, but they route people back to their own state program, tell them to follow up with the state, and advise them to gather documents that may establish an exclusion.

The Spanish-language landing page makes the architecture explicit: the changes vary from state to state, and beneficiaries are asked to select the state where they live before getting the next layer of guidance.

That is more than a communications detail. It reinforces the operating reality that one federal requirement will be implemented through state-specific beneficiary, verification, exclusion, notice, and support pathways. For later PERM, MEQC, quality, or appeal review, the state still must be able to reconstruct which pathway applied and what evidence supported the resulting eligibility action.

Missouri’s current public guidance says Adult Expansion Group members subject to community-engagement requirements will renew every six months beginning in 2027.

For an enrolled member, Missouri says the requirement is met if the person satisfies it in at least one month since the last renewal. The state says it will first use information already available to determine whether the person meets the requirement or an exemption. If the state cannot verify the information, the member may be asked for additional proof through the renewal process.

Operationally, that creates a relatively narrow compliance target inside a six-month period.

But narrow does not mean simple.

The state still must identify the correct population, apply exclusions and exemptions, search available data, identify at least one qualifying month, preserve the basis for the decision, and route unresolved cases into an information-request and notice process.

The central control question is not merely whether one month is easier than two.

It is whether the system can reliably identify and preserve the right month.

Nebraska provides an unusually clear example because its approved state-plan amendment records the choices directly.

At application, Nebraska selected one month immediately before application.

At renewal, it selected one month during the individual’s eligibility period.

Nebraska also selected no additional periodic community-engagement verification between renewals.

The amendment further specifies that the state should use reliable information already available whenever possible before requesting information from the individual. If the state cannot verify compliance at renewal after checking reliable information, the noncompliance-notice process follows.

That produces a defined decision chain:

That sequence is exactly the kind of architecture that must survive both systems automation and later reconstruction.

Iowa’s public guidance takes a different path.

Applicants must meet the requirement for the month immediately preceding application.

For current Iowa Health and Wellness Plan members with renewal dates beginning in February 2027, Iowa says members must meet the requirement for any two months during the review period since the previous eligibility determination or renewal.

That is not simply “twice as strict” as a one-month state, and it should not be described that way.

It is a different evidence design.

Two qualifying months create a larger verification universe. Depending on how the state builds its automation, that may require more data matches, more month-level calculations, more exception logic, more opportunities for an incomplete source to produce a failed match, and potentially more manual follow-up.

It may also provide a state with more information about sustained compliance.

Whether that improves accuracy depends on the controls around the process.

More evidence is not automatically better evidence.

A two-month requirement supported by weak data matching, unclear rule versioning, inconsistent exclusion logic, or poor evidence retention can still produce an indefensible eligibility decision. A one-month requirement supported by reliable data, clear exception handling, and strong audit trails may be easier to reconstruct.

The meaningful question is not which number is better.

It is whether the state’s operating model can execute the number it chose.

Indiana FSSA adds a fourth evidence design. For applications and redeterminations initiated on or after January 1, 2027, the state says a January applicant must meet the requirement for October, November, and December. For existing HIP members, the lookback is the three months before the renewal month or the three months before a quarterly work-requirement review.

That produces a three-month evidence window plus recurring quarterly compliance checks. It is not simply a more or less strict version of the one- and two-month approaches. It requires the state to establish month-level compliance or an exemption across three months, preserve the relevant source evidence, and distinguish an unresolved data match from a final noncompliance determination.

On October 5, Indiana FSSA also estimated that more than 58,000 HIP members were not currently in compliance with the pending requirements. That number is a preliminary implementation/readiness signal—not a projected disenrollment count, not a final eligibility determination, and not a PERM finding. Members may later demonstrate qualifying activity, establish an exemption, or resolve incomplete evidence.

The comparison now spans one, two, and three-month evidence designs under the same federal framework.

The difference between one month and two months reaches several operational layers.

First, it changes the data-search problem.

A state must define which months are eligible for review and which sources can establish compliance in each month. Income data, wage files, education records, SNAP or TANF information, exemption evidence, volunteer documentation, and other sources do not necessarily update on the same schedule.

Second, it changes exception handling.

A person may be excluded from the requirement, deemed compliant for a month, or qualify because of a short-term hardship. The system must know not only that an exception exists, but when it applies.

Third, it changes failed-match volume.

CMS requires states to use reliable information available to them where possible. A failed automated match is not necessarily evidence of noncompliance. It may mean only that the state cannot yet verify the requirement from the available source.

That distinction has to survive into notices, worker instructions, and final determinations.

Fourth, it changes evidence retention.

If an eligibility decision is reviewed later, the state needs to reconstruct the rule and evidence that existed when the determination was made. A current data match cannot automatically substitute for the historical basis of the earlier decision.

And fifth, it changes quality-control design.

MEQC, internal sampling, targeted audits, and pre-PERM review should test the state’s actual configuration—not a generic federal checklist.

A one-month state should test whether one valid month is consistently found and preserved.

A two-month state should test whether both qualifying months are correctly identified, whether they fall within the proper review period, and whether the same exclusions, exceptions, and verification hierarchy are applied consistently.

This comparison reinforces a broader point.

More eligibility transactions do not automatically create more accurate eligibility.

Neither does requiring more months of evidence.

Accuracy comes from the quality of the decision path.

A state can increase renewal frequency, increase verification requirements, and add more data sources while still increasing error risk if the new transactions depend on poor synchronization, unresolved interfaces, manual workarounds, inconsistent rules, or evidence that cannot later be reproduced.

That is why community-engagement implementation should be treated as a control-design exercise, not merely a policy-installation exercise.

The federal government has established the requirement.

The states are building the machinery.

The quality of that machinery will help determine whether more activity produces better decisions or simply more opportunities for defects.

Before community-engagement determinations begin, a state should be able to answer ten questions clearly:

Those questions apply whether a state chooses one month, two months, or a different permitted design.

The answer cannot be “the system does it.”

The system has to do a specific thing, under a specific rule, with evidence that can be explained later.

It is too early to say that one state design will produce a lower PERM eligibility error rate than another.

PERM is payment-weighted. State populations differ. Claims experience differs. Exclusions differ. Systems differ. Data quality differs. Worker processes differ. The same policy choice can perform differently in different operating environments.

But it is not too early to identify the variable.

How many months of community-engagement evidence a state requires—and how it verifies those months—belongs in the national eligibility-control conversation.

It should also belong in future comparative research.

The states are not simply implementing the same rule on different calendars.

They are choosing different evidence architectures.

By 2027, those choices will be running through real eligibility systems, real renewal processes, real notices, real manual exceptions, and real beneficiary records.

By the time those decisions enter a future PERM sample, the important question will not be whether the state had a community-engagement policy.

It will be whether the state can prove it made the right eligibility decision under the version of that policy that applied on that day.

Same federal rule.

Different evidence architecture.

That is where the operational risk begins.

This is independent PERM Insights & Perspectives analysis. It compares publicly available CMS and state implementation materials and does not rank the states or predict their future PERM performance. State requirements may change as implementation proceeds; all state-specific descriptions should be rechecked immediately before publication. Source review through October 8, 2026.

Indiana FSSA — HIP Work Requirements

Indiana FSSA — Information for HIP Members / three-month lookback

Indiana FSSA — HIP Work Requirements Partner Toolkit / quarterly checks

© 2026 PERM Insights & Perspectives LLC. All rights reserved.

Ralph Choate, Founder, Editor & Principal Author | perminsights.org