What is a preventable denial?

A denial the practice could have avoided with information it already had — documentation that existed in the chart but was not attached, a code that did not match the payer's policy, or a plan that had changed. Preventable denials should be tracked as a distinct rate, because they are the ones automation and template discipline actually fix.

How do you reduce prior authorization denials?

Assemble documentation against the payer's published criteria rather than a generic template, validate eligibility and coding before submission, submit within the required window, and triage every denial by reason code so recurring defects get fixed once instead of appealed repeatedly.

Should we appeal every denial?

No. Appeal genuine medical-necessity disagreements, and correct-and-resubmit administrative denials, which is usually faster. Appealing a documentation defect spends clinical time on a problem a complete packet would have avoided.

How do denials affect referral leakage?

Each denial adds days to the timeline, and abandonment rises with every day a patient waits. A denied-then-approved referral often still ends in no visit, so the denial rate belongs in the same report as keepage and time-to-appointment.

What denial metrics should we report?

Four: overall denial rate, preventable denial share, denial rate by reason code and payer, and turnaround impact — how many extra days a denied request adds before determination. Report by payer and specialty, because denial patterns are payer-specific.

Get a Demo

Guide

Reducing Prior Authorization Denials

Which denials are process defects rather than clinical disagreements, what the rework actually costs, how to prevent the preventable categories at submission, and when to appeal instead of resubmitting.

The five preventable denial categoriesMost denials are defects, not disagreements

01Documentation
The note existed in the chart but was never attached. The most common single defect.
02Coding
CPT or diagnosis pairing that does not match the payer's published criteria for the request.
03Eligibility
Plan changed, coverage lapsed, or the wrong member ID was submitted.
04Timing + provider data
Submitted after the window, or against a stale NPI, TIN, or site of service.

~70%

of denials fall into categories a process change can prevent

2×

staff time consumed by every request that has to be reworked

+Days

added to turnaround — which is what drives abandonment

Track preventable denials as their own rate. That is the number a process change can actually move.

Short answer

Why do prior authorization requests get denied?

Most prior authorization denials are administrative rather than clinical: missing documentation, the wrong code or site of service, an eligibility or plan mismatch, a late submission, or a request sent to the wrong payer entity. Those categories are preventable at submission. Reducing the denial rate means fixing them at the source and reserving appeals for genuine medical-necessity disagreements.

Key takeaways

Track preventable denials as their own rate — that is the number a process change can move.
Documentation that exists in the chart but was not attached is the most common single defect.
Correct-and-resubmit is usually faster than appealing an administrative denial.
Denial rework inflates turnaround, and every extra day raises referral abandonment.
Report denial rate by reason code and payer; patterns are payer-specific and contract-relevant.

Why prior authorization requests actually get denied

Denials fall into two very different buckets, and conflating them is why denial rates stay flat. The first bucket is process defects: something about the submission was incomplete, mismatched, or late. The second is a genuine disagreement about whether the service meets the plan's medical-necessity criteria.

The first bucket is far larger in most practices, and it responds to workflow change. The second responds only to clinical argumentation. A program that treats every denial as an appeal spends specialist time on paperwork problems.

The five preventable denial categories

Documentation gaps. The payer's criteria required evidence of prior conservative treatment, a specific diagnostic, or a recent note, and it was not attached even though it existed.
Coding and site-of-service mismatches. The submitted code does not match the payer's policy for that service, or the requested setting is not covered.
Eligibility and plan mismatches. The patient's plan changed, the product differs from what was assumed, or the request went to the wrong payer entity.
Timing defects. The request arrived after the required window, or after the service was already scheduled or delivered.
Provider data defects. The rendering provider's network status, NPI, or location on the request does not match the payer's record.

Each of these is knowable before submission, which is exactly why automated documentation assembly and validation moves the denial rate rather than merely moving the work.

Ranked causes

Denials are a documentation problem with five names

Ninety percent of preventable denials fall into the five categories below. Each is paired with the control that removes it at the source.

Denial Reasons — and the Control That Prevents Each OneTrailing 12 months

Missing or incomplete clinical documentation34%
Auto-assemble the payor's required fields from the chart
Medical necessity criteria not evidenced23%
Check policy criteria before submission, not after
Authorization not obtained / expired18%
Trigger auth at referral creation and watch the expiry
Wrong site of care or wrong code14%
Validate CPT and site against the plan's policy
Eligibility or coverage lapse11%
Re-verify eligibility the morning of the visit

Rank your own denials this way before building controls — the order of the list decides where the first month of work goes.

What denial rework costs, on a worked example

Authorization requests per year12,000

Illustrative volume. Start from your own submission counts by payer.

Approved first pass9,000 · 75%

Cleared with no additional-information cycle and no resubmission.

Denied or returned for information3,000 · 25%

Each one restarts the clock and consumes staff time twice.

Preventable share of those denials2,100 · 70%

Documentation, coding, eligibility, timing, and provider-data defects.

Recoverable staff hours at 25 minutes of rework each≈875 hours

