Building a first-year MA plan's network.

A first-year Medicare Advantage application is a build on a fixed CMS deadline with no flexibility. The plan year begins January 1. CMS requires the application — including network submission — to be filed by a date that falls months before the plan year begins. Between the CMS submission deadline and the go-live date, there is a network validation (NV) review process that can surface adequacy problems requiring remediation, on a timeline that doesn't leave much room for fixes.

Organizations that underestimate the compression of this timeline don't build with enough margin. That leads to either a missed submission deadline (which means waiting another year), a submitted application with an inadequate network (which fails the NV review), or a frantic final push that produces contracts that are signed but not credentialed.

The CMS application timeline

CMS publishes the MA application calendar annually as part of the Call Letter cycle. The broad structure is consistent from year to year:

• February/March: CMS releases the Call Letter with updated adequacy standards, benefit parameters, and application requirements for the coming plan year.
• Spring (typically May/June): Applications open in HPMS (the Health Plan Management System). Organizations entering for the first time submit their initial application package, including the attestation of network adequacy.
• Summer: CMS conducts network validation reviews. This involves pulling your provider file against your service area and running it against adequacy standards. Deficiencies are returned to the plan with a deadline to respond.
• Late summer/Fall: Responses to NV deficiencies are due. Additional contracting or documentation may be required.
• October/November: CMS completes its review cycle. Plans with approved applications can begin marketing.
• January 1: Plan year begins. Members are enrolled. Claims start flowing.

This means that the network you submit in spring needs to be substantially built — not in progress, but built. The contracting and credentialing work to support that submission needs to start no later than Q1 of the year before the plan year begins. For a January 1 launch, you are looking at a 12- to 15-month build cycle if you start on time.

The network validation review

CMS network validation is not a pass/fail review with a clean outcome — it is an iterative process where CMS identifies specific adequacy gaps and asks the plan to address them. The response options are: submit additional contracted providers who fill the gap, document an exception (for rural counties where adequacy cannot be achieved), or dispute the finding.

First-time applicants often underestimate how specific the NV deficiencies are. CMS identifies gaps at the county level, by specialty, by the specific time-distance standard that was not met. “We have adequate primary care coverage” is not a response. “Here are the two additional primary care contracts we executed since submission, which fill the gap in County X” is a response. The specificity of the deficiencies requires you to have additional contracting capacity held in reserve to respond to NV findings — you cannot commit your entire contracting pipeline to the initial submission and have nothing left for remediation.

The provider file submission format

CMS has specific requirements for how provider data is submitted as part of the network attestation. The provider file must include NPI, specialty taxonomy codes, practice location addresses, and a credentialing status indicator for each provider. Errors in the provider file — incorrect taxonomy codes, addresses that don't geocode correctly, providers who appear in the file but don't have executed contracts — create NV deficiencies that you have to respond to.

Running a validation pass on your provider file before submission is not optional. It is the only way to catch data quality problems before CMS does. Common issues: specialty taxonomy codes that don't match the specialty the provider is being credited for, practice location addresses that are building addresses rather than suite-level addresses that geocode to the correct location, and NPI numbers for providers who have been deactivated in the NPPES registry.

The NV review is not a technicality. It is CMS looking at your network through the same lens that will determine whether your members can actually access care. Submit a clean file.

First-year credentialing capacity

First-year plans often don't have a credentialing committee yet — they are building the governance structure at the same time they are building the network. This is a legitimate operational challenge. Options include: delegating credentialing to a hospital or medical group that has an existing NCQA-certified credentialing program, contracting with a credentialing verification organization (CVO) to run the process, or establishing your own committee with the understanding that it will need NCQA certification within the first year of operation.

Whatever the approach, the credentialing infrastructure needs to be in place before the first contracts are executed — not simultaneously, and not after. Contracting ahead of your credentialing capacity produces a large backlog that you will spend the rest of the build trying to clear.