Free Network Build Assessment
Score your buildA network that isn't ready on CMS's calendar can cost you the county. Here's how to map CMS's dates to concrete internal milestones so your build and your bid land together.
Most health plan teams understand the technical requirements of CMS network adequacy: the 29 provider and 14 facility types, the time-and-distance thresholds, the exception filing process. What is harder to internalize is that none of those requirements exist in isolation. They sit inside a fixed calendar that CMS controls, and the bid cycle sets the clock for everything else. A plan that builds a compliant network but misses the filing window is in the same position as a plan that never built one: it cannot enter the market.
This article maps the Medicare Advantage bid calendar from start to finish, identifies every network adequacy touchpoint within it, and lays out a backward-planning framework that network operations teams can use to set internal recruitment milestones. The goal is a single integrated timeline that eliminates the disconnect that so often exists between the network build function and the actuarial-regulatory team managing the bid itself.
The MA bid cycle is anchored by a statutory date: plans must submit their bids to CMS no later than the first Monday in June. For the 2026 benefit year, that fell on June 2, 2025. CMS then reviews and negotiates bids over the summer.
Around that date sit several CMS-controlled events that are less well-publicized but equally binding for network operations purposes:
Understanding these dates as a system, not a list, is the starting point for an integrated timeline.
Network adequacy is not a technicality: it is a gate. Under 42 CFR 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. CMS has never sanctioned a plan for network adequacy, according to MedPAC's June 2024 report, but new applications have been denied on that basis.
In practice, this means the network adequacy review is a prerequisite for entering a new market, not a parallel track. If a plan's network shows unresolved deficiencies, counties below threshold with no approved exception, it risks losing those counties, or the application, for the year.
For plans with multi-state or multi-county service areas, this creates a portfolio management problem: every county in the service area must meet the standards independently. A county with a very small Medicare-eligible population faces the same review as a large one, so each county on the list has to be worth the work.
Plans entering a new service area for the first time must file an application with CMS demonstrating that the plan has the administrative and network infrastructure to serve the proposed area, and CMS reviews network adequacy as part of that application.
Applications are due early in the calendar year, months before the bid deadline; confirm the exact date in CMS's application materials each cycle. This means that plans expanding their service areas must have credible network build progress, signed LOIs, executed contracts, and documented recruitment pipelines with identified targets, before the application is due. An application submitted with no evidence of network progress is effectively a non-submission.
CMS reviews applications over the following months, and network deficiencies identified in that review must be cured within the windows CMS sets, compressing the timeline further. CMS can deny an application for failure to demonstrate an adequate network.
The most effective approach to MA bid cycle planning is strict backward planning from CMS's dates. Here is a representative framework. The dates in parentheses are CMS's contract year 2027 dates, shown as examples; the rest are planning suggestions, so confirm everything at the start of each cycle:
Each milestone should have a named accountable owner and a written sign-off requirement. Milestones that exist only in a project plan without accountability tend to slip.
The most common failure mode is a bid and network build that proceed as parallel tracks rather than integrated ones. The actuarial team prices the bid assuming a certain network; the network operations team builds the network against different assumptions; neither team reconciles until shortly before the deadline. The result is either a bid that prices incorrectly (because the network is narrower than assumed) or a network adequacy filing that doesn't support the service area the bid covers.
A second common failure is late recruiting. Contracts take time, and so does credentialing, and the two don't compress just because a date is close. Plans that start signing providers shortly before an upload discover that the provider isn't under a fully executed contract or hasn't cleared the plan's own credentialing policy when the tables are due, which means the gap remains.
A third failure is service area overreach, including counties in the bid that the plan has not adequately evaluated for network feasibility. This is most common in plans that are expanding aggressively and add counties late in the planning cycle. Each new county added to the service area must be fully evaluated for adequacy in all 43 provider and facility types, and adding a thin county with no plan to fill it is a liability, not an asset.
Exception requests are not a fallback position: they are a legitimate part of bid cycle planning for plans operating in Rural or CEAC counties. Under 42 CFR 422.116(f), a plan can show that the providers needed to meet the standard are not available, and that the providers it did contract with are accessible to most enrollees, consistent with the local pattern of care. Inability to contract is not a valid reason.
Effective exception requests take real lead time. MedPAC's June 2024 report says the most common reason for denial was that CMS found providers within the criteria that the plan "failed to include." A census that accounts for every provider in the county and specialty, with a reason for each one not contracted, cannot be assembled in two weeks. Requests rushed in as emergency documents tend to be the thin ones.
Start exception work well before the application is due, and plan on rerunning it: plans must resubmit all previously approved exceptions whenever CMS requests an HSD upload.
Blueprint gives a team a build plan with milestones, adequacy scoring by county and specialty against the CMS 2026 HSD standards on straight-line distance, and a contracting pipeline for each provider. It also produces HSD-format provider tables and a printable draft of an exception request for your team to review and file. It doesn't file anything with CMS, and a straight-line pass shows as unconfirmed because drive time is not measured.
Passing CMS's check on the first upload has real advantages. An applicant stays out of the deficiency and Notice of Intent to Deny rounds, the last of which leaves only 10 days. And the network operations team has capacity to begin planning for the following benefit year rather than spending the spring managing remediation.
The investment required is real: it means starting the network build earlier, moving credentialing along sooner, and integrating network planning with bid planning from the beginning of the cycle. Weigh that against what it can cost not to. CMS may deny an application based on its network evaluation, and for an applicant with a gap, that can mean losing the county.
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.