Medicaid Renewals Playbook

Plays and Resources

On this page:

  1. Establish Trust and Urgency
  2. Identify Problems
  3. Generate Solutions
  4. Prioritize and Implement

1. Establish Trust and Urgency

Three people sitting at a table with laptops, having a discussion

It’s crucial to establish a relationship of trust and clear expectations with state partners at the beginning of the project. Every stage of the process is predicated on an open exchange of details and data about how systems are performing.

In addition, all members of the team – including vendors – must understand the urgency and criticality of the project. Leadership should be engaged regularly from the beginning, and the work should be made a top priority. Common goals should be established at the beginning of the project so that everyone understands what success looks like.

Resources

Guides

Templates

Workshops


2. Identify Problems

A person standing in front of a large preresntation of file, doing analysis

Working with the state and external partners, determine the largest sources of administrative burden and churn during renewal. Where are people being moved from automatic renewal to manual renewal? Where are people struggling or falling off when completing a renewal? What methods are most commonly utilized, and what are the biggest problems with those methods?

When determining the problems, it’s important to keep the focus on the “end-to-end” renewal process. An ex parte attempt is only the first step in a person’s renewal. For the millions of people manually renewing, there are vast opportunities to improve the experience and increase renewal rates.

A Sankey diagram showing the flow of Medicaid renewals. The first benchmark is labeled 'Medicaid population: 100,000. This splits into two benchmarks: 'Manual renewal: 60,000' and 'Ex-parte: 40,000'. Manual renewal splits into two benchmarks: 'Renewal NOT submitted on time: 20,000' and 'Renewal submitted on time: 40,000'. 'Renewal NOT submitted on time' flows entirely into 'Terminated: 37,000'. 'Renewal submitted on time' splits into three paths: one that leads to 'Terminated', one that leads to 'Receive request for info: 10,000', and one that leads to 'Renewed: 73,000'. 'Receive request for info' splits into two paths: 'NOT submitted on time: 5,000' and 'Submitted on time: 5,000'. 'NOT submitted on time' leads entirely to 'Terminated'. 'Submitted on time' splits to 'Terminated' and 'Renewed'. 'Ex-Parte' leads entirely to 'Renewed'.

This example funnel depicts the a population of Medicaid renewals and their various states. Full-size image here.

Resources

Guides

Templates

Workshops


3. Generate Solutions

Two people looking at a diagram. The diagram shows two blocks of text, and a circle with arrows pointing towards each block.

Once problems have been identified, work with the broader cross-functional team to start generating solutions. Often times there will be more problems available to solve than possible to talk through in the given time. Start with high-impact and/or low-effort problems, and present them in turn for consideration. Solutions should be high-level, but estimable. Whenever possible, rely on data or similar solutions in other states as evidence that the solution will, in fact, solve the problem.

Whenever possible, scope should be reduced towards the minimum viable solution. When implementation timelines are given, look for reasonable opportunities to reduce estimates and remove unnecessary requirements. Ask for clarity on the stages of implementation, and which are projected to take the most amount of time. Can they be reduced? For example, if a change is completely back-end, eliminate any front-end testing. If a change will only affect mobile users, eliminate desktop testing. If a website is not functional on mobile, change only the pieces to make it functional (as opposed to friendly). Keep asking “why” until the timeline is definitively as small as possible.

Resources

Workshops


4. Prioritize and Implement

Three people surround a browser window, making manual edits to it by placing components on the window itself

There will always be more problems to solve than there are resources available to solve them. State Medicaid teams are overwhelmed with priorities and ongoing work, and providing clarity through data-driven prioritization is critical. Driving clear prioritization with stakeholders allows the implementation teams to focus correctly on areas with the highest impact and quickest timelines.

The two most important metrics to consider when prioritizing are impact and speed. Impact is typically measured in number of successful renewals per month, while speed is measured in time to implementation. Importantly, these numbers are almost always estimates, and can be very rough; for example, improving the design of a renewal notice may increase the number of successful renewals based on the number of people receiving the notice, but it is difficult to estimate.

Once a set of solutions is prioritized, the state and vendor work together to schedule implementation and begin work. If helpful, play a part in that process as well, taking on roles ranging from advisor to individual contributor.

Resources

Templates

Guides

Workshops