Field notes from network builds — not white papers.

Should you hire an internal contracting and credentialing team or use a consultancy? A practical look at true cost, timeline, deadline risk, and hybrid models.

Ghost networks break access and trigger enforcement. Learn why provider directories go stale, what CMS and the No Surprises Act require, and how to fix yours.

CMS gives Medicare Advantage plans a 10-point telehealth credit for certain specialties. See how it works, which specialties qualify, and how to use it honestly.

How your provider network composition and engagement directly drive Medicare Advantage STAR scores — and why most plans don't connect the two until they're chasing a 3.5.

A single case agreement covers one member when your network has a gap. How SCAs and letters of agreement work, how rates get set, and the compliance risks.

Moving from fee-for-service to value-based arrangements changes who you contract with and what they need to be able to do — not just how you pay them.

Entering the ACA Marketplace? Learn the QHP network adequacy standards — time-and-distance, wait times, ECP thresholds — and how they differ from Medicare Advantage.

The ECP standard trips up Marketplace filings every year. What Essential Community Providers are, the 35% CMS threshold, write-ins, and how to build early.

The Medicare Advantage application cycle runs on a fixed annual calendar, and network adequacy documentation is always the last thing ready.

Why provider fee schedules are set as a percent of Medicare, how to build a defensible benchmark by specialty and geography, and how to negotiate from there.

CMS is pushing D-SNPs toward tighter Medicaid integration. Understand SMACs, Exclusively Aligned Enrollment, applicable integrated plans, and network impact.

The mechanics of a CMS network adequacy submission — what goes in, what reviewers flag, and what triggers an RFI.

A plain-English walkthrough of the key clauses in a participating provider agreement — and the ones that quietly cause problems long after the contract is signed.

HEDIS scores are decided by which providers you contract and the data they return. Learn which measures are network-sensitive and how to build for quality.

Most credentialing committees are structured for compliance, not velocity. Here's how to design one that meets NCQA standards and keeps pace with a network build.

When a provider leaves the network or a member is mid-treatment, continuity-of-care rules protect the patient. Learn the timelines and how to operationalize them.

A signed contract is not a working provider. Learn the steps between signature and a credentialed, loaded, directory-listed, payable provider, and how to track them.

Delegation agreements with hospitals and health systems can accelerate credentialing — or create compliance problems. The difference is in what you're actually delegating.

Why a two-week diagnostic with named owners outperforms a six-week strategy engagement, every time.

Sequencing matters in a county-level network build. Not all providers are equally important at the start — here's the order that moves the adequacy clock fastest.

IPAs that accept financial risk before their infrastructure can support it are the most common failure mode we see. Here's what readiness actually looks like.

CMS, state DOIs, and federal exchange rules — what passed last review fails the next, and how to build a network that anticipates the diff.

Why credentialing should drive your go-live date, not the other way around — and how to staff it accordingly.

Plans entering Medicaid managed care from an MA background face a different adequacy framework, a different provider population, and a different compliance environment.

What a network management leadership review actually looks like, agenda included.

Fee schedule updates, quality addenda, and value-based modifications happen annually. Most plans have no formal process for managing them — and providers notice.

The No Surprises Act, state penalties, and the operational discipline required to keep your directory honest.

The pattern repeats on nearly every build. Week six is when the plan meets reality — and why it always hits the same way.

Fee negotiations are where provider relationships get made or broken. Here’s how to have the conversation in a way you can live with for the next decade.

Inheriting a build in progress is one of the harder engagements there is. Here’s what to do in the first five days.

The standard outreach model was designed for suburban commercial networks. Rural providers have different economics, different leverage, and different reasons to say yes.

CMS gives you a 60-day provisional credentialing window. Your go-live date lives inside it. Most plans don’t plan for this until it’s a problem.

The three most common reasons providers decline to join aren’t the ones you expect. Two of them are recoverable.

Most people have a general sense of time-and-distance standards. The specifics are where plans get surprised — especially on specialty thresholds and driving-vs.-straight-line methodology.

D-SNP adequacy requirements differ from standard Medicare Advantage in ways that matter at the build phase. Here’s what changes and what doesn’t.

In network builds, behavioral health adequacy is usually the last thing standing. Here’s why it’s its own problem and how to treat it that way.

Network adequacy is not a one-time achievement. It’s a condition you maintain, and attrition is the force that works against you every week.

CAQH underpins most credentialing workflows. When the data is stale, the credentialing process stalls. The maintenance program is straightforward — most organizations just don’t have one.

Large health systems operate on different contracting timelines, with different internal decision-making structures. What works for independent physicians rarely works here.

First-year Medicare Advantage applications are the most time-constrained builds in this business. The CMS timeline leaves less room than most organizations expect.

’Go-live’ means four different things to four different stakeholders. Confusing them has real operational and regulatory consequences.

Every build we run is designed to hand back a functioning operation. What the package contains and how to set the new team up to hold it.

Provider data lives in the gap between your credentialing system, contracting system, claims system, and directory. Nobody owns that gap by default.

ACO REACH entities have network requirements that don’t map neatly onto Medicare Advantage frameworks. Here’s what’s different and where the build actually starts.

The question isn’t whether to build in a given market. It’s which county to stand up first — and that decision has outsized consequences for everything that follows.

The No Surprises Act was framed as a billing reform. Its implications for network adequacy and contracting leverage are larger than most plans planned for.

Provider outreach gets the contract. Provider relations keeps the provider. Most network organizations fund the first and skip the second.