Network Build Timeline Planning: Working Backwards from Your Filing Deadline

The Immovable Constraint

Unlike most project management problems where the deadline can be negotiated or pushed, CMS filing deadlines are fixed. The annual Medicare Advantage bid submission deadline — typically June 1 — does not move. Neither does the QHP certification application window. If your network build is not complete by the date your adequacy model must run, you are filing with an incomplete network.

This makes network build timeline planning fundamentally different from most project management. You don't plan forward from a start date; you plan backward from the filing deadline, identifying every milestone that must be met and the dependencies between them.

The 52-Week Master Timeline

For a plan targeting a June 1 MA bid submission (which is standard for a new benefit year or new service area), here is the backward-planned master timeline:

Week 52 (June 1): CMS Submission

The adequacy attestation, provider roster, and all supporting exception filing documentation are submitted to CMS. Every provider counted in your adequacy model must have a credentialing effective date before this date.

Week 48–51: Final Adequacy Model Run and Quality Audit

Run your final adequacy model against confirmed contracted and credentialed providers. Conduct the internal pre-submission audit. Prepare exception filing documentation for any remaining gaps. Allow two weeks for this process — the first model run almost always reveals issues that require remediation.

Week 40–47: Credentialing Close

The credentialing committee must approve all providers by Week 47 to allow administrative processing time before submission. This means PSV for all providers must complete by Week 45, CAQH applications must be complete by Week 40. Credentialing that isn't in process by Week 40 almost certainly cannot complete before submission.

Week 24–40: Contracting Close

Fully executed contracts must be in place by Week 40 to feed the credentialing pipeline. The contracting close deadline for providers you need for adequacy is Week 40; providers being added for coverage enhancement can close later. During this phase, your contracting team should be focused on finalizing LOIs and executed agreements, not new outreach.

Week 8–24: Active Outreach Campaign

The 6-touch provider outreach sequence (16 weeks for full campaign completion) runs during this period. Week 8 is the absolute latest start for outreach targeting Week 40 contracting close. Week 4 is the recommended start — which gives you a buffer cycle if a key provider needs a second outreach effort.

Week 1–8: County Selection and Adequacy Pre-Modeling

Service area finalization and pre-flight adequacy analysis happen in the first 8 weeks. This produces your target provider list by county and specialty, which drives the outreach campaign. Rushing this phase produces an outreach list that doesn't align with your actual adequacy gaps.

Common Timeline Killers

• Late county selection: Service area decisions made in Week 12 instead of Week 4 compress the outreach window and prevent adequate pre-modeling
• Sequential credentialing: Starting credentialing after contracting close (Week 40) instead of in parallel guarantees a credentialing crunch at submission
• Provider directory lag: Failing to keep the adequacy model current with credentialing status means the final model run produces surprises
• Exception filing procrastination: Starting exception filing documentation in Week 50 instead of Week 40 produces rushed, low-quality filings that draw CMS scrutiny
• Staffing ramp-up delays: Adding network ops staff in Week 20 instead of Week 1 means experienced staff are ramping during the most critical outreach phase

Buffer Planning

Every milestone in the backward plan should have a 2-week buffer built in. If PSV must be complete by Week 45 to meet the credentialing committee cycle, start it as if the deadline is Week 43. If outreach must start by Week 8, target Week 6. Buffers that aren't consumed are a gift; buffers that are consumed are what prevent cascade failures.