Free Network Build Assessment
Score your buildA network adequacy filing captures one point in time, but networks change throughout the year. Provider terminations, credentialing lapses, and practice relocations can erode adequacy between filings. Here's how to monitor continuously and respond before you have a material gap.
When a plan files its network adequacy submission with CMS, it is documenting the state of its network at a specific point in time. But the filing date and the contract year are not the same thing, and the network that passed at filing may not stay adequate.
The gap between filing adequacy and current network adequacy is a real compliance exposure. CMS's application asks for a network meeting 42 CFR 422.116 "for each county in the requested service area during the entire contract year." Plans that fall short during the year, even if they passed at filing, still have a problem to deal with.
The practical consequence is that a plan whose network erodes during the year, due to provider terminations, credentialing lapses, or practice closures, may be out of compliance for weeks or months before anyone in the organization identifies the gap. By the time the gap surfaces through a member complaint, a CMS data request, or the next annual adequacy model run, the plan may have significant exposure.
Understanding the specific mechanisms by which networks erode during the year is the foundation for designing an effective monitoring program. Networks don't fail randomly: they fail through predictable, often foreseeable events that can be monitored and responded to if the right systems are in place.
Provider terminations are the most common source of mid-year adequacy erosion. A provider who terminates their participation agreement during the year reduces the provider count in every county where they were counted. In counties where the provider was the sole or near-sole provider in a specialty category, a single termination can immediately erode adequacy below threshold.
Credentialing lapses are a less visible source of erosion. A provider whose recredentialing didn't happen on time may not be able to keep seeing members. NCQA requires recredentialing at least every 36 months, so track those dates next to your adequacy work.
Practice closures and relocations affect adequacy at the county level even when the provider remains contracted. A provider who closes their county practice and opens a new practice in a different county may still be contracted with the plan but no longer counts toward adequacy in the county where the member population is concentrated. Provider directory updates often lag these geographic changes by weeks or months.
Under CMS's December 2024 network adequacy guidance, contract networks are reviewed on a triennial basis, and a termination CMS considers significant, a network access complaint, or a gap the plan discloses can bring a full review forward. Plans must report gaps they find to their CMS Account Manager.
The practical point: don't assume you are safe until the next scheduled review. Watch your network yourself, respond when gaps arise, and keep a dated record of what you did.
An effective continuous monitoring program is built around triggering events: specific occurrences that automatically prompt an adequacy review for the affected county and specialty. Defining these triggers clearly, and building workflow automation to respond to them, is the operational core of a continuous monitoring capability.
The most important triggering events include: receipt of a provider termination notice (which should prompt an adequacy review for every county and specialty where the terminating provider was counted); an upcoming recredentialing date (which should prompt a check on the provider's status); a member complaint citing access-to-care in a specific specialty in a specific area; a member grievance related to inability to find an in-network provider; and a provider directory complaint that suggests a provider listed as in-network is not actually seeing members.
Each trigger should be linked to a specific response workflow: who reviews the adequacy impact, what the timeline is for completing the review, what threshold of impact triggers escalation, and what the response options are (replacement recruitment, exception filing preparation, member notification if required).
A continuous monitoring process that actually functions at scale has four operational components: a monthly adequacy check routine, a termination notice response workflow, a credentialing expiration tracking workflow, and a replacement recruitment trigger protocol.
The monthly adequacy check involves running the adequacy model against the current active provider roster, not the roster as of the annual filing date, but the current contracted and credentialed provider population, and comparing the output against the filed thresholds. Any county-specialty combination that has dropped below threshold since the last check triggers an immediate review and a recruitment response.
The termination notice response workflow begins the moment a provider termination notice arrives. The network operations team should run an adequacy analysis promptly, identifying every county and specialty where the terminating provider is counted, and assessing the adequacy impact of the termination. If the termination creates or threatens to create a gap below threshold, replacement recruitment should begin before the termination effective date if the notice period allows. For terminations a plan considers significant, Chapter 4 of the Medicare Managed Care Manual asks for notice to the CMS Account Manager at least 90 days before the effective date, and 42 CFR 422.111(e) requires enrollee notice 45 calendar days ahead for primary care and behavioral health providers, and 30 for other specialties.
Credentialing date tracking needs a current view of file status for the providers you depend on. A credentialing report only helps if someone connects an upcoming date to the county and specialty it affects.
Provider directory accuracy is both a compliance obligation in its own right and a useful proxy for the health of the underlying network. A plan with a highly accurate provider directory, where listed providers are actually contracted, actually credentialed, and actually seeing members, is likely maintaining the underlying network with similar rigor. A plan with widespread directory inaccuracies is likely also experiencing underlying network management problems.
Under 42 CFR 422.111(m), for plan years beginning on or after January 1, 2026, MA plans submit directory data to CMS for Medicare Plan Finder, with 30-day updates and an annual attestation. A 2026 law adds 90-day verification and 5-business-day removals starting in plan year 2028.
For continuous monitoring purposes, treat provider directory updates as a leading indicator of network changes. A provider who requests removal from the directory has, in effect, given the plan an early warning of a potential adequacy impact. Building a directory update workflow that triggers an adequacy review for any provider removal from the directory gives the network operations team a timely alert before the termination formally processes.
CMS's December 2024 guidance says plans must report a gap they find to their CMS Account Manager, and that a disclosed gap can trigger a full network review. Talk to your Account Manager about what to report and when, and be ready to show your plan to close the gap.
Manual processes struggle with continuous monitoring at scale. A plan serving a 10-county service area graded on CMS's 43 provider and facility types has 430 county and type combinations to watch, plus the provider changes driven by credentialing, terminations, and contract amendments.
Look for: a provider database with current contracting and credentialing status; an adequacy calculation you can run on demand against current providers; and a way to track each event through to resolution. In Blueprint, a team can score adequacy by county and specialty against CMS's standards, see which providers a county depends on, and receive scheduled digests. A straight-line pass shows as unconfirmed, because Blueprint doesn't measure drive time.
The annual adequacy filing is both a compliance deliverable and a forcing function for an annual snapshot of network health. But teams that treat the annual filing as the primary adequacy event, rather than a scheduled reporting output from an ongoing monitoring process, face a characteristic problem: they discover gaps at filing time that have been developing for months, and they have insufficient time to close them before the submission deadline.
Teams that monitor continuously invert this relationship. Their annual filing is largely a documentation and formatting exercise on top of data that they have been actively managing throughout the year. Their adequacy model is current because they run it monthly. Their provider roster is accurate because they update it with each triggering event. Their exception files are complete because they build them as they go, not at the last minute.
The goal is fewer surprises and a network that is actually adequate throughout the year, not just on the filing date, which is what CMS's application asks for and what members deserve.
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.