Free Network Build Assessment
Score your buildYour PBP and your network adequacy filing must tell a consistent story to CMS. Service area elections, county-level coverage decisions, and bid timing all create interdependencies that network teams and bid teams must coordinate carefully to avoid compliance exposure.
The Plan Benefit Package (PBP) and the network behind it are separate pieces of work that have to tell the same story. A Medicare Advantage plan's PBP defines the benefits it will offer, the service area in which it will offer them, and the cost-sharing structure members will face. The HSD tables show whether the plan has a contracted network that meets 42 CFR 422.116 across that service area. If the two disagree, for example, if the bid includes a county the network can't support, the plan has a problem no matter how good the rest of the bid is.
Under 422.116, a plan must have a contracted network that meets CMS's minimum provider counts and time and distance standards, or an approved exception, in every county in its service area. So the service area is effectively setting the adequacy requirement: put a county in your bid, and you are committing to a network for it.
The practical consequence is that bid strategy and network strategy must be developed in coordination, not in sequence. A plan that adds counties without checking that its network team can build an adequate network in them is creating a risk that may not surface until a deficiency notice arrives, when the options are few.
Plans define the counties in each plan benefit package's service area as part of the bid, which is due the first Monday in June for the following benefit year. The network clock runs differently. Applicants for a new or expanded service area have to demonstrate network compliance inside the application, which comes months before the bid: for contract year 2027, applications were due February 11, 2026.
Each county in the service area creates a distinct adequacy obligation. CMS applies its standards to every county independently, and a plan must meet them in each county for each required provider and facility type. A plan adding five new counties is not adding five uniform challenges: it is adding five potentially different landscapes, each with its own specialty mix, provider supply, and geographic characteristics. A Large Metro county in a new market may have abundant provider supply but a complex contracting environment; a Rural or CEAC county may have supply so thin that meeting the standards without an exception is structurally difficult.
Network development teams should receive the preliminary PBP service area election list as early as possible in the bid development cycle: ideally at the point when the plan is evaluating potential county expansions, not after the election has been finalized. This allows the network team to conduct a provider supply assessment for candidate counties before the election is made, giving leadership an adequacy feasibility input to weigh alongside the actuarial and market opportunity inputs that typically drive service area decisions.
The bid and the network review do not run on one schedule, and the gap between them creates a coordination challenge. Bids are due the first Monday in June. For a new or expanded service area, the network has to pass in the application, months earlier, through three HSD upload rounds: the initial submission, the deficiency response, and the Notice of Intent to Deny response. Existing contracts are on a different clock: CMS reviews networks on a triennial basis, prompting contracts due for review to upload full HSD tables in mid-June.
For plans with stable networks in existing service areas, the job is to keep data current and fix gaps as they appear, and to test tables in the Network Management Module, which any organization with a contract ID can do at any time. For plans expanding into new counties, the job is much bigger: provider identification, outreach, contract negotiation, and credentialing all have to be far enough along that every provider on the tables is under a signed contract or a mutually signed letter of intent by the time the application is due.
The timing implication is clear: expansion network builds start long before the bid, not after it. A plan considering new counties should begin provider outreach and contracting conversations the year before, treating the network build as a precondition for adding the county, not a consequence of it. See the service area expansion timeline for the dates.
Plans that discover a network gap in a county after the bid face a limited set of options: close the gap through additional contracting, request an exception if the supply really isn't there, or ask to remove the county from the service area.
We won't restate CMS's procedures for service area changes from memory. Confirm the process, the window, and what happens to current enrollees with your CMS Account Manager and the current instructions before you count on this option. If the county has current enrollees, plan for how they will be told and how their care will transition.
The practical lesson is that removing a county is a contingency, not a routine tool. Adding counties speculatively and dropping those that turn out to be hard costs real operational effort and can leave members in the middle.
The clearest consequence is on applications. Under 42 CFR 422.116(a)(2)(ii), applicants must demonstrate compliance as part of the application, and CMS "may deny an application" based on its network evaluation. MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, and then adds: "However, new applications have been denied on this basis."
That makes adequacy a real gate for growth rather than a filing exercise. Operating contracts with gaps also face possible compliance or enforcement action, and applicants that used letters of intent go through the triennial review in their first operational year.
The more durable strategy is to match service area decisions to the plan's actual network development capacity: add counties where the plan has or can confidently build an adequate network, and be disciplined in markets where provider supply is thin or contracting timelines are uncertain. This requires that network development leadership have a substantive role in evaluating the feasibility of each candidate county before the bid is finalized, not just a seat at the table afterward.
The PBP defines not only the service area but also the benefit design: what services are covered, what cost-sharing members face, and how services are accessed. Certain benefit design decisions have direct implications for the network adequacy filing and for the plan's practical ability to deliver on its PBP commitments. Plans designing their PBP should evaluate these implications before finalizing benefit elections.
Plans offering a restricted network design, such as an HMO where members are required to use contracted providers for covered services, have a higher practical bar than plans offering a PPO design where members may access out-of-network providers with different cost-sharing. An HMO plan where members cannot access out-of-network providers must have a network that can genuinely meet all of the member's covered care needs within the contracted panel. An adequacy gap in an HMO network is a direct access failure for enrolled members; in a PPO network, the gap is mitigated by out-of-network access, though still a compliance issue under 42 CFR 422.116.
Similarly, plans that include supplemental benefits, transportation, expanded dental, behavioral health, that require specific provider types must ensure those provider types are adequately represented in the network. Adding a supplemental benefit that members cannot access because the required providers are not in the network undermines the benefit's value and can create member grievances. Network teams should see supplemental benefit decisions before they are finalized so they can assess whether the contracted providers support those benefits across the service area.
Blueprint has the CMS 2026 HSD standards for every county and scores a county and specialty against them on straight-line distance, so a bid team and a network team can look at a candidate county together; a straight-line pass shows as unconfirmed because drive time is not measured. A build plan with milestones and a contracting pipeline then track the work on each provider. Blueprint doesn't touch the bid or file anything with CMS.
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.