Multiply by loaded hourly cost, then add the abandonment cost of the added delay.

The volumes above are illustrative arithmetic, not a customer result. Verified customer outcomes are sourced on the facts page.

Where 12,000 authorization requests actually end up

The same illustrative volume, followed forward. Each bar is the share of the original 12,000 still on track to become a completed appointment.

Requests submitted in a year12,000

Denied or returned for more information−3,000

75% left

9,000 clear on the first pass. Every denial restarts the determination clock and consumes staff time a second time.

Abandoned by the patient during the added wait−600

70% left

Full administrative cost incurred, no visit, no revenue, no closed care gap.

Upheld on appeal or never resubmitted−300

67.5% left

Genuine criteria disagreements plus requests that simply fell out of the queue.

2,100 of the 3,000 denials were reworked and approved — recovered volume at full duplicate labor cost, which is why the labor line moves even when the approval rate looks healthy. Illustrative arithmetic, not a customer result. Verified customer outcomes are sourced on the facts page.

Modeling the true cost of a denial

A denial costs three things: the staff minutes to diagnose and rework it, the additional calendar days before a determination, and the share of patients who abandon the referral during those extra days. Practices usually model only the first.

The third is the expensive one. A referral that is eventually approved but never scheduled consumed full administrative cost and produced no visit, no revenue, and no closed care gap. That is why denial reduction shows up in leakage and abandonment reporting.

Preventing denials at submission

Build the packet against the payer's criteria, not a generic internal template.
Validate eligibility and plan at the moment of order, not at submission.
Check code and site of service against that payer's policy before sending.
Confirm rendering-provider data — NPI, location, network status — matches the payer's record.
Submit inside the required window, triggered by the order rather than by a coordinator remembering.
Feed reason codes back into the templates, so each recurring defect is fixed once.

Appeal or correct and resubmit?

Decide by denial reason, not by dollar value. If the reason code names a documentation, coding, eligibility, timing, or provider-data defect, correct and resubmit — it is usually faster and does not consume clinical time.

If the payer applied its criteria to a complete packet and reached a different clinical conclusion, appeal, and escalate to peer-to-peer review where the plan offers it. Track both paths separately: a program that cannot distinguish them cannot tell whether its denial rate is a paperwork problem or a policy problem.

The four denial metrics to report

Denial rate — share of submissions denied or returned for additional information.
Preventable denial share — the portion attributable to process defects.
Denial rate by reason code and payer — where the fixes and the contract conversations live.
Turnaround impact — extra calendar days added by the denial cycle.

Report these next to keepage and time-to-appointment from the referral management guide, so authorization performance is visible as a patient-access measure rather than a back-office one.

Prevention in the workflow

Where a denial is actually prevented

Appeals recover revenue after the fact and cost labour twice. Pre-submission checks prevent the denial from ever being issued.

Deny, then appeal

1
Request submitted without checking policy criteria
7 min
2
Denial returned 4–11 days later
delay
3
Coordinator rebuilds the packet for the appeal
26 min
4
Appeal filed; patient rescheduled
2nd delay

Check, then submit

1
Payor policy criteria evaluated at order entry
0 min
2
Missing evidence flagged while the chart is open
3 min
3
Request submitted complete on the first pass
0 min
4
Approval recorded; appointment held
same day

The right-hand column is the same request with criteria evaluated before submission rather than after the denial arrives.

Running the program

The exception queue a denial-prevention program produces

When criteria are checked up front, staff only see the requests that genuinely need a human — the rest never surface.

Prior Authorization WorklistTouchless rate: 71%

Patient	Request	Payor	Rule applied	Status
James T.	Orthopedics — MRI knee	Aetna	Conservative therapy documented	Auto-approved
Maria G.	Cardiology — stress echo	BCBS	Clinical criteria met	Submitted
Linda R.	Neurology — EEG	UHC	Missing prior imaging	Needs 1 document
David M.	Oncology — PET/CT	Humana	Site-of-care policy	Peer review queued
Ruth A.	GI — colonoscopy	Medicare	No auth required	Exempt

Median decision time

5h 20m

was 3.4 days

Requests never touched by staff

71%

auto-assembled and filed

First-pass approval

94%

criteria checked before submit

Two of the five rows below need attention. The other three were resolved by rule.

FAQ

Frequently Asked Questions

In practice, five causes dominate: incomplete or non-matching clinical documentation, coding or site-of-service errors, eligibility and plan mismatches, submission after the required window, and medical-necessity criteria that genuinely were not met. Only the last is a clinical disagreement; the rest are process defects that can be removed at submission.

Keep reading

Prior authorization guide

The full workflow, cost model, metrics, and regulatory picture.

Read

Automation mechanics

How automated submission removes the defects that cause most denials.

Read

Referral leakage

How authorization delay turns into abandoned referrals and lost volume.

Read

Ready to Get Started?

Cut the denials you can prevent

We analyze your denial reason codes by payer and show which categories a workflow change removes.

Schedule Personalized Demo