The Assumption That Gets Plans in Trouble
Ask the CEO or CFO of a Medicare Advantage plan whether they could face an enrollment freeze, and you'll likely hear: not us. We have a compliance team. We would know if something was that wrong.
On the public record, they're mostly right about the freeze and wrong about the risk. Suspension of enrollment is one of the intermediate sanctions listed in 42 CFR 422.750. But MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, then adds: "However, new applications have been denied on this basis." For an operating contract, CMS's guidance says a failed review may bring compliance or enforcement actions. For an expansion, a gap can cost you the county.
The six questions below are not designed to be reassuring. They are designed to surface real risk. Answer them honestly.
Question 1: Do We Have a Documented Outreach Log for Every Provider We Contacted?
Not a spreadsheet with a "Notes" column. A structured log that captures: who was contacted, the date, the method (phone, fax, portal, in-person), and the outcome. It won't excuse a gap, because CMS's guidance says inability to contract is not a valid exception reason. But it tells you who is still worth calling, and it gives you dated dispositions if a gap turns out to be a real supply problem. If your answer to this question is "sort of" or "our team keeps track of it," your answer is no.
Question 2: Do We Have Coverage in Every Required Specialty in Every County in Our Service Area?
Not most counties. Every county. Plans with 20- or 30-county service areas often have clean data on their core markets and thin, manually-compiled records on the edge counties. If someone on your team would need more than 10 minutes to pull a specialty-by-county adequacy scorecard, you do not have a real answer to this question. Uncertainty here is itself a risk indicator.
Question 3: Do We Have a Process for Monitoring Provider Changes Between Submission Windows?
Providers retire, relocate, close panels, and terminate mid-year. A network that was adequate in October may have a gap by February. A significant termination, a network access complaint, or a gap you disclose can each trigger a CMS review outside the triennial cycle. If your process for catching mid-year provider changes is "we find out when members call," you have a live exposure.
Question 4: Have We Responded to Every CMS Inquiry on Time and with Complete Documentation?
CMS correspondence comes with hard dates, and an applicant's response to a Notice of Intent to Deny is due within 10 days. Teams tracking due dates in someone's inbox or on a shared calendar are one distraction away from a missed deadline. If your compliance team cannot immediately confirm the status of every open CMS inquiry, that is an answer.
Question 5: Is Our Provider Directory Updated Within the 30-Day CMS Standard?
Under 42 CFR 422.111(m) and 422.120, directory information has to be updated within 30 days, and plans attest at least annually that what they submit is accurate. An attestation is easier to sign than a workflow is to run. If your directory update process depends on providers self-reporting changes, and you have no independent verification step, your 30-day compliance is largely theoretical.
Question 6: Do We Know What a Network Adequacy Failure Would Cost Us in Lost Enrollment Revenue?
This is a CFO question, not a compliance question, and it often goes unanswered until something goes wrong. Model the county you couldn't enter: projected members, revenue per member, months lost. If your compliance team has never presented this number to the CFO or CEO, that conversation is overdue.
What Your Answers Tell You
If you answered "yes" confidently to all six questions, your plan is in a defensible position. If you hedged on two or more, or if you realized while reading that you do not actually know the answer, you have real exposure that your current systems are not covering.
A failed review doesn't announce itself in advance. It starts with a gap nobody noticed until CMS did.
You don't need a perfect network to be in a good position. You need complete records, a fast response process, and a compliance function that treats network adequacy as ongoing work, not an annual paperwork exercise.
The Blueprint team
Provider network build practice
Written by the people behind Blueprint, who between them have spent 30 years building provider networks for health plans: recruiting and contracting providers, chasing credentialing, and filing adequacy. Blueprint is new. The experience behind it isn't.
