A Prior Authorization Tracking Checklist for Medical Practices

A prior authorization request can fail even when the planned service is appropriate. Common operational causes include using the wrong payer channel, missing clinical records, mismatched codes or dates, an incomplete response to a request for information, or an approval that does not match the service ultimately scheduled. A tracking checklist helps the practice find those gaps before the appointment or claim.

CMS rules that took effect for impacted payers in 2026 require a specific reason when a prior authorization request is denied. The same federal rule includes decision-timeframe and public-metrics requirements for specified payer groups, while API requirements generally begin in 2027. These provisions do not make every payer, plan, drug, or service follow one process. Your tracker should preserve payer-specific details.

Build one record for each authorization

Scattered portal screenshots, inbox messages, and notes make it difficult to see what is pending. Create a single authorization record in the system your team already uses. Limit access to staff who need the information and follow your organization’s privacy and security procedures.

At minimum, capture:

• Patient and payer identifiers needed for the workflow
• Payer, plan, and product type
• Ordering and rendering provider
• Requested service, codes, units, frequency, and site of service
• Scheduled date and the date the request was submitted
• Submission channel, confirmation or reference number, and assigned owner
• Records sent, payer requests for more information, and response dates
• Status, decision, authorized dates and units, denial reason, and next action

Step 1: verify the requirement before submitting

Confirm active coverage and identify the exact plan. Then check whether the planned service requires authorization, notification, a referral, step therapy, or a site-of-service review. Use the payer’s current provider portal, medical policy, provider manual, or other authoritative instruction. Record the source and review date.

Do not treat a prior authorization as a substitute for eligibility, benefits, coverage, coding, or medical necessity review. It is one part of the payment workflow, and payer notices commonly state that authorization does not guarantee payment.

Step 2: match the request to the scheduled service

Before submission, compare the order and schedule with the proposed codes, units, frequency, provider, location, and date range. If the service changes after submission, decide whether the existing request must be updated or replaced. A small mismatch can create a denial even when an approval number exists.

Step 3: send a complete, traceable request

Use the payer’s required channel and include the documentation requested for that service. Save the submission confirmation, a list of attachments, the date and time, and the payer reference number. Avoid recording unnecessary clinical information in a general tracking sheet; link authorized users to the appropriate record instead.

Step 4: manage follow-up by due date

Give every open request a next-follow-up date rather than waiting for the appointment day. The date should reflect the payer’s stated timeframe, the scheduled service, and the urgency supported by the clinical situation. Escalate overdue requests according to the payer’s process and document who was contacted and what was said.

A practical queue uses clear statuses such as not started, submitted, additional information needed, under review, approved, denied, withdrawn, or expired. Define each status so that staff use them consistently.

Step 5: resolve requests for additional information

Route clinical questions to qualified clinical staff. The billing or authorization team can identify what the payer says is missing, but it should not create clinical facts or direct a clinician toward an unsupported conclusion. Record the exact request, the response owner, the deadline, what was sent, and the new confirmation number.

Step 6: validate the decision before the visit

For an approval, compare the authorization notice with the scheduled service. Confirm the approved codes or service description, units, dates, provider, facility, and any conditions. Store the authorization number where the claim team can find it. For a denial, record the payer’s specific reason and the review or appeal instructions, then coordinate the next step with the ordering clinician and patient-facing team.

Step 7: reconcile the authorization with the final claim

After the service, make sure the claim reflects what actually occurred. Check the authorization record when the billed code, units, provider, location, or date differs from the original request. Route discrepancies for review before releasing the claim rather than copying an authorization number onto a claim it may not cover.

Use a short daily and weekly routine

Daily, review requests approaching their follow-up or service dates, new payer messages, and cases waiting for records. Weekly, review aging by status, denials by payer and reason, expired approvals, and cases repeatedly returned for missing information. Assign one owner and one dated next action to every exception.

FlowClaim supports practices with prior authorization tracking, eligibility verification, and denial management. Request a free billing audit to review where authorization handoffs may be creating delays or rework.

Frequently asked questions

Does an authorization number guarantee payment?

No. Confirm the approved scope and other applicable coverage and billing requirements. The approval must be compared with the service actually performed.

Who owns a pending authorization?

Assign one accountable coordinator while clinical and administrative staff complete their parts. The coordinator tracks deadlines, missing information, and the next action.

What happens if the planned service changes?

Compare the new plan with the approval and obtain payer guidance on whether an update or new request is required. Do not assume the old approval covers the change.

Sources

• CMS: Interoperability and Prior Authorization Final Rule
• CMS: Final Rule Fact Sheet
• CMS: Improving Prior Authorization Processes

Editorial note: Requirements vary by payer, plan, service, and date. Confirm current instructions directly with the payer before changing a workflow or making a coverage decision.

← Back to all articles