Managing Prior Authorizations Without Delaying Care

Published by
Throne of Profit Editorial

Reviewed by
William Hassell
Founder & Chief Editor, Throne of Profit

A provider orders a treatment, a referral, or an imaging study, and then it sits. The authorization request goes out — or worse, it doesn't go out for two days because nobody owns it — and the patient waits. Staff spend afternoons on hold, resubmitting forms that came back for a missing code, chasing a payer for a decision that should have taken a phone call. Meanwhile the patient calls the front desk asking why their procedure hasn't been scheduled. A prior authorization backlog isn't a paperwork problem; it's a delayed-care problem and a wasted-labor problem wearing a paperwork disguise.

The work itself is unavoidable — payers require it and that isn't changing. What is in your control is whether the request moves through your practice on a predictable track or gets lost between the person who ordered it and the person who submits it. The difference between those two states is a defined workflow.

   THE AUTHORIZATION PATH

   order placed
        │
        ├─ owned + submitted same day → tracked → approved → care proceeds
        ├─ sits unassigned / delayed  → forgotten → patient waits → chase
        └─ submitted incomplete       → denied → resubmit → weeks lost

Owner symptoms

  • Treatments, referrals, and imaging get scheduled late because the authorization wasn't ready.

  • Staff spend hours each week on hold or resubmitting requests that came back incomplete.

  • Patients call asking why their procedure is stuck, and no one can say where it stands.

Why this happens

Prior authorization falls into the gap between roles. The provider orders the service and moves on to the next patient; the front desk assumes clinical staff are handling it; billing assumes it was done before the visit. Because no single person clearly owns the request from order to decision, it stalls at the handoff. Add to that the fact that each payer wants different documentation, and a request submitted without the right codes or notes bounces back days later — restarting a clock that was already running against the patient. Without a tracked list and a clear owner, the whole thing runs on memory and good intentions.

Common mistakes

  • No single owner for the request, so it sits between roles until someone notices.

  • Submitting incomplete requests, which get denied and have to start over.

  • No tracking list, so a pending authorization is only remembered when the patient calls.

  • Scheduling before approval, then scrambling to cancel or delay when it doesn't clear.

  • Ignoring denials instead of appealing, leaving approvable care unapproved.

Business consequences

Every stalled authorization is a delayed treatment for a patient and idle capacity for the practice — a scheduled slot that could have been filled, a referral that erodes the relationship with the ordering provider. The labor cost compounds it: staff time spent on hold and on rework is time not spent on patients who are in the building. Denials that should have been clean approvals turn into multi-week appeals. The practice that runs authorizations on a tracked, owned workflow gets patients into care faster, wastes far less staff time, and stops losing revenue to slots that sat empty waiting on a form.

This is general business information, not medical/clinical or professional advice. Consult a qualified professional for your situation.

How experienced operators think about it

They treat prior authorization as a pipeline to be managed, not a task to be remembered. The mental shift is from "someone will handle it" to "every request has an owner, a status, and a next action." They know the two levers that matter are speed at the start — submit the same day, complete the first time — and visibility throughout, so nothing goes dark. They also accept that denials are part of the process, not a dead end, and build appeals into the workflow rather than treating a denial as the final word. The goal isn't heroics; it's a boring, reliable track that keeps care moving.

Practical actions

  1. Assign clear ownership. One role owns each request from the moment it's ordered until a decision comes back — no ambiguous handoffs.

  2. Submit same-day and complete. Build a per-payer checklist of required codes and documentation so the first submission is the clean one.

  3. Keep a live tracking list. Every pending request with its status and next action, visible to the team, so nothing depends on memory.

  4. Don't schedule against an unapproved request unless you've decided to accept the risk — and flag it clearly when you do.

  5. Build appeals into the routine. Treat denials as a step, not an ending; assign and track them like any other open request.

Questions every owner should ask

  • If I asked right now, could someone tell me the status of every pending authorization?

  • How many of our denials come from incomplete first submissions we could have prevented?

  • How often does a scheduling delay trace back to an authorization nobody owned?

Frequently asked questions

How much of this can we control when payers are the ones causing delays?
More than it feels like. You can't change what a payer requires or how fast it decides, but those aren't usually where the biggest delays live. The controllable losses are internal: the days a request sits before anyone submits it, the denials caused by missing documentation, and the pending requests nobody is tracking. Tighten those and a large share of the delay disappears, even though the payer never changed a thing.

Should one person handle all authorizations, or should it be spread across the team?
Either can work; what matters is that each individual request has a clear owner, not that one person owns all of them. Small practices often centralize it with one coordinator for visibility; larger ones distribute it by service line or provider. The failure mode to avoid is diffuse responsibility — where it's "the team's" job and therefore no one's. Pick a structure, make ownership explicit per request, and keep the tracking list shared.

Related articles

Every business has more decisions than time

Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.

Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.

Explore Throne of Profit

Previous
Previous

Building a Recall System That Fills Its Own Schedule

Next
Next

Which Insurance Contracts Actually Pay You