Free Network Build Assessment
Score your buildCMS Enforcement · Enrollment Freeze
A suspension of enrollment stops a plan from accepting new Medicare members, and it's one of the intermediate sanctions listed in 42 CFR 422.750. MedPAC's June 2024 report says CMS has never imposed intermediate sanctions for network adequacy noncompliance, but new applications have been denied on this basis. This guide covers what the record shows, where the real risk lands, and how to lower it.
What the Public Record Says
Never
Sanctions for network adequacy
MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance
Denied
New applications
The same report adds: "However, new applications have been denied on this basis"
58%
Exception requests denied
CMS denied 259 of 448 exception requests in 2021, per MedPAC
10 days
To answer a Notice of Intent to Deny
An applicant's final upload opportunity, under 42 CFR 422.502(c)(2)(ii)
Freeze Triggers
On the public record, a network adequacy problem is more likely to cost you a county or bring a compliance action than a freeze. Here's what is documented, by category.
A failed application review
Since contract year 2024, applicants must demonstrate compliance inside the application. The review runs in three HSD upload rounds: the initial submission, the response to CMS's deficiency notice, and the response to the Notice of Intent to Deny. CMS may deny the application based on its network evaluation, and MedPAC says new applications have been denied on this basis.
A failed review on an operating contract
CMS reviews contract networks on a triennial basis. An application, a termination CMS considers significant, a network access complaint, or a gap the plan discloses can pull a review forward. CMS's December 2024 guidance says contracts that fail may face compliance or enforcement actions.
A denied exception request
An exception is no safety net. MedPAC reports CMS denied 259 of 448 exception requests in 2021, or 58%. When a request is denied, the county still fails.
Intermediate sanctions under 42 CFR 422.750
Suspension of enrollment is one of the intermediate sanctions the regulation lists. MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, so treat a network adequacy freeze as a low-probability, high-consequence risk.
Problems outside the network
CMS's sanction authority isn't limited to network adequacy. Which grounds apply to a given situation is a question for your compliance lead and counsel, working from the regulation itself.
Missing a CMS date
CMS sets the dates, and they can change. For contract year 2027, the Notice of Intent to Apply was due January 23, 2026 and completed applications February 11, 2026, and CMS said it "will not accept applications from organizations that fail to submit a timely NOIA."
Provider directory non-compliance
Under 42 CFR 422.111(m), directory information must be updated within 30 days of the plan learning of a change, and attested at least annually. Persistent inaccuracy is a compliance risk in its own right.
HSD tables that don't match reality
CMS's guidance says plans list providers with a fully executed contract. Letters of intent work only for applicants during the application, and they end when the contract year starts. CMS's check reads addresses exactly as typed, so each one has to be the office where the provider sees patients.
Prevention
Nobody can promise a clean review. What you can do is see your gaps before CMS does, and treat network adequacy as year-round work. This order of work is our advice, not a CMS process.
Score every county and specialty against the current HSD Reference File
Finding a gap early leaves time to recruit, contract, and credential before CMS's date
Work your outreach and record every contact and outcome as it happens
A log won't excuse a gap, because inability to contract is not a valid exception reason. 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
Make a deliberate decision on each county that is falling short
Your options are to keep recruiting, change the offer, use telehealth for the credit where it applies, drop the county, or, where supply really isn't there, build the case for an exception
Check each provider against NPPES, then test in the Network Management Module if you hold a contract ID
Any organization with a contract ID can upload at any time to test, and CMS offers an informal Consultation upload before the formal triennial review. Treat every internal pass as unconfirmed until CMS's check agrees
Upload your HSD tables on CMS's date, with any exceptions on CMS's current template
Plans must resubmit all previously approved exceptions whenever CMS requests an HSD upload, so re-verify each one first
Send any CMS notice to your network director, compliance lead, and legal counsel on day one
The response date is set by CMS. Set an internal date well ahead of it, with room for review and for problems with the upload
Update the provider directory within 30 days of learning of a change, and track terminations
Tell your CMS Account Manager about terminations you consider significant, since one can trigger a network review outside the triennial cycle
Recovery
We don't publish a recovery timeline or a step-by-step CMS process, because we know of no network adequacy precedent to point to. These are general steps, and they aren't legal advice. CMS's notice and your counsel govern.
Start with the notice itself: what CMS cited, what it suspended, and every date in it. Get it to your network director, compliance lead, and legal counsel on day one.
Raise questions, and any problem you see coming, before a deadline rather than after.
Separate what CMS cited from what caused it. If network data is part of the problem, re-score every county and specialty against the current HSD Reference File, not only the ones named.
Give each cited item a fix, an owner, a due date, and a visible status, and track it like any other operational commitment.
Keep proof of each fix as it's finished, such as executed contracts and corrected HSD tables. Reconstructing work that really happened is legitimate. Invented records are not.
Don't assume what will lift a sanction, or how long it will take. Ask CMS, and let counsel advise you on any appeal rights.
Blueprint Platform
Blueprint doesn't file with CMS, track CMS notices, or promise an outcome. It gives your team one place to see where the network falls short and to work the providers who could close the gap.
Score your network against CMS's 2026 Medicare Advantage standards for every county, including minimum counts and CMS credits. Distance is straight-line: a straight-line pass shows as unconfirmed, and drive time isn't measured.
Outreach sequences send automatic emails and put calls and tasks on your team's lists. Decline reasons are recorded, and each provider's history shows who did what and when.
See which providers a county depends on, and a ranked list of who to recruit next to close a gap.
Produce HSD-format provider tables, and print a draft exception request listing available providers with CMS-accepted reasons and your pattern of care. Your team reviews and files both.
FAQ