Tracking authorization status and deadlines

Once a request has been filed, the work is not finished. A pending request sits in the payer's queue until a reviewer renders a decision, and until that decision is captured the requesting organization does not know whether the service is authorized, partially authorized, or denied. Tracking is the discipline of following each request through to a documented outcome rather than assuming a submission will resolve itself. It sits between submitting a prior authorization request and the moment the service is delivered and billed, and it is where many otherwise-valid authorizations are quietly lost.

Deadlines are what make tracking time-sensitive. Every authorization exists inside several clocks that run at the same time: the payer's own turnaround for making a decision, the window during which the approved service must actually be performed, and the timely filing limit that governs the eventual claim. Because these clocks are independent, an organization can do everything else correctly and still lose payment by letting one of them expire. Seeing where this step fits in the broader prior authorization workflow clarifies why monitoring cannot wait until the date of service.

Effective tracking depends on capturing a consistent set of data points for every request, so that status can be looked up quickly and the eventual approval can be matched to the claim. The exact fields a payer returns vary, but the following elements are almost always relevant.

Request or reference number

The identifier assigned when the request is submitted. It is the key used to look up status through a portal, an electronic transaction, or a phone call, and it should be recorded before the confirmation screen is closed.

Current status

Where the request stands — for example received, in clinical review, approved, partially approved, denied, or returned for additional information. A partial approval in particular is easy to miss and requires careful reading.

Authorization number

The identifier issued when a request is approved. It generally must appear on the claim for the authorized service to be recognized, which is why it is captured verbatim at the time of the decision.

Decision date and validity window

When the payer made its decision, and the date span during which the approved service must be performed. Services rendered outside that window may not be covered by the authorization even though it was granted.

Approved units, visits, or quantity

The amount the payer approved. The billed service must stay within it, a point covered in matching authorized units to billed services.

Denial reason and next steps

If the request is denied, the stated reason and the available options, which may include submitting more documentation, correcting the request, or requesting a peer-to-peer review.

The deadlines attached to a single authorization are easy to conflate, but they answer different questions and are set by different parties. Treating them separately prevents the common mistake of assuming that an approval, once granted, remains usable indefinitely. Each window below varies by payer, plan, service, and jurisdiction, and several are also shaped by federal or state regulation, so current figures should be confirmed against the governing contract or rule rather than a remembered number.

Status can usually be checked through more than one channel, and choosing the fastest reliable one keeps staff time focused on the requests that actually need intervention. The available channels differ by payer, and not every payer supports every method.

1. 01

   Prefer a self-service channel

   A payer portal or an electronic status transaction generally returns information faster than a phone call and creates a record that can be saved to the request log.
2. 02

   Check on a cadence tied to expected turnaround

   Rather than checking at random, staff review pending requests on a schedule aligned to each payer's decision-turnaround expectation, so nothing sits untouched past the point where a decision should have arrived.
3. 03

   Document every check and its outcome

   Recording who checked, when, the channel used, and the result turns tracking into an auditable trail and prevents duplicate work across a team.
4. 04

   Escalate stalled requests

   When a request exceeds the expected turnaround, it is escalated — through the payer's expedited pathway when clinically appropriate, or by contacting the payer directly — rather than left to age.

Increasingly, status checks are handled through standardized electronic exchange rather than phone or fax. The standard electronic authorization transaction (the X12 278) and the payer interfaces described under electronic prior authorization let some systems retrieve status automatically. Separately, the CMS Interoperability and Prior Authorization rule requires certain impacted payers to make status available through a standardized interface and to communicate decisions within defined timeframes; the specific timeframes, the payers affected, and the phased effective dates are set by the rule and continue to change, so the current CMS source should be consulted rather than assumed.

Most tracking failures are not dramatic; they are quiet lapses that surface only when a claim is denied. Recognizing the recurring patterns helps an organization design controls against them.

• Treating a submitted request as an approval, and scheduling or performing the service before a decision is captured.
• Missing a partial approval — reading an approval as full when the payer authorized fewer units, a narrower service, or a shorter window.
• Letting the validity window expire between approval and the date of service, so the authorization no longer applies.
• Recording the authorization number incorrectly or in the wrong field, which can lead to an authorization-related denial even though approval existed.
• Failing to escalate a request that has stalled past the payer's expected turnaround, delaying care and compressing later deadlines.

Ad hoc tracking works until volume grows or a key staff member is out. A durable approach uses a single work queue or log where every open request is visible with its status, its deadlines, and its next action, so no request depends on an individual's memory. Designing that queue — its fields, ownership, and follow-up cadence — is the subject of building a prior authorization tracking process, and a simple starting point is a structured authorization status log that captures the data points described above.

Over time, the same log becomes a source of insight. Reviewing how long requests take, how often they stall, and how many expire unused turns tracking data into prior authorization performance measures that show where the process is leaking. A repeatable, documented workflow — such as the one outlined in the guide to setting up an authorization tracking workflow — is what keeps status monitoring reliable as the mix of payers and rules keeps changing.