Why builds stall in week six.

I've run enough network builds to know that the first five weeks usually feel fine. The pipeline is getting populated. Outreach is going out. The contracting team is logging activity. Leadership sees green on the status report and feels good about the trajectory. Then week six hits, and the whole thing slows down.

It's not a coincidence. Week six is a predictable inflection point, and the reasons it stalls are almost always the same three things: the contracting pipeline turns out to be shallower than it looked, the credentialing committee schedule creates a bottleneck nobody planned for, and the internal champion who was driving the build gets pulled onto something else.

The pipeline illusion

In weeks one through five, you are filling a funnel. Outreach is going out, providers are responding, and the number of “in conversation” records is climbing. That looks like progress — and it is, to a point. The problem is that the distance from “in conversation” to “signed contract” is not uniform. Some providers take two weeks to sign. Some take twelve. And the ones you most need — the specialists with geographic coverage in your adequacy gaps — tend to be the ones with the longest runways.

By week six, the fast signers are done. The remaining pipeline is everything that required a second and third conversation, a rate negotiation, or a decision by someone other than the person you first called. The velocity in the pipeline report drops, not because the team stopped working but because the easy wins are behind you.

If you haven't built this into your timeline from the beginning — and most teams haven't — week six looks like a stall. It isn't, exactly. But it requires a different mode of working than weeks one through five.

The credentialing committee problem

Most credentialing committees meet monthly. Some meet every six weeks. A few — particularly at smaller organizations or organizations using delegated credentialing — meet quarterly. Whatever the cadence, it is fixed. CMS and NCQA standards set the timeline for primary source verification, and the committee has to review files that have cleared that process.

Here is what this means practically: a provider who signs their contract in week four is not going to be credentialed until the next committee meeting after their file clears verification — which typically takes 30 days. If the committee meets monthly, you might be looking at a 45- to 60-day lag between contract signature and credentialing completion. If you hit week six and the first batch of contracts are just now clearing verification, you have at least another four to six weeks before those providers are ready for the directory.

Plans that didn't model this explicitly hit week six and suddenly realize the credentialing timeline is going to push go-live by six weeks. That is an avoidable problem, but only if you build the credentialing calendar before the build starts, not after.

The internal champion problem

Network builds require an internal champion — someone inside the organization who owns the project, has authority to make decisions, and is available to the build team when things need to move. In large health plans, that person is usually a VP of Network Management or a Director of Provider Contracting. In smaller organizations, it might be the CEO or COO.

What tends to happen in week six is that the organization has had five weeks to move other things forward, and the internal champion is now being pulled into whatever other priorities have stacked up. They are still nominally the sponsor of the network build, but their attention is 40% there instead of 80%. The build team starts getting slower responses to questions, decisions take longer, and the weekly check-in starts getting pushed to every other week.

This is not a character flaw — it is just how organizations work. The fix is structural: before the build starts, explicitly carve out the champion's calendar, assign a dedicated deputy who has authority to make day-to-day decisions, and build a clear escalation path so that the champion is only needed for exceptions.

What to do when you're already in week six

If you are reading this because you are currently in week six of a build that has slowed down, the first thing to do is stop and produce an honest pipeline inventory. Not a status report — an actual count of contracts at each stage, the realistic date for each one to close, and a credentialing timeline for each group of closures. Map that against your go-live date and see what the math actually says.

Most of the time, the math says one of two things: either the pipeline is fine and the velocity drop is expected, or the pipeline is not going to fill the adequacy gaps on the current timeline and you need to either accelerate outreach in specific geographies or have an honest conversation with leadership about the go-live date.

Neither of those is fun. But surfacing it in week six is a lot better than surfacing it in week ten.

Week six isn't where builds go wrong. It's where builds that were already going wrong stop being able to hide it.

The antidote to week-six stalls is building a plan that accounts for them before the build starts — credentialing committee dates mapped out, pipeline velocity modeled conservatively, champion availability protected, and go-live date calculated from the regulatory deadline backward rather than from the kickoff date forward.

We build that plan in the diagnostic. Two weeks of inventory before the build starts is worth more than six weeks of running before anyone looked at the credentialing calendar.