Crises Are Not Surprises: They Are Ignored Warnings
When a network adequacy problem reaches the board, the warning signals have usually been there for months. Marginal counties that appeared in the prior year's HSD analysis and were not remediated. Spot-check calls that surfaced provider responsiveness problems that were noted internally and not acted on. Credentialing pipeline reviews that showed a growing backlog without triggering a resource conversation. Deficiency remediation timelines that were slipping without visible accountability.
Boards encounter network adequacy as a crisis because operational leadership did not convert those early signals into action. Sometimes the signals were not recognized for what they were. Sometimes they were recognized and deprioritized. Sometimes they were escalated internally and absorbed without response. The result is the same: a compliance situation that should have been managed at the operational level becomes a governance-level emergency, which is the most expensive form of network adequacy problem in existence.
Here are three scenarios through which adequacy problems can reach the board. Understanding each scenario, the mechanics of how it escalates, what the early warning signs look like, and what operational disciplines prevent it, is the foundation of a proactive adequacy governance posture.
Scenario One: A Failed Review on an Operating Contract
Under CMS's December 2024 guidance, operating contracts that fail a network review may face compliance or enforcement actions. Suspension of enrollment is one of the intermediate sanctions in 42 CFR 422.750, though MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance. So be accurate with your board: this is a low-probability, high-consequence risk, and the likelier outcome is a compliance action and a lot of work.
The escalation path looks like this. The triennial review, or a trigger such as a significant termination or a network access complaint, shows deficient counties. CMS issues a deficiency notice. The plan commits to remediation. The same counties come up again. Now it is a board conversation.
The warning signs: the same counties appear in the HSD gap analysis in consecutive cycles, remediation commitments are documented but not tracked against completion, and nothing triggers executive attention when a county flagged last year is flagged again. Treating deficiency remediation as an episodic event rather than continuous tracking is how you get here.
The operational discipline that prevents this scenario: a standing county-level deficiency tracking system that carries forward any county flagged in a prior cycle as a watch-list item in the current cycle, with explicit ownership, monthly status reviews, and an escalation trigger that brings network leadership into the conversation when a remediation commitment is not on track. The commitment made in a corrective action plan should be tracked in the same system as any other operational KPI: with a due date, an owner, and a visible status.
Scenario Two: The Access Problem That Becomes Public
Network and directory problems do get published. The Senate Finance Committee's majority staff published a secret shopper study of MA mental health listings in 2023, and HHS-OIG has published reviews of behavioral health and maternal health networks. Under the REAL Health Providers Act, CMS will post MA directory accuracy scores for plan years beginning on or after January 1, 2029, and plans must list their score on their own directory. In Medicaid, state secret shopper results must be posted on the state's website.
When an access problem becomes public, the board conversation that follows isn't only about the problem. It is about why the board did not know, whether the plan's governance provides adequate oversight of compliance functions, and what the plan's public posture will be. All three are harder if the board is hearing about it for the first time in public.
The early warning sign is the absence of board-level adequacy reporting. Without it, there's no way to tell "the board knows about this" from "the board is encountering this for the first time."
The difference between a managed disclosure and a governance failure narrative is whether the board has been regularly informed, not whether the problem itself exists.
The operational discipline that prevents this scenario is the same regular adequacy reporting structure described elsewhere: quarterly board-level dashboards that make adequacy status visible as a continuous function, not as a crisis notification. A board that receives adequacy reporting in quarters one and two will not be hearing about a problem in quarter three for the first time.
Scenario Three: Adequacy Failures That Delay Market Entry
The third scenario has the most direct revenue consequence, and it's the one with a public record: a planned market expansion that can't proceed because the network doesn't pass. MedPAC reports that new applications have been denied on network adequacy grounds. The board approved the expansion, allocated the budget, and included the projected enrollment in the financial plan. Because applications run on an annual cycle, the delay is likely a full year.
This scenario escalates quickly because it has a financial reporting consequence. Revenue that was in the financial plan is no longer coming, and the next enrollment period is twelve months away. The CFO, the board, and in some cases investors or parent-company leadership need to understand what happened, why it was not caught earlier, and what it means for the annual plan.
The warning signs appear well before the application. A mid-build HSD re-score against the current contracted roster will show whether the county is on track. A gap found with months to go is painful but potentially closeable. A gap found in the 10-day window after a Notice of Intent to Deny is not. As a rule of thumb, we'd re-score around six to eight months out.
The operational disciplines that prevent this scenario are sequenced: feasibility analysis before the expansion decision, a backwards-planned build timeline with explicit milestones, a mid-build re-score, and an internal trigger that brings network leadership into an active remediation conversation immediately if it shows a gap. Treat the upload as the first moment of reckoning, and your expansion timeline can slip a whole year.
The Common Thread: Operational Disciplines Before Crisis Creates Them
Each of the three scenarios has a different external trigger, a failed review, public disclosure, a revenue miss, but they share a common organizational failure: adequacy was managed as a compliance function rather than a business function, without the monitoring, escalation triggers, and governance visibility that business functions receive.
The preventive posture is not exotic. It is the same operational discipline plans apply to their highest-stakes clinical and financial functions: continuous monitoring, defined ownership, explicit escalation triggers, and regular reporting to the appropriate governance level. The network won't be perfect. The aim is to surface and address problems at the operational level, where they are manageable, before they reach the board.
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.