Prior Authorization Workflow: 4 Handoffs That Cause Denials and Delays
Many RCM directors have heard some version of this argument: prior authorization is just paperwork, and the teams that struggle with it simply need to get better at paperwork. It's a reasonable objection. The steps seem straightforward enough, clinical criteria are well-defined, and payers publish their requirements. So why do denials, delays, and write-offs keep piling up?
The honest answer is that the prior auth process is not primarily a paperwork problem. It's a handoff problem. The work moves across at least four distinct roles, often across different systems, and the gaps between those roles are where most failures occur. What follows is a step-by-step account of who owns each stage, what tends to go wrong at each transition, and what well-run teams do differently.
Step 1: The Scheduling Team Determines Whether Auth Is Required
The process begins before any clinical work happens, when a patient is scheduled for a service. The scheduling team is responsible for identifying whether prior authorization is required, and this determination depends on the patient's specific plan, not just the payer. The same insurer may require auth on a procedure for one plan tier and waive it entirely for another.
This is where the first structural failure tends to happen. If the scheduling team is working from a static payer list, or relying on memory, they will miss edge cases. CAQH data has consistently shown that a large share of prior auth transactions still involve manual phone-based inquiry, which creates delays at exactly this stage, when catching a requirement early would cost almost nothing (CAQH, 2024).
The practical fix is straightforward but requires investment: the scheduling team needs access to a benefits verification workflow that can return plan-level auth requirements in real time, not just payer-level rules. Without that, errors compound downstream.
Step 2: Clinical Staff Compile and Submit the Request
Once the requirement is confirmed, clinical documentation enters the picture, and ownership shifts to the clinical or care coordination team. They are responsible for pulling the relevant records, applying the payer's medical necessity criteria, and submitting the request with the right supporting documentation.
This step is where the volume problem becomes acute. According to the American Medical Association's prior authorization physician survey, physicians and their staff reported spending well over ten hours per week on prior authorization tasks, with the most recent survey data indicating the burden has continued to grow (AMA, 2024). Most of that time is not spent on clinical judgment. It is spent locating documents, reformatting information to match payer templates, and waiting for payer systems to respond.
The handoff failure here is between the EHR and the submission channel. Clinical staff frequently have to re-enter information that already exists in the patient record, because the payer's portal or fax system does not connect to the EHR in a meaningful way. Electronic prior authorization (ePA) standards are designed to close this gap. CMS has been advancing interoperability requirements that would mandate payers to support electronic PA transactions, with ongoing HHS-led efforts to accelerate adoption among major health plans (CMS, 2025).
Step 3: AR or Auth Teams Track Status and Follow Up
Once a request is submitted, tracking responsibility typically shifts to the authorization or AR team. This is the stage that receives the least structural attention and generates the most waste.
Payer timelines vary. CAQH CORE has established guidelines encouraging faster prior authorization turnaround, with standards intended to set a new industry benchmark for response windows, though these are not universally enforced across all entities (CAQH, 2024). In practice, many requests sit longer than those guidelines suggest, and without a systematic follow-up queue, requests expire, services proceed without coverage confirmation, or denials arrive after care has already been delivered.
The workflow failure here is a monitoring gap. Many teams track initial submission but do not maintain a structured follow-up cadence keyed to each payer's typical response window. When a request goes quiet, it is often assumed to be pending rather than lost. A working system assigns explicit follow-up triggers: if no response arrives within a defined window, the request surfaces in a work queue automatically.
Step 4: The Billing Team Validates Auth Before Claim Submission
Even after authorization is granted, there is one more handoff that frequently fails: confirming that the authorized service matches what was actually delivered before the claim goes out.
This step belongs to the billing team, and it is often skipped under volume pressure. When auth numbers are entered manually, they are sometimes transposed or applied to the wrong service line. When authorized dates or units differ from what was documented, payers deny the claim on technical grounds, and the revenue cycle restarts from a much worse position.
KFF research has noted that patients and providers alike struggle with the opacity of payer criteria, which is compounded on the billing side when authorization records are stored inconsistently or not linked to the corresponding claim (KFF, 2024). Integrating auth confirmation into the billing workflow, as a required step before claim release rather than a post-submission check, catches a meaningful share of these errors before they become denials.
Who This Workflow Design Does Not Fit
The step-by-step structure described here assumes a team large enough to have distinct scheduling, clinical, AR, and billing functions. For a solo practitioner's office with two or three staff members covering all of those roles simultaneously, the handoff model is less relevant because there are no handoffs. Those practices tend to have a different problem: concentration of knowledge in one or two people, with no redundancy when those people are unavailable.
Similarly, practices with a narrow payer mix and a small set of recurring procedures, certain single-specialty clinics, for instance, may find that a simplified checklist approach serves them adequately. When the same five CPT codes flow through the same three payers every week, the cognitive load is low enough that a rigid workflow structure adds overhead without adding value.
The teams that benefit most from redesigning this workflow around handoffs are mid-size billing companies and provider groups managing broad payer contracts, high procedure variety, or significant claim volumes. For those operations, the handoff is not a detail. It is where the money is lost.
Sources
- CAQH. "2024 CAQH Index." 2024. https://www.caqh.org/insights/caqh-index
- CMS. "Electronic Prior Authorization." Updated 2025. https://www.cms.gov/priorities/electronic-prior-authorization/overview
- KFF. "Insurers' Prior Authorization Data Offers Little Insight Into What Gets Approved or Denied." 2024. https://www.kff.org/quick-insights/insurers-prior-authorization-data-offers-little-insight-into-what-gets-approved-or-denied
- American Medical Association. "AMA Prior Authorization Physician Survey." 2024. https://www.ama-assn.org/practice-management/prior-authorization/prior-authorization-survey
Run a pilot on a real workflow.
Bring a representative batch, define the output schema, and validate ROI with your payer mix in 30 to 90 days.

