
A prior authorization tracking tool puts every request on one board, with its stage, payer, due date and the staff member assigned to it, so a stalled approval gets noticed before the patient's appointment. We build that board as a custom app for small medical, specialty and therapy practices, and your staff still submit every request.
This guide is for practice managers and the people who work authorizations. Our guide to medical office automation covers which office tasks to automate first, and AI for small business gives the bigger picture. This post goes deep on one of those tasks.
What a prior authorization tracking tool shows
A prior authorization tracking tool shows every open request in one place, with the patient, the service, the payer, the stage, the date it is needed by and its owner. It also shows the last status anyone saw and when. A request that has gone quiet stands out days before the visit, not on the morning of it.
The stages follow how a request really moves:
- Gathering. The order is in, and the packet is being built.
- Submitted. A staff member sent it to the payer.
- Pending. The payer has it and has not answered.
- More info asked. The payer wants notes, records or a call.
- Approved or denied. The payer's answer, with its reference saved on the request.
- Appeal. A denial the clinician chose to contest, with the file staff are building.
For some payers, federal clocks now apply. A CMS rule on prior authorization (opens in a new tab) requires Medicare Advantage plans, Medicaid programs and the Children's Health Insurance Program (CHIP), including their managed care plans, to send decisions on items and services other than drugs within set deadlines for urgent and standard requests. Those payers must also give a specific reason for a denial, and the tracker saves it for the appeal. Employer plans and most commercial plans sit outside those deadlines, so the board tracks each payer's own pace.
Why do fax logs and spreadsheets leave gaps?
Fax logs and spreadsheets leave gaps because they record what was sent, not what happens next. Nobody sees a request that has sat untouched for days. The date it is needed by lives in one person's head, and when that person is out, the trail goes cold.

