Skip to content
Definition

What Is Prior Authorization, and Why Do Claims Get Delayed?

Prior authorization is one of the biggest sources of delayed care and avoidable denials in the revenue cycle. Here is what it is, how the workflow runs, and where it breaks down.

Explore Prior Authorization SupportDiscuss Your Auth Volume
Salt HealthOps RCM TeamReviewed by Nilesh B GadekarPublished
Quick answer

What is prior authorization?

Prior authorization (also called prior auth, pre-authorization, or pre-certification) is a requirement that a provider obtain a payer's approval before delivering certain services, procedures, medications, or imaging. Without an approved authorization on file, the payer can deny the claim — so prior auth is both a clinical gate that can delay care and a frequent, preventable cause of claim denials.

Prior authorization, pre-certification, referral: the terms

These terms get used interchangeably but mean slightly different things. Knowing which one a payer requires for a given service avoids submitting the wrong request and losing days.

CriteriaTermWhat it means
Prior authorizationPayer approval required before a specific service or item is provided.
Pre-certificationConfirmation that a service (often inpatient) is medically necessary and covered.
ReferralA primary care provider's authorization to see a specialist, required by some plans.
NotificationInforming the payer a service occurred, without a formal approval step.

Why prior authorization causes so many delays

Prior auth is administratively heavy and time-sensitive, which is why it stalls so often. Each request is a small project with its own payer rules, documentation, and turnaround window.

  • Requirements vary by payer, plan, and service, and change frequently
  • Each request needs the right clinical documentation attached
  • Turnaround can take days, and care is often blocked until approval
  • Staff lose hours on payer phone queues and portal status checks
  • Authorizations expire, so even approved auths lapse if the service is delayed

The prior authorization workflow, step by step

A clean prior auth process is a disciplined sequence. Skipping or rushing a step is usually what produces a missing-auth denial later.

  1. 01

    Check the requirement

    Confirm whether the specific service and plan require authorization before scheduling.

  2. 02

    Gather documentation

    Assemble the clinical notes and codes the payer needs to support medical necessity.

  3. 03

    Submit the request

    Send the request through the payer's portal, fax, or phone per its rules.

  4. 04

    Track status

    Follow up until a decision lands, rather than assuming silence means approval.

  5. 05

    Record the approval

    Capture the auth number and validity dates in the system so the claim can reference it.

  6. 06

    Monitor expiry

    Flag authorizations before they lapse so rescheduled care does not lose coverage.

Where prior authorization breaks down

Most auth-related denials trace back to a handful of failure points. Each one is preventable with tracking and a consistent process.

Requirement missed

The service needed an auth and none was requested, because the requirement was not checked up front.

Incomplete documentation

The request was submitted without the clinical detail the payer needs, triggering a delay or denial.

No status follow-up

The request sat in the payer's queue and care proceeded before approval came through.

Expired authorization

An approved auth lapsed before the rescheduled service, so the claim was denied for no valid auth.

Wrong codes or units

The service billed did not match what was authorized, creating a mismatch denial.

How to reduce prior-auth denials

Prior auth is a front-end control: the cheapest place to prevent a denial is before the service, not in the appeals queue afterward. A few habits do most of the work.

  • Verify auth requirements at scheduling, alongside eligibility
  • Use a documentation checklist per payer and service type
  • Track every pending auth by status and age until it is resolved
  • Flag expirations early so rescheduled care stays covered
  • Match billed codes and units to exactly what was authorized

KPIs worth tracking for prior authorization

If you cannot measure the auth process, you cannot see it slipping. These metrics surface problems before they become denials.

Auth turnaround

Time from request to payer decision, trended over time.

Pending auths by age

Open authorizations grouped by status and how long they have sat.

Expiry flags

Authorizations caught before they lapse to prevent denials.

Auth-related denials

Share of denials tied to missing, expired, or mismatched auth.

How Salt HealthOps supports prior authorization

Salt HealthOps runs prior auth as a co-managed workflow: checking payer requirements, preparing and submitting requests, tracking documentation and status, and monitoring expirations — inside your systems, under US-based accountability, with QA review and reporting. We handle the administrative work and escalate anything needing clinical judgment to your team. We do not make clinical decisions.

Go deeper

Prior Authorization SupportCommon claim denial reasonsEligibility & Benefits VerificationWhat is RCM back-office support?

Frequently asked questions

Why do payers require prior authorization?

Payers use prior authorization to confirm that a service is medically necessary and covered before it is delivered, which lets them manage utilization and cost. For providers it acts as a gate: without an approved authorization on file, the payer can deny the claim even if the care was appropriate.

What happens if a service is provided without prior authorization?

If the payer required authorization and none was obtained, the claim is typically denied for no valid auth. Some payers allow a retro-authorization or appeal in limited circumstances, but recovery is not guaranteed, so the cost often falls on the practice or the patient. Prevention up front is far more reliable.

How long does prior authorization take?

It varies widely by payer, service, and urgency — from same-day for some electronic requests to several business days for others. Because turnaround is unpredictable and care is often blocked until approval, consistent status follow-up is essential to avoid both care delays and missed-auth denials.

Can outsourcing prior authorization reduce denials?

It often helps, because many auth denials come from missed requirements, incomplete documentation, lapsed approvals, or no follow-up — all administrative gaps. A co-managed team that checks requirements, submits complete requests, tracks status, and monitors expirations closes those gaps. We baseline and report auth-related denials rather than promising a specific reduction.

Next step

Drowning in prior auth?

Tell us about your auth volume and specialties. We will recommend a co-managed setup that moves authorizations faster and prevents auth-related denials.

Explore Prior Authorization SupportDiscuss Your Auth Volume