Why Backwards Planning Is the Only Way to Start
CMS sets the dates. For contract year 2027, applications were due February 11, 2026, and operating contracts due for triennial review are prompted to upload in mid-June. Then builds begin at a point that makes a clean submission 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 backwards planning guide that uses your HSD upload date as the anchor and works back 18 months. The intervals are our rule of thumb, not CMS requirements. Adjust them to your own deadline, your own throughput, and your market; the phase logic and sequencing are what matter. For a dated version against a real application cycle, see our service area expansion timeline.
Submission Minus 18 to Minus 13 Months: Foundation Work
Submission minus 18 months: County selection and CMS designation audit: Before any provider outreach begins, the plan must know exactly which counties it intends to serve, how CMS designates each county (Large Metro, Metro, Micro, Rural, or CEAC), and what the applicable time-distance standards are for each county 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 your own designation data. CMS sets each county's designation from its population and density and publishes it in the HSD Reference File; internal models often carry a stale designation, or a state's own urban and rural category, instead. A county your model treats as Rural that CMS designates Micro faces tighter time-distance limits on most provider types. Getting the designation 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. A county with no in-network providers of a required type is different from a county one provider short of its minimum count, and a miss on the count is different from a miss on time and distance. They need different outreach strategies.
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 holds the contact history for every provider. This is also the moment to identify counties where no viable provider target may exist, and to start the census of who is really in range there.
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. Letters go out to the full list. Phone follow-up begins for top-tier targets.
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.
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. Hospital system negotiations usually run longest. Open the credentialing file as soon as a provider says yes.
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? Divide one by the other and you have your clearing date. Does that work against the date you need them? 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. 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 a weak exception request.
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 for the credit where it applies, establish an AMC contract, change the offer, drop the county, or, where supply really isn't there, commit to an exception request. These decisions shouldn't be deferred further: each option takes time.
Submission minus 4 months: Outreach wave four and exception evidence: Final documented outreach attempts for providers who have not contracted. For genuine supply gaps, assemble the evidence 42 CFR 422.116(f) asks for: every provider in range with a disposition, dated proof for those not available, and pattern-of-care evidence. If you've kept good records throughout the build, this phase is straightforward. If you've been maintaining a spreadsheet, it will be painful.
Submission minus 3 months: Pre-submission HSD validation: Check every provider in the HSD table against NPPES for correct specialty and practice location. Confirm each address is where the provider sees patients. Re-score against the current HSD Reference File. If you hold a contract ID, test in the Network Management Module. Treat your internal result as unconfirmed until CMS's engine agrees.
Submission minus 6 weeks: Internal review and data correction: Address every data quality issue from the validation. Confirm every row is a fully executed contract or, for an applicant, a mutually signed letter of intent marked "Y". Confirm exception files are complete and organized.
Submission minus 2 weeks: Final data lock and submission preparation: The HSD table data is locked. 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.
The milestone logic does not change based on when your organization is ready to begin. CMS's date is CMS's date. The question is whether your plan is designed to reach it with a compliant network or a deficiency notice.
The Blueprint team
Provider network build practice
Written by the people behind Blueprint, who between them have spent 30 years building provider networks for health plans: recruiting and contracting providers, chasing credentialing, and filing adequacy. Blueprint is new. The experience behind it isn't.