Tracking prior authorizations across payers without losing one.
A practice working with a dozen payers is juggling a dozen portals, a dozen submission formats, and a dozen different turnaround expectations. Nothing about that is unified, which is exactly why authorizations get lost — not through one dramatic failure, but through a tracking gap that quietly repeats across every recurring-visit patient in the schedule.
Key takeaways
- The problem is rarely one dramatic miss. It's a tracking gap that repeats quietly across every recurring-visit patient until a denial audit surfaces the pattern.
- A tracker needs six fields at minimum to answer the two questions that actually matter: is this request stalled, and is this approval about to lapse.
- The discipline matters more than the tool. A spreadsheet checked daily by a named owner outperforms an expensive system nobody actually opens.
- A missed authorization costs one of two ways — a delayed service, or care delivered unauthorized and written off weeks later.
Why authorizations get lost across a multi-payer schedule
Every payer runs its own version of the prior authorization process — its own portal or submission channel, its own documentation requirements, its own turnaround expectations, and its own definition of what counts as urgent versus standard. A practice billing a dozen payers is effectively running a dozen different processes in parallel, often for the exact same handful of high-volume procedures, and nothing forces those processes to stay consistent with each other. That fragmentation is the root cause behind most of the tracking failures that eventually surface as denials: not a single dramatic miss, but the same small gap — an expiration date nobody calendared, a visit count nobody was watching — repeating quietly across every recurring-visit patient in the practice.
The reason this stays invisible for so long is that a single missed authorization looks, from the billing desk, like an isolated denied claim. It's only when someone deliberately reconciles a batch of denials and traces each one back to its root cause that the pattern becomes visible — and by then, the same gap has usually repeated across dozens of encounters, not just the one that triggered the review. Building a tracker isn't about handling the occasional exception; it's about closing the systemic gap that produces that pattern in the first place.
What a tracker needs to capture
A tracking system, whether it's a dedicated module, a shared spreadsheet, or something in between, has to be able to answer two questions at a glance for every open authorization: is this request stalled somewhere it shouldn't be, and is this approval about to lapse before the next scheduled appointment. Answering those two questions reliably requires six fields, at minimum, tracked consistently for every request.
| Field | What it's for |
|---|---|
| Submission date and method | Starts the clock for follow-up, and is the first thing a payer's representative asks for on any status call |
| Payer reference / confirmation number | Without it, every status inquiry starts from zero and takes longer to resolve |
| Expected decision date | Converts open-ended waiting into a specific date to follow up on if nothing has come back |
| Visits or units authorized | Enables tracking a running balance against the schedule, rather than discovering the count was exceeded after a claim denies |
| Expiration date | Has to be checked against the actual scheduled appointment date, not the date the authorization was originally requested |
| Escalation trigger and owner | A specific day past which a stalled request gets escalated, and a named person responsible for doing it |
The escalation field deserves particular attention because it's the one most trackers skip, and it's the one that actually prevents a stalled request from sitting silently until it expires. A tracker that only logs status without a defined trigger for action is a record-keeping exercise, not an operational tool — the value comes from someone being told, automatically or through a daily review habit, that a specific request has gone past its expected decision date and needs a phone call, not from the data simply existing somewhere.
Spreadsheet, EHR module, or dedicated software
The tool matters far less than the discipline behind using it. A well-maintained spreadsheet, reviewed by a named owner on a fixed daily schedule, reliably outperforms an expensive dedicated authorization system that nobody actually opens between submission and the day a claim denies. What makes a tracker work is the daily habit of checking it against the fields above, not the sophistication of the software underneath it.
Where volume genuinely justifies it, dedicated software or an EHR's authorization module earns its cost by surfacing expirations and stalled requests automatically, rather than depending on someone remembering to scroll through rows looking for dates that are approaching. That's a meaningful advantage at scale, because the failure mode of a manual system under high volume is exactly the silent-lapse pattern this guide describes: the tracker exists, the data is even accurate, but nobody looked at row 340 on the day it mattered. Whichever tool a practice uses, the test is the same — can someone, today, answer "which authorizations expire in the next two weeks" and "which requests have gone quiet past their expected decision date" without manually re-deriving both from scratch.
What it actually costs to lose track of one
The cost of a tracking failure lands in one of two places, and neither is good. If the gap is caught before the appointment — because a patient calls to confirm, or someone happens to check — the service gets delayed while staff scramble to re-verify status or resubmit a lapsed request, which disrupts both the patient's care and the day's schedule. If the gap isn't caught in time, the service gets delivered on the assumption the authorization was still in force, and the practice finds out otherwise when the claim denies weeks later, at which point it's very often the same full write-off this whole topic opened with: unbillable to the payer, and usually not billable to the patient either, because most payer contracts treat the missing authorization as the practice's failure.
Either outcome is avoidable with the same fix: a tracker that captures the six fields above, checked on a fixed schedule by someone whose job includes actually looking at it, with a defined escalation trigger before either the visit count or the expiration date is reached. That's the operational discipline that turns prior authorization from a source of quiet, recurring loss into a managed process — and it's the same discipline that, over time, builds the approval-rate history described in our gold-carding guide, so the tracking effort pays off twice.
Not confident you'd catch a lapsing authorization before the appointment?
We track every open request against your schedule, with a named owner and an escalation trigger before anything expires or runs out of visits.
Frequently asked questions
What fields does a prior authorization tracker actually need?
At minimum: submission date and method, the payer's reference or confirmation number, the expected decision date, the number of visits or units authorized, the expiration date, and a named escalation owner with a specific trigger date. Fewer fields than that and the tracker can't answer the questions that actually prevent a lapse — whether a request has gone quiet past its expected decision date, or whether an approved authorization is about to expire or run out of visits before the next scheduled appointment.
Is a spreadsheet good enough, or do we need dedicated software?
A well-maintained spreadsheet, reviewed daily by a named owner, is genuinely good enough at lower volume — the discipline of checking it matters more than the tool. At higher volume, across many payers and many recurring-visit patients, a system that surfaces expirations and stalled requests automatically, rather than relying on someone remembering to scroll through rows, becomes worth the cost because the failure mode of a manual system at scale is the exact silent-lapse pattern this guide is about.
What actually happens when an authorization is missed or expires?
One of two things, and neither is good: the service gets delayed while staff scramble to re-verify or resubmit, disrupting the patient's care and the day's schedule, or the service gets delivered anyway on the assumption the authorization was still in force, and the practice finds out otherwise when the claim denies weeks later — usually as a full write-off, since most payer contracts treat a missing authorization as the practice's failure rather than the patient's responsibility.
Confirm before you rely on this. Prior authorization requirements, payer portals and turnaround times change by payer, plan and service. The process information on this page reflects standard industry practice as of August 2026 and is provided for general education — verify current requirements directly with the specific payer before relying on it.