Provider Enrollment Maintenance Calendar: Put Every Renewal and Attestation on One Timeline

Put recurring and event-driven enrollment work on the same control table

Medicare revalidation is generally every five years, with three-year cycles for DMEPOS suppliers.

CAQH credentialing attestation runs on a 120-day cadence and location confirmation on a 90-day cadence in current CAQH materials.

Licenses, liability policies, certifications, contracts, and payer recredentialing dates follow their own schedules.

The master table needs more than provider and due date. Add requirement type, source system, state or payer, current status, preparation start, hard deadline, owner, backup owner, document dependencies, submission date, confirmation reference, and next follow-up. Use separate rows when the same clinician has independent obligations, such as a state license renewal and a payer recredentialing. That prevents one completed checkbox from hiding another unfinished task. Event-driven items belong in the same table but can use the triggering event date instead of a fixed expiration. A shared system is preferable to personal reminders because the work survives vacations and staff turnover.

Use preparation dates so renewal work starts before the official deadline

Medicare change events may require action within 30 or 90 days rather than waiting for a renewal.

A maintenance calendar should therefore track both fixed expirations and event-driven changes.

A maintenance calendar is not a collection of due dates. It is a workload forecast with owners, preparation dates, and proof of completion.

For each deadline, decide how much lead time the practice needs. A license renewal may be simple in one state and slow in another; malpractice renewal may depend on a broker; payer recredentialing may require refreshed work history and attestations. Set a preparation date based on the dependency, not a universal 30-day reminder. Add an escalation date before the hard deadline so a supervisor sees work that is stuck. When a replacement document arrives, update the source file first and then the downstream systems that use it. This turns maintenance into a planned queue instead of a series of urgent emails that arrive when the old document is already expiring.

Track Medicare revalidation from CMS data, not from a homemade anniversary rule

Medicare revalidation is generally on a five-year cycle for providers and suppliers, with a three-year cycle for DMEPOS suppliers, but CMS can also request off-cycle revalidation. The practice should use the current Medicare revalidation information available through CMS/PECOS rather than calculating the next due date by adding five years to an old approval. Store the due date, the date CMS requested action, the submission date, and the MAC disposition separately. If an off-cycle request appears, create a new work item without deleting the ordinary maintenance history. The calendar should reflect what CMS currently requires, not what the office expected based on a prior cycle.

Treat CAQH attestation and payer directory requests as separate maintenance streams

Using personal calendar reminders that disappear when staff leave. This tends to surface later, when billing or scheduling discovers that a supposedly completed file still has an unresolved dependency.

Tracking only expiration dates and not preparation dates. A brief second-person check before submission is usually faster than answering a development request after the fact.

Keeping Medicare/CAQH/payer calendars in separate systems. When this happens, correct the source record first and then update the downstream copies that are actually affected.

Missing event-driven updates because no one owns change intake. Do not bury this under a generic “pending” label. Name the blocker, the owner, and the next action.

CAQH maintenance is its own stream. Current CAQH guidance requires re-attestation every 120 days for most providers and 180 days for providers practicing in Illinois. After profile changes, re-attestation is what makes updated information available to authorized organizations. Separately, health-plan location review requests in CAQH can carry a 90-day response window; that is not the same thing as saying every provider must perform a universal 90-day location attestation. Keep those tasks distinct in the calendar. Also track commercial payer directory validations and recredentialing notices independently because a current CAQH profile does not prove a particular plan has completed its own maintenance cycle.

Create an intake lane for ownership, location, legal, and practitioner changes

Master maintenance table: Preserve the prior version when an effective-date sequence could matter in a later review.

Cms revalidation lookup: Keep the current version and enough history to show when it changed.

Caqh attestation dates: Use a filename that includes the provider or entity, document type, and the date that matters.

License/insurance expirations: Store it with the transaction rather than in a personal downloads folder or one coordinator’s inbox.

Payer recredentialing notices: Tie the document to the specific field or decision it supports.

A renewal calendar will still miss major risks unless the practice has change intake. Create a simple form or ticket for events such as new ownership, legal name or TIN change, opened or closed location, adverse legal action, clinician hire or departure, new state license, or bank/EFT change. The event should route to credentialing before staff alter payer or billing systems. For Medicare, some changes carry 30-day reporting expectations while other changes generally fall within 90 days; the team should verify the current rule for the affected enrollment. Event intake converts an operational fact into a dated compliance task instead of hoping the credentialing coordinator hears about it informally.

Publish a rolling 90-day workload view and keep evidence with every completed item

Once a month, publish the next 90 days of maintenance work grouped by owner and risk. Show items waiting on external documents, items ready for submission, and items already submitted but awaiting payer or MAC action. When a task closes, attach or link the evidence: renewed license, CAQH attestation history, PECOS confirmation, payer email, roster, or portal screenshot as appropriate. Do not delete the prior evidence; retain the history so claim and audit questions can be tied to the version that was valid at the time. A calendar with proof becomes an operational record. A calendar with only colored due dates remains a reminder system.

Operational checklist

• Create one master table with item, provider/entity, source system, due date, preparation date, owner, and evidence.
• Add recurring CAQH and directory confirmations.
• Add Medicare revalidation dates from the current CMS lookup rather than estimating anniversaries.
• Load license, certification, and liability expirations with early-prep reminders.
• Create a separate intake lane for ownership, location, adverse-action, and other reportable changes.
• Review the calendar monthly and publish the next 90 days of work to the team.

Sources reviewed