What “go-live” actually means.

In every network build, at some point someone asks “what does go-live mean?” — and the answer they get depends entirely on who they are asking. The regulatory team has one definition. The contracting team has another. The credentialing team has a third. And operations has a fourth. If you haven't explicitly aligned on a single definition before the build starts, you will discover the misalignment at the worst possible moment: when someone reports that the build is “live” and someone else says it isn't.

Go-live to the regulatory team

To the regulatory team, go-live means CMS application approval — or state filing approval — with a network that passed the adequacy review. This is a date driven by the CMS application cycle or the state DOI approval process. It is the earliest date on which the plan can legally operate.

This date is non-negotiable. You can't push the CMS application cycle. You can't ask the state DOI to delay its review. The regulatory go-live is fixed, and everything else has to be built around it.

Go-live to the contracting team

To the contracting team, go-live means that all necessary provider contracts are executed — signed by both parties, with effective dates that cover the plan year. This is a date that depends on contracting velocity and is subject to the volatility inherent in negotiating with a large number of independent parties.

Contracting go-live and regulatory go-live are not the same date, and they don't have to be. Contracts can be executed before CMS approval — the effective date of the contract can be set at plan year start even if the contract is signed months before. What cannot happen is having CMS approval and a plan year that has started without sufficient contracts to pass adequacy. The regulatory go-live depends on the contracting work being done first.

Go-live to the credentialing team

To the credentialing team, go-live means that providers are credentialed and ready to see members — specifically, that their credentialing files have been approved by the credentialing committee and their status in the claims system is active.

This is where the provisional credentialing provision becomes critical. A provider can be contracted but not fully credentialed on day one of the plan year. Under CMS provisional credentialing rules, they can still see members for up to 60 days while the full credentialing process completes. But this requires advance planning — you need to know which providers will be in provisional status, track their 60-day windows, and ensure full credentialing is completed before the window closes.

Go-live to operations

To operations — the people who actually run the plan once it is live — go-live means something different from all of the above: it means the claims system is ready to adjudicate claims, the provider directory is accurate and accessible to members, member ID cards have been issued, prior authorization protocols are in place, and the member services team has been trained to handle provider and member inquiries.

Operational go-live is often the one that gets the least explicit attention during the network build because it falls in a different workstream from contracting and credentialing. But an operational go-live failure — a claims system that can't adjudicate for a provider who is contracted and credentialed, a member who calls to ask who their in-network cardiologist is and gets no answer — creates member complaints, regulatory notifications, and provider relations problems that linger long after the build is declared complete.

The most common go-live failure isn't missing the CMS date. It's having the CMS date cleared while a different definition of go-live is silently failing.

Aligning on a single definition

In the build plans we produce, we define go-live explicitly and specifically: the date on which the plan can begin enrolling and serving members, with all necessary regulatory approvals in place, an adequate network of contracted and credentialed providers, a live claims system, and an accurate provider directory. Every workstream tracks against that definition — not against their own version of it.

This sounds basic. It is also one of the things that most builds don't do explicitly until someone asks why the build is “live” but claims are failing.