Case Study: How a 3-Physician Practice Stopped Auth Expirations

An expired authorization is one of the most frustrating leaks in a practice, because the hard part was already done: the payer said yes. Then the approval lapsed before the service happened, and that yes turned into nothing. This documents how a three-physician practice stopped that from happening, and the fix is more about visibility than effort.

An honest note on the numbers

A transparency note first, because it matters and it is the reason this reads the way it does. The figures below are representative numbers grounded in published benchmarks and the mechanics of a real tracking system, used to document how the fix works, not an audited client testimonial with guaranteed results. We do not publish fabricated case studies or promise specific dollar outcomes, because no honest process can guarantee what your particular practice will recover. What we can show is the method, the levers it pulls, and why it works, using realistic numbers a small practice would actually see. Your starting point and your results will differ. What stays constant is the mechanism, and that is what this documents. When we have a client who has approved sharing their actual audited numbers, we will publish those and say so plainly; until then, this shows the method honestly rather than dressing up invented results as a testimonial.

The problem: a silent leak

The practice looked like many small ones: three physicians, a busy front desk, and prior authorizations handled competently but informally. Auths were requested and, when granted, noted, in an email here, a sticky note there, a field in the schedule that no one systematically watched. There was no single list of every open authorization, no tracking of expiration dates, and no one person accountable for acting before a deadline. The result was a quiet, recurring leak: authorizations that were granted but expired before the service was scheduled or delivered, because nothing flagged the approaching deadline and the auth simply aged out of everyone's memory. This is the crucial point, the failure was not clinical or even effort-related; it was a visibility failure. The staff were working hard; they just could not see, in one place, which auths were open and which were about to lapse. A representative practice like this loses several authorizations a month this way, each one revenue for care that was approved and then forfeited, the silent version of the leak described in the expiring-auths guide. Nobody decided to let auths expire; the system just had no way to stop it.

The fix: one dated pipeline

The fix was not more effort or new software; it was visibility, built three ways. First, one dated pipeline: every open authorization in a single tracked list, each with its status and its expiration date, replacing the scattered notes with one place to look, the core of the Zero-Slip system and the structure in the tracking spreadsheet. Second, alerts before every deadline: each authorization flagged well before its expiration, so an approaching lapse announced itself instead of passing silently. Third, a single accountable owner: one person responsible for working the pipeline and acting on the alerts, so the task was someone's explicit job rather than everyone's vague assumption. That is the entire fix, and its modesty is the point: no expensive tool, no added headcount, just every auth tracked with a date, a flag before every deadline, and a clear owner. Built into a system the practice already used, it took a matter of weeks to stand up, and it turned an invisible leak into a visible, managed pipeline.

Why it worked

The fix worked because it addressed the actual cause. Expirations from oversight happen for one reason, no one saw the deadline coming, so a system that makes every deadline visible before it arrives removes the cause directly. That is why the effect is fast and reliable rather than gradual: the moment every authorization is tracked with a date and flagged ahead of its expiration, the specific failure mode, an auth aging out unnoticed, largely stops, because it can no longer happen silently. The representative result is that expirations from oversight fall toward zero, which for a practice losing several a month is a meaningful recovery of revenue for care that was already approved. But the honest framing matters: the exact number depends on the practice's volume, specialty, and starting point, which is why we document the mechanism rather than promise a figure, and it connects directly to what a real guarantee can and cannot cover, in the guarantee guide. What is universal is the logic, make deadlines visible and assign an owner, and oversight-driven expirations stop, which works in any practice that installs it.

There is a second-order benefit worth naming, because it compounds the revenue effect. When authorizations stop expiring, the downstream chaos they caused stops too: the scramble to re-request a lapsed auth, the awkward call to reschedule a patient whose approval expired, the staff stress of discovering a miss after the fact. A visible pipeline does not just recover the revenue from the auths that used to lapse; it removes the rework and the friction those lapses generated, which frees the same staff to do more valuable work. So the fix pays back twice, in recovered revenue and in reclaimed capacity, and both come from the same modest change of making the work visible and owned.

The representative numbers

Here is what the change looks like in figures, with the standing caveat that these are representative and benchmark-grounded to show the method, not one client's audited results. Before the fix, a busy three-physician practice tracking auths informally might lose on the order of several authorizations a month to expiration, each one revenue for a service that was approved and then forfeited. Put a conservative dollar figure on each lapsed authorization and even a handful a month compounds into a meaningful annual leak, entirely from oversight rather than any clinical issue. After the fix, expirations driven by oversight fall toward zero, because the mechanism that caused them, deadlines passing unseen, no longer exists.

Read the table and the pattern is clear: the "after" column is not the result of heroics, it is the result of visibility and ownership that were simply absent before. That is why the fix is durable rather than a temporary push.

How to run it yourself

The fix is repeatable, and you do not need anyone's help to start. Put every open authorization in one dated list, with its status and expiration, so you finally have a single place to see them all. Set alerts that fire before each expiration, so no deadline arrives unannounced. Assign one accountable owner to work the pipeline and act on the alerts, making it their explicit job. And build the follow-up cadence so pending auths are chased and expiring ones are acted on before they lapse, the submission-speed side covered in the speed guide. That is the whole system, and it is well within reach of a small practice using tools it already has. Run it and the silent leak closes, not because anyone worked harder, but because the work finally became visible and owned, exactly the measure-fix-systematize pattern in the process improvement guide. Authorizations are hard-won approvals; letting them expire is forfeiting money you already earned. A dated pipeline, alerts, and an owner make sure you stop.

Where to go next

• How do you stop prior authorizations from expiring before the visit? live

  How do you stop prior authorizations from expiring before the visit? Put every approved auth on.

• The Zero-Slip Prior Auth System: Exactly What $1,250 Buys (Full Scope) live

  The full scope of the Zero-Slip Prior Auth System: a 14-day build in your own tools, the.

• Free Prior Authorization Tracking Spreadsheet (Sheets, Excel, and ClickUp) live

  A free prior authorization tracking spreadsheet for Sheets, Excel, and ClickUp. One board per.

Frequently asked questions