The Network Adequacy Timeline Every MA Plan Needs

Why Backwards Planning Is the Only Way to Start

The HPMS submission deadline does not move. CMS sets it, plans acknowledge it, and then — with remarkable consistency — plans begin their network build at a point that makes clean submission structurally unlikely. The operative failure is forward planning: someone picks a start date that feels reasonable, projects outreach and credentialing timelines forward from that date, and discovers in month ten that the math does not close.

The correct approach is backwards planning from the submission deadline. Start at the deadline and work backwards through every required phase of the build, assigning concrete milestones with the calendar dates that make the submission achievable. When the backwards plan produces a project start date that is earlier than the organization is comfortable with — which it almost always does — that is information about what the build actually requires, not a negotiating position. The timeline is what it is. Organizations that argue with it end up arguing with CMS.

The following is a month-by-month backwards planning guide built from the realities of network adequacy operations. It assumes an HPMS submission deadline as the anchor point and works backwards 18 months. Adjust the specific calendar dates to match your submission deadline; the phase logic and milestone sequencing apply regardless of when your plan files.

Submission Minus 18 to Minus 13 Months: Foundation Work

Submission minus 18 months — County selection and CMS classification audit: Before any provider outreach begins, the plan must know exactly which counties it intends to serve, how CMS classifies each county (urban, suburban, rural, frontier), and what the applicable time-distance standards are for each county-type and specialty combination. This is not work that can be done in parallel with outreach — it determines the outreach target. County selection decisions made at this stage affect every subsequent phase of the build. Plans that change their county scope at submission minus six months are restarting the build for those counties.

At this stage, also audit for CMS classification errors. County-type designations in HPMS are derived from RUCC codes, but they are not always accurate — particularly for counties that have experienced significant population shifts. A county classified as suburban that should be classified as rural faces different time-distance thresholds. Getting the classification right before you model the network is significantly less expensive than discovering the error after you have built to the wrong standard.

Submission minus 16 months — HSD table modeling: Run the initial HSD analysis against your existing provider roster and your target county list. The output is a gap map: which specialties are deficient in which counties, and by how much. This gap map is the outreach prioritization document. Counties with zero in-network providers in a required specialty are different from counties with two providers when the standard requires three — they require different outreach strategies and different exception documentation approaches.

Submission minus 14 months — Outreach segmentation and campaign design: Using the gap map, segment the provider target list by county priority and specialty priority. Design the outreach sequence for each segment. Assign FTE resources and establish the tracking infrastructure — the CRM or outreach log that will generate the documented contact record CMS expects to see in exception requests. This is also the moment to identify counties where no viable provider target exists, and to begin the exception documentation process for those counties immediately.

Submission minus 13 months — Outreach wave one launches: First documented contact attempts across the full target list, with priority sequencing for high-gap counties and high-shortage specialties. Certified mail goes out to the full list. Phone follow-up begins for top-tier targets. The exception documentation clock starts for no-contract counties.

Submission Minus 12 to Minus 7 Months: Active Build

Submission minus 12 months — Mid-wave one gap review: Four weeks into outreach wave one, pull the conversion data and refresh the HSD analysis against the current contracted-but-not-yet-credentialed pipeline. Some gaps are closing; others are not. Redirect outreach resources toward the counties and specialties where conversion rates are lowest and adequacy risk is highest. This is also the first checkpoint for exception documentation quality — the counties that have been in non-contact status for four weeks should already have two documented outreach attempts logged.

Submission minus 10 months — Outreach wave two and contract negotiations begin: Providers who expressed interest in wave one move to active negotiation. The contracting team takes over relationship management from the outreach team. Provider negotiations for independent practices typically run four to eight weeks to contract execution; hospital system negotiations run longer. Contracts executed at submission minus ten months complete credentialing by submission minus eight months — the earliest the credentialing team can begin clearing the first cohort of new providers into the HPMS-ready roster.

Submission minus 9 months — Credentialing pipeline review: How many contracts have been executed but are still in the credentialing queue? At what rate is the credentialing team processing files? Project forward: if the team is processing 25 files per month and 80 contracts are pending credentialing, those providers will clear in approximately three months. Does that math work against the submission deadline? If not, the credentialing team needs additional capacity now — not at submission minus four months when the backlog is visible to everyone.

Submission minus 8 months — Outreach wave three for high-priority non-converters: Third documented contact attempt for providers who have not responded to the first two waves. At this point, the no-contract exception documentation record for unresponsive providers has grown substantively. Escalation contacts — medical director outreach, plan president letters — begin for the highest-priority providers who still have not engaged.

Submission minus 7 months — Mid-build HSD refresh: Re-run the full HSD time-distance analysis against the current credentialed roster plus the contracted-and-pending-credentialing pipeline. The output tells you where the build will stand at submission if the current trajectory holds. If the analysis reveals that specific counties or specialties will still be deficient at submission, remediation work must begin now — not at submission minus three months when the options are limited to emergency contracting or exception documentation that CMS will find thin.

Submission Minus 6 to Day Zero: Final Phase

Submission minus 6 months — Gap remediation decisions: For counties that the HSD refresh shows will be deficient at the current trajectory, the plan must make a deliberate decision: continue outreach, pursue telehealth alternatives, establish an AMC contract, or commit to an exception documentation strategy. These decisions cannot be deferred further — each option requires time that submission minus six months is the last moment to start spending.

Submission minus 4 months — Outreach wave four and exception file assembly: Final documented outreach attempts for providers who have not contracted. Good faith exception files begin formal assembly: outreach logs, provider response records, alternative access documentation, and the narrative that frames the exception request. Plans that have maintained rigorous outreach documentation throughout the build will find this phase straightforward. Plans that have been maintaining a spreadsheet will find it painful.

Submission minus 3 months — Pre-submission HSD validation: Cross-reference every provider in the HSD table against NPPES and PECOS to verify active enrollment, correct specialty designation, and current practice location. Run the time-distance calculation against the validated roster. The results of this analysis are your expected adequacy determination — the assessment of how CMS will read your network before you submit it.

Submission minus 6 weeks — Internal review and data correction: Address every data quality issue identified in the pre-submission validation. Verify that credentialing is complete for every provider in the HSD table. Confirm that exception documentation files are complete and organized for the counties where they will be needed.

Submission minus 2 weeks — Final data lock and submission preparation: The HSD table data is locked. No new providers are added at this stage — any provider whose credentialing has not completed is not in the submission. The submission package is finalized.

A backwards plan is not a project schedule. It is a constraint map that tells you whether your build is feasible given the time, staff, and resources you have allocated. The sooner you run the analysis, the sooner you know what you are actually working with.

Plans that have run this backwards plan honestly — and started the build when the plan said to start — consistently file cleaner networks than plans that start when it is comfortable. The milestone logic does not change based on when your organization is ready to begin. The submission date is fixed. The question is whether the plan is designed to reach it with a compliant network or a deficiency notice.