Health plans, pharmacists, and even some denial letters use "prior authorization" and "formulary exception" almost interchangeably, which is part of why so much confusion exists about them. They're not interchangeable. They apply to different starting situations, get reviewed through different processes, and — this is the part that trips people up most — don't always follow the timeline you'd assume.
The One-Sentence Distinction
If your drug is on your plan's formulary but needs clinical sign-off first, that's prior authorization. If your drug isn't on the formulary at all, that's a formulary exception. Everything else in this guide is detail on top of that one distinction, but it's the distinction that determines which form you should actually be filling out.
| Question to Ask | If Yes |
|---|---|
| Is the drug listed on your plan's formulary at any tier? | Prior authorization is likely the right request |
| Is the drug absent from the formulary entirely? | Formulary exception is the right request |
| Is the drug on the formulary, but on an expensive tier? | Tiering exception is the right request |
| Does your plan's benefit document exclude this category of drug entirely? | Neither request will typically work — see below |
Prior Authorization: What It Actually Asks
Prior authorization is a utilization management tool. Your plan has already decided to cover the drug — it's sitting on the formulary — but it wants proof, before paying, that you meet specific clinical criteria the plan has set. Those criteria vary by drug and by plan, but commonly include a specific diagnosis, lab values or other objective measures, documentation that a preferred, cheaper alternative was tried first (step therapy), or age and dosing parameters that match the drug's approved or plan-recognized use.
The underlying question a PA reviewer is answering is narrow: does this patient meet the criteria this plan has already established for this drug? It's a yes/no clinical checklist question, not an argument about whether the plan should cover the drug category at all.
Formulary Exception: What It Actually Asks
A formulary exception starts from a different place entirely. The plan has decided not to include this specific drug on its formulary — usually because it prefers a different drug in the same category — and you're asking it to make an exception to that decision for you specifically.
The question a formulary exception reviewer is answering is broader and more specific to you as an individual: why won't the formulary alternative work for this particular patient? That's a meaningfully harder question to answer well. The plan already knows a covered alternative exists; a request that doesn't address that alternative directly tends to fail.
Why this distinction gets lost in practice: both processes often use similarly named forms — sometimes literally the same "coverage determination request form" on Medicare Part D — and both eventually route to something an insurer calls a "prior authorization team" internally. The paperwork can look identical at a glance while asking for two structurally different justifications.
Tiering Exception: The Third, Often-Confused Request
A tiering exception gets bundled into "formulary exception" conversations constantly, but it solves a different problem. Your drug is already covered — it's on the formulary — but it sits on an expensive, non-preferred cost-sharing tier, and you're asking the plan to charge you the rate of a cheaper tier instead.
| Request | Starting Situation | What a Win Changes |
|---|---|---|
| Prior authorization | Drug is covered, criteria not yet met | Approval to fill at existing cost-sharing |
| Formulary exception | Drug is not covered at all | Coverage added, usually at non-preferred cost-sharing |
| Tiering exception | Drug is covered, but on an expensive tier | Cost-sharing reduced to a lower tier's rate |
Two limits are worth knowing before requesting one. Tiering exceptions generally aren't available for drugs placed on a specialty tier — the highest-cost tier plans use for expensive biologics and similar drugs. And under Medicare Part D rules specifically, a brand-name drug generally can't be granted the exact cost-sharing that applies to a generic on a lower tier, even with an approved tiering exception — you're moving down a tier, not being treated as though you're taking the generic itself.
Why the Timelines Aren't What Most Articles Say
This is the section most competing explainers either skip or get wrong, usually by citing a single federal timeline as if it applied uniformly everywhere. It doesn't, and the details matter enough to walk through carefully.
The 2026 rule everyone's citing doesn't cover drugs yet
The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) took effect for many provisions on January 1, 2026, and set a 7-calendar-day standard and 72-hour expedited decision timeline for Medicare Advantage plans, Medicaid managed care plans, CHIP managed care entities, and ACA marketplace Qualified Health Plans sold on the federally-facilitated exchanges. This is a genuinely significant rule, and it's the one most 2026 articles reference when discussing prior authorization timelines.
Here's the detail that gets dropped: this rule's faster-decision provisions apply to non-drug items and services — procedures, durable medical equipment, and similar requests — not to prescription drug prior authorizations. A separate proposed rule (CMS-0062-P), specifically aimed at extending similar interoperability and timeline requirements to drug-related prior authorization requests, was still in the public comment period as of mid-2026, with an anticipated effective date no earlier than late 2027 if finalized. Until and unless that rule is finalized, prescription drug PA timelines for these plan types continue to be governed by a patchwork of state law and individual plan policy, not one federal standard.
Medicare Part D already had a faster, unified rule — for years
Separately from all of that, Medicare Part D has long operated under its own "coverage determination" process, which applies the same timeline to both routine prior authorization requests and formulary/tiering exceptions: 72 hours for a standard request, 24 hours for an expedited one, once your prescriber's supporting statement is received. This isn't new for 2026 — it predates the CMS-0057-F rule by years — and it means Part D doesn't have a separate, slower track for exceptions the way people often assume.
ACA-regulated commercial plans have their own exception-specific clock
Separately again, federal rules governing non-grandfathered health plans (45 CFR § 147.136) require a formulary exception process with similar fast timelines — generally 72 hours standard, 24 hours expedited — for most ACA-regulated commercial and marketplace plans. This regulation, focused specifically on formulary exceptions, doesn't set an equivalent universal timeline for ordinary prior authorization requests on these same plans, which instead follow state law or individual plan policy.
The upshot: depending on your specific plan type, a formulary exception request can legitimately be the faster of the two processes, not the slower one — the opposite of what most people assume when they hear "exception" and picture something exceptional and therefore slow.
Comparison by Plan Type
| Plan Type | Prior Authorization (Drugs) | Formulary/Tiering Exception |
|---|---|---|
| Medicare Part D | 72 hrs standard / 24 hrs expedited | 72 hrs standard / 24 hrs expedited (same rule) |
| Medicare Advantage (medical, non-drug) | 7 days standard / 72 hrs expedited (CMS-0057-F) | Not typically applicable — non-drug context |
| ACA marketplace / most non-grandfathered commercial | Varies by state/plan — no uniform federal drug PA timeline yet | 72 hrs standard / 24 hrs expedited (45 CFR 147.136) |
| Medicaid managed care | Varies by state; CMS-0057-F's faster clock applies to non-drug services | Handled via state PDL/PA process — no separate federal exception clock |
| Self-funded employer (ERISA) | Plan-specific; not uniformly bound by the above federal rules | Often similar in practice, but not federally mandated the same way |
What Documentation Each One Needs
Because the two requests answer different questions, the strongest supporting documentation for each looks different too.
Strong Prior Authorization Documentation
- Diagnosis matching the plan's approved-use criteria
- Relevant lab values, imaging, or objective measures the plan requires
- Evidence step therapy requirements were met, if applicable
- Dosing consistent with the plan's covered parameters
Strong Formulary Exception Documentation
- A specific, individualized reason the formulary alternative won't work — not general preference
- Documented intolerance, inadequate response, or adverse reaction to the alternative, if tried
- History of stability on the requested drug, if switching would disrupt established treatment
- For tiering exceptions specifically, a reason the tier-appropriate alternative isn't suitable
The One Denial Neither Can Fix
There's a third category of denial that both prior authorization and formulary exceptions run into and neither one can generally solve: a plan-level or benefit-level exclusion, where the plan's actual policy document excludes an entire category of treatment, regardless of which specific drug is prescribed.
This shows up most often for categories insurers treat as elective or lifestyle-adjacent by design — weight-management medications are the most visible current example, where some plans exclude the entire drug category rather than managing it through the formulary. When that's the situation, the denial gets evaluated as a contract question — does the plan document include this benefit at all — rather than a medical necessity question, and clinical documentation, however strong, generally doesn't change that outcome. Our deep dive on Wegovy formulary exceptions walks through a real, published case that illustrates exactly this distinction.
How to tell which situation you're in before filing anything: check your plan's Summary of Benefits and Coverage or full plan document, not just the drug formulary. A formulary might not even list a category if the underlying benefit doesn't exist on your plan at all — checking only the formulary can miss a plan-level exclusion entirely.
Decision Tree: Which Do You Need?
Does your plan cover this category of drug at all?
Check the plan document, not just the formulary
Is your specific drug on the formulary?
On formulary → prior authorization. Excluded → formulary exception
File the matching request
Address the plan's specific criteria or preferred alternative directly
Neither request will typically work
This is a benefit design question, not a clinical one
Look for a different covered pathway
A different indication, employer HR escalation, or self-pay comparison
Denied anyway?
File an internal appeal, then request external review if needed
What Happens After a Denial
Both prior authorization and formulary exception denials generally lead to the same next step: an internal appeal with your plan, and if that's denied too, an independent external review. On Medicare Part D, denials upheld internally are automatically forwarded to an independent review entity. On most commercial and ACA marketplace plans, external review is a formal right after internal appeals are exhausted, and a decision that overturns a denial is legally binding on the insurer — not a recommendation. What differs is timing: Part D's appeal timelines mirror its fast coverage-determination clock, while commercial appeal timelines are typically longer (often around 30 days standard, 72 hours for urgent situations) even when the original exception request moved quickly.
Real Examples
The general framework above plays out differently drug by drug, which is exactly why it's worth seeing it applied to specific, current situations rather than left abstract.
A formulary exclusion, fought successfully: our Vyvanse formulary exception guide covers a real, published external appeal case where a patient's Vyvanse exception denial — after the drug was dropped from formulary in favor of covered alternatives — was overturned once an independent reviewer evaluated the patient's documented treatment history against those specific alternatives.
A benefit-level exclusion, upheld on appeal: our Wegovy formulary exception guide covers the opposite outcome — a real 2026 case where a formulary exception was denied and upheld on external review specifically because the plan excluded the entire weight-management drug category, making it a contract question rather than a clinical one, regardless of how strong the patient's documented results were.
Reading both side by side is a genuinely useful exercise: the clinical facts in each case were arguably comparable, but the outcome depended entirely on which of the two structurally different situations — formulary exclusion versus benefit-level exclusion — each patient was actually in.
Common Mistakes
- □ Filing prior authorization paperwork for a drug that's actually excluded from the formulary entirely.
- □ Assuming a formulary exception is automatically slower than prior authorization — it often isn't.
- □ Citing the 2026 CMS prior authorization rule as if it already covers prescription drugs — it currently doesn't.
- □ Writing a formulary exception request that argues drug preference instead of addressing the specific covered alternative.
- □ Treating a benefit-level plan exclusion as if it's a formulary problem an exception can fix.
- □ Not requesting expedited review by name when a delay genuinely could cause harm.
Bottom Line
Prior authorization and formulary exceptions solve two different problems — one clears a covered drug through clinical criteria, the other asks a plan to cover something it doesn't normally cover — and confusing them costs real time. The federal timelines attached to each are more specific and, in places, more counterintuitive than most explainers suggest: the widely cited 2026 CMS rule doesn't yet touch drug prior authorizations at all, while Medicare Part D and ACA-regulated formulary exceptions have quietly operated on a fast 72-hour clock for years. Know which situation you're actually in before you file anything, and don't assume the exception route is the slow one.