Therapist Credentialing: Using AI to Track Applications and Renewals

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Therapist Credentialing: Using AI to Track Applications and Renewals.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Therapist Credentialing: Using AI to Track Applications and Renewals.

Yes, for the tracking and the writing, not the deciding. A group practice can keep one tracker row per clinician per payer, set reminders from the expiry dates, and have AI draft status checks and follow-up emails from those rows. Payers decide approvals, and clinicians or authorised staff complete and attest the applications themselves.

The money is in the gaps between steps. An application sits at "pending" for weeks because nobody asked; a malpractice certificate lapses because it lived in one person's inbox. A tracker plus a simple weekly routine prevents most of that, and AI turns the routine from an hour of writing into ten minutes of reviewing.

Follow me on Instagram@sagnikteaches

What goes wrong in a group practice without a tracker

Credentialing is the process by which an insurance payer verifies a clinician's licence, training, insurance and history before listing them in-network. Clinicians cannot usually bill a payer for its members until they are accepted, so every week of delay is a week of either lost income or awkward conversations with clients about paying out of pocket.

Connect on LinkedInSagnik Bhattacharya

In a growing practice the same failures repeat:

Subscribe on YouTube@sagnikteaches
  • A new clinician starts on the first of the month, but applications to three payers have not been sent, because the documents were incomplete.
  • An application is "in review" for 90 days and nobody has called.
  • A licence or liability certificate expires, the profile in the provider data portal is out of date, and a payer pauses the clinician's listing.
  • Re-credentialing letters arrive at an old address or an inbox nobody checks.

None of that needs AI to fix; it needs a list and a routine. AI helps because the routine involves a lot of repetitive writing, and because it can read your tracker and tell you what is due. If you want wider context for the practice, the roll-out plan for AI in mental health group practices lays out where this job sits among the others.

The Complete Excel Course with AI Integration thumbnail

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Step 1: build the tracker sheet

A spreadsheet is enough for most practices of up to 20 clinicians. One row per clinician per payer. Illustrative columns:

ColumnExampleWhy it matters
Clinician IDC07 (not the name)Keeps the sheet usable in AI prompts
Role and licence typeLicensed counsellorDifferent payers accept different roles
PayerPayer AOne row per payer
StageDocuments ready / Submitted / In review / Query / Approved / DeclinedDrives the weekly routine
Submitted on2026-09-08Starts the waiting clock
ReferencePayer's application numberQuote it on every call
Last contact2026-10-14Triggers a chase after 14 days of silence
Next actionCall payer for statusOne clear action
OwnerPractice managerA name, not "admin"
Effective date2026-11-01Date from which billing is allowed
Re-credentialing dueDate from payer letter or contractThe date to work backwards from

Keep names and identifiers out of the version you paste into AI. Use codes (C07, Payer A), and hold the key in a separate, access-controlled sheet. The coded tracker works for prompts; the real details sit in your practice management system.

Step 2: build a document checklist for each clinician

Most applications ask for the same pack. Whatever the payer, a "CAQH-style" checklist, referring to the common provider data profile many payers read from, is a helpful base. CAQH now trades as DataSpring ("DataSpring, powered by CAQH"), and its CAQH Provider Data Portal lets clinicians enter their details once and share them with the health plans they authorise. DataSpring also says profiles are kept current on a 120-day attestation cycle, so each clinician re-confirms their profile roughly three times a year. Check the current names and steps in the portal, because they change.

A document tab, with one row per clinician per document and an expiry date, might include:

  • Professional licence, with number and expiry.
  • Professional liability (malpractice) insurance certificate, with expiry and cover amounts.
  • Degree and training certificates.
  • Government-issued photo identification, held securely.
  • Work history with no unexplained gaps, usually in a CV format.
  • Disclosure answers (any past sanctions or claims), completed by the clinician.
  • Any national provider identifier, tax or business details that payers ask for.
  • A signed release or attestation, completed by the clinician.
  • The date of the clinician's last portal attestation, with the next one due 120 days later.

The expiry date column is the part that saves you. A conditional format that turns a date amber at 90 days and red at 30 means nobody has to remember. For a more general approach to dates like these, a compliance calendar for licences, insurance and certificates sets out the layout.

