Case · Published Aug 22, 2026 · Updated Sep 2026

13 Hours to 3: A Prior Auth Turnaround, With the Numbers

The AMA says prior authorization eats about 13 hours a week per physician. Most of that is not the work itself, it is the disorganization around it. Here is a full worked turnaround showing how a tracked system takes that number down, what drives each hour saved, and what it means in money.

Prior authorization consumes about 13 hours per physician per week, per the AMA, but most of that time is lost to disorganization and rework, not the submissions themselves. This worked model shows how a tracked system, batching, templating, expiration tracking, systematic appeals, and clear ownership, takes the number down sharply, and what drives each hour saved. It is a representative illustration, clearly labeled, built to show the mechanics; real client-approved numbers will be published as engagements produce them.

Thirteen hours a week. That is what the AMA says prior authorization costs the average physician and their staff, and it is a number that sounds like a fact of life. It is not. Most of those 13 hours are not spent doing prior authorizations; they are spent losing them, redoing them, and hunting for them, which is a disorganization problem, not a volume problem. This is a worked model of what happens when you fix the disorganization, and where each recovered hour comes from.

The starting point: 13 hours

Start with the honest baseline, because the whole turnaround is measured against it. The published AMA figure is that prior authorization consumes roughly 13 hours of physician and staff time per week per physician, a number that has held stubbornly steady across recent surveys, detailed in the 13-hours guide. For a practice, that is close to two full working days a week of skilled staff time spent obtaining approvals, and it is heavy enough that, per the AMA, about 40% of practices employ someone working exclusively on prior authorization. The instinct is to treat that time as fixed, the unavoidable cost of dealing with payers. But when you look closely at how those hours are actually spent in a practice running prior auth ad hoc, a different picture emerges: a large fraction of the time is not the irreducible work of submitting an authorization, it is the overhead of doing it without a system, chasing status, redoing expired auths, re-gathering the same payer requirements, and reworking denials that a better front end would have prevented. That overhead is what a system removes, and it is why the starting number is so much higher than it needs to be. The model below takes a representative practice at the 13-hour baseline and walks through what changes.

Where the time actually goes

To fix the number you have to see where it hides, so break the 13 hours into where the time actually goes in an unsystematized practice. Some of it is genuine, irreducible work: gathering the clinical information and submitting a legitimate authorization takes time no system eliminates. But a large share is waste of specific, nameable kinds. There is rework from expirations: authorizations obtained and then allowed to lapse before the service, so the whole effort is repeated. There is rework from denials: authorizations denied for preventable front-end reasons, then reworked or appealed, when a cleaner submission would have avoided the denial. There is repeated lookup: re-finding the same payer's requirements, forms, and portals every time, because nothing is templated or saved. There is status chasing: calling and checking on pending authorizations because there is no tracked pipeline showing their state. And there is time lost to no ownership: authorizations sitting unhandled because no one clearly owns them. Add these up and, in a disorganized practice, they can rival or exceed the irreducible work itself, which is the key insight: the 13 hours is mostly recoverable, because most of it is overhead, not authorization. The denial-driven share connects directly to the front-end fixes in the front-desk PA workflow and the cost math in the rework cost guide.

The four moves

The turnaround comes from four operational moves, each targeting a specific slice of the waste above. Batch and template the repetitive work: save each payer's requirements, forms, and criteria so they are reused rather than re-found, and group submissions so similar work is done together, which collapses the repeated-lookup time. Track every authorization in a pipeline with its status and deadline, so none expires unused, which eliminates the single most wasteful category, expiration rework, and ends the status-chasing because the pipeline shows state at a glance. Work denials systematically with a real appeal process, so preventable denials are reduced at the front end and the denials that do occur are worked and appealed rather than abandoned, recovering both time and revenue, the approach in the appeal success rate guide. And assign clear ownership, so every authorization has someone accountable and nothing sits unhandled. These four moves are the core of the Zero-Slip Prior Auth System in the Zero-Slip guide, and none of them is exotic; they are the difference between running prior auth as a tracked operation and running it ad hoc. Together they attack exactly the overhead that inflates the 13 hours, which is why the recovery can be dramatic.

The turnaround, hour by hour

Here is the model, showing where the hours go in a representative practice before and after the four moves. These figures are illustrative, chosen to show the mechanics, not a specific client's audited results.

The model takes the practice from 13 hours to about 3, and the point is not the exact number, which will vary by practice, but the composition: nearly all the recovery comes from eliminating waste, expirations gone, status chasing gone, lookup and denial rework collapsed by templating and a cleaner front end, while the irreducible submission work barely moves, because that part was never the problem. That is why a turnaround of this shape is realistic rather than optimistic: it does not require doing authorizations faster through heroics; it requires stopping the redoing, re-finding, and chasing, which a system simply removes. A small practice sees the same proportional recovery even if the absolute hours are lower, because the waste is proportional to the disorganization, not the scale, the methodology behind the benchmark methodology guide.

What it means in money

Translate the hours into money, because that is the language of the decision. Ten recovered hours a week is the headline, and it pays off in two ways. First, direct labor: ten hours a week of skilled staff time returned is time that goes to patients, to revenue-generating work, or to simply not needing an extra dedicated prior auth hire, real money at any staff rate, multiplied across a year. Second, and often larger, recovered revenue: eliminating expired authorizations means services that were being done and not billed as authorized now get billed, and working denials means recoverable revenue that was being abandoned now gets collected, since the industry evidence is that most denials are ultimately payable and most appealed denials are overturned, yet many are never appealed, the numbers in the denial statistics. So the turnaround is not only a time story; it is a revenue story, and for most practices the recovered revenue from stopped expirations and worked denials dwarfs the labor savings. That is the real case for treating prior auth as a system rather than a chore: it gives back the hours and stops the leak at the same time. The figures here are a representative model to show how the pieces fit; your practice's actual numbers are what matter, and the free prior authorization guide and a Leak Audit are how you find them. When ClinicOps has client-approved results to report, they will appear here alongside this model.

Frequently asked questions