Free Network Build Assessment
Score your buildEvery provider on your active roster has a recredentialing date. When it passes without a decision, the provider may have to come off the roster, which can open an adequacy gap. Here's how to build a system that keeps every credential current.
Network adequacy compliance is typically discussed in terms of gaps that appear at filing time: counties below threshold, specialties with insufficient providers, exception filings that weren't approved. But there is a category of adequacy risk that develops invisibly between filing cycles: the credentialing expiration. A provider who was fully credentialed at your last HSD upload may have a lapsed credential months later. Taking them off the active roster may open an adequacy gap in a county that passed CMS's check.
A lapsed credential can also become a directory problem, if a provider is listed as active when they shouldn't be. A systematic approach to expiration management is much cheaper than untangling both at once.
This article explains the credentialing timeline, how to build an advance warning system, the recredentialing workflow, how to handle gaps during recredentialing, and what records to keep.
NCQA requires recredentialing at least every 36 months. If your plan holds a different accreditation, or none, check what your accreditor, your state, and your own credentialing policy require.
Some provider types may be on a shorter cycle under state law or plan policy. Plans with mixed-cycle policies must track each provider's cycle length individually rather than applying a blanket assumption.
Some monitoring happens between cycles. NCQA's September 2025 credentialing e-book describes monthly monitoring of practitioner sanctions, license expiration, complaints, and quality issues for Credentialing Accreditation. These interim checks do not reset the cycle, but their results should be documented and may call for a special review if a problem turns up.
An advance warning system gives you time to finish recredentialing before a date passes. One workable pattern is reminders at 90, 60, and 30 days before each due date. That pattern is our suggestion, not a CMS or NCQA rule, so adjust it to how long your own files actually take. Remember that NCQA's verification limits run element by element, so starting too early can also mean re-running a verification before committee.
An effective system has three components: a list of recredentialing dates that is kept current as providers are credentialed or recredentialed; alerts at the intervals you choose; and a task that routes each recredentialing file to the right staff member at the first alert.
The alerts are only as good as the underlying data. When credentialing dates live in spreadsheets or disconnected systems, a date can pass without an alert because the data wasn't current or the alert wasn't set up. Generating alerts from the same record that drives the active roster closes that gap.
A secondary element of the warning system should be provider-facing communication. Sending the provider a notice at 90 days, requesting attestation completion, updated malpractice certificate, and current licensure documentation, starts the process from the provider's side simultaneously with the internal workflow. A provider who gets no advance notice may be caught off guard when contacted close to the due date, which delays the process further.
The recredentialing workflow mirrors initial credentialing in structure but benefits from an existing record. The core steps are:
If a recredentialing file is not complete and approved before the expiration date, the plan faces a temporary credential gap. The provider's credential has lapsed; they cannot be carried as an active panel member during the gap period. How the plan handles this situation has significant implications for both member access and compliance.
Your accreditor's standards and your own written policy decide what happens in that window, so check them before you need them rather than assuming a grace period exists. Whatever the policy allows, document each decision and why it was made.
The adequacy effect is simple to state. If a provider comes off the active roster, the county's numbers rest on the providers who remain. If that drops the county below the CMS standard, the plan has a gap to close, and a gap the plan identifies itself must be reported to its CMS Account Manager.
The practical implication is that a recredentialing file shouldn't approach its due date without a committee decision in sight. If a file is still incomplete as the date nears, missing provider attestation, outstanding primary source verification, incomplete sanctions check, the credentialing coordinator should escalate immediately. An extra committee review is disruptive; an adequacy gap is more so.
For every provider on the active roster, keep a complete credentialing file that includes the initial credentialing file, all subsequent recredentialing files, all primary source verification records, all sanctions check results, committee minutes reflecting the review and decision, and provider notification letters.
Check your files for the obvious weaknesses: missing elements, undated documents, verification obtained from the provider rather than from the issuing source, minutes that approve a batch of files by number without identifying each one, and approvals dated after the due date with no explanation.
Keep files for providers who have left the network as well, since a question about a past period may cover them. Confirm the retention period with your compliance team against your CMS contract and 42 CFR 422.504(d) rather than purging records when a provider terminates.
Blueprint does not perform credentialing. It tracks credentialing status on each provider, screens rosters against the OIG exclusion and Medicare opt-out lists, and shows which providers a county depends on, so a team can see which lost provider would hurt adequacy most.
Blueprint automates the network build workflows described in this article: from adequacy modeling to provider outreach tracking. See it with your state and line of business.
Credentialing Timeline Planning: Build Around the Real Clocks, Not a Rule of Thumb
7 min read
CredentialingDelegated Credentialing in Network Builds: Accelerating Provider Onboarding at Scale
8 min read
CredentialingRunning an Effective Credentialing Committee: Structure, Cadence, and Compliance Requirements
8 min read