What Does 40 Authorizations a Week Actually Cost a Practice in Hours and Payroll?

How to Take the Weekly Authorization Drain Off Your Practice

The goal is simple: every clean request submitted same business day and the weekly hours returned to your clinical team, without hiring a full FTE against a peak you cannot predict. Here is what does that, move by move.

1. Measure What the Volume Actually Costs in Hours

Before you staff against it, put a real number on it. Count your authorizations per week by service line, biologics, sleep testing, imaging, and multiply by the honest time each takes end to end: the submission, the follow-up, the peer-to-peer, the appeal. Most specialty practices find the total lands near the AMA benchmark of roughly 13 hours a week per physician, which is close to a day and a half of clinical and staff time. You cannot right-size capacity for a workload you have never measured, and the number is almost always larger than the practice assumed.

2. Scale Capacity With Volume, Not Against a Peak

The core problem is that authorization volume flexes with visit volume while your headcount is fixed. Hire one full-time coordinator and you are underwater in a busy month and overpaying in a slow one. The move is elastic capacity: a dedicated pod that scales up when requests spike and down when they ease, so you pay for the volume you actually have rather than betting on a peak. That is how a two-physician practice covers the equivalent of an extra FTE it could never justify hiring outright.

3. Guarantee Same-Business-Day Submission for Clean Requests

Aging is where the cost turns clinical. A request that sits three days can miss a deadline, delay a study, and push care past when it mattered. The fix is a same-business-day submission guarantee for every clean request: it goes out the day it is ordered, tracked to a decision, with only the genuinely incomplete ones held for a quick clarification. When submission stops queuing behind everything else, the backlog that used to age past deadlines simply stops forming.

4. Report the Hours Returned Every Week

The drain is invisible until you measure what you got back. Every week, the practice sees a simple report: requests submitted, average time to submission, hours of clinical and staff time returned, and any request at risk of a deadline. That number is the point of the whole exercise, because 13 hours a week per physician handed back to patient care is the return that pays for the coverage several times over, and it is only real if someone reports it.

5. Hand the Volume to a Dedicated Team That Scales

Practices that stop drowning in authorization volume do it by handing it to a dedicated team that scales with their requests: remote specialists who submit same day, track every decision, own the peer-to-peer, and report the hours returned, live in 1 to 2 weeks. The physicians go back to reading studies and seeing patients, a trained backup covers every gap, and the auth queue stops growing faster than anyone can work it. Below is what it sounds like when nobody owns it yet, in providers’ own words.

Why This Keeps Happening

If it is just paperwork, why does the volume cost so much? Because a single authorization is not one action; it is a chain. The American Medical Association’s prior authorization survey reports practices average roughly 39 authorizations per physician per week and spend about 13 hours a week processing them, close to a day and a half of physician and staff time. Each request can carry a submission, a follow-up, a peer-to-peer, and an appeal, and specialty categories like biologics, sleep testing, and advanced imaging are among the most heavily managed. Multiply that chain by 40 a week and the hours are not a rounding error; they are a part-time job that no one budgeted, absorbed by clinical staff who already had one.

The structural trap is that volume and capacity move in opposite ways. Authorization volume flexes with visit volume, up in a busy month, up again when you add a service line, while your coordinator headcount is fixed. The AMA survey found 40 percent of physicians now have staff who work exclusively on prior authorization, which is exactly the FTE a growing practice needs and often cannot justify hiring against an unpredictable peak. So the gap between requests and capacity widens every good month, and that is what an AI prior authorization automation workflow with human oversight is built to close, by scaling with the volume instead of against a headcount number.

And the cost is not only payroll; it turns clinical when requests age. The same AMA work reports that 94 percent of physicians say prior authorization delays necessary care, and that 78 percent say it leads patients to abandon a recommended treatment. When a sleep study or a biologic sits three extra days because the queue is too long, that delay is not an administrative footnote; it is a patient waiting on a decision that should have gone out same day. The lost hours are real, and the delayed care behind them is worse.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

The Solution

So what does “someone whose whole job it is” look like against 40 requests a week? The pod absorbs the volume and flexes with it, up when a busy month or a new service line spikes requests, steady when it eases, so the practice pays for the work it actually has instead of a fixed headcount guessed against a peak. Every clean request goes out same business day and is tracked to a decision, so the backlog that used to age past deadlines stops forming. Most of what drains a specialty practice is submission and follow-up labor, and that is exactly what dedicated prior authorization support is built to absorb.

For the categories that fight back, biologics, sleep testing, advanced imaging, the specialist owns the peer-to-peer and the appeal too, so the physician is not pulled off the floor to argue a study. For a pulmonology practice specifically, that coverage maps to the exact service lines that generate the most requests, which is why pulmonology prior authorization services are scoped to the studies your practice actually orders rather than a generic template. The hours that used to disappear into the auth queue come back to patient care.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow assembles the request, flags the deadline, and tracks the decision; a person confirms the clinical case is right and owns the peer-to-peer and appeal. Every security control that protects the chart data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving clinical documentation through an auth workflow at volume is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team handle your authorization volume better than your own staff? Because processing authorizations is their entire day, not the thing they squeeze between check-ins. The people working your requests are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US prior authorization and specialty workflows. They know how each payer wants a biologic or a sleep study documented, how to run a peer-to-peer so the physician wins the call, and how to keep 40 requests a week moving without a check-in line pulling them away. That is not a task handed to whoever is free; it is a specialty that scales.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and because capacity flexes with your volume, you are never overpaying in a slow month or underwater in a busy one. No one on our side goes out without a trained backup already inside your workflow, so the queue never stalls because one coordinator is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented authorization workflow with elastic capacity: how each payer wants each service line documented, the submission standard for a clean request, the peer-to-peer rules, and the weekly report of hours returned, all written down and worked the same way every time. Before we take a single request for a new practice, we count your authorization volume by service line and measure the hours it consumes, so we can size capacity against your real workload rather than a guess, and scale it as your volume moves.

From there the workflow becomes a living playbook rather than tribal knowledge in one coordinator’s head. It records how each payer wants biologics, sleep testing, and imaging documented, the same-business-day submission standard, the peer-to-peer path, and the weekly hours-returned metric so the value stays visible. It is written down, kept current as payers change their rules, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so the queue never backs up because one person is gone.

That is the difference between surviving this month’s volume and fixing the process for good, and it is what a dedicated prior authorization partner actually buys you. A coordinator leaving used to mean the queue backed up and requests started aging again. Under this model the workflow keeps running, the playbook stays, the backup steps in, and 40 auths a week stops being the workload that quietly eats your clinical hours.

The Whole Thing in Four Sentences

Forty authorizations a week costs a practice roughly 13 hours of physician and staff time, close to a day and a half, plus the unbudgeted payroll of an FTE that fixed headcount cannot cover once volume outruns capacity, and the clinical cost of requests that age past their deadline. Absorbing it with front-desk staff, hiring one coordinator against a moving peak, or making physicians run their own peer-to-peers all fail the same way. The fix is to measure the true hours, scale capacity elastically with request volume, guarantee same-business-day submission for clean requests, and report the hours returned every week. A pulmonology and specialty group runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to take back your auth hours? Try us risk free: two weeks, your real weekly volume, a dedicated pod submitting same day and reporting the hours returned, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Written By

Dan Nandan

Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From