Each tool a practice already has covers one slice:
- Payer portals. Each shows its own requests, behind its own login, one payer at a time.
- The records system's order screen. It holds the order, but it has no stages, no owner and no due date.
- A shared spreadsheet. It lists everything, but it never reminds anyone, and it keeps no history of who changed a row.
What is missing is one view across every payer, due dates tied to the schedule, an edit history and a clean report of how long each payer takes. Off-the-shelf prior authorization software often covers the submission but not your office's own follow-up. Forms before the visit belong to patient intake software, and this tracker covers approvals before the service.
What does our prior authorization tracker do?
We build the tracker as a full web application that sits beside your records system. Staff see one board of every request, each with an owner and a due date, and the owner gets a reminder when a request stops moving. Nothing goes to a payer until a staff member has reviewed and submitted it.
- The board. Every request as a card in its stage column, showing patient, service, payer, due date and owner, with filters by payer or owner.
- The needed-by date. Worked back from the scheduled service, using the lead time you set for each payer.
- Stall reminders. When a request has not moved in the time you set, its owner gets a reminder.
- The packet. The app's AI gathers the order, the notes the payer asks for and the patient's plan details into one packet for staff to review and submit.
- History and notes. Every status, call, reference and note on the request, with who logged it and when.
- The payer report. How long each payer takes from submitted to answered, by service, from your own records.
- Access and the log. Only staff who work authorizations open a request, and every view and change is logged.
- The records link. The app reads orders and the schedule from your records system, so nobody switches systems, and it can save each payer's answer back once you turn that on.
We can set up the Admin Agent to draft status checks and send the stall reminders. Staff submit every request, and a clinician decides what care the patient needs. With one plan you get the right to use the software we build, and with another you get full ownership of it, while your patient records stay yours either way.
How is the tracker built and tested?
The tracker is built from a written spec of your services, your payers, your stages and the lead time each payer needs. One authorization coordinator then runs it on live requests beside the old log. Everyone else starts after that pilot passes its checks, with write-back to the records system turned on at the end.
Before anyone else joins, the pilot must clear these six checks on live requests.
- A request for a scheduled visit shows the right needed-by date.
- A request that has not moved in the set time sends a reminder to its owner, and only its owner.
- A packet missing a required note is flagged incomplete before anyone can mark it submitted.
- A status change keeps the old status, who made it and when.
- A login without authorization access cannot open a request.
- The payer report matches a hand count of the pilot's requests.
Under HHS rules on business associates (opens in a new tab), a vendor that handles patient information for a covered provider needs a written agreement on how it may use that information. That agreement is in place before the tracker holds a single patient name.
This is an illustration, not a customer story. Keisha works authorizations at a small physical therapy practice. One Monday, the board showed a request due that week still sitting in pending. The Admin Agent had drafted a status check. Keisha called the payer, learned it wanted the latest visit note and sent it from the packet. She logged the call on the card before lunch, so the request was back in pending with a clear trail.
What stays with your clinicians and staff?
Every care decision stays with your clinicians, every submission stays with your staff, and every coverage answer comes from the payer. The tracker keeps the list, the dates and the paper trail. It never picks a service, changes an order or touches a dose, and it never tells a patient a request will be approved.
- Care. What the patient needs, and what to do after a denial, is the clinician's call.
- Submitting. A staff member reviews each packet and sends it.
- Appeals. The clinician decides whether to appeal, and staff build the file.
- Patient talks. Staff tell patients where a request stands and what comes next.
- Calls with the plan's reviewer. Clinicians handle any call about medical need.
Same team. Same jobs. More capacity.
Frequently asked questions
What is prior authorization?
Prior authorization is a health plan's approval, given before a service, test or drug, that it will cover that care. The practice sends the order and supporting notes, and the plan says yes, says no or asks for more. It is a coverage step, and the clinician still decides the care.
How long does prior authorization take?
Prior authorization takes as long as the payer needs, which depends on the plan, the service and how complete the request is. A federal rule sets decision deadlines for services other than drugs in Medicare Advantage plans and Medicaid and CHIP programs. Other plans follow their own timelines, so tracking each payer's real pace helps you schedule visits.
Who is responsible for prior authorization?
The provider's office is usually responsible for prior authorization, since it orders the service and holds the notes the payer needs. Staff gather and submit the request, the clinician supplies the medical reasons and the payer decides. Patients help by keeping their plan details current with the office.
How do you check prior authorization status?
You check prior authorization status on the payer's portal, by phone or through your clearinghouse, using the reference from the submission. A tracker keeps the last status anyone saw, with the date. Staff then know which requests need a check today instead of calling on every one.
How can you speed up prior authorization?
You cannot make a payer answer sooner, but you can stop losing time on your side. Start the request as soon as the service is ordered, send a complete packet the first time, keep each payer's notes list handy and follow up the day a request stalls. A tracker makes each of those steps visible.
Next step
Book a free workflow consult and bring your current authorization log, whatever shape it is in. We will look at where requests stall and which payers take the longest, then sketch the board, the packet screen and the stall reminders. We work from the Kansas City metro and meet owners face to face or by video call.
Our standards
- The examples in our guides are illustrations, not customer stories.
- Your AI runs on private and on-premise models, not public AI tools, and nothing you give us is used to train AI models.
- Agents are built so each action is logged in a record that shows any later edit.
- Every call and text opens with a short line saying it is the business's AI assistant, and asking for a person always works.
- Texts go only to people who contacted you or gave you permission, and every message says how to stop.
- If anyone may be hurt or in danger, the only instruction an agent gives is to call 911.
- Depending on the investment package you choose, you get either the right to use the software we build for you or full ownership of it.
- We work from the Kansas City metro and meet owners face to face or by video call.
- Same team. Same jobs. More capacity.
About the ScaleAlphaSi team
ScaleAlphaSi is a Kansas City firm specializing in Advanced AI Engineering. We design and build AI agents and custom software for small businesses, trades and growing companies. Each guide draws on our experience with owners and office teams: where AI delivers, where your people stay in charge, and how to begin with a single workflow.
Meet the team

