Prior authorization is a waiting game with a deadline. If nobody is watching the clock, a submission can sit for days after a payer has already requested more information, and the delay surfaces only when the patient calls. A status tracker fixes that by making every authorization a visible record with an owner, a current state, and an age.
The tracker is an administrative tool. It tracks submission status, documents, and follow-up. It does not decide whether a service is medically necessary, and it does not guarantee an approval. Those remain with the clinical team and the payer.
Design the states first
A useful tracker has a small set of unambiguous states:
- Not started, authorization may be required; eligibility check pending.
- Submitted, request and required documents sent to the payer.
- Acknowledged, payer has confirmed receipt and provided a reference number.
- Info requested, payer needs additional documentation.
- Under review, payer is actively reviewing; no action available.
- Approved, authorization number and validity dates recorded.
- Denied, denial reason recorded; routed for the appropriate next step.
- Closed, service completed or case withdrawn.
Every state needs an exit condition. "Submitted" exits when the payer provides an acknowledgment number. Without that, a submission can look complete when it never arrived.
Add age and next-action fields
Two fields turn a status list into a working queue:
- Age in current state, how many business days since the last state change.
- Next action and due date, the specific next step and who owns it.
Set aging thresholds that match your payers' typical timelines. A reasonable starting point is a follow-up if a submission has been in "Acknowledged" for more than two business days without movement, and a daily check once an item reaches "Info requested." Your thresholds should reflect your actual payer mix, not a generic number.
Record documents explicitly
Most delays come from missing documents. Track each required item as its own checkbox with a received date:
- Referral or order documentation (per clinic policy).
- Clinical notes requested by the payer.
- Prior treatment history the payer requires.
- Any payer-specific forms.
The coordinator confirms that each document exists and was sent. The coordinator does not edit clinical content, summarize it, or decide what it should say.
Make escalations rule-based
Write down when an item escalates and to whom:
- Payer non-response past threshold → billing or authorization lead.
- Repeated denial of the same type → clinical and billing leads for a joint review.
- Missing clinical information → the clinician or clinical reviewer.
- Eligibility or benefits discrepancy → the verification owner.
Rule-based escalation prevents both extremes: staff chasing payers for weeks on their own, and items being escalated so often that the queue becomes noise.
Daily and weekly rhythm
- Daily: update ages, action anything in "Info requested," and record payer responses. Spend the time on items closest to breaching a threshold.
- Weekly: review aging distribution, denial reasons, and average time to approval. Look for a payer or service type that consistently slows down.
The weekly review is where operational improvement happens. If one payer consistently requests the same missing document first, adjust the submission packet going forward.
Worked example
A clinic submits an authorization for a therapy visit. The coordinator records the submission date and sets a two-day follow-up. On day three, the payer confirms receipt and supplies a reference number; state moves to "Acknowledged." On day five, the payer requests additional documentation. The coordinator logs the specific document, marks "Info requested," and routes the request to the clinical reviewer, who supplies the note content. The coordinator sends it, records the send date, and returns the item to "Under review." The approval arrives with a reference number and validity window, both recorded. If the request instead produces a denial, the coordinator records the denial reason and routes it to the billing and clinical leads; the coordinator does not argue medical necessity directly.
Checklist: tracker readiness
- States defined with explicit exit conditions.
- Age-in-state and next-action fields present.
- Aging thresholds match your payer mix.
- Required documents tracked individually with received dates.
- Escalation matrix names owners and triggers.
- Reference and authorization numbers stored on approval.
- Denial reasons captured and routed, not debated.
- Daily update and weekly review cadence scheduled.
- Role boundary documented: status and documents, not clinical decisions.
- Access to the tracker limited to authorized staff.
Where this fits with verification
Authorization depends on accurate benefits information, so the tracker should connect to Insurance Verification rather than duplicate it. A verification step confirms what the plan requires; the Prior Authorization tracker follows the request to a decision. Keeping the two separate avoids the common error of treating an eligibility check as an authorization.
Done well, a tracker converts a stressful, opaque process into a predictable queue with visible aging and named owners, without asking administrative staff to make a clinical call.
Sources and further reading
- Centers for Medicare & Medicaid Services: https://www.cms.gov/
- U.S. Department of Health & Human Services, 45 CFR Part 162 (Administrative requirements, including transactions and code sets): https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-162
Ready to Give the Workflow an Owner?
Discuss a remote operations role built around your workflow, systems, access requirements, and decision boundaries.
Talk with a Staffing Specialist