The Board Learns About Adequacy the Wrong Way
A board's introduction to network adequacy is often a deficiency notice. Before that event, adequacy has been a compliance function: reported in committee, tracked by staff, and assumed to be under control. After the deficiency notice, it becomes a governance concern, discussed urgently, with the distinct disadvantage that the board is now reactive rather than informed.
This pattern, board engagement triggered by crisis, is not a failure of board attention. It is a failure of how network adequacy has been presented, or more accurately, not presented, to the board as a business issue. When adequacy is framed as a regulatory compliance checkbox, boards reasonably treat it as such. When it is framed as a function with direct consequences for revenue, Star Ratings, market access, and enrollment, boards engage with it at the level the function deserves.
The reframing is not difficult. It requires understanding how boards think, in terms of risk, revenue, and strategic optionality, and translating the operational reality of network adequacy into each of those three frameworks. Done well, this reframing converts adequacy from a compliance line item into a capability the board actively wants to fund and monitor.
Frame One: Adequacy as a Risk Function
Every board understands risk framing. The language of probability-weighted loss, tail risk, and downside scenarios is native to governance. Network adequacy has a clear risk story, and it should be told in those terms.
The risk landscape has three layers. The first is deficiency risk: the probability, based on current network coverage and historical gap patterns, that the next CMS review produces a deficiency notice in one or more counties. Deficiency notices are not catastrophic in isolation, but they start a remediation process with real cost: contracting on worse terms, rushed credentialing, and diverted compliance staff.
The second layer is sanction and application risk. Suspension of enrollment is one of the intermediate sanctions in 42 CFR 422.750, but MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, and that new applications have been denied on this basis. So tell the board the realistic version: a low probability of a sanction, and a real risk of a denied county in any expansion.
The third layer is Star Rating risk. Network gaps may affect access-related CAHPS measures, which are a component of Star Ratings, which determine Quality Bonus Payment eligibility. According to KFF, plans rated at least 4 stars get a higher benchmark, usually by 5 percentage points. Have your actuaries size what a half-star decline would mean at current enrollment, and be clear that the link from network gaps to ratings is an assumption you are testing.
When presenting risk, quantify it in dollars, not categories. "Adequacy failure could result in a Star Rating decline" is governance background noise. "A 0.5 Star decline from current ratings would reduce Quality Bonus Payments by approximately $X per year based on current enrollment" is a board-level finding.
Frame Two: Adequacy as a Revenue Function
Network adequacy is a direct determinant of revenue in two specific ways that boards should understand explicitly.
The first is the quality bonus. Plans at 4 stars or higher get the benchmark increase, and star ratings also set the rebate share: 70% at 4.5 stars or higher, 65% from 3.5 to 4.5 stars, and 50% below 3.5, according to KFF. A plan hovering at 4.0 stars has little room. Treat the access side of that as revenue protection, and test the assumption.
The second revenue function is market entry. For any plan considering county expansion or new market entry, network adequacy determines whether entry is possible and when. Since contract year 2024, applicants must demonstrate compliance as part of the application, and CMS may deny it. Compare the revenue from projected enrollment in that county to the network build cost.
Every expansion decision is a network adequacy decision first. The counties where the plan can build a compliant network are the counties where growth is possible. The counties where it cannot are the counties where growth will wait, or not happen at all.
Present market entry pipeline to the board in terms of network feasibility. For each target market in the strategic plan, the board should see a network feasibility assessment: current provider availability, estimated build timeline, estimated build cost, and projected revenue from enrollment once the market is open. This context converts adequacy from a back-office constraint into a visible strategic input.
Frame Three: Adequacy as a Growth Readiness Function
The third frame is the most forward-looking and often the most compelling to strategy-oriented boards: network adequacy capability as a competitive differentiator for growth.
A plan with current HSD modeling, disciplined outreach, credentialing pipelines that track against deadlines, and good records should be able to move into new markets more reliably than one that builds compliance capability reactively. The plan that can enter a county this cycle gets a year in that county that a slower competitor doesn't.
Present adequacy capability to the board with a concrete metric: the number of counties in which the plan could achieve a compliant network within a single application cycle if the decision to enter were made today. That number is a direct measure of the plan's growth options.
The Reporting Package That Makes Adequacy Visible
Board reporting on network adequacy should appear in a consistent format at a regular cadence, not only when something goes wrong. A quarterly board-level adequacy dashboard should include: current county-level adequacy status by service area (compliant, marginal, deficient); the trend in adequacy coverage over the prior four quarters; the Star Rating trajectory in access-related CAHPS categories; the pipeline of counties under active build or expansion consideration with network feasibility status; and a forward look at the next CMS review or application date and current build progress against it. Label anything measured internally as unconfirmed until CMS's Network Management Module agrees.
This reporting structure does two things. It makes adequacy visible as a function with continuous status, not an event that surfaces only at crisis. And it creates a record of board-level oversight. Boards that have been receiving regular adequacy reporting have that history. Boards that engaged with adequacy for the first time in response to a deficiency notice do not.
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.