The Medicare Advantage Bid Cycle and Network Adequacy: Aligning Your Build to CMS Deadlines

Why Timing Is the Hardest Part of Network Adequacy

Most health plan teams understand the technical requirements of CMS network adequacy — the 22 specialty categories, 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 Calendar: Key Statutory and CMS-Set Dates

The MA bid cycle is anchored by two statutory dates. First, plans must submit their bids to CMS no later than the first Monday in June — for the 2026 benefit year, that falls on June 2, 2025. Second, CMS must notify plans of bid acceptance or rejection no later than the first Monday in August, giving the agency approximately nine weeks to review submissions.

Within that window sit several CMS-controlled events that are less well-publicized but equally binding for network operations purposes:

• HPMS availability period for network adequacy submissions — CMS typically opens the Health Plan Management System (HPMS) network adequacy module in late February or early March, approximately 13–15 weeks before the bid deadline. Plans may begin filing network data as soon as HPMS opens, and early filing is strongly advisable.
• Network adequacy filing deadline — For most plan types, the HPMS network data must be submitted no later than two to three weeks before the bid deadline. CMS has set this deadline as early as the second week of May in recent benefit years. The exact date is published in the annual CMS Call Letter, released each spring.
• Prior approval window — New plans or plans expanding into new service areas must receive prior approval from CMS before submitting a bid. The prior approval application — which includes a preliminary network adequacy demonstration — is typically due in late January or early February, roughly 16–18 weeks before the bid deadline.
• Contract notification deadline — CMS issues contract notifications (approval or denial of new contracts and service area expansions) in mid-to-late April. Plans that receive a negative notification at this stage have very limited time to cure deficiencies before the bid deadline.

Understanding these dates as a system, not a list, is the starting point for an integrated timeline.

How Network Adequacy Approval Interacts with Bid Acceptance

CMS does not accept a bid from a plan that has not demonstrated network adequacy for the service area covered by the bid. This is not a technicality — it is a hard gate. Under 42 CFR 422.112, a plan must have a contracted network that meets CMS time-and-distance standards (or an approved exception) for every county in its service area before CMS will accept the bid for that service area.

In practice, this means the network adequacy review is a prerequisite for bid review, not a parallel track. CMS reviewers confirm network adequacy status before the actuarial review of the bid itself advances. If a plan's HPMS network submission shows unresolved deficiencies — counties below threshold with no approved exception — the bid for those counties will not proceed.

For plans with multi-state or multi-county service areas, this creates a portfolio management problem: every county in the service area must pass adequacy review independently. A single county that fails — even one with a very small Medicare-eligible population — can hold up the entire bid if it is included in the service area.

The Prior Approval Timeline for New Plans and Service Area Expansions

Plans entering a new service area for the first time must navigate the prior approval process under 42 CFR 422.501, which requires a separate application demonstrating that the plan has the administrative and network infrastructure to serve the proposed area. The network adequacy component of this application requires a preliminary demonstration — typically a draft HPMS submission or a structured attestation — showing that the plan is on track to meet standards by the full filing deadline.

Prior approval applications are due in late January. This means that plans expanding their service areas must have credible network build progress — signed LOIs, executed contracts, or at minimum documented recruitment pipelines with identified targets — by mid-January at the latest. A prior approval application submitted with no evidence of network progress is effectively a non-submission.

CMS reviews prior approval applications over approximately eight to ten weeks and issues its determination in April at the contract notification stage. Plans that receive conditional approval may be required to submit additional network evidence before HPMS filing opens, compressing the timeline further.

Working Backward: Setting Recruitment Milestones from the Bid Deadline

The most effective approach to MA bid cycle planning is strict backward planning from the bid deadline. Here is a representative milestone framework for a plan targeting the first Monday in June bid deadline:

