Free Network Build Assessment
Score your buildA CMS filing date doesn't move. Your build timeline has to be engineered backwards from that date, accounting for credentialing cycles, adequacy modeling time, and contracting lead times. Here's how to build the plan.
Unlike most project management problems where the deadline can be negotiated or pushed, CMS application dates are set by CMS. For contract year 2027, CMS's Part C application listed the Notice of Intent to Apply deadline as January 23, 2026, completed applications due February 11, 2026, and bids due in June. CMS notes the dates are subject to change, so confirm them each cycle. Since contract year 2024, applicants must show network compliance as part of the application under 42 CFR 422.116(a)(2)(ii). If your network is not ready by then, you are filing with an incomplete network.
This makes network build timeline planning fundamentally different from most project management. You don't plan forward from a start date; you plan backward from the filing deadline, identifying every milestone that must be met and the dependencies between them.
Here is the order of work, last step first. Set the dates using your own application date, committee calendar and past turnaround times.
HSD tables for the requested service area go in with the application. After that, the review runs in three upload rounds: the initial submission, the response to CMS's deficiency notice, and the response to the Notice of Intent to Deny. The last round has a 10-day window under 42 CFR 422.502(c)(2)(ii). That is enough to fix a typed address, not to recruit a specialist.
Run your final adequacy check against confirmed contracted providers, and test the tables in CMS's Network Management Module. Conduct the internal pre-submission audit. Prepare exception requests for any gaps that truly meet 42 CFR 422.116(f). Leave real time for this step: the first check almost always reveals issues to fix.
Under 42 CFR 422.116(d)(7), applicants may use letters of intent signed by both the MA organization and the provider in place of signed contracts at the time of application and during the review. Everyone on the tables needs a signed contract or a mutually signed LOI by the filing date, and each LOI has to turn into a fully executed contract before the plan is operational.
In most plans, a provider isn't loaded as participating until the credentialing committee approves the file. Start credentialing alongside contracting, not after it, so signed providers are ready when members need them.
Your provider outreach sequence runs here. The first call is rarely the one that works, and hard specialties in Rural and CEAC counties do not close in a few weeks. Leave room for a second outreach effort when a key provider doesn't answer.
Service area decisions and pre-flight adequacy analysis come first. They produce your target provider list by county and specialty, which drives the outreach campaign. Rushing this phase produces an outreach list that doesn't match your actual adequacy gaps.
Every milestone in the backward plan should have a buffer built in. Buffers that aren't consumed are a gift; buffers that are consumed are what prevent cascade failures.
Blueprint automates the network build workflows described in this article: from adequacy modeling to provider outreach tracking. See it with your state and line of business.