Running a credentialing committee that doesn't slow the build.

The credentialing committee is the bottleneck most plans don't see coming. It is a regulatory requirement — you cannot credential providers without one — and it operates on a fixed meeting cadence. If your committee meets monthly and your network build is running forty providers a month through credentialing, you have a structural problem. You cannot outpace a monthly committee with a weekly outreach team.

The mistake we see most often is designing the credentialing committee for steady-state operations — monthly meetings, standard review process, a physician on the committee who has other things to do — and then launching a network build that immediately overwhelms that structure. By the time the problem is visible, you are six weeks from a submission deadline and two committee cycles behind.

The committee structure needs to be designed for the volume of the build before the build starts. Not reconfigured mid-build when you realize you have a problem.

What NCQA requires — and what it doesn't

NCQA's credentialing standards (CR 1 and related elements) require a credentialing committee or its functional equivalent. The "equivalent" language gives you design flexibility. Understanding what NCQA actually requires — versus what organizations assume it requires — matters for building a committee that works under build-phase pressure.

The committee must include a physician or clinical peer. This is a hard requirement. Someone with clinical credentials and appropriate licensure needs to participate in the review process. That person doesn't need to personally review every file — but their oversight of the process and their participation in decision-making on complex cases is required.

Meeting frequency is not prescribed as monthly. NCQA does not mandate a monthly cadence. Bi-weekly is compliant. Weekly is compliant during an intensive build phase. The frequency just needs to be documented and consistent.

Delegation of routine approvals is both permitted and underutilized. NCQA allows the plan's CMO or medical director to approve providers with clean files — no sanctions, no adverse history, no flags — without full committee review, as long as the delegation is documented in policy and the committee retains oversight of the overall process. This is a legitimate tool for accelerating throughput during a build.

Structure for velocity

A credentialing committee designed for a network build looks different from one designed for a 200-member steady-state network. Here is what we configure:

• Meet bi-weekly during the build phase, monthly at steady state. Announce this cadence at the start of the build. The committee's schedule is a constraint that everything else in the build has to work around — contracting teams, outreach teams, and credentialing staff all need to know when the next committee meeting is and work backward from it.
• Require file completion sign-off before files are queued for committee. Incomplete files are the biggest waste of committee time. If a file goes to committee with missing primary source verifications, a CAQH record that hasn't been validated, or incomplete sanction screening, the committee either tables the file or approves something they shouldn't. Build a file completion checklist and assign someone to certify completion before the file hits the committee queue.
• Delegate provisional and clean-file approvals to the CMO. Let the committee focus its time on complex cases, flagged providers, and exception decisions. Standard approvals — clean sanctions check, complete PSV, no adverse history — can move through delegated authority. This dramatically increases effective throughput without adding committee meetings.
• Publish the committee calendar for the entire build period on day one. If the build runs six months, publish six months of committee dates. Contracting teams can then work backward: to hit a committee meeting, a provider's file needs to be complete by a certain date, which means the contract needs to be executed by a prior date, which means outreach needs to start on a specific week. The calendar is the scheduling backbone of the whole build.
• Track file completion rates weekly, not just approvals. Most credentialing delays are not committee delays — they are upstream file completion delays. Primary source verification that takes longer than expected, CAQH records that are out of date, DEA certificates that haven't been received. Track where files are in the pipeline weekly and escalate completion blockers. Slow file completion is more common than slow committee decisions.

The provisionals question

CMS and NCQA allow provisional credentialing for up to 60 days while full credentialing is pending committee review. Provisional status lets you activate a provider in your network — and count them in your adequacy submission — before the committee has formally reviewed the file, as long as certain preliminary checks have been completed (sanction screening, license verification, malpractice review).

Provisional credentialing is a legitimate tool for go-live situations where you need to activate providers before the next committee meeting. We use it when the build is running close to a submission deadline and the committee cycle creates a gap that adequacy cannot absorb. Document provisional approvals carefully — they have an expiration date, and the committee review still needs to happen within the window.

What provisionals are not: a workaround for an underpowered credentialing process. If you are routinely relying on provisionals because your committee can't keep pace with the build volume, the problem is the committee cadence and file completion throughput — not a shortage of provisional authority. Provisionals buy time. They don't fix the underlying process.

The committee isn't the bottleneck. File completion is. Fix that first.

Design the credentialing committee for the volume of the build, not for steady-state operations. That means bi-weekly meetings, published calendar, clean-file delegation, and weekly file completion tracking from day one. You can always downshift the cadence after go-live — monthly meetings are fine when you are activating five new providers a month rather than forty. You cannot accelerate a monthly committee when you are sixty days from a submission deadline.