Step 3: set reminder rules in plain language

Write the rules down before you automate anything, because AI will only apply the rules you give it. A practical set (illustrative; adjust to your payers' timescales):

  1. Any row "Submitted" with no contact for 14 days: flag for a status check.
  2. Any row "Query": next action must be dated within 2 working days.
  3. Any document expiring in 90 days: ask the clinician to send a renewed copy.
  4. Any document expiring in 30 days and not replaced: escalate to the practice manager.
  5. Any re-credentialing due date within 180 days: start the refresh pack.
  6. Any approved row with an effective date: check the billing system is set up before the first claim.
  7. Any portal attestation due within 14 days: remind the clinician to log in and re-attest.

The 180-day figure is a planning buffer of your own, not a payer's rule. Choose a buffer long enough that a missed letter will not matter. The 120-day attestation cycle is different: it is the portal's own schedule, and a lapsed attestation can leave payers looking at a profile they treat as out of date.

A quick sum shows why rule 7 earns its place. With six clinicians each re-attesting every 120 days, the practice has about 18 attestations a year, roughly one every three weeks. Nobody remembers that pattern unaided, but a date column and a reminder handle it without effort.

Step 4: the weekly routine, with AI doing the drafting

Pick a fixed 30-minute slot every week. Paste the coded tracker rows and run this prompt.

You are helping a group therapy practice manage insurance credentialing. Below is a coded tracker (no names). Today's date is [date].
1. List every row that breaks one of these rules: [paste rules].
2. For each, state the rule it breaks and the single next action, with a suggested owner role.
3. Group the list: Do today / Do this week / Watch.
4. Do not invent any dates, references or payer requirements. If a column is empty, say "missing".

TRACKER:
[paste rows]

What comes back, and what to fix

A realistic reply (illustrative):

DO TODAY
- C03 / Payer B: Submitted 2026-09-08, last contact 2026-10-14 (22 days). Rule 1. Next action: call or message payer for status. Owner: practice manager.
- C05 / Payer A: Query open since 2026-10-28. Rule 2: no dated next action. Next action: respond to payer query. Owner: clinician plus practice manager.
DO THIS WEEK
- C07: Liability certificate expires in 74 days. Rule 3. Next action: request renewed certificate. Owner: practice manager.
WATCH
- C02 / Payer A: Re-credentialing due date missing. Next action: find the date from the payer letter.

Check three things. First, count: does the list contain every red row you can see in the sheet by eye? Second, the day-count arithmetic: 22 days is right only if today is 5 November; recompute one or two. Third, the owner: the AI proposes a role, and you assign the name. The "missing" line is useful, because an empty cell on a re-credentialing date is itself a risk.

Step 5: AI drafts the follow-ups

Once the list exists, ask for the messages. Always use placeholders for names and numbers, then merge from your own system.

Status chase to a payer

Draft a short, polite email to a payer's credentialing team asking for a status update on an application. Include placeholders for: clinician name, application reference, submission date, practice name. Mention that we submitted [N] days ago and ask for the current stage and any outstanding items. Under 90 words. Do not apologise or threaten.

Result (illustrative): "Hello, we would like to check the status of the credentialing application for [clinician name], reference [reference], submitted on [date]. Could you confirm the current stage and whether anything further is needed from us? We are happy to supply documents quickly. Thank you, [your name], [practice name]." The edit is small: add the payer's preferred contact route, and send it from the practice's own email, with the application reference in the subject line.

Reminder to a clinician for a renewed document

Write a friendly internal email to a clinician asking them to send a renewed professional liability certificate. Mention it expires on [date], we need it by [date] so profiles stay current, and ask them to send a PDF to [address]. Under 80 words.

Keep a simple library of these prompts in a shared folder so a colleague can use them in your absence. The pattern is the same as in chasing missing client records with AI before deadlines: polite, factual, dated.

A before and after for a poor chase

Before: "Hi, any update on the application? It's been ages." After: "Hello, we submitted the application for [clinician name], reference [reference], on [date], 31 days ago. Could you let us know the current stage and any outstanding items?" The second gives the recipient what they need to find the file in under a minute, which is the real driver of a quick reply.

A worked example: six clinicians, three payers

Say a practice has six clinicians and three payers, which makes up to 18 rows (some clinicians are not yet applying to every payer). Illustrative numbers:

  1. Set-up (about 4 hours, once). Build the tracker and document tab, import the dates you already know, and mark unknowns as "missing".
  2. Weekly routine (30 minutes). Run the prompt, check the output, assign names, send chases. Previously the practice manager spent roughly 90 minutes a week hunting through email.
  3. Month one. The first run flags 5 rows with no date, 3 documents expiring within 90 days and 2 applications untouched for more than 3 weeks. All of it was already true; none of it was visible.
  4. Month three. Average time from document pack complete to submission falls from 11 days to 3, because the document checklist makes gaps visible at once. The average status-chase interval falls from "whenever someone remembers" to 14 days.

In this illustration the practice gets back about an hour a week and starts new clinicians sooner. A faster start has a direct value: each week of earlier billing for a clinician with a full diary is a week of income that would otherwise be delayed. Treat the figures above as an illustration and track your own, starting with the time spent and the days from submission to approval.

A second example: a new clinician starting in six weeks

The tracker earns its keep at onboarding. Say a clinician accepts an offer and will see clients from the first of next month. Working backwards gives a timeline you can paste into the tracker as dated next actions (illustrative):

  • Week 6 before start: send the document checklist; the clinician uploads licence, insurance certificate, training certificates and a CV with no unexplained gaps.
  • Week 5: practice manager checks every expiry date; anything within 90 days is renewed first. The clinician completes their own profile in the provider data portal and authorises the payers.
  • Week 4: applications submitted to each payer; references recorded; "Submitted on" dates entered.
  • Week 2: first status chase, drafted by AI, sent to each payer.
  • Start date: the practice decides, per payer, whether to book that payer's clients with the clinician yet. Where approval is not confirmed, the clinician starts with self-pay clients or with other payers, and the client is told plainly why.

The point of listing it is that the delay lives in payers' queues, which you cannot control, so the part you can control, a complete pack submitted early, is where all the effort goes. AI can produce this timeline from a start date, but you must replace its assumptions with the actual timescales each payer states in its manual.

When a payer queries or declines

A query is a normal part of the process. The payer asks for a missing page, a clarification on a gap in work history, or an updated certificate. Treat it as a task with a clock. Record the date, the question and the deadline in the tracker the same day, and set "Query" as the stage so the weekly routine surfaces it.

A decline is different. Read the letter closely, because it usually states the reason and the route to appeal or reapply. Ask the clinician, not the AI, whether the facts in the letter are right. You can then use an assistant to draft a response from the facts you provide:

Draft a short, factual reply to a payer's request for clarification. The payer asked: [paste the question, with names removed]. The facts are: [your facts]. Write 3 to 5 sentences, state only these facts, and add a line offering supporting documents. Do not argue and do not speculate about the payer's reasons.

Read the result against the facts you gave it, send it from a person's account, and log the date. If the issue touches a disclosure answer or a complaint history, the clinician writes or approves every word.

A monthly health check on the tracker itself

Once a month, spend 15 minutes asking whether the tracker is still trustworthy. Paste the coded sheet and ask:

Review this credentialing tracker for data quality. List rows where: a stage is "Submitted" or "In review" but "Submitted on" is empty; an effective date exists but the stage is not "Approved"; a re-credentialing date is earlier than today; or the owner is blank. Return the row codes only, grouped by problem.

The output is a clean-up list, not a verdict. Fix the rows, and note the number of problems: if it keeps climbing, the routine is not being followed and the fix is a conversation about ownership, not a better prompt. Track three numbers over time: days from complete pack to submission, days from submission to approval per payer, and the number of documents that went past expiry. The last should stay at zero.

Where AI should not be used

  • Attestation. The clinician confirms their own information is accurate. A person does this in the portal.
  • Disclosure questions. Answers about past complaints, sanctions or claims are the clinician's own, and they must read each one.
  • Interpreting payer requirements. Payers publish manuals and contracts, and the rules differ. Read the payer's own document; AI summaries of requirements are a starting point at best.
  • Documents with identifiers. Do not paste scans of licences, identification or insurance certificates into a general assistant. If you want AI to read documents, use a tool your data-protection lead has approved and understand how it stores them.
  • Promising a start date to a client. Only the payer's confirmation counts.

The practice's wider confidentiality position matters too. The confidentiality checklist for AI note-taking tools in therapy sets out the questions to ask any vendor, and the same questions apply to a document tool.

Doing it with the tools you already have

You do not need a specialist credentialing product to start. A spreadsheet with conditional formatting and a shared calendar covers a small practice. Some practice management systems and credentialing services bundle tracking; others do not. If yours does, use that first, and apply the AI step to its exports.

Two practical options if you want automatic reminders without paying for new software:

  • Calendar events. For each expiry or due date, create an event 90 and 30 days before, assigned to the owner. It is dull and reliable.
  • A weekly summary email. Many spreadsheet tools can send a weekly digest of rows that meet a condition, such as "next action date is before today". Set it up once and check it works with a test row.

Whichever route you take, the human step stays: someone owns the list, someone opens the portal, someone calls the payer.

Mistakes to look for in the first three months

  • Empty cells treated as fine. A missing re-credentialing date is a risk. Chase it, do not skip it.
  • Two sources of truth. One tracker in the sheet and another in someone's inbox. Pick the sheet, and put a rule on it: if it is not in the tracker, it did not happen.
  • Letting reminders go to one person. If the practice manager is on leave, who sees them? Name a deputy.
  • Over-trusting the arithmetic. Assistants miscount days. Use spreadsheet date formulas for counting and ask the AI only for the wording.
  • Drift in payer names. "Payer A", "PayerA" and "A Payer" split the data. Use a drop-down.

If you also run a medical or multi-disciplinary service, tracking payer renewals in a medical practice with AI uses a similar structure with different documents, and the onboarding checklist for doctors shows how credentialing fits into a new starter's first weeks.

A checklist to start this week

  1. Create the tracker with one row per clinician per payer, using codes rather than names.
  2. Fill in every date you know; type "missing" for the rest.
  3. Build the document tab with expiry dates and amber and red formatting.
  4. Write seven reminder rules in plain language and save them as a prompt.
  5. Choose a weekly 30-minute slot and an owner, with a named deputy.
  6. Run the weekly prompt, check the count and the arithmetic, and send the follow-ups.
  7. Keep attestation, disclosures and portal logins with the clinicians and authorised staff only.
  8. Record time spent and days from submission to approval for three months, then decide whether to extend automation.

If you would like help turning this into a routine your whole practice follows, it falls squarely within my AI implementation consultation; you can book a call. The tracker and prompts above are enough to start on your own.

Questions group practices ask about AI and credentialing

Can AI submit credentialing applications for us?

It can draft cover notes, checklists and follow-up emails, and summarise status from your tracker. The application itself is completed and attested by the clinician or an authorised person, in the payer's or the data portal's own system. Attestation is a personal declaration, so keep it with a human.

What should a credentialing tracker record?

One row per clinician per payer: application date, status, next action and owner, submission reference, effective date, expiry or recredentialing due date, and the date you last contacted the payer. Add columns for the documents each payer wants, with the expiry date of each document, so renewals do not catch you out.

Is it safe to put clinician documents into an AI tool?

Avoid it. Licences, insurance certificates and identifiers are sensitive. Give the AI the tracker rows with identifiers removed, ask for drafts and reminders, then merge the details yourself. If you want AI to read documents, use a tool approved by your data-protection lead and confirm how it stores and uses them.

How often do credentials need to be renewed?

It depends on the licence, the insurance certificate and each payer, which sets its own recredentialing cycle in its contract or letters. The CAQH Provider Data Portal runs on a 120-day attestation cycle, according to DataSpring. Record the exact dates shown in each portal, letter or contract, and do not rely on a general rule.

Further reads

Sources: DataSpring (CAQH) clinicians page and CAQH Provider Data Portal sign-in page (checked 4 November 2026); payer manuals for each payer you work with must be checked directly for forms, timescales and renewal dates.

Want your credentialing admin out of spreadsheets and memory?

On a 1:1 call we can walk through how applications and renewals run in your practice today, build a tracker and reminder routine, and decide which follow-ups AI drafts and which stay with a person.

Book a 1:1 call with me