Medallion has acquired Andros. Together, we’re the largest AI-native credentialing platform in the country.Medallion has acquired Andros.Read moreRead more

Credentialing

4 questions to ask a credentialing vendor before you sign

Updated November 2026

The most useful question to ask a credentialing vendor before you sign is what the contract says happens when a file stalls or a deadline slips. A demo may not always be able to answer that question. It shows speed, and accountability lives in the SLA terms, which spell out who owns the problem when something goes wrong.

Most evaluations give that distinction too little weight. Demos tend to show files moving on schedule, but stalled files decide when providers can see patients and bill. Stalls are common: in a November 2025 MGMA Stat poll, 32% of medical groups reported a credentialing backlog, a CVO delay, or files slipping into the next quarter. The groups that stayed on time pointed to a few habits, including holding their CVOs to written turnaround targets in an SLA.

The four questions below help you separate what a vendor commits to in writing from what it shows in a demo. They’re most useful when you’re choosing between two models: a software-only tool your team runs, or a partner that pairs AI-native automation with credentialing specialists who work the exceptions.

4 key questions at a glance

Ask thisListen for
Is turnaround a contract term, or a platform average?A clause in the SLA section of the agreement, not a number from the website
When a credentialing file stalls, who's accountable?A named role or team, not "our platform will flag it"
If the vendor misses its own timeline, is there a remedy?A specific escalation step, not "we'll look into it"
Does the accuracy number describe your file, or the platform?A response that goes into detail about the credentialing specialists who will review every file for compliance before it goes to committee.

Why the usual credentialing vendor checklist can miss the real risk

Many vendor checklists test for a product or a team’s capability (e.g., integrations, pricing tiers, onboarding time, feature breadth). Most platforms may be positioned to clear that bar in a single demo, because the typical capability questions are about what a vendor says it does.

Accountability questions measure what happens on a bad day. They ask who acts when a credentialing committee flags a gap in a provider’s file, and what the agreement says if that pushes back a provider’s start date. Platform-wide marketing numbers stop helping here because they often describe the average credentialing file, and your risk sits in the tail.

Many software-only platforms are built around data infrastructure — pulling in, normalizing, and distributing provider data at scale. That’s a legitimate capability and it’s one worth having. It’s also a different job than getting a provider ready to bill and positioned to deliver care.

Medallion, for example, pairs an AI-native platform with embedded credentialing specialists to help move providers through credentialing and enrollment, with a person working files that may stall.

The questions below help you see which job a credentialing vendor is committing to.

1. Is turnaround a contract term, or is it a platform average?

A platform average describes what many customers may experience. A contract term describes what you’re owed. Ask the vendor under evaluation to point to the turnaround language in the SLA section of the master services agreement. If a figure appears only in marketing copy, that can be a signal to treat it as a benchmark rather than a commitment.

Averages may also hide the shape of the work. Across Medallion customers over the past 12 months, the median time to credential a provider with a payer was about seven days, and the average was 24 days.

The gap between those two numbers is the tail — a smaller group of files that take much longer. In credentialing, payers and state boards can control part of the clock, so some files run long. A vendor that quotes a single number may be showing you half the picture. A contract can't shorten a payer's clock, but it can decide who pays when the vendor's part runs late.

How Medallion answers it: Medallion's master services agreement sets turnaround SLAs for new license requests, payer enrollment requests, and credentialing file generation, so the commitment is in writing before work starts.

2. When a credentialing file stalls, who's accountable?

A platform built around automation still needs a person accountable for the exception, because exceptions are where delays tend to start. An example: a payer asks for more documentation, or a license renewal slips behind a state's backlog.

When talking with credentialing vendors, ask what happens to a file once it leaves the API (not what happens when the API call succeeds).

Ask about NCQA status, too. When an NCQA-accredited health plan or health system delegates credentialing work, it has to oversee that work, typically by auditing a sample of the delegate’s files.

If the delegate holds NCQA Credentialing Accreditation or Certification, the organization may choose to forgo that audit (NCQA). A vendor’s certification status can change how much oversight work lands back on your team.

How Medallion answers it: Credentialing specialists stay embedded to handle escalations, so a stalled file has a named person working it, not just an automated flag. Medallion holds NCQA Credentialing Certification across all 11 elements, effective through August 2029, which can mean less audit work lands back on your team.

