The Cost-Center Frame Is Wrong
In most Medicare Advantage organizations, network adequacy sits in the compliance function. It has a compliance budget, a compliance headcount, and a compliance success metric: no deficiency notices. When leadership asks the CFO about network adequacy spend, the answer is typically a cost figure, staffing, contracting support, credentialing resources, with an implicit justification that it is the price of regulatory compliance.
We think that framing leads to underinvestment in a function with real revenue consequences. Network adequacy isn't only a cost center. It decides which counties you can enter, and its failures can cost more than preventing them. Whether they do, for your plan, is something to calculate rather than assume.
The CFO who builds that model will make different investment decisions than the CFO who treats adequacy as overhead. We don't print dollar figures or multiples here, because we haven't found a public benchmark we would stand behind. Use your own inputs.
Quantifying Deficiency Response Costs
A deficiency notice is not a letter. It is an operational event that generates direct costs across multiple functions at once.
Start with the staff hours required to analyze the deficiency, identify the gap counties and specialties, develop a remediation plan, and manage the response. Estimate them from your own last response, excluding any contracting or credentialing activity, and multiply by fully loaded labor cost.
Add the contracting cost. When a plan needs a provider in a specific county quickly, the contracting team negotiates from a position of visible need, and the provider knows it. If you can, compare the rates on contracts signed under deadline against normal-cycle rates for the same provider types.
Add credentialing. Expedited processing, extra committee time, or outside support are costs you only pay because the deficiency happened.
The Cost of Delayed Market Entry
Network adequacy failures in a new market, a county expansion, a new service area, or a new product type, are not just compliance problems. They are revenue delays with a calculable cost, and they're likely the largest number in your model. MedPAC's June 2024 report says new applications have been denied on network adequacy grounds.
The math is simple: projected members in the county, times expected revenue per member per month, times the months lost. Because MA applications run on an annual cycle, plan on a lost county meaning a lost year, not a lost quarter.
Compare that figure to the cost of building a compliant network in that county before the deadline. Plans that treat network build as a budget item to minimize may be optimizing for the wrong variable.
Enforcement Risk and QBP Exposure
Two more risks belong in the CFO's model, with honest probabilities.
The first is enforcement. Suspension of enrollment is one of the intermediate sanctions in 42 CFR 422.750. But MedPAC says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, so give this a low probability. Operating contracts that fail a review may still face compliance actions, and those carry staff and legal costs.
The second is Quality Bonus Payment exposure. According to KFF, plans rated at least 4 stars get a higher benchmark, usually by 5 percentage points, and star ratings also set the rebate share: 70% at 4.5 stars or higher, 65% from 3.5 to 4.5, and 50% below 3.5. Network gaps may affect access-related member survey measures, which are part of the ratings. We don't know of a published estimate of how much, so state your assumption openly.
The question is never whether network adequacy investment costs money. The question is whether that cost is larger or smaller than the consequences of an inadequate network. Do the math with your own numbers.
Building the Internal Financial Case
The CFO who wants to make the internal case has a straightforward model to build: four risk scenarios, each with a probability estimate and a dollar consequence.
Scenario one: deficiency notice in one specialty across a few counties. Probability based on prior-year near-misses. Cost: remediation labor, emergency contracting differential, and credentialing acceleration.
Scenario two: a planned expansion county that fails at application. Cost: foregone premium revenue in that market for the contract year.
Scenario three: a Star Rating decline you attribute in part to access problems. Cost: QBP and rebate impact at current enrollment, projected forward to capture the lag between an access failure and the payment change.
Scenario four: an enforcement action in a high-growth market. Low probability on the public record. Cost: projected member growth over the period, multiplied by revenue per member, plus remediation.
Sum the probability-weighted costs of those four scenarios, then compare that figure to the incremental cost of the network investment that would reduce them. If the investment is smaller than the risk, you have your case, and you built it from numbers your finance team trusts.
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.