7 Adequacy Filing Mistakes That Cause Network Submissions to Fail

Why Filings Fail When Teams Think They're Ready

Most adequacy filing failures aren't caused by genuine network gaps — they're caused by process errors that produce inaccurate submissions. A plan can have a contractually complete network that fails adequacy review because of how the data was prepared, classified, or submitted. These are fixable problems, but only if you know to look for them before submission, not after a deficiency notice arrives.

The following seven mistakes account for the overwhelming majority of correctable adequacy filing failures. Each one is preventable with the right process checkpoints.

Mistake 1: Wrong Specialty Mapping

CMS evaluates adequacy across 22 specific specialty categories, each with a precise definition. The mistake is mapping providers to the wrong category — for example, counting a physician who primarily practices internal medicine as a "primary care physician" when CMS's definition of PCP for adequacy purposes requires a specific primary care designation in PECOS enrollment data.

Why it gets caught: CMS's adequacy review system cross-references your provider roster against PECOS enrollment data. If your specialty designation doesn't match PECOS, the provider is flagged and potentially disqualified from counting toward that specialty category.

How to prevent it: Validate every provider's specialty designation against their PECOS enrollment record before building your adequacy model. PECOS data is publicly available through the CMS Provider Data Catalog. Build a mapping table that translates PECOS taxonomy codes to CMS adequacy specialty categories and apply it systematically.

Mistake 2: Stale NPI Data

Provider NPI records change — providers move, change practice affiliations, retire, or update their enrollment status. An adequacy model built on NPI data that is 6 months old will count providers who have since left the county, retired, or are no longer accepting Medicare.

Why it gets caught: CMS validates submitted provider rosters against current PECOS enrollment. Providers with deactivated or inactive NPI records are automatically excluded from the adequacy calculation.

How to prevent it: Refresh your NPI data from PECOS no more than 30 days before your adequacy model run date. Set a standing process to pull updated PECOS data monthly for any county where you are at or near threshold, so NPI attrition doesn't create a surprise gap.

Mistake 3: Missing County-Level Documentation

Adequacy is measured at the county level. Some teams submit provider rosters without clearly mapping each provider to the specific counties toward which they count for adequacy purposes. A provider who is 8 miles from County A's geographic centroid and 22 miles from County B's centroid counts toward County A but not County B — but if the submission doesn't make this mapping explicit, reviewers may misassign the provider.

Why it gets caught: CMS reviewers who can't determine which county a provider is serving will either exclude the provider from the count or request clarification — which adds time and creates a deficiency flag.

How to prevent it: Include a county-to-provider mapping table in your submission package. For each county, list every provider counted toward adequacy for each specialty category, with the provider's address, NPI, and calculated distance to the county centroid.

Mistake 4: Time-Distance Calculation Errors

CMS uses specific methodologies for calculating time and distance between a county centroid and a provider location. Plans that use straight-line distance when CMS uses drive-time (or vice versa for specific county types) produce systematically incorrect adequacy assessments.

Why it gets caught: CMS's own adequacy calculation system will produce different results than your model if you've used the wrong methodology, and the discrepancy can flip a passing county to a failing one.

How to prevent it: Review CMS's published adequacy methodology for each benefit year — it specifies which measurement approach applies to which county classification. For urban and suburban counties, CMS typically uses drive-time distance; for very rural counties, straight-line distance is used. Apply the correct methodology for each county type in your service area.

Mistake 5: Not Accounting for Panel Closures

A contracted provider who has closed their panel to new patients cannot fulfill their adequacy function for members who need to see them. Plans that count all contracted providers without verifying panel status are building an adequacy model that overstates actual member access.

Why it gets caught: CMS's timely access standards and member complaint monitoring increasingly catch the gap between "adequate" networks on paper and genuinely accessible networks in practice. Plans with high member complaints about appointment unavailability draw audit scrutiny that can retroactively call into question the adequacy filing.

How to prevent it: Conduct a panel status audit — call every provider counted toward adequacy for critical specialties and confirm they are accepting new patients and accepting your plan. Do this 60 days before submission so there is time to replace providers with closed panels.

Mistake 6: LOB Crossover Errors

Plans operating in multiple lines of business — MA, Medicaid managed care, QHP — sometimes build a single provider roster and use it for all LOB adequacy filings without accounting for the fact that a provider may be contracted for MA but not for Medicaid, or vice versa. The same provider cannot count toward Medicaid adequacy if they don't have a Medicaid contract with the plan.

Why it gets caught: Medicaid adequacy reviewers cross-reference against the plan's Medicaid provider contract file. A provider who appears in the adequacy filing but doesn't have a Medicaid contract is immediately flagged.

How to prevent it: Maintain separate provider rosters by line of business and validate that each provider's contract explicitly covers the LOB for which they are being counted. LOB crossover tables in your provider management system should be a standard data field, not an afterthought.

Mistake 7: Late Submission

This sounds obvious, but late submissions are among the most common adequacy filing problems — not because teams miss the deadline by weeks, but because they miss internal milestones that make an on-time submission impossible. The final submission requires legal attestation, executive signature, and in many cases multiple system uploads. Teams that complete their adequacy analysis on the day of the deadline cannot complete the submission process in time.

Why it gets caught: Late submissions are automatically flagged. CMS's submission portal timestamps every filing, and a submission received after the deadline triggers an automatic deficiency notice regardless of the quality of the underlying data.

How to prevent it: Build your internal submission deadline two full weeks before the CMS deadline. Use the two-week buffer for quality review, legal sign-off, and system upload. If the buffer is consumed by remediation, you still meet the real deadline. If it isn't, you've built in a quality check that almost always finds something worth fixing.