Free Network Build Assessment
Score your buildCMS reviews Medicare Advantage contract networks on a triennial basis, and certain events can trigger a review sooner. Here's what triggers one, what gets checked, and how network ops teams can prepare before the call comes.
Under CMS's December 2024 network adequacy guidance, contract networks are reviewed on a triennial basis. Contracts due for review are prompted to upload their full HSD tables into the Network Management Module in mid-June, for the current contract year. Applicants upload as part of the application, for the upcoming year.
Certain events can bring a full review forward: an application (initial or service area expansion), a termination CMS considers significant, a network access complaint, and a gap the plan discloses itself, which plans must report to their CMS Account Manager. A triggered full review may reset the triennial clock. Applicants that used letters of intent go through the triennial review in their first operational year.
CMS gives you two ways to see its answer early. Before the formal triennial review, it offers an informal Consultation upload with technical assistance. And any organization with a contract ID can upload HSD tables to the Network Management Module at any time and get an Automated Criteria Check, which scores every provider and facility type in every county.
Take the exact request and deadline from CMS's communication to you. Whatever it asks for, these records are worth keeping ready.
First, provider roster accuracy. Confirm that the providers on your HSD tables are actually contracted, active, and available to serve members. Compare the tables against your executed contract records. Operating contracts need fully executed agreements, and any LOI flag left over from an application should be gone.
Second, credentialing records. Keep files complete and current, and know where each provider stands. NCQA requires recredentialing at least every 36 months, and its verification time limits apply to each file.
Third, your adequacy method. Be able to explain which providers you included, how you placed members, and how you applied the time and distance limits. CMS places members using a sample only it can see, so where your internal results differ from the Automated Criteria Check, CMS's result is the one that counts.
Fourth, exception requests. Plans must resubmit all previously approved exceptions whenever CMS requests an HSD upload, so re-verify each one. Keep the provider census, the checkable reason for each provider not in network, and your pattern-of-care evidence together.
Fifth, prior correspondence. If CMS raised a deficiency before, keep what you told CMS you would do, and the proof that you did it.
Treat preparation as a year-round discipline rather than a response to an incoming request.
Provider roster accuracy: Regularly reconcile your provider roster against executed contract records. Flag contracts approaching expiration and start renewal before they lapse.
Credentialing currency: Track recredentialing dates next to your adequacy work, so an upcoming expiration shows up before it becomes a problem.
Exception file completeness: For every county-specialty exception in your current or prior submissions, keep the full package in one place, along with a current note on whether the gap is resolved or ongoing.
CMS correspondence: Keep an indexed archive of every CMS notice and every response submitted, including what was done and whether the gap closed.
The deadline depends on what CMS is asking for, so read it the day the request arrives. For an applicant's final upload, the response to a Notice of Intent to Deny, the regulation allows 10 days.
It helps to name a response coordinator and know ahead of time where each record lives, so you aren't searching for documents against a deadline.
CMS may deny an application based on its network evaluation, and operating contracts that fail may face compliance or enforcement action. MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, though new applications have been denied on that basis.
If CMS asks for corrective action, be specific about what you will do, by when, and how you will monitor the network afterward.
Keep your documentation in one searchable place, where provider contracts, credentialing status, exception files, and CMS correspondence are linked to specific providers and counties. Blueprint keeps a history of work on each provider, including who did it and when, along with contracting stage, credentialing status, outreach and decline reasons.
Blueprint automates the network build workflows described in this article: from adequacy modeling to provider outreach tracking. See it with your state and line of business.