The Best Medicare Advantage Plans Start Network Adequacy 12 Months Early. Here's Why.

Six Months Is the Industry Norm. It Is Not Enough.

The de facto standard for Medicare Advantage network builds is roughly six months of active work before the CMS submission deadline. This timeline is not the result of careful analysis. It is the result of repeated organizational decisions to start planning later than is warranted — delayed by budget approvals, competing priorities, or the reasonable-sounding belief that six months is enough time to get the work done.

It is not enough time. Not for a plan that wants to file a clean network, maintain good faith documentation on hard-to-contract providers, complete credentialing before submission, and negotiate contracts without the pressure of an imminent deadline. The plans that consistently file without deficiency notices, that have clean exception documentation, and that do not lose negotiating leverage on provider contracts are the plans that start 12 months out. The gap between those two timelines is not a comfort margin. It is the operational difference between a compliant network and a reactive scramble.

What the Six-Month Timeline Actually Costs You

When a plan starts its network build six months before the submission deadline, it loses specific capabilities that cannot be recovered on a compressed timeline. These are not abstract risks. They are concrete, calendar-driven losses.

• Provider outreach rounds: A 12-month build allows four or more documented outreach attempts per provider before submission. A 6-month build allows one or two. For providers who don't respond to initial outreach — which is common in high-shortage specialties — the difference between two attempts and four attempts is the difference between a thin exception record and a defensible one. CMS expects evidence of sustained outreach. One letter and one follow-up call is not sustained outreach.
• Credentialing time: Provider credentialing takes 60 to 90 days after a contract is executed. In a 6-month build, a contract signed in month three does not complete credentialing until month five or six — leaving almost no margin for credentialing delays, which are common. A plan that starts 12 months out can complete credentialing for the majority of its network with two to three months of buffer remaining. That buffer handles the inevitable delays without creating adequacy gaps at submission.
• Exception documentation quality: Good faith exception documentation is not a form. It is a record of sustained, multi-channel outreach efforts across a documented time period. A plan that identifies a no-contract county in month one of a 12-month build has 10 months to build that record. A plan that identifies the same county in month four of a 6-month build has two months — and the resulting exception request is substantially weaker.
• Contract negotiating position: Providers know when a plan is under deadline pressure. A contracting team calling providers in month five of a six-month build is negotiating from a weak position — the provider understands that the plan needs the contract more than the provider needs the patient panel. Plans operating on a 12-month timeline can walk away from a contract that doesn't meet rate or term requirements and pursue alternatives. Plans in month five cannot.

The 12-Month Calendar, Specifically

A 12-month build does not mean twelve months of undifferentiated activity. It means a structured sequence that matches the workload to the available time. The broad outline:

• Months 1–2: County-level risk assessment. Identify high-risk counties for each required specialty. Map existing provider relationships against adequacy standards. Identify markets where exception documentation will be needed and begin the outreach record immediately.
• Months 3–5: Initial outreach wave. First documented contact attempts across the full provider target list. Record all contacts, responses, and non-responses. Begin contract negotiations with responsive providers.
• Months 6–8: Contract execution and credentialing queue. Signed contracts enter the credentialing pipeline. Second outreach wave to non-responsive providers. Begin assembling exception documentation for no-contract markets.
• Months 9–10: Third and fourth outreach attempts for unresponsive providers. Credentialing nears completion for most of the network. Exception files are substantive, not thin.
• Months 11–12: HSD table compilation and data validation. Final NPPES cross-reference. Pre-submission internal review. Submission with time to respond to HPMS flags before the deadline.

A plan starting at month six cannot execute this sequence. It compresses months three through ten into months three through six, which means fewer outreach rounds, less credentialing buffer, thinner exception documentation, and a data validation phase that runs directly against the submission deadline.

Making the Case Internally

The obstacle to starting 12 months early is rarely strategic disagreement. It is organizational inertia and the difficulty of making a capital case for work that does not have a visible deadline for another year. The budget for next year's network build is always competing with this year's immediate priorities.

The case to make is a financial one. Deficiency notices require remediation, which costs staff time and may require emergency contracting at unfavorable rates. Inadequate exception documentation increases the probability of a deficiency finding. Contract terms negotiated under deadline pressure are typically worse than terms negotiated with time. And as discussed in a prior post, Star Rating impacts from access failures have multi-year revenue consequences that dwarf the cost of an earlier build start.

A plan that starts 12 months early is making a capital investment in negotiating leverage, documentation quality, and credentialing buffer. A plan that starts 6 months early is borrowing against all three — and the interest rate is high.

The plans that consistently file clean networks are not doing something that other plans cannot do. They made an organizational decision to treat the network build timeline as a strategic constraint rather than a compliance deadline. That decision, made early, is what separates the plans that file on time and without deficiencies from the plans that are perpetually in remediation — same staff, same provider markets, different calendar discipline.