When to use this playbook
-
You are outsourcing credentialing for the first time and need to distinguish full execution from application preparation or software access.
-
Your internal team is missing expirables, payer follow-ups, or recredentialing deadlines, but another full-time hire does not make sense.
-
You are replacing a vendor because applications disappear into a spreadsheet, updates require repeated emails, or nobody owns stalled cases.
-
You need payer contracting, government enrollment, multi-state expansion, or ownership changes in addition to routine provider credentialing.
What success looks like
By the end of a 45- to 60-minute vendor call, you should know exactly what triggers a fee, who submits each application, what proves submission, how often follow-up occurs, and who is accountable when a case stalls.
A credentialing company cannot control when a payer makes its final decision. It can commit to the work it controls: readiness review, submission, deficiency responses, follow-up, escalation, status reporting, and confirmation of effective dates.
Step 1: Normalize every quote to the same pricing unit
Action
Spend 15 minutes converting each proposal into a cost by provider, payer, state, and year. Public pricing reviewed on August 31, 2026 shows that credentialing firms use per-provider packages, per-payer or per-application fees, monthly retainers, and hybrids of these models.
| Examples of current market structures: PayerReady pricing, Niyutsa pricing, and AMS Solutions maintenance pricing. | |||
| Pricing model | What the unit should mean | Frequently bundled | What to price separately |
|---|---|---|---|
| Per provider | One provider across a defined payer panel, state footprint, or initial setup scope | Provider intake, CAQH setup or audit, and a specified number of enrollments | Additional payers or states, group setup, maintenance, and contracting |
| Per payer | Usually one provider-payer combination, but the contract must define products, states, groups, and locations | Application preparation, submission, routine follow-up, and approval documentation | Multiple payer products, group linking, appeals, revalidation, and location changes |
| Per application | One discrete enrollment transaction | Preparation and filing of the initial transaction | Resubmissions, deficiencies, reassignments, TIN changes, and recredentialing unless expressly included |
| Monthly retainer | Ongoing management of a defined provider roster and payer workload | CAQH maintenance, expirables, roster updates, recredentialing, reporting, and routine follow-up | New applications or project work may be excluded, capped, or billed separately |
Require every line item to be marked included, additional fee, or out of scope. Cover initial enrollment, group and individual applications, Medicare and Medicaid, commercial payers, CAQH, recredentialing, expirables, EDI/EFT/ERA, closed-panel appeals, contract negotiation, and ownership or TIN changes.
Expected outcome
You can calculate the full first-year cost for the same roster and payer list across every vendor, rather than comparing unrelated headline prices.
Gotchas
-
“Per payer” may count group enrollment, individual enrollment, each state, and each payer product separately.
-
“Unlimited credentialing” is meaningless without defined provider, payer, state, and monthly-volume limits.
-
A low monthly fee may cover maintenance while charging every new application as project work.
-
Confirm whether rework caused by a vendor error is included at no additional cost.
Step 2: Make the vendor assign an owner to every milestone
Action
Use 10 minutes of the call to map responsibilities from provider intake through billing handoff. Ask who gathers documents, completes forms, obtains signatures, submits applications, responds to deficiencies, follows up, escalates stalled cases, and confirms approval.
| Milestone | The answer you need |
|---|---|
| Provider intake | Who contacts providers, checks completeness, and chases missing documents? |
| Application preparation | Who selects the correct entity, TIN, location, payer product, and enrollment path? |
| Submission | Does the vendor file directly, or return completed paperwork to your team? |
| Deficiencies and rejections | Who receives payer requests, prepares corrections, and resubmits? |
| Follow-up and escalation | Who contacts the payer, on what cadence, and when does escalation begin? |
| Completion | Who confirms the effective date, provider ID, group linkage, and billing readiness? |
| Ongoing maintenance | Who owns CAQH reattestation, expirables, rosters, revalidation, and demographic changes? |
Arctic Health handles document collection, application completion, payer submission, rejection management, follow-up, status tracking, and ongoing maintenance. It also assigns a dedicated partner with regular check-ins. That is the level of operational ownership buyers should require vendors to define in writing. Arctic Health credentialing workflow
Expected outcome
The statement of work contains a responsibility matrix that identifies what the vendor owns, what your team supplies, and which events require provider signatures or organizational approval.
Gotchas
-
“We manage credentialing” can mean the vendor prepares forms but expects your staff to submit and follow up.
-
A portal does not replace an accountable operator.
-
Shared ownership usually becomes unclear ownership when a payer requests corrections.
Step 3: Verify that applications are actually submitted
Action
Ask for a screen-share of a de-identified application record. A submitted case should contain the payer, provider, entity or TIN, location, submission timestamp, confirmation or tracking number, submitted documents, current status, and next follow-up date.
A completed CAQH profile is not proof that a payer-specific enrollment was filed. CAQH lets providers maintain professional information and authorize selected organizations to access it; the payer enrollment still needs its own submission path and evidence. CAQH Provider Data Portal guide
For Medicare applications, PECOS generates a submission confirmation, identifies the processing contractor, supplies a tracking number, and displays application status. Commercial-payer evidence may take the form of a portal confirmation, email receipt, case number, or documented transmission. CMS Medicare provider enrollment guidance
Expected outcome
The contract defines the artifact that changes an application from “in preparation” to “submitted,” and your organization can access or export that evidence.
Gotchas
-
A tracker marked “submitted” without a receipt, timestamp, or case number.
-
Counting CAQH attestation as proof of enrollment with every target payer.
-
A screenshot that does not identify the provider, payer, entity, or application type.
-
Submission evidence that remains in an employee’s email account instead of the shared record.
Step 4: Test status visibility and communication ownership
Action
Spend 10 minutes inside the system the vendor expects you to use. Ask the vendor to locate one stalled application, explain what happened, show the underlying evidence, identify the current owner, and state the next action without consulting a separate spreadsheet.
The minimum useful record includes:
-
Provider name and NPI
-
Group, legal entity, and TIN
-
Practice location, state, payer, and payer product
-
Application type and current status
-
Submission date and confirmation number
-
Outstanding item and responsible party
-
Last payer contact and next follow-up date
-
Approval date, effective date, and provider ID when complete
Require a named primary contact, a backup contact, a response target, and a recurring review cadence. Arctic Health combines a dedicated credentialing specialist with record-level visibility from document collection through payer approval. Arctic Health and Taiga Billing case study
Expected outcome
Your RCM, operations, or compliance lead can determine the condition of the roster without waiting for a custom report or chasing the vendor by email.
Gotchas
-
A dashboard that shows labels but not submission receipts, notes, owners, or next actions.
-
A generic support inbox with no person accountable for the roster.
-
Status reports sent only when requested.
-
No ability to export records and attachments at termination.
Step 5: Put controllable turnaround commitments into the SLA
Action
Use 10 minutes to separate the vendor’s turnaround from the payer’s processing time. Ask the vendor to fill in each commitment below and define when its clock begins.
| Vendor-controlled milestone | Required commitment |
|---|---|
| Readiness review | Identify missing or conflicting information within a stated number of business days after intake. |
| Initial submission | Submit within a stated number of business days after the file is complete and required signatures are received. |
| Payer deficiency | Review, assign, and respond within a stated period after receipt. |
| Routine follow-up | Contact the payer at a defined cadence and document every attempt. |
| Escalation | Escalate after a defined period or number of unsuccessful contacts. |
| Status reporting | Maintain current record-level status and deliver a recurring roster summary. |
| Completion | Provide approval evidence, effective date, provider ID, and billing handoff. |
Expected outcome
The SLA measures work the vendor can perform rather than promising a payer approval date the vendor does not control.
Gotchas
-
“Turnaround time” without defining whether it means intake, preparation, submission, or approval.
-
An SLA clock that restarts whenever the vendor asks a minor question.
-
“Regular follow-up” without a documented cadence.
-
No escalation rule for closed panels, missing applications, or unresponsive payer representatives.
Step 6: Run reference checks against your actual operating model
Action
Schedule two or three 20-minute reference calls. At least one reference should resemble your organization in provider count, specialty, state footprint, payer mix, and credentialing complexity.
Ask each reference:
-
Did the vendor submit applications directly, or did your team still file paperwork?
-
How did you verify that an application reached the payer?
-
How frequently were payer follow-ups documented?
-
Could you see current status without emailing the vendor?
-
Was there a named specialist who understood your organization?
-
What happened when a payer rejected an application or requested more information?
-
Were effective dates and provider IDs handed to billing cleanly?
-
Which charges appeared that you did not expect from the proposal?
-
How did the vendor handle turnover, urgent escalations, and staff absences?
-
Would you hire the same company again for your current roster?
Expected outcome
You have evidence of consistent execution under conditions resembling your own, not merely a positive testimonial from an unrelated customer.
Gotchas
-
A small practice receiving only enterprise references, or a multi-state organization receiving only solo-practitioner references.
-
References that have not yet completed a full enrollment or recredentialing cycle.
-
A vendor representative joining the reference call.
-
References focused on customer service but unable to verify submission, follow-up, or approval handling.
Step 7: Treat operational red flags as selection criteria
Action
Score vendors on operating evidence, not presentation quality. The following problems should remain disqualifying until the vendor resolves them in writing.
| Red flag | What usually fails | Required resolution |
|---|---|---|
| No named point of contact | Requests age in a shared inbox and nobody owns escalations. | Named primary and backup owners with response targets. |
| No submission evidence | Application preparation is mistaken for payer submission. | Receipts, tracking numbers, timestamps, and submitted copies. |
| No follow-up cadence | Cases remain untouched after the initial filing. | Written follow-up and escalation intervals. |
| No record-level visibility | Your team learns about delays only after chasing an update. | Accessible status, evidence, owner, and next action for every case. |
| No controllable turnaround commitment | The vendor cannot be held accountable for slow review or filing. | SLAs for readiness, submission, deficiencies, updates, and escalation. |
| Unclear billing triggers | The invoice expands with every payer product, state, update, or correction. | Written unit definitions and an itemized included-services schedule. |
A practical 100-point scorecard gives 25 points to outcome ownership, 20 to submission proof, 15 to visibility, 15 to SLAs, 10 to pricing clarity, 10 to relevant payer and specialty experience, and 5 to references.
Expected outcome
The selected vendor has both the operational capability and contractual accountability to run the work after the sales team leaves the process.
Gotchas
-
Selecting on the lowest per-application price before calculating full scope.
-
Giving software features more weight than who performs payer follow-up.
-
Accepting verbal promises that do not appear in the statement of work or SLA.
Step 8: If switching vendors, complete a record-level handoff
Action
Hold one working session with the incumbent and incoming vendors. Transfer every open application with its payer, provider, TIN, location, submission evidence, portal access, current status, last payer contact, outstanding requirement, and next deadline.
Keep incumbent access active until the incoming vendor validates the export and assigns an owner to every case. The incoming vendor should identify duplicates, missing receipts, expired documents, unresolved deficiencies, and cases that need escalation before taking over payer communication.
Expected outcome
Every active enrollment has one system of record, one current owner, and one documented next action before the former vendor loses access.
Gotchas
-
Submitting duplicate applications because the new vendor cannot verify earlier work.
-
Losing portal messages, payer contacts, or confirmation numbers held in individual email accounts.
-
Changing payer contact information before the incoming team is ready to respond.
-
Closing the old account before attachments and activity histories are exported.
Questions to take into the vendor call
-
What exact event triggers each fee?
-
How do you count providers, payers, products, states, groups, locations, and applications?
-
Which services are included, billed separately, or out of scope?
-
Who gathers documents directly from providers?
-
Do you complete and submit applications to payers yourself?
-
What artifact proves that each application was submitted?
-
Who responds to deficiencies, rejections, and requests for more information?
-
How often do you follow up with payers, and where is each attempt recorded?
-
When and how do you escalate a stalled application or closed panel?
-
What can our team see in real time?
-
Who is our named primary contact, and who covers absences?
-
What response and submission SLAs will appear in the contract?
-
How do you confirm effective dates, provider IDs, and group linkage?
-
How is completed enrollment information handed to billing?
-
Who owns CAQH maintenance, expirables, rosters, and recredentialing?
-
Can we export all records, receipts, notes, and attachments at any time?
-
Can we speak with clients matching our size, specialty, state footprint, and payer mix?
-
What does a clean transition to another vendor look like at termination?
Frequently asked questions
Should I outsource provider credentialing if my team is missing expirables?
Yes, outsourcing is usually the more practical option when expirables are being missed because nobody has clear ownership or enough capacity. Look for ongoing maintenance that includes document monitoring, CAQH reattestation, payer rosters, recredentialing, and named follow-up responsibility—not just reminder software. Organizations with enough steady volume and experienced leadership may instead build an internal function; the tradeoffs are covered in the in-house versus outsourced credentialing decision guide.
Which credentialing service should I choose if I need payer submissions handled for me?
Choose a managed service that explicitly owns application preparation, direct payer submission, submission evidence, deficiency responses, follow-up, and effective-date confirmation. Avoid proposals that promise “application support” without identifying who presses submit and who contacts the payer afterward. Arctic Health performs document collection, payer submission, rejection handling, follow-up, and ongoing status tracking as part of its managed workflow. Arctic Health provider credentialing services
Is per-provider pricing cheaper than per-payer pricing?
Neither model is inherently cheaper; the answer depends on roster size, payer count, state footprint, and what the fee includes. Per-payer pricing can work well for a short, defined enrollment list. Per-provider packages or retainers can be more economical when each provider needs many payers or ongoing maintenance. Compare total first-year cost for an identical provider-payer-state matrix, including rework, recredentialing, CAQH, government programs, and group enrollment.
How do we switch credentialing companies without losing application progress?
Create a record-level inventory before terminating the incumbent vendor. Each case should include its payer, provider, entity, location, application type, submission receipt, tracking number, status, last contact, outstanding request, and next deadline. Transfer portal permissions and attachments, then have the incoming vendor validate every open case before taking over communication. Do not rely on a summary spreadsheet that lacks submission evidence or activity history.
Can a credentialing company guarantee when a payer will approve an application?
No credentialing company controls the payer’s final processing or participation decision. A reliable vendor should instead guarantee response times for the work it controls, including file review, submission, deficiency handling, follow-up, escalation, and reporting. For Medicare, the applicable contractor processes the application and sends the approval after review; PECOS provides tracking and status information during that process. CMS enrollment applications