Managing Network Builds Across Multiple States: Coordination, Prioritization, and Avoiding Bottlenecks

The Scale Challenge in Multi-State MA Network Operations

Most competitive Medicare Advantage plans operate in more than one state. Mid-size plans typically operate in 5 to 15 states; large national plans operate in 30 or more. Each state represents a distinct operational environment: a different mix of counties with different RUCA classifications, different provider landscapes, different state regulatory overlays that affect D-SNP MOUs and Medicaid managed care requirements, and different competitive dynamics in the contracting market. The coordination challenge of managing all of these simultaneously — while meeting CMS's universal adequacy requirements and operating under a single HPMS filing window — is qualitatively different from running a network build in a single state.

Plans that manage multi-state networks successfully do so through deliberate design: structured calendars, defined staffing models, scalable technology, and explicit prioritization frameworks. Plans that manage multi-state networks reactively — addressing whichever state is most on fire at any given moment — consistently find themselves in adequacy trouble in the states that were not on fire when they looked. The core principle of multi-state network management is that you must have visibility into every state simultaneously, even if you can only actively work on a subset of them at any given time.

Building a State Portfolio Calendar

The foundation of multi-state network management is a state portfolio calendar that maps every material deadline across every state in the plan's service area. At minimum, this calendar should include: CMS HPMS adequacy filing open and close dates (which are universal across states but affect all states simultaneously); state-specific D-SNP MOU renewal deadlines; state Medicaid managed care contract renewal deadlines where applicable; credentialing committee cycle dates (which affect when new provider contracts can become effective); and major provider contract expiration clusters (months where a large number of contracts expire simultaneously, creating renewal workload spikes).

Working backwards from each deadline, the calendar should identify the trigger dates — the dates by which the team must begin a given activity to meet the downstream deadline with adequate margin. For example, if the HPMS adequacy filing window opens June 15 and closes July 31, and the team needs 3 weeks to prepare its adequacy submission, the trigger date for completing gap remediation recruitment is approximately July 10. Working backwards further, if credentialing takes 60 days after contracting is complete, new provider contracts need to be signed by approximately May 10 to be credentialed and effective by the HPMS filing date. The calendar makes these dependencies visible — and makes it clear when resource conflicts exist between states.

Staffing Model Options: Centralized, State-Based, and Hybrid

Multi-state MA plans have three broad staffing model options for network development, each with different tradeoffs. The centralized model uses a single network development team that works all states — specialists focus on provider type (primary care, behavioral health, specialists) rather than on geography, and geographic coverage is managed through market knowledge and travel. The centralized model achieves economies of scale and consistent process discipline but can struggle with the depth of local market knowledge that drives contracting success in individual states.

The state-based model assigns dedicated network development staff to each state or small group of states. State-based staff develop deep local provider relationships and market knowledge, which typically produces better contracting outcomes in individual states. The tradeoff is higher staffing cost, potential inconsistency in contracting practices and data quality across states, and coordination overhead when providers practice across state lines. The hybrid model — a small centralized team providing analytical support, process governance, and multi-state provider system management, with state-based staff handling local outreach and relationship management — is the approach most large multi-state plans have converged on. The hybrid model captures most of the benefits of both approaches if the interface between the centralized and state-based functions is well-designed.

Vendor and Delegated Contracting Entity Management Across States

Most multi-state plans use a combination of direct contracting and delegated contracting (through IPAs, PHOs, MSOs, and hospital systems with downstream provider agreements) to build their networks. Delegation creates efficiency at scale — contracting with a single regional health system's MSO can add hundreds of providers to the network simultaneously — but it also creates complexity in multi-state operations. The same delegated entity may operate in multiple states with different contracts, different credentialing standards, and different provider panel compositions in each state. Managing this complexity requires the plan to track delegation relationships at the entity level and at the individual provider level, and to have clear ownership of the adequacy impact in each state where the delegate operates.

Third-party network development vendors — contractors who conduct provider outreach and preliminary contracting on behalf of the plan — are commonly used for geographic expansion and specialty gap remediation in multi-state builds. Managing multiple vendors across multiple states requires clear scope definition (which states, which specialties, which counties), consistent data handoff protocols (so vendor-developed contract data lands cleanly in the plan's CRM and credentialing system), and active performance management. Vendors that consistently produce low conversion rates from outreach to executed contract are a resource drain regardless of how much activity they generate.

Adequacy Modeling at Scale: Building a Framework That Works Across State Landscapes

The analytical foundation of multi-state network management is an adequacy model that can evaluate gap status across all states, all counties, and all HSD categories simultaneously — and that applies CMS's T&D standards correctly given each county's RUCA classification. In a single-state plan, this model may be manageable in a well-structured spreadsheet. In a 15-state plan with 400 counties and 30-plus HSD categories, spreadsheet-based adequacy modeling is not a viable approach. The model requires too many data relationships, too many point-in-time calculations, and too many simultaneous what-if scenarios for a spreadsheet to handle reliably.

Purpose-built adequacy platforms — or well-configured CRM systems with an adequacy modeling layer — provide the analytical foundation that multi-state operations require. At scale, the platform needs to: maintain a real-time or near-real-time view of network composition by county and specialty; apply current-year CMS T&D standards correctly by urbanicity; identify gaps by county-specialty combination; model the adequacy impact of pending provider additions (contracts signed but not yet credentialed) and pending terminations; and produce gap reports that can be filtered, sliced, and prioritized by state, by specialty, or by urgency. Plans that invest in this infrastructure operate with a level of situational awareness that manual tracking simply cannot replicate.

Gap Analysis Triage Across States: Prioritizing Recruitment Resources

In a multi-state build, there will always be more gaps than can be addressed simultaneously with available resources. The key operational competency is triage — identifying which gaps to work first given the constraints of time, staffing, and provider availability. A useful triage framework considers four dimensions: adequacy impact (a single-source county gap is higher priority than a depth gap in a county with multiple providers); geography (gaps in counties where the plan has high enrollment or strong growth targets are higher priority than gaps in low-enrollment counties); specialty (newly required specialties that were added to the HSD table in the current year's Call Letter have deadline urgency that established specialties do not); and remediability (gaps in counties where providers exist but haven't been contracted are higher priority than structural shortage gaps where no providers are available within any reasonable T&D radius).

Gap triage output should be a ranked work list that directs network development staff's outreach priorities. The work list should be updated dynamically as providers are contracted, credentialed, and added to the network — closing gaps that had been open and potentially revealing new ones as the baseline shifts. In multi-state operations, the gap work list is the primary operational document that keeps network development activity aligned with adequacy outcomes rather than with activity metrics.

Managing Border Counties and Multi-State Provider Systems

One operational complexity unique to multi-state networks is the management of providers who practice across state lines. Border county providers — physicians whose primary office is in one state but who see patients from an adjacent state — may need to be contracted and credentialed in multiple states. Large regional health systems (Geisinger in Pennsylvania/New Jersey, Intermountain in Utah/Idaho/Nevada, Mayo Clinic across Minnesota/Wisconsin/Iowa) operate across multiple states with different subsidiary entities, different contracting contacts, and potentially different rate structures in each state.

Plans that contract with multi-state provider systems should designate a single contracting lead who manages the relationship at the system level — understanding the system's organizational structure, identifying the correct contracting entity in each state, and coordinating the multi-state contracting and credentialing process. Ad hoc, state-by-state outreach to multi-state systems produces inconsistent results, duplicated effort, and sometimes conflicting terms. A system-level contracting approach is more efficient and produces better outcomes because multi-state health systems respond better to a coordinated plan counterpart than to multiple uncoordinated contacts from different state offices.

Reporting to Leadership: Communicating Build Status Across a Complex Portfolio

One of the underappreciated challenges of multi-state network management is communicating build status, risk, and adequacy trajectory to plan leadership in a way that is accurate, actionable, and not overwhelming. Leaders who are not network operations specialists need a portfolio-level view — which states are on track, which are at risk, what the timeline looks like, and what decisions or resources are needed — without the level of county-specialty detail that network ops lives in daily.

Effective multi-state portfolio reporting typically uses a state-level adequacy scorecard that shows: current gap count by state (number of county-specialty combinations below the CMS standard); change from prior reporting period (net improvement or deterioration); exception count (number of gaps expected to require exception vs. expected to be filled through contracting); and time-to-filing risk flag (green/yellow/red based on whether the team is on track to resolve gaps before the HPMS window closes). This scorecard format gives leadership the visibility they need to make resource decisions and escalation decisions without requiring them to review individual county-level gap data. The underlying county-level data should be available as a drill-down for leaders who want it, but the scorecard should be the default communication format.