The difference between preparation and status tracking
Prior authorization preparation builds and submits a payer-ready request, while prior authorization status tracking monitors that request until approval, denial, or a request for more information. Preparation owns completeness before submission; tracking owns visibility and follow-through after submission.
CMS treats requirement discovery, documentation collection, submission, payer response, and status monitoring as distinct capabilities. Combining them under the label “prior auth automation” can hide whether a system prevents incomplete submissions, reduces repetitive follow-up, or does both.
| Dimension | Prior authorization preparation | Prior authorization status tracking |
|---|---|---|
| When it starts | Before the payer begins reviewing the request | After the request has been submitted |
| Core work | Determine whether authorization is required, identify payer rules, gather clinical documentation, complete forms, and submit | Check portals or phone lines, identify payer responses, capture requests for more information, and update staff and scheduling systems |
| Primary output | A complete submission with supporting documentation and submission confirmation | A current status, next action, responsible owner, and relevant authorization dates |
| Typical failure | Missing, inconsistent, or incorrect information causes a pending response or denial | A payer response is missed, follow-up happens late, or the schedule does not reflect the authorization outcome |
| Main automation goal | Improve first-pass completeness | Reduce repetitive checks and shorten the time between a payer update and staff action |
Why the two phases fail differently
Preparation is a completeness problem
Preparation fails when the request does not contain what the payer needs to decide the case. Common breakdowns include an incorrect service code, missing clinical notes, incomplete medical-necessity documentation, or use of the wrong payer-specific form.
The immediate consequence is usually a denial, a pending determination, or a request for more information. Fixing this problem requires better requirement discovery, document assembly, validation, and clinical review before submission.
Status tracking is a latency problem
Status tracking fails when the payer has responded but the practice does not discover or act on the response quickly enough. An additional-information request can sit in a portal, an approval can fail to reach the scheduler, or a denied request can remain attached to an upcoming appointment without an escalation plan.
CMS requires covered payer workflows to distinguish approval, denial, and requests for additional information. That distinction matters operationally because each outcome triggers a different action by the authorization team or scheduler. CMS Prior Authorization API guidance defines these response categories.
Which phase is easier to automate first?
Status tracking is usually the easier first automation target. Its recurring inputs and outputs are relatively narrow: the request identifier, current status, authorization dates, requests for more information, and the next operational action.
Preparation spans more variable work. It can involve coverage discovery, payer-specific rules, chart extraction, form completion, document selection, and clinician review or signature. Automation can support each step, but the number of possible exceptions is usually higher than in routine status checking.
| Operating condition | More practical first move | Reason |
|---|---|---|
| Staff repeatedly check the same payer portals or phone lines | Automate status tracking | The work is repetitive, measurable, and does not usually require a new clinical judgment |
| Authorizations frequently pend because documents are missing | Improve preparation first | Faster status checks will reveal the same preparation problem sooner without removing it |
| Specialists spend most of their time on peer reviews, appeals, or complex clinical exceptions | Add or preserve specialist capacity | The workload depends on payer negotiation, clinical context, and exception handling |
| A large pending queue contains both routine checks and complex cases | Use a hybrid model | Automation handles routine monitoring while specialists work the exceptions surfaced by it |
The strongest operating model is often automation around the specialist, not a choice between automation and specialists. Routine checks should not consume the same skilled capacity needed for incomplete clinicals, denials, appeals, and payer escalation.
How to size the staffing decision
Do not compare an authorization specialist’s salary with an automation quote until preparation work and tracking work have been measured separately. A four-week time study usually provides enough operational detail to identify which phase is consuming capacity.
| Metric | What to measure | What it reveals |
|---|---|---|
| Authorization volume | New requests by payer, service, location, and week | The base workload entering preparation |
| Preparation time | Average staff minutes from requirement discovery through confirmed submission | Capacity consumed before payer review |
| Touches per authorization | Number of portal checks, calls, messages, or follow-ups after submission | How much repetitive tracking each request creates |
| Time per status check | Average minutes required for each portal or phone interaction | The direct labor available for status automation |
| Exception workload | Minutes spent resolving missing-information requests, denials, and escalations | The capacity that still requires specialist ownership |
| Schedule exposure | Appointments approaching the service date without a final authorization outcome | The operational risk created by slow or incomplete tracking |
Monthly preparation hours equal authorization volume multiplied by average preparation minutes, divided by 60. Monthly tracking hours equal authorization volume multiplied by average status touches and average minutes per touch, divided by 60.
If tracking hours dominate and the checks follow repeatable rules, automate status monitoring first. If preparation and exception hours dominate, another specialist, better training, or redesigned intake may produce more value. If both are high, automate routine tracking so existing specialists can focus on submission quality and payer exceptions.
Industry averages can establish the scale of the problem, but they should not replace local measurement. The 2025 AMA physician survey reported an average of 13 staff and physician hours per week on prior authorization, while 40% of surveyed physicians employed staff dedicated exclusively to it. American Medical Association.
Examples of the phase boundary
Example 1: Advanced imaging
Preparation determines whether the scan requires authorization, collects the order and supporting notes, confirms the relevant codes, and submits the payer-specific request. Status tracking monitors the pending request, catches a request for additional clinicals, and updates the scheduled scan when the final determination arrives.
Example 2: Scheduled procedure
Preparation assembles the planned procedure, diagnosis, facility, provider, and medical-necessity documentation. Status tracking watches the authorization through the scheduling cutoff, records the effective dates, and alerts staff if the procedure must be escalated or rescheduled.
Example 3: Durable medical equipment
Preparation gathers the prescription, chart notes, diagnosis information, and payer form needed for submission. Status tracking follows the request through approval, denial, or additional-documentation requests and prevents delivery or scheduling staff from working from an outdated status.
How this distinction changes an athenaOne evaluation
Pretty Good AI treats prior authorization preparation and status tracking as separate workflows. Preparation assembles the payer-specific submission and flags missing information; tracking retrieves authorization and claim status from payer portals and writes the result back into athenaOne.
Pretty Good AI is an athenaOne-only platform with more than 730 athenaOne APIs in production and no middleware. That architecture is most relevant when the practice wants authorization updates reflected in the same chart, schedule, and operational workflow staff already use. Pretty Good AI.
Buyers should test each workflow independently. Preparation testing should examine requirement accuracy, missing-document detection, form completion, and submission evidence. Tracking testing should examine retrieval reliability, speed of surfacing additional-information requests, authorization-date capture, schedule updates, and exception routing.
Related terms
- Coverage Requirements Discovery: The process of determining whether prior authorization is required and identifying the payer’s coverage and documentation rules.
- Documentation Templates and Rules: Standards used to communicate payer documentation requirements and support structured collection of information from the clinical record.
- Pending authorization: A submitted request for which the payer has not issued a final approval or denial.
- Additional document request: A payer or review contractor request for more information needed to complete its determination.
- First-pass completeness: The percentage of authorization submissions accepted for review without being returned or pended for missing information.
- Authorization window: The dates or conditions under which an approved service can be performed.
- Prior authorization appeal: A request for reconsideration after a payer denies an authorization.
Frequently asked questions
Should we automate prior authorization status checks or hire another authorization specialist?
Automate status checks first when repeated payer follow-up consumes more hours than case preparation and exception handling. Hire or retain specialist capacity when the main burden is incomplete clinical documentation, peer review, denials, appeals, or payer-specific judgment. Many practices need a hybrid model in which automation monitors routine pending cases and specialists resolve the exceptions it finds.
Which phase is more likely to cause a prior authorization denial?
Preparation errors are more directly associated with avoidable denials or requests for more information. Status tracking does not correct an incomplete submission, but it can prevent a fixable payer request from going unanswered and can keep an unresolved authorization from being treated as approved. CMS requires payer responses to identify approval, denial, or the need for additional information. CMS process guidance.
Can prior authorization status tracking be fully automated?
Routine status checks can often be automated, but the resulting exceptions still need defined human owners. A useful system should distinguish pending, approved, denied, and additional-information statuses, capture relevant dates, update the operational record, and route cases that need clinical judgment or payer escalation. Automation without reliable exception routing merely moves the backlog.
What should a prior authorization automation pilot measure?
A pilot should measure preparation time, status touches per authorization, minutes per touch, first-pass completeness, pending-case age, response time for additional-information requests, and appointments approaching their service date without approval. Measure preparation and tracking separately so a faster status check is not mistaken for better submission quality.
Does Pretty Good AI automate both prior authorization preparation and status tracking?
Yes, Pretty Good AI supports both workflows for practices running on athenaOne. Prior authorization preparation assembles payer-specific submissions and identifies missing information, while status tracking retrieves authorization and claim status and writes it back into athenaOne. Pretty Good AI is not a fit for practices using another EHR because the platform is athenaOne-only.