Prior Authorization Turnaround Time: Deadlines and Workflow Delays
Separate payer decision deadlines from internal workflow delays. Understand the scope of CMS-0057-F and build an auditable prior authorization work queue.
There is no single turnaround number that should be assigned to every prior authorization. Start by separating the payer's applicable decision deadline from the time your team spends identifying requirements, preparing a request, and acting on the response.
This guide offers a workflow measurement method. It does not claim a national average, predict an individual decision, or promise that automation will secure approval.
What CMS-0057-F changes—and what it does not
CMS-0057-F generally begins its decision-timeframe requirements in 2026 for affected Medicare Advantage, Medicaid, and CHIP payers: seven calendar days for standard requests and 72 hours for expedited requests. Those timeframe requirements exclude QHP issuers on the federally facilitated exchanges. The rule's prior-authorization provisions exclude drugs. API requirements generally begin in 2027; they are not a promise that every plan offers the same interface today. CMS final-rule fact sheet.
Check the product, service, urgency, controlling policy, and any applicable exceptions or extensions. Do not apply the rule's general timeframe to every commercial plan or medication request. A decision deadline is not a guarantee of approval, and an approval is not a guarantee of claim payment.
Measure the handoffs, not just the final result
Use a small event log so staff can distinguish an internal delay from a pending payer decision. The following is a proposed operational record, not a statement of required fields under the CMS rule.
| Event | Evidence to retain | Question it answers |
|---|---|---|
| Requirement checked | Plan, service, source, and check time | Did we use the right requirements? |
| Packet ready | Reviewer, attachments, and unresolved gaps | Is preparation complete? |
| Request transmitted | Channel, time, and submission reference | What did we send? |
| Payer receipt confirmed | Acknowledgment and payer reference | Did the payer receive it? |
| Follow-up requested | Requested information, owner, and due date | What action is needed now? |
| Decision received | Decision, scope, dates, and next action | What must scheduling or clinical staff review? |
Keep the original timestamps when a request is corrected. Do not assume that sending more information restarts a legal decision clock; record the payer's instructions and escalate uncertainty to the responsible team.
Check seven potential sources of delay
- Requirement identification. Confirm the actual member plan and intended service. Keep the policy reference with the task so another staff member can repeat the check.
- Documentation preparation. Assign an owner for missing information. Route clinical interpretation and any proposed medical-necessity text to an appropriately qualified reviewer; do not invent facts to complete a packet.
- Submission. Confirm the permitted channel and save acknowledgment evidence. A successful upload to an internal tool is not necessarily payer receipt.
- Payer follow-up. Track the applicable response deadline independently from your internal service target. Escalate using the plan's published process.
- Additional information. Record exactly what was requested and who will respond. Link each response to its request rather than replacing the original history.
- Internal routing. Give each unresolved task one accountable owner and a backup. Make a missed internal target visible before a scheduled service is affected.
- Decision handoff. Ensure the responsible staff review the authorized service, dates, units, and any limitations before updating downstream work.
These checks identify where to investigate. They do not establish how often each delay occurs or how many days a particular intervention will save.
Evaluate automation against the same record
In a pilot, ask a tool to demonstrate requirement lookup, packet preparation, submission evidence, exception routing, and decision handoff for the plans actually in scope. Test an unavailable interface and an incomplete request as well as a successful case.
Compare the same event definitions before and during the pilot. Report incomplete and withdrawn requests separately, preserve the denominator, and distinguish staff handling time from elapsed time. Treat any modeled improvement as an estimate until the corresponding outcomes are observed.
The prior verification guide covers the relationship between eligibility and authorization. The payer directory provides starting references; use its source limitations and verify the current plan-specific policy before relying on a deadline.
Public-reference check: September 6, 2026. This article is operational education, not clinical advice, a legal interpretation for an individual plan, or evidence of a QuickIntell customer result.