What you inherit when you take over a stalled build.

When an organization calls us to take over a build that has stalled — and this happens more often than you'd expect — the most important thing to understand is that you are not inheriting a build. You are inheriting a set of claims about a build. Claims about how many contracts are signed, how many providers are in the credentialing pipeline, how many counties have cleared adequacy. Some of those claims are accurate. Some aren't. Your first job is to find out which is which.

The people who ran the build before you are usually not lying. They are reporting the world as they understood it. But builds that stall tend to stall because the tracking was not rigorous — because “in conversation” became interchangeable with “committed,” because a contract that was “sent for signature” was treated as equivalent to a contract that was signed. The gap between the reported state of the build and the actual state of the build is where you have to start.

Day one through three: build the real inventory

Do not trust the status report. Pull the actual data. This means:

• Contracts:Get a list of every provider claimed as signed or contracted. For each one, verify that a fully executed contract exists — both signatures, effective date, not just an LOI or a verbal. The gap between “contracted” and “executed contract on file” is often 20% to 30% of the reported total.
• Credentialing:Pull the credentialing system. How many applications are actually complete and in committee review? How many are partially complete, waiting on primary source verification, or waiting on the provider to respond to a deficiency notice? “In the credentialing pipeline” is not a useful status — you need to know which step each file is at.
• Adequacy:Run a fresh adequacy analysis using your current contracted providers — only the ones with executed contracts and completed credentialing. Not the ones “in process.” Compare that against CMS or state DOI requirements by county and specialty. That is your actual gap.
• Provider data:Check CAQH for every contracted provider. Are CAQH profiles current? Have any re-attestation windows lapsed? A provider whose CAQH profile is more than 120 days out of date cannot be credentialed until it's updated — and updating it takes two to three weeks.

This inventory takes two to three days. It is not glamorous work. But it is the only foundation you can build from.

Day three through five: find out why it stalled

Stalled builds have causes. The cause is not usually “the team wasn't working hard enough” — it is structural: a resourcing problem, a decision authority problem, a timeline problem, or a market problem (some counties just don't have the providers to meet adequacy standards under the proposed fee schedule).

Talk to the people who were running the build. Not in a blame-seeking way — in a diagnostic way. What did they try that didn't work? Where did they keep hitting walls? Who were the providers they couldn't get to sign? What was the reason those providers gave? The answers will tell you whether the problems were execution issues you can fix or structural issues you need to plan around.

Also talk to any providers who were in active negotiation. The outreach team's version of why a negotiation stalled is not always the same as the provider's version. If a provider says the rate was too low, that is useful information. If a provider says they had a bad experience with a claims dispute from a prior relationship with your organization — that is a different problem entirely.

Building the new plan

Once you have an honest inventory and a clear picture of why things stalled, build a new plan from current state. Not from the original kickoff timeline — from today. Set a new go-live date that is calculated from the regulatory deadline backward, accounting for realistic credentialing lead times and current contracting velocity.

If the honest math says the original go-live date is not achievable, surface that immediately. The worst thing you can do when you take over a stalled build is inherit the original timeline and then miss it again. Organizations can adjust to a new date. What they cannot recover from easily is a second missed date.

You are not there to defend the previous plan. You are there to build a new one that is actually achievable — and then hold it.

The organizations that handle build transitions well are the ones that give the new team explicit authority to reset expectations and rebuild the plan from scratch. If leadership is expecting you to rescue the original timeline, you have a different problem to solve before you can solve the build.