Credentialing is the critical path. Treat it that way.

In most network builds, credentialing is treated as a downstream function — something that happens after contracting is done. Contracts go out, contracts come back signed, and then someone sends the files to the credentialing team. That sequencing is exactly wrong, and it is one of the most reliable ways to miss a go-live date.

Credentialing has fixed lead times. A primary source verification takes as long as it takes — state licensing boards don't move faster because your launch is in six weeks. The credentialing committee meets when it meets — monthly, every six weeks, quarterly. You cannot compress the timeline with urgency or goodwill. What you can do is start earlier, staff it correctly, and build your go-live date around what credentialing can actually deliver.

Why credentialing gets deprioritized

Credentialing is administrative, process-driven, and unglamorous. It doesn't have the negotiation energy of contracting or the strategic weight of adequacy modeling. In most organizations it sits in a department that is separate from network management and reports to a different leader. When build timelines are set, the contracting team sets the date and the credentialing team is expected to work around it.

This is exactly backwards. Contracting velocity is something you can influence — you can add outreach staff, accelerate negotiations, prioritize the providers you need most. Credentialing velocity is largely fixed. The committee schedule is set months in advance. Primary source verification has minimum timelines that regulators and accreditors require. If you don't build from the credentialing timeline outward, you will discover the constraint when it is too late to do anything about it.

How to set the credentialing calendar first

Before the build starts, get the credentialing committee dates for the next 12 months. Map the file completion deadlines for each committee meeting — most committees require complete files a minimum of 10 to 14 days before the meeting. Then work backward from your target go-live date:

• Which committee meeting is the last one before go-live?
• What is the file completion deadline for that meeting?
• Working backward 30 days for primary source verification, what is the application completion deadline for providers who need to be fully credentialed at go-live?
• How many providers can the credentialing team realistically complete per week given current staffing?

That math tells you your contracting deadline — the date by which executed contracts need to be in hand for credentialing to complete in time. If your contracting team isn't done by that date, those providers will not be fully credentialed at go-live, and you will need to either invoke provisional credentialing or accept that they will not be in the network on day one.

Staffing the credentialing function for build volume

A network build generates a burst of credentialing volume concentrated at the end. For six months, the contracting team is signing providers. Then, in the final eight to ten weeks, all of those files need to move through the credentialing process simultaneously. If the credentialing team is staffed for steady-state operations — a few re-credentials per week — they cannot handle a burst of 80 or 100 new applications without either extending the timeline or making errors.

There are three ways to handle burst volume: add temporary staff, engage a credentialing verification organization (CVO) to handle primary source verification, or plan for a larger proportion of providers to come in under provisional credentialing. All three are legitimate. None of them can be decided at the last minute. The staffing plan for credentialing needs to be part of the build plan from week one.

Contracting velocity is something you can control. Credentialing velocity is mostly fixed. Build your go-live date around the thing you can't change — not the thing you can.

The provisional credentialing bridge

CMS allows Medicare Advantage plans to use provisional credentialing for up to 60 days — a provider can see members and have claims paid while the full credentialing process completes, provided the preliminary checks are clean. This provision exists precisely because the credentialing timeline is fixed and builds always have some providers who don't make the pre-go-live committee meeting.

Using provisional credentialing is not a failure. It is a planning tool. What fails is discovering in week ten that you needed to invoke it for 40% of your network and nobody told compliance. Know your provisional credentialing population before go-live, track the 60-day windows, and ensure full credentialing completes before each window closes.

The organizations that handle credentialing well treat it as the constraint it is — building the entire schedule around it from the beginning, staffing it adequately, and using provisional credentialing deliberately rather than reactively. The ones that treat it as downstream administrative work consistently find that the critical path was exactly where they weren't looking.