Free Network Build Assessment
Score your buildWorking backward from CMS's dates takes a detailed 12-month calendar. Here's one way to sequence provider recruitment, gap analysis, credentialing, and HSD uploads so the network is ready when CMS looks.
The Medicare Advantage bid cycle feels like a single event, the bid deadline on the first Monday in June, but the network behind it runs on its own clocks. Applicants for a new or expanded service area have to pass network review inside the application, which for contract year 2027 was due February 11, 2026. Existing contracts due for CMS's triennial review are prompted to upload full HSD tables in mid-June. Either way, the work starts the summer before. Plans that treat it as a first-quarter activity can find credentialing pipelines that can't clear in time, provider agreements that haven't been executed, or gap counties identified too late to recruit into them.
The 12-month frame also fits how CMS publishes its standards. There is no annual Call Letter for network adequacy standards: the framework lives in 42 CFR 422.116 and changes through rulemaking, and the county-level numbers, designations, time and distance maximums, and minimum counts, come in the HSD Reference File for each contract year. Plans need to load the current file as soon as it is available, model its impact on the existing network, and initiate remediation early enough to credential new providers before the network has to pass. Every month spent waiting is critical path time lost.
This playbook walks through the calendar month by month, with milestones for gap analysis, provider recruitment, credentialing pipeline management, and HSD uploads. The months are a planning template, not CMS dates. Confirm CMS's actual dates each cycle, and add buffer for larger service areas or new states, particularly in credentialing and provider agreement execution, where processing times are highly variable.
The work begins in July with a network baseline assessment. This means taking a complete inventory of the contracted network as of July 1, every provider, every specialty, every county, every panel status, and running that inventory against the current benefit year's CMS adequacy standards to confirm the baseline adequacy position. This step is often skipped by plans that assume their network is adequate because they passed the prior year's submission; in fact, the network has changed since that submission through attrition, panel closures, and geographic shifts, and the starting point for the new year's preparation may be worse than assumed.
Once the baseline is established, the next step is preliminary gap modeling against the anticipated next benefit year standards. In July and August, the next year's standards are not yet final, but the current HSD Reference File and any pending proposed rules give a strong basis for modeling. The base standards are set in regulation, so the current file is a reasonable starting point. The goal is not precision at this stage, it's identifying which counties and specialties are likely to be the most challenging and beginning recruitment planning accordingly.
Preliminary gap modeling should produce a tiered county risk list: counties where the current network is likely to be clearly adequate under anticipated standards (green), counties where adequacy is marginal and may require minor recruitment (yellow), and counties where significant recruitment is likely needed regardless of final standard specifics (red). The red counties drive the August recruitment planning conversation. These are the counties where the plan needs to be actively in market, identifying target providers, initiating outreach, and getting participation agreements into the execution pipeline, by September at the latest.
Plans should be running their gap analysis against the most current HSD Reference File by September, and rerunning it whenever CMS publishes a new file. The September gap analysis should be the definitive internal version: the document that drives recruitment prioritization, staffing, and credentialing capacity planning for the coming months.
Provider recruitment for high-priority gap counties should launch in September. Nobody publishes a reliable national figure for how long a provider takes to go from first outreach to participating; it depends on agreement negotiation, the completeness of the credentialing application, and the capacity of the plan's credentialing committee. So work backward from your own date. An applicant's tables have to pass in the application, so every provider on them needs a signed contract or a mutually signed letter of intent by late January, which puts outreach for slow-moving situations in September or October at the latest.
Recruitment in this phase should be explicitly sequenced by priority. Primary care providers in red counties come first. Specialists with the thinnest supply in your market, often behavioral health, oncology, and cardiology, come second. The remaining gap counties and specialties follow. This sequencing ensures that if the recruitment pipeline experiences delays (which it invariably does), the plan has addressed its highest-risk exposures before the pipeline backs up. Recruiting in alphabetical order by county, or in the order providers happen to return calls, leaves the hardest gaps for last.
November and December are the peak months for credentialing pipeline management. Providers recruited in September and October are now submitting applications, and the credentialing operation needs to process those applications as quickly as possible to create buffer time in case of complications. Credentialing complications are the rule rather than the exception, missing documents, primary source verification delays, licensing issues, malpractice history that requires medical director review, and plans that have not built adequate buffer into their credentialing timeline can find in the spring that providers they counted as in-pipeline are not going to be credentialed in time.
Effective credentialing pipeline management in this phase requires a daily or weekly pipeline report that tracks every provider application from submission through committee approval. The report should identify applications that are stalled, waiting for a document, pending primary source verification, in queue for medical director review, and flag those applications for expedited attention. A stalled application that is not flagged and addressed promptly can slip from the November cohort into the February cohort without anyone noticing, and may ultimately miss your deadline entirely.
Plans with large credentialing volumes should assess whether their credentialing operation has sufficient capacity to process the November and December pipeline without creating a backlog that extends into January. Temporary credentialing staff, outsourced application intake, or a credentialing process improvement sprint, addressing common bottlenecks like document collection and primary source verification, may be needed to maintain throughput. Weigh the cost of that capacity against the cost of losing a county.
January marks the transition from recruitment and credentialing pipeline management to final gap closure and adequacy verification. By mid-January, the plan should have a clear picture of which providers will clear in time and which are at risk. For providers at risk, the question becomes: can the process be expedited, or does the plan need contingency recruitment for backup providers in the same county and specialty? Make that call early, because contingency recruitment started late is unlikely to produce a usable provider in time.
Applicants need to finish final adequacy verification before the application is due. Everyone else should finish it by the end of February. Run the full county and specialty model against the contracted provider list as of that date, counting only providers who have cleared your credentialing policy and whose agreements are fully executed (or, in an application only, covered by a mutually signed letter of intent), and identify any remaining deficiencies. Deficiencies at this stage have three possible resolutions: recruiting a provider who can be under contract in time; an exception request under 42 CFR 422.116(f), if the supply really isn't there; or a service area change that removes the county. All three have significant consequences and should be evaluated by network operations, actuarial, and compliance leadership together.
Don't wait for CMS's review to see CMS's answer. Any organization with a contract ID can upload HSD tables to the Network Management Module in HPMS at any time and get an Automated Criteria Check (ACC), and CMS offers an informal Consultation upload before the formal triennial review. Use them at this stage, so discrepancies between your internal model and the ACC surface while there is still time to address them.
For applicants, the review runs in three HSD upload rounds: the initial submission with the application, the response to CMS's deficiency notice, and the response to the Notice of Intent to Deny (NOID), which 42 CFR 422.502(c)(2)(ii) gives 10 days to answer. For everyone else, this is the time to rerun test uploads ahead of any mid-June prompt for a triennial review.
The ACC scores your tables against CMS's standards using a sample census of members that plans can't see, and it reads provider addresses exactly as typed. Plans that see an unexpected deficiency should first check whether it reflects a genuine gap or a data problem: whether the provider's address is entered correctly and consistently, and whether the provider's specialty code matches the CMS type being evaluated. The ZIP Code Report for Failed Counties shows where the misses cluster.
For genuine deficiencies, plans have three paths: an exception request, a service area change, or a last-minute recruitment push. An exception request under 42 CFR 422.116(f) has to show that the providers needed to meet the standard are not available, and that the providers the plan did contract with are currently available and accessible to most enrollees, consistent with the local pattern of care. Inability to contract is not a valid reason. A service area change can have actuarial consequences. Last-minute recruitment rarely closes a gap, so start any contingency outreach early.
Bids are due the first Monday in June, so May is when the bid and the network have to agree. Reconcile the service area and network assumptions in the bid against what is actually contracted, so the plan isn't bidding on a network it doesn't have. Contracts due for triennial review should also have their HSD tables ready for the mid-June prompt.
This does not mean all network activity stops. Credentialing of providers recruited earlier in the year continues, and outreach to providers who can't be ready this cycle becomes the starting cohort for the following contract year's preparation: effectively beginning the next 12-month cycle.
Plans should use May to conduct a retrospective on the adequacy preparation process: What counties were hardest to fill? What specialty categories created the most credentialing complexity? Were there counties where the contingency recruitment was needed? What would have improved the process if started earlier? This retrospective informs the July baseline assessment for the next contract year and, done consistently, produces a continuously improving adequacy preparation machine rather than a reactive annual scramble.
The dates CMS controls are the application deadline, the deficiency and NOID rounds that follow it, and the mid-June prompt for contracts due for triennial review. Confirm them every cycle in CMS's application materials and HPMS memos. The timing you do control is how early you run your own test uploads.
The earlier the first test upload, the more time there is to correct addresses, recheck specialty coding, and build exception evidence. A plan that first sees a failure in the NOID round has 10 days. That is enough time to fix a mistyped address or add a provider whose contract was already signed. It is not enough time to recruit a specialist.
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.