Free Network Build Assessment
Score your buildThe MA bid and the network test run on separate CMS dates, and they share one list of counties. Here's what network teams need to understand about how those dates affect contracting strategy.
The Medicare Advantage bid and the network adequacy review are separate processes with separate uploads, but they depend on each other in ways network operations teams often underestimate. The bid encodes assumptions about the plan's service area, benefit structure, and cost base that directly constrain the network build. The network adequacy filing must demonstrate that the plan has contracted the providers necessary to deliver those benefits in that service area. When bid assumptions and network reality diverge, the consequences can range from inadequate adequacy filings to contract actions that affect the plan's ability to operate.
Understanding the MA bid submission process from the network operations perspective is not optional for plans that want to pass adequacy review on first submission. The bid encodes the geographic footprint of the network (which counties), the benefit categories that must be covered (which specialties and provider types), and the cost assumptions that shape contracting strategy (provider payment rates, hospital relationships, pharmacy access). Each of these elements has direct implications for what the network adequacy filing must demonstrate, and plans that leave network operations out of bid development can find that their network commitments don't match their adequacy obligations.
This article covers the key dates, how bid assumptions translate into network build scope, and the coordination that keeps network development aligned with what the plan has committed to.
CMS publishes its application and bid dates each year, and they are subject to change. For contract year 2027, the Notice of Intent to Apply was due January 23, 2026, completed applications were due February 11, 2026, bids were due June 1, 2026, and CMS executed contracts in September 2026.
For network teams, the most important date for a new or expanding service area is the application, not the bid. Under 42 CFR 422.116(a)(2)(ii), beginning with contract year 2024, applicants must demonstrate compliance with the network adequacy standards as part of the application, and CMS may deny an application based on its network evaluation. So the HSD tables for the requested counties go in months before the bid is due. By the bid date, the county list is being priced, and late county changes ripple into the bid.
That makes early county scoring a critical planning step. Plans that settle on counties before scoring each one may commit to places where they cannot demonstrate adequacy, and that problem has no good late solution. Score all candidate counties early enough to decide whether to include them, drop them, or step up recruitment before the application goes in.
The bid submission encodes a set of assumptions about the plan's service area and benefit design that collectively define the scope of the network that must be built. Each major bid assumption has a corresponding network implication, and the translation between bid assumptions and network requirements is where many plans encounter unexpected surprises.
The county selection assumption defines the geographic footprint of the network. Each county selected in the bid must be adequately served by contracted providers within the applicable time-distance thresholds for every required specialty category. Counties that are added to a plan's service area for the first time, expansion counties, require a complete provider recruitment effort across all required specialties, typically in a compressed timeline relative to the bid submission date. Expansion county decisions made late leave too little time for the network build, and plans that expand without accounting for recruitment lead times are likely to face gaps in those counties when they upload.
The benefit design assumption defines which provider types and specialties must be in the network. Plans offering supplemental benefits, vision, dental, hearing, fitness, need a network that can actually deliver those benefits, in addition to meeting the medical network adequacy requirements. Plans offering Special Needs Plan (SNP) benefits have additional network requirements tied to the conditions or populations served by the SNP. The benefit design decisions made during bid development must be informed by a clear understanding of the network's current and projected capacity to deliver those benefits across the service area. Benefit additions that look attractive from a competitive positioning standpoint can become adequacy liabilities if the provider infrastructure to support them doesn't exist or can't be built in the available time.
Network data goes to CMS as HSD tables, uploaded in the Network Management Module in HPMS. For an applicant, that upload is part of the application, followed if needed by a response to a deficiency notice and a response to a Notice of Intent to Deny. Under 42 CFR 422.502(c)(2)(ii), the applicant has 10 days to respond to that notice. Existing contracts are reviewed on a triennial basis and are prompted to upload in mid-June, for the current contract year.
The timing matters. Under 42 CFR 422.116(d)(7), letters of intent signed by both parties can stand in for contracts during the application and its review, along with a 10-percentage-point credit toward the share of beneficiaries. Both end at the start of the contract year, when the plan must have signed contracts. So a plan can bid on a network that is still partly promises. Treat conversion of those letters as its own workstream, and build county decisions around realistic recruitment lead times.
The stakes are highest for applicants. MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, then adds that new applications have been denied on this basis. An applicant with a gap can lose the county.
The Plan Benefit Package (PBP) is the detailed benefit specification document that accompanies each MA bid. The PBP defines the specific services covered under the plan, the cost-sharing structure for each service category, and the provider access rules that govern how members use their benefits. PBP design decisions that seem primarily financial or actuarial in nature often have significant network implications that are not always fully considered during the benefit design process.
Cost-sharing differentials between in-network and out-of-network care are a common example. PBPs that establish aggressive out-of-network cost-sharing differentials, designed to incentivize in-network utilization and support actuarial assumptions about in-network care rates, require a network robust enough to give members genuine access to the services they need within the network. Plans that design aggressive in-network incentives while operating with thin networks create a member access problem: members who cannot access in-network care are effectively penalized by the cost-sharing design for a network failure they did not cause.
Prior authorization requirements encoded in the PBP have similar network implications. PBPs that require prior authorization for specialist visits, diagnostic imaging, or surgical procedures require a network of contracting specialists, imaging facilities, and surgical facilities dense enough to accommodate the utilization patterns that the prior authorization process is designed to manage. Restrictive prior authorization in counties with thin specialist networks invites member access complaints, and a network access complaint can pull a CMS review forward.
The MA bid development process involves three functional disciplines, actuarial, product/benefit design, and network operations, that must work from a shared set of assumptions about provider availability, contracting costs, and network capacity. In many plans, these three disciplines operate in silos, with actuarial developing cost assumptions based on historical utilization and trend data, product developing benefit designs based on competitive analysis and member preference data, and network operations building the provider network based on adequacy requirements. The result is often a bid that contains internally inconsistent assumptions, with actuarial costs that don't reflect the network's actual provider mix and benefit designs that presume network capacity that doesn't yet exist.
Ways to prevent this problem include a shared adequacy model that is visible to all three functions throughout the bid development process, formal alignment checkpoints at key bid calendar milestones where actuarial, product, and network teams review and reconcile their assumptions, and a single source of truth for county selection and provider availability data that all functions reference rather than maintaining separate spreadsheets or tracking systems.
Network operations should have a seat at the bid strategy table from the earliest stages of county selection and benefit design, with the authority to flag network feasibility concerns that should influence bid decisions. In plans where network operations is brought in after bid strategy decisions are made and asked to build the network that the bid requires, the work is reactive from the start, and gaps are harder to avoid.
When the network that a plan actually builds differs materially from the network that the bid assumed, whether because of provider recruitment shortfalls, contracting failures, or mid-year panel closures, the consequences depend on the size of the gap and where the plan is in the cycle.
For an applicant, the path runs through CMS's review rounds: the initial upload, the response to the deficiency notice, and the response to the Notice of Intent to Deny. Those rounds are for cleanup. Ten days is enough to fix a mistyped address or add a provider whose contract was already signed. It is not enough to recruit a scarce specialist.
For an operating contract, a gap can bring compliance or enforcement action. CMS has authority to impose intermediate sanctions on plans that fail network adequacy requirements, though MedPAC reported in June 2024 that it has never done so for network adequacy; new applications, however, have been denied on that basis. An exception request is not a safe fallback either: MedPAC also reported that CMS denied 259 of 448 exception requests in 2021, about 58%.
Blueprint scores candidate counties by specialty against CMS's 2026 HSD standards on straight-line distance, showing a straight-line pass as unconfirmed, and its build plan tracks milestones while the contracting pipeline tracks each provider. The bid itself stays with your bid team.
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.