Prior Authorization Deadline Tracker
Authorizations run out quietly, and the denial is how most practices find out. Project the run-out date and the renewal date before that happens.
Authorizations run out quietly. A patient keeps coming, the visits keep getting billed — and only the denial reveals that the approval was exhausted three visits ago. This tracker projects the date your authorized visits run out at the current pace, and the date to submit the renewal request: 14 days before the run-out date.
Project the authorization
Managing authorizations so they never lapse
The math is the easy part; the workflow is where authorizations die. Three habits separate practices that rarely see an auth denial from those that chase them weekly. Count at every check-in: the remaining-visit count should live on the schedule and the encounter form, not in a spreadsheet someone updates monthly. Renew on a trigger, not a date: when the remaining count hits two weeks of visits, the renewal request goes out the same day — this tracker’s 14-day renewal date is a backstop, not the plan. Mind the other dimension: most authorizations expire by date range as well as by visit count, and some are limited by units or dollars. If the approval letter carries an end date, the visits must fit inside it — check both limits before projecting a schedule. Retro-authorizations exist, but payers grant them inconsistently and often only within a short window after the service, which is why a lapsed auth so often becomes a write-off. If tracking approvals across a full patient panel is eating staff time, it is exactly the kind of front-end work our prior authorization assistance team takes over.
Frequently asked questions
Why does the renewal date sit 14 days before the run-out date?
Renewal (re-authorization) requests need payer processing time, and many payers will not accept a continuation request until the current approval is close to exhaustion. Fourteen days is a practical buffer: late enough that the request is reviewable, early enough that a slow payer or a request for clinical records does not strand scheduled visits. Payers with longer published turnaround times deserve a bigger buffer.
The authorization also has an end date. Which limit wins?
Whichever comes first. Visits used after the approval’s end date are not covered even if visits remain, and visits beyond the count are not covered even inside the date range. Enter the schedule so that both limits hold, and if the end date arrives first, ask for an extension before it passes.
What if the patient’s visit pace changes?
Re-run the projection. The run-out date is only as good as the weekly pace you enter — doubling visits per week roughly halves the calendar time left. Practices that re-project at every visit catch accelerations weeks earlier than those that set the date once and forget it.
Disclaimer: This tool is provided for educational and planning purposes only. It is not billing, coding, legal, or financial advice, and it does not replace the rules of any specific payer. Requirements and figures change over time — always verify against current CMS guidance and your own payer contracts before acting on a result.