• T-minus 26 weeks (mid-December) — Complete gap analysis using updated CMS time-and-distance standards for the target benefit year. Identify every county and specialty combination below threshold. Prioritize by risk: specialties with few available providers in thin counties are highest risk.
• T-minus 22 weeks (mid-January) — Execute contracts or LOIs for high-risk county/specialty gaps. Initiate credentialing for any newly contracted providers. For service area expansions, finalize prior approval application with network evidence.
• T-minus 18 weeks (mid-February) — HPMS adequacy module is expected to open. Begin loading provider data. Verify that all contracted providers are listed in HPMS with accurate panel status and location data.
• T-minus 14 weeks (mid-March) — Run internal adequacy model against HPMS data. Identify remaining gaps. Begin drafting exception filings for counties where recruitment has stalled.
• T-minus 10 weeks (mid-April) — Finalize exception filings. All exception documentation — outreach logs, market analysis, attestations — must be complete and internally approved. Receive CMS contract notifications for service area expansions.
• T-minus 6 weeks (late April) — Final HPMS network submission. No additional providers can be added to the adequacy demonstration after this point. Confirm that credentialing is complete for all counted providers.
• T-minus 3 weeks (mid-May) — Actuarial and regulatory teams finalize bid based on confirmed network. Conduct final review of bid documents against network adequacy status.
• T-minus 0 (first Monday in June) — Bid submission deadline.

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.

What Happens When the Timelines Don't Align

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 recruiting providers who are not credentialed in time for the HPMS filing deadline. Under CMS rules, a provider who has not completed credentialing cannot be counted toward adequacy. Plans that sign contracts with providers in April and expect to count them in a May HPMS filing regularly discover that credentialing cannot be completed in time. The provider is contracted but not creditable, which means the adequacy 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 22 specialty categories, and adding a thin county with no plan to fill it is a liability, not an asset.

The Role of Exception Filings in Bid Cycle Planning

Exception filings are not a fallback position — they are a legitimate component of bid cycle planning for plans operating in rural or frontier markets. CMS allows plans to demonstrate that a deficiency exists because qualified providers are genuinely unavailable in the area, not because the plan failed to recruit them. An approved exception converts a deficiency into a documented market reality.

Effective exception filings require months of lead time. The outreach log that CMS expects to see — documented contacts with every eligible provider in the county and specialty, with follow-up attempts and recorded responses — cannot be assembled in two weeks. Plans that treat exceptions as emergency documents rather than planned filings consistently produce thinner documentation and receive more requests for additional information from CMS, which creates delays that compress the bid timeline further.

Exception filings should be initiated no later than T-minus 14 weeks, with outreach logs current through T-minus 8 weeks. This gives the plan enough lead time to demonstrate genuine recruitment effort and enough time to resolve any CMS questions before the HPMS filing deadline.

Integrating Blueprint into the Bid Cycle Calendar

Blueprint's county-level adequacy dashboard is designed to support exactly this kind of integrated timeline management. By maintaining a live view of gap status — contracted providers, credentialing stage, HPMS-ready status — against the fixed CMS deadline calendar, network operations teams can see in real time whether their recruitment trajectory is aligned with the bid cycle or falling behind.

The platform's milestone tracking feature allows teams to set internal deadlines for each county and specialty combination, with automated alerts when a milestone is at risk. Exception filing documentation — outreach logs, provider contact records, market availability analyses — is maintained in the platform and can be exported in the format CMS expects. The result is a bid cycle in which network adequacy is not a last-minute scramble but a managed process with predictable outcomes.

The Strategic Value of a Clean First Submission

Plans that pass CMS network adequacy review on the first submission — without correction requests, deficiency notices, or corrective action plans — operate with a structural advantage over plans that don't. A clean first submission means the bid advances to actuarial review without network-related holds. It means the plan can reach final approval and begin member enrollment activities on the earliest possible schedule. And it means the network operations team has capacity to begin planning for the following benefit year rather than spending the spring managing remediation.

The investment required to achieve a clean first submission is real: it requires starting the network build earlier, credentialing more aggressively, and integrating network planning with bid planning from the beginning of the cycle. But the cost of remediation — corrective action plans, extended review timelines, potential service area reductions — is substantially higher. For plans treating network adequacy as a compliance cost to be minimized, the MA bid cycle is a reliable mechanism for converting that attitude into a competitive disadvantage.