Network Build Project Management: Running a 40-Week Build Like a Program

Why Network Builds Need Program Management, Not Project Management

A Medicare Advantage network build is not a project in the traditional sense — it is a program consisting of multiple parallel workstreams, each with its own timeline, dependencies, and deliverables, all converging on a single regulatory deadline. The workstreams include county selection and feasibility analysis, provider data research, outreach campaign execution, contract negotiation, credentialing intake and processing, provider directory build, adequacy analysis, and HPMS submission preparation. None of these can be managed as independent projects — they are deeply interdependent, and delays in one cascade through the others.

Plans that treat network builds as a series of tasks assigned to team members without a formal program management structure consistently experience schedule drift, missed handoffs, and filing-period crises that could have been anticipated and prevented with better planning discipline.

The Master Schedule: Building from the Deadline Back

The foundation of network build program management is a master schedule built backwards from the CMS filing deadline. Every milestone in the build — from the first provider outreach to the final HPMS upload — must be anchored to the filing deadline and sequenced to account for the dependencies between workstreams.

Key milestone dates in a 40-week MA network build, working backwards from a typical mid-October HPMS deadline:

• Week 40 (filing deadline): HPMS submission complete
• Week 38–39: Pre-submission adequacy analysis and validation; waiver documentation finalized
• Week 36–37: Provider data file assembled, validated, and reviewed for accuracy
• Week 34–35: Final credentialing committee reviews completed
• Week 30–33: Credentialing files in final review; credentialing intake closed for new providers
• Week 26–30: Provider contracting close target (contracts executed)
• Week 20–26: Primary contracting negotiation period
• Week 10–20: Outreach campaign execution; initial responses and negotiations
• Week 6–10: Outreach materials prepared; provider target list finalized
• Week 1–6: County selection finalized; HSD planning; provider supply analysis

Workstream Lead Structure

Each major workstream should have a designated lead who owns the workstream's schedule, escalates risks, and reports status at the program level. The typical workstream leads for an MA network build include:

• Network Strategy Lead: Owns county selection, HSD planning, and adequacy analysis
• Outreach and Contracting Lead: Owns provider outreach, negotiation tracking, and contracting close metrics
• Credentialing Lead: Owns intake, primary source verification, committee scheduling, and credentialing completion tracking
• Provider Data Lead: Owns provider data quality, directory accuracy, and submission file preparation
• Submission Lead: Owns HPMS submission preparation, waiver documentation, and regulatory correspondence

In smaller network development teams, one person may lead multiple workstreams — but the workstream structure should still be maintained, because it defines ownership and accountability even when capacity is consolidated.

Weekly Program Status Cadence

Network build programs need a weekly status cadence that surfaces risks early enough to address them. A weekly network build status meeting should cover:

• Contracted provider count versus target by county and specialty type (with adequacy gap analysis)
• Credentialing pipeline status: how many providers are in intake, in primary source verification, ready for committee, approved?
• Schedule variances: which workstream milestones are at risk, and what is the plan to recover?
• Escalations: what decisions or resources are needed from leadership to keep the build on track?

A status meeting that produces a one-page summary with red/yellow/green status indicators for each workstream gives leadership the visibility they need to provide support without requiring deep operational involvement.

Risk Management: Anticipating What Will Go Wrong

Network build programs have predictable risk patterns. Effective program managers identify likely risks at the start of the build and have contingency plans before the risks materialize:

• Anchor negotiation delays: If a major hospital system negotiation drags past Week 20, what is the fallback strategy? Which other providers could substitute?
• Credentialing pipeline backup: If the credentialing team receives 40% more applications than projected in a short window, how will they surge capacity? Is there a credentialing vendor on standby?
• Provider data quality problems: If a significant percentage of provider addresses geocode incorrectly in the submission file, is there a data correction process ready to deploy?
• Waiver counties: Which counties are at waiver risk, and is good faith effort documentation being built for those counties starting from Week 1?

Technology as Program Infrastructure

Running a 40-week network build on spreadsheets requires a program management overhead that most teams cannot sustain. Spreadsheets do not automatically flag aging contracts, approaching credentialing committee deadlines, or counties that are falling below adequacy thresholds as contracting progresses. Purpose-built network adequacy platforms that integrate provider data, outreach tracking, contracting status, credentialing pipeline, and real-time adequacy scoring reduce the manual program management burden and give workstream leads and program managers shared, real-time visibility into build status across all dimensions simultaneously.

Post-Build Retrospective

Every network build cycle should end with a formal retrospective that documents what worked, what didn't, and what process improvements will be applied to the next cycle. Plans that conduct post-build retrospectives and implement the identified improvements consistently improve their build performance year over year. Plans that move immediately from one filing cycle into the next without reflection repeat the same problems annually.