A simpler application should feel simpler to the applicant

The change behind the paperwork

CMS announced an enrollment and renewal streamlining final rule (opens in a new tab) in March 2024, covering Medicaid, the Children’s Health Insurance Program, and the Basic Health Program. Its stated aim included:

“reduce the administrative burden on states and people”

— Centers for Medicare & Medicaid Services, March 2024

The March 2024 announcement described provisions with different implementation arrangements; it did not mean every application changed immediately. For a service team reviewing its own process, the important test is what becomes easier for the applicant. How much information must someone repeat, and which questions can the team answer more clearly?

Follow one applicant through the whole journey

Imagine a hypothetical older adult applying for support with help from a trusted neighbor. They complete a form online, receive a request for more information by post, and call a number printed on the letter.

Each step may appear reasonable in isolation. Together, the steps can require someone to move between formats, find documents again, and explain what has already happened.

A service review should follow that entire journey. Counting the questions on the first screen will miss the work that arrives later. Ask where the applicant has to wait, repeat information, or make a decision without enough explanation.

Separate necessary information from familiar habit

Some information is required for a decision. Other requests survive because a team has always asked for them. The people responsible for the process need to know the difference.

That review belongs with qualified program and policy staff. It should not become an invitation for a helpful colleague to skip required steps or advise someone that a document is unnecessary.

Ask those staff to explain the purpose of each request in plain language. When the reason is clear, the team can better identify duplication, confusing instructions, and opportunities to use information through permitted processes.

Check the joins between channels

A person might begin online and finish by telephone. They may need an accessible format, an interpreter, or in-person assistance. These should be usable routes through the process rather than entirely separate experiences with conflicting instructions.

In our example, the neighbor should not need to guess whether the paper notice relates to the original application. Clear identifiers and appropriate assistance can help the applicant ask the right question.

Test the wording across letters, websites, and staff guidance. If one channel says to wait while another says to act, the organization has created a problem that the applicant cannot resolve alone.

Measure effort that people can describe

Application completion is useful information, but it does not tell the whole story. Ask participants about repeated requests, time spent seeking clarification, and whether they knew what would happen next.

Keep feedback separate from the eligibility decision. A person should not feel that criticism of a confusing process could affect their application.

Staff can contribute observations too. They may know which instruction generates the same question every week. Bring those patterns to the people who can change the process, with enough detail to investigate and without circulating unnecessary personal information.

Leave room for the person’s preferred help

Some applicants want to handle each step independently. Others want a chosen supporter involved. Ask rather than assume.

Explain the available assistance, any authorization requirements, and how the applicant can keep control of the conversation. A shorter process should not remove the opportunity to ask a question.

For organizations receiving referrals, be clear about what you can help with. Finding official information or arranging a qualified appointment is different from deciding someone’s entitlement. Honest boundaries make the help more dependable.

A current role for genus

Today, genus content and pathways can arrange reviewed explanations and resources into a sequence for a defined audience. An organization might use that approach to help people understand where to begin and which official service handles the next step.

The content needs an owner and a review date. genus is not an enrollment system or an eligibility authority, and a prepared pathway cannot remove requirements imposed by the responsible agency. Its contribution is helping the organization present its part clearly, without pretending to control the whole process.

A small trial with willing participants can reveal those joins before revised instructions reach everyone. Ask what was clear, what was missing, and where they needed another person to translate the process.

A useful test for the next review

After our change, what will an applicant no longer have to repeat, guess, or chase—and how will we know?