3. If the credentialing vendor misses its own timeline, is there a remedy?

There should be, and it should be in writing. A missed deadline with no consequence is a policy that doesn’t bind anyone. Ask a credentialing vendor what happens when a committed timeline slips. Is there a credit, a right to terminate, or a refund? Or does the relationship roll forward on a new, unstated timeline, with your team absorbing the cost?

This is the practical difference between a promise and an SLA. A promise depends on the goodwill of whoever made it. An SLA survives a change in account manager, and an SLA with a remedy moves the cost of a miss from you to the vendor.

How Medallion answers it: If Medallion falls below 95% of requests completed within SLA for a service in any three-month period, the requests it missed don't count against your contracted volume. Missed work doesn't use up what you paid for.

4. Does the accuracy number describe your file, or the platform?

A platform-wide accuracy percentage often describes the platform. It may be an average across hundreds to thousands of files, and it may not tell you whether your files land in the typical case or the exception. That kind of figure is easy to quote and hard to use. Instead, ask a credentialing vendor you’re speaking to about what happens to the file that needs a second look: who catches it, and what process they follow.

How Medallion answers it: Credentialing specialists review every file for compliance before it goes to committee. On timing, 99.9% of recredentialing on Medallion was completed before the deadline over the past 12 months.

Bonus: Another area to consider is around credentialing volume. When volume spikes, who absorbs it?

Your vendor should absorb it before a backlog becomes a compliance gap or a potential delayed start date. The real test comes with growth. There are more states, more payers, and more exceptions than a configured tool or a lean internal team can absorb. Ask the credentialing vendor who is responsible for taking on that volume when it arrives, and whether its SLAs are sized to cover it.

How Medallion answers it: For example, Ivy Health, a rapidly growing network of outpatient clinics that provides physical, occupational, speech, and ABA therapy services, scaled provider onboarding across 700+ clinics nationwide with zero additional headcount, with Medallion's credentialing expertise embedded in its process.

What this means for your credentialing team and providers

These questions aren’t meant to trip up a vendor. They show you, before you sign, which parts of a sales conversation are contractual and which are confidence. A vendor built for enterprise risk should be able to answer all five in writing.

  • Bring these questions to every finalist, including the one that feels furthest along.
  • Ask for the SLA, credit, and termination sections of the agreement early, before pricing is settled. A lower price without a remedy means your team carries each miss.
  • Compare how each vendor handles the exception path, since that’s where your risk sits.

Talk with our team to see how Medallion’s SLA-backed commitments show up in the contract.

FAQ about the questions to ask a credentialing vendor before you sign

What's the difference between an SLA and a guarantee?

An SLA is a contractual commitment to a specific timing or service level, often with a defined remedy if it’s missed. A guarantee implies an outcome is assured regardless of circumstance. Credentialing vendors can commit to timing through an SLA. No vendor can guarantee a credentialing decision, because that decision sits with the payer or committee.

What happens if a credentialing vendor misses a deadline?

It depends on the contract. Some agreements include an escalation path or a defined remedy for a missed turnaround commitment. Others say nothing about it, which can leave a missed deadline with no defined consequence. Under Medallion's MSA, missing an SLA earns a credit, and repeated misses give you the right to terminate that service and recover prepaid fees for the period after termination. Review any vendor’s SLA section before signing.

Should credentialing turnaround time be written into the contract?

Yes, for the steps the vendor controls. A turnaround figure that appears only in marketing materials generally isn’t a contractual commitment, while the same figure in the SLA section of the agreement typically is. Expect the commitment to cover the vendor’s own work, such as getting a file committee-ready. Timing that depends on a payer or committee decision sits outside any vendor’s control.

Why do median and average credentialing turnaround times differ?

The median is the midpoint file. The average gets pulled up by a smaller set of files that take much longer, often while waiting on a payer or state board. Ask credentialing vendors for both numbers, since the gap between them shows how much of the work runs long.

What should I ask about credentialing vendor accountability, not just features?

Ask what happens when a file is the exception: who’s accountable, what credit or termination right applies to a missed deadline, and whether that accountability is contractual or implied. The five questions above are a starting point.