Prior Authorization

How to Track Prior Authorization Expirations (and Never Treat on a Lapsed Auth)

Getting the approval is only half the job. Here is a practical system for tracking expiration dates and approved visits, renewing on time, and keeping ongoing therapy covered.

November 20269 min read
Front desk staff reviewing patient authorization status on a screen

Why Expired Authorizations Cost More Than Denials

Most practices measure prior authorization by the front end: how many requests go out and how many get approved. The expensive failures often happen later, when an approved authorization quietly runs out.

An authorization can lapse in two ways:

  • The date passes. Most approvals carry a valid-through date. Procedure authorizations are often short, and drug or therapy authorizations commonly need renewal every six to twelve months, depending on the payer and the plan.
  • The units run out. Many approvals cover a set number of visits, units or doses. A physical therapy course, an infusion series or allergy immunotherapy can exhaust its approved units well before the end date.

When either happens and nobody notices, the patient gets treated, the claim goes out, and the payer denies it for no valid authorization. Retro-authorization is often refused, so the service is written off or the practice spends hours on an appeal. For ongoing therapy, a missed renewal can also mean a gap in treatment while the new request is pending.

The fix is not working harder. It is a tracking system where every authorization has an owner, a countdown and an alert.

What to Record for Every Authorization

A tracking system is only as good as what goes into it. For every approved authorization, capture:

  • Patient, payer and plan, including the member ID used on the request.
  • Authorization number exactly as the payer issued it.
  • Service and codes approved (CPT, HCPCS or drug and NDC), and the diagnosis codes the approval is tied to.
  • Start date and end date.
  • Approved quantity: visits, units, doses or sessions, and how many have been used.
  • Rendering provider and site of service, because some approvals are only valid for the provider or location on the request.
  • Renewal requirements: what the payer needs to extend it, such as updated clinical notes, scores or labs.
  • Owner: the staff member responsible for the renewal.

The last two fields are the ones most practices skip, and they are the ones that make renewals fast. If you already know a payer wants a new PASI score or a functional status update, you can collect it at the visit before the renewal is due.

Set Alerts on Both Dates and Units

Date-only reminders miss half the problem. Set two kinds of alerts:

Date alerts. A practical default is 30, 14 and 7 days before the end date. Use longer lead times for payers that are slow to respond and for therapies where a gap in treatment is clinically risky.

Unit alerts. Trigger an alert when a set number of approved visits remain, for example three visits left on a therapy course or one dose left on a drug authorization. Count scheduled visits, not just completed ones: if all remaining units are already booked, the renewal is due now.

Each alert should go to a named person with a due date, not to a shared inbox. An alert nobody owns is the same as no alert.

Check Authorization Status When the Visit Is Booked

The cheapest place to catch a lapsed authorization is the schedule, before the patient arrives.

  • At booking, check that the visit falls inside the authorization's dates and that units remain.
  • Two to three days before the visit, re-check, because earlier visits may have used up units.
  • At check-in, flag any patient whose authorization expires before their next scheduled visit.

If the authorization will not cover the visit, staff have options: move the visit, start the renewal, or have the financial conversation with the patient before the service, not after the denial.

Stop Treating on Expired Auths

See how clinIQ tracks every authorization's dates and visits, alerts staff before it lapses and queues the renewal, in a 15-minute demo.

Request a Demo

Build a Renewal Workflow, Not a Reminder

A reminder tells someone a renewal is due. A workflow gets it done.

1. Start from the last approval. Pre-fill the renewal with the original request: codes, diagnosis, provider and the clinical rationale that worked last time.

2. Attach what changed. Add the latest visit notes and the measures the payer asks for at renewal, such as response to therapy, scores or labs.

3. Submit early. Payer turnaround varies. Since January 2026, the CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) requires Medicare Advantage, Medicaid, CHIP and ACA marketplace plans to decide standard requests within seven calendar days and expedited requests within 72 hours. Commercial plans may take longer, so submit with a buffer.

4. Track pending renewals. Follow up on any request that has not been decided within the payer's normal turnaround.

5. Record the new approval. Update the dates and units the day the approval arrives, and reset the alerts.

If a renewal is denied, move straight to the appeal or peer-to-peer review while the patient is still on schedule.

Spreadsheet vs Authorization Tracking Software

Many practices start with a spreadsheet. It works for a few dozen authorizations and one person who keeps it current. It breaks when:

  • More than one person updates it, and versions drift.
  • Units have to be counted by hand against the schedule.
  • Nobody is alerted unless they remember to open the file.
  • You need to know which authorizations expire this week across every provider and payer.

Authorization tracking software solves those problems by tying each authorization to the schedule. clinIQ's pre-authorization tracking records dates and approved units for every authorization, counts units down as visits are booked and completed, alerts the owner on the schedule you set, and queues the renewal pre-filled from the last approval. Staff see one list of what expires this week, what is pending with the payer and what was denied, filterable by provider, payer or therapy.

Whichever tool you use, the rules are the same: every authorization has an end date, a unit count, an owner and an alert.

Where Expirations Hurt Most, by Specialty

Some services are especially prone to lapsed authorizations:

  • Infusion and specialty drugs. Biologics and infusions need regular renewals with evidence of response. See infusion prior authorization.
  • Allergy and asthma biologics. Renewals often require updated symptom control and exacerbation history. See asthma biologic prior auth.
  • Dermatology biologics. Renewals commonly ask for updated PASI or body-surface-area scores. See psoriasis biologic prior auth.
  • Physical, occupational and speech therapy. Visit limits run out mid-course, so unit tracking matters more than dates.
  • Wound care. Hyperbaric oxygen and advanced dressings are approved for set numbers of treatments. See wound care prior auth.
  • Oncology. Treatment plans change, and an approval may not cover a new regimen. See oncology prior auth.

The Metrics to Watch

Track a handful of numbers each month:

  • Authorizations expiring in the next 30 days, and how many have a renewal in progress.
  • Visits delivered without a valid authorization. The target is zero.
  • Denials for missing or expired authorization, by payer.
  • Renewal turnaround: days from submission to decision, by payer.
  • Treatment gaps: patients whose therapy was delayed waiting on a renewal.

These numbers show whether the system works and which payers need longer lead times. For the wider picture, see the prior authorization denial prevention guide.

Stop Treating on Expired Auths

See how clinIQ tracks every authorization's dates and visits, alerts staff before it lapses and queues the renewal, in a 15-minute demo.

Request a Demo

Frequently Asked Questions

Never Miss a Prior Auth Renewal

clinIQ tracks expiration dates and approved visits for every authorization and queues renewals before they lapse.

Request DemoNo credit card required