Prior Authorization Process Flow Chart: A Visual Reference for Healthcare Staff

The prior authorization process has multiple paths depending on whether the request is standard, urgent, denied and appealed, or retroactive. This page provides four visual flow charts covering each path, plus a short explanation of what happens at each step. Designed as a desk reference for PA coordinators, billing staff, and operations leaders.

The prior authorization process has multiple paths depending on whether the request is standard, urgent, denied and appealed, or retroactive. This page provides four visual flow charts covering each path, plus a short explanation of what happens at each step. Designed as a desk reference for PA coordinators, billing staff, and operations leaders. Screenshot any diagram for printing or training use.

How do the four prior authorization pathways compare at a glance?

A quick summary across pathway, timeline, when to use, and decision logic before the detailed flowcharts.

What does the standard prior authorization process flow look like?

Most PA submissions follow the standard pathway. Order placed, documentation gathered, submission made, decision returned, service scheduled.

Step-by-step explanation:

1. Order placed. Provider orders the service. Coordinator captures the order.
2. Payer policy check. Coordinator confirms PA is required for this CPT under the patient's specific plan.
3. Eligibility verification. Real-time eligibility check confirms active coverage.
4. Documentation gathering. Coordinator pulls clinical notes, imaging, lab results, and prior treatment history required by the payer's medical necessity criteria.
5. Submission. PA submitted through payer's preferred channel (portal, API, or fax).
6. Status tracking. Coordinator monitors payer system for decision.
7. Decision. Payer returns approval, denial, or pend (request for additional information).
8. Service scheduling. Approved PAs allow scheduling. Denied PAs route to appeal workflow.

Standard turnaround under CMS-0057-F is 7 calendar days maximum for impacted payers starting in 2026.

How does the urgent (expedited) prior authorization process flow work?

When delay could jeopardize the patient's life, health, or ability to regain function, the expedited pathway applies. Faster timelines, same decision logic.

Step-by-step explanation:

1. Urgency identified. Provider clinically determines that delay would jeopardize patient outcome.
2. Expedited flag. Coordinator marks the submission as expedited per payer protocol.
3. Fast documentation. Documentation must be assembled urgently. The clinical case for urgency itself becomes part of the medical necessity argument.
4. Submission. Same channel as standard but flagged urgent.
5. 72-hour decision window. Under CMS-0057-F, impacted payers must decide within 72 hours.
6. Decision handling. Approval enables immediate scheduling. Denial can be appealed on expedited timeline or addressed through P2P review.

The expedited pathway is underused. Many coordinators are not trained on when to invoke it, which leaves urgent cases stuck in standard queues.

What does the prior authorization appeal process flow look like?

When a PA is denied, the appeal pathway provides multiple recovery options. The right choice depends on the denial reason.

Step-by-step explanation:

1. Denial received. Payer returns denial with reason code under CMS-0057-F requirements.
2. Triage by reason. Different denial reasons route to different recovery paths. Resubmission is faster and cleaner than appeal when applicable.
3. Resubmit when correctable. Missing documentation, coding errors, and eligibility issues are correctable through resubmission, not appeal.
4. Appeal when medical necessity is the issue. Medical necessity denials require formal appeal with strong clinical documentation.
5. Peer-to-peer review. When appeals are denied, P2P review provides clinician-to-clinician dialogue with the payer's medical director. P2P approval rates run 50 to 70% for prepared physicians.
6. External review. When internal options are exhausted, external review provides an independent third-party decision. Rare in routine PA workflow.

Most denials get resolved at the resubmission or first-level appeal stage. P2P and external review are reserved for complex medical necessity disputes. For payer-by-payer denial pattern analysis, see the top reasons prior authorizations get denied.

How does retroactive (retro) authorization work?

When a service is provided before authorization is obtained (typically in emergency or urgent situations), retroactive authorization may be possible. Payer policies vary widely.

Step-by-step explanation:

1. Service provided. Service rendered before PA was obtained, typically due to clinical urgency or administrative oversight.
2. Retro auth check. Coordinator confirms whether the payer accepts retroactive authorization requests. Many do not.
3. Documentation. Clinical urgency or extenuating circumstances must be documented explicitly. The case for why PA was not obtained beforehand is part of the submission.
4. Submission. Retro auth submitted through payer's retro process (often different from standard PA workflow).
5. Decision. Approval allows normal claim submission. Denial means the practice absorbs the cost or bills the patient.

Retro authorization is operationally difficult to rely on. Most payers limit retro auth to clearly defined emergency or urgent care scenarios. Practices that bank on retro auth as a workflow shortcut typically lose money.

How does automation change each flowchart?

The four pathways change in specific ways when PA submission is automated.

Standard flow. Documentation gathering happens automatically from EHR. Submission goes electronic instead of fax or manual portal. Status tracking happens in the platform. Total cycle time drops from 7 to 14 days to 2 to 5 days.

Urgent flow. Coordinator identifies urgency. The rest (eligibility, documentation, submission) happens within minutes instead of hours. Total cycle time drops from 72 hours to often under 24 hours.

Appeal flow. Denial reason codes auto-parse and route to the right recovery path. Resubmissions happen automatically when the issue is correctable through documentation or coding. Appeals route to the right workflow based on denial reason.

Retro flow. Automation provides limited improvement here because the human judgment about whether retro auth is appropriate is the bottleneck. Documentation generation can still be automated.

Where PA automation works (and where it does not)

Best fit:

• Specialty practices with PA volume above 50 per week
• Multi-payer practices with high rule complexity
• Practices on MA-heavy or Medicaid-heavy panels
• Multi-site or PE-backed groups standardizing workflows

Less ideal fit:

• Practices with PA volume below 25 per week
• Practices on commercial PPO panels with minimal PA requirements
• Organizations without basic EHR integration capability

Frequently asked questions

For a printable cheat sheet covering payer-by-payer turnaround norms and the most common denial codes, see the prior authorization cheat sheet.