Prior Authorization Turnaround Time: Deadlines, Clocks, and Escalation
Understand prior authorization turnaround time by separating payer deadlines, internal preparation, clinical need dates, pends, and overdue escalation.
On this page: Direct answer
Direct answer
Prior authorization turnaround time: what operators need to know
Understand prior authorization turnaround time by separating payer deadlines, internal preparation, clinical need dates, pends, and overdue escalation. Calculate deadlines from the applicable payer, product, service, and rule source. Track internal preparation time separately from payer decision time. Record when the payer says a request is received and whether it is considered complete.
There is no single prior authorization turnaround time. The answer depends on payer type, product, service, request completeness, standard versus expedited status, governing state or federal rule, contract, and the event used to start the clock.
Operations teams need more than one due date. They need a sourced payer deadline, an earlier internal work date, and the date by which a decision is needed to avoid disrupting care.
Key takeaways
The short version
- Calculate deadlines from the applicable payer, product, service, and rule source.
- Track internal preparation time separately from payer decision time.
- Record when the payer says a request is received and whether it is considered complete.
- Use clinical criteria, not convenience, to classify expedited requests.
- Escalate overdue cases through a defined path while preserving every contact and response.
Use four clocks for one request
Do not pause or restart a clock silently. If a payer requests information, record the request, its source wording, whether the governing rule treats it as a pend or new completeness event, the response time, and the revised deadline calculation.
| Clock | Starts | Stops |
|---|---|---|
| Preparation | Complete intake or accepted request | Packet ready for approved submission |
| Payer decision | Applicable payer receipt/completeness event | Decision or qualifying response |
| Internal service level | Team-defined trigger | Defined handoff or action |
| Care access | Referral, order, scheduling, or clinical need | Usable decision for care planning |
Apply CMS-0057-F timeframes precisely
CMS-0057-F established operational requirements beginning in 2026 for defined impacted payers. The final rule generally requires specified payers to send expedited decisions within 72 hours and standard decisions within seven calendar days, with category-specific scope and exceptions described by CMS.
Do not turn those numbers into a universal rule for every commercial plan, exchange product, drug request, or state program. Store the line of business and governing source on the case so the calculated due date is explainable.
Control the receipt and completeness events
A portal upload time is not always the same as the payer's recognized receipt or complete-request event. Reconcile differences early. When a payer rejects or cannot locate a submission, preserve the original proof and follow the approved resubmission or escalation process.
- Submission timestamp and channel
- Transmission or transaction acceptance
- Payer reference and payer-recorded received date
- Request type and urgency status
- Payer statement that information is missing or the request is pended
- Additional-information response and confirmation
- Original and recalculated due dates with rule source
Keep expedited classification clinically governed
Expedited review exists for circumstances defined by the applicable rule or plan, often involving serious risk from delay. Scheduling pressure, an approaching internal deadline, or late packet preparation does not automatically satisfy the standard.
Route the urgency question to the qualified clinician, capture the applicable criterion and rationale, follow the payer's certification process, and track a separate rapid internal handoff. If the payer reclassifies the request, preserve the notice and evaluate the response path.
Build an overdue escalation ladder
- 01
Verify
Confirm the source rule, request receipt, completeness, due-date math, and absence of a hidden portal response.
- 02
Contact
Use the payer's provider escalation channel and capture representative, reference, timestamp, and promised action.
- 03
Escalate internally
Notify operational and clinical owners of the access impact and interim plan.
- 04
Use available plan/program paths
Follow applicable supervisor, grievance, complaint, contracting, or regulator processes with authorized guidance.
- 05
Close the clock
Record the response, outcome, delay cause, and prevention or contracting follow-up.
Common questions
Answers before you build.
How long does prior authorization take?+
It varies by payer, product, service, urgency, completeness, and governing rule. Defined CMS-impacted payers have specific 2026 timeframes, but those are not universal.
When does the prior authorization clock start?+
The applicable rule or plan defines the event, which may involve payer receipt and completeness. Record the source and payer-confirmed timestamp.
Can every delayed request be marked expedited?+
No. Expedited status should follow the applicable clinical standard and payer process, with qualified clinician involvement.
What should happen when a payer misses the deadline?+
Verify the calculation and status, use the documented payer escalation route, communicate access impact internally, and evaluate available plan, program, contract, complaint, or regulatory paths.
Practical closeout
Use this operator checklist.
- Calculate deadlines from the applicable payer, product, service, and rule source.
- Track internal preparation time separately from payer decision time.
- Record when the payer says a request is received and whether it is considered complete.
- Use clinical criteria, not convenience, to classify expedited requests.
- Escalate overdue cases through a defined path while preserving every contact and response.
Continue through the cluster
Verified customer case studies are added only with customer permission and supporting evidence; none is implied by these operational examples.
Sources & methodology
Trace the operational claims.
Marsa Health Editorial reviewed the primary and research sources below on July 22, 2026. We translate them into workflow controls, distinguish proposals from final rules, and flag where plan, program, state, contract, or clinical requirements vary.
- 01CMS Interoperability and Prior Authorization Final Rule CMS-0057-F Centers for Medicare & Medicaid ServicesCurrent implementation dates, decision timeframes, denial-reason requirements, metrics, and API provisions for impacted payers.Accessed or rechecked July 22, 2026
- 02Electronic Prior Authorization Centers for Medicare & Medicaid ServicesCurrent CMS provider-readiness guidance for 2027 electronic prior authorization, EHR questions, FHIR testing, and workflow preparation.Accessed or rechecked July 22, 2026
- 03How to appeal an insurance company decision Centers for Medicare & Medicaid ServicesFederal overview of internal appeals, external review, notices, and general appeal timing. Plan and state rules can differ.Accessed or rechecked July 22, 2026
- 04Minimum Necessary Requirement U.S. Department of Health and Human ServicesHIPAA guidance on limiting uses, disclosures, and requests for protected health information when the standard applies.Accessed or rechecked July 22, 2026
Organizational author. Editorial review covers source accuracy, search intent, workflow boundaries, and human-oversight requirements. This material is educational and does not provide clinical, legal, coding, or coverage advice.
No named clinical or legal expert reviewer is attributed to this version. Marsa Health does not invent reviewer credentials.
Read our editorial methodRevision history
What changed and when
July 22, 2026
Initial publication, source review, and operational editing.