Free Network Build Assessment
Score your buildHealth plans that operate MA networks across multiple states face a coordination challenge that single-state plans don't: managing different filing windows, different state regulatory overlays, and different provider landscapes simultaneously. Here's how multi-state teams can stay on top of it.
Each state a plan operates in is a distinct operational environment: a different mix of counties with different CMS designations, different provider landscapes, different state rules that affect D-SNP state contracts and Medicaid managed care requirements, and different competitive dynamics. Managing all of these at once, on one CMS calendar, is a different job from running a build in a single state.
Managing multi-state networks well takes deliberate design: structured calendars, defined staffing models, the right tools, and explicit priorities. If you only work whichever state is most on fire, trouble grows in the states you aren't looking at. 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.
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 application dates and HSD upload rounds, along with any triennial review prompts; state-specific D-SNP state contract 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. Use your own turnaround times for preparing a submission, closing contracts, and completing credentialing. The calendar makes these dependencies visible, and makes it clear when resource conflicts exist between states.
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, tries to capture the benefits of both, if the interface between the two is well-designed.
Multi-state plans may 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, since a single regional health system's MSO can add many providers at once, 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, can help with geographic expansion and specialty gaps 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.
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 designation in the HSD Reference File. In a single-state plan with few counties, this may be manageable in a well-structured spreadsheet. CMS scores 43 provider and facility types in every county, so the number of combinations grows quickly with each county you add, and a spreadsheet stops being reliable.
A tool for multi-state operations needs to: show network composition by county and specialty; apply current-year CMS standards correctly by county designation; identify gaps by county-specialty combination; show the effect of pending provider additions and pending terminations; and produce gap reports you can sort by state, specialty, or urgency.
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 (specialties where the current HSD Reference File set a new or higher minimum count 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.
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 may 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 invites inconsistent results, duplicated effort, and sometimes conflicting terms.
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.
Blueprint automates the network build workflows described in this article: from adequacy modeling to provider outreach tracking. See it with your state and line of business.