General operational information only. Payer, state, contractual and regulatory requirements vary. Confirm current requirements with the applicable payer or agency.
Quick answer
What practice leaders need to know
Prior authorization works best when one team owns intake completeness, submission, follow-up, decision capture and the handoff to scheduling and billing. The record should connect the approved service, provider, location, dates and units to the care and claim that follow.
Confirm coverage, provider and service before intake
Validate the patient, plan, network arrangement, ordering or rendering provider, location and planned service before building the request. Determine which payer or delegated administrator manages authorization and which submission channel applies. Do not assume that a requirement from one product applies to every plan under the same insurer. If eligibility, enrollment or network information is unresolved, label the dependency and escalate it instead of submitting with guessed identifiers. Record the source and date of the requirement check because policies change. This first control prevents teams from collecting extensive clinical records for the wrong entity or discovering after submission that the request used an inactive provider relationship.
Create a complete intake standard
Define the administrative and clinical elements required before a request is ready. These may include the order, diagnosis, planned service, codes when appropriate, frequency or units, provider and facility, requested dates, relevant notes and prior treatment information. Requirements differ by payer and service, so use a current matrix and the payer's official instructions. Mark missing items by owner and due date. Administrative staff should not invent clinical rationale, and clinical staff should not be expected to navigate every payer portal without a clear handoff. A complete intake checklist reduces preventable requests for additional information and makes later follow-up more precise.
Separate clinical judgment from administrative coordination
The treating or ordering clinician supplies and validates clinical information, while authorization staff coordinate payer requirements, submission evidence and status. Define who may discuss medical necessity, participate in peer review or approve changes to the treatment request. Preserve the clinical record and avoid altering it merely to match a payer's preferred wording. Administrative teams can identify missing documents and deadlines but should not make unsupported clinical conclusions. The handoff should show exactly what the payer requested, when it is due and who will respond. Clear boundaries protect accuracy while allowing each team to work efficiently.
Submit through the correct channel and retain proof
Use the payer-designated portal, transaction, fax or other approved route and confirm that the request reached the intended department. Retain the submission date, confirmation, reference number, documents sent and responsible staff member. Protect clinical information through appropriate secure methods and verify recipient details. A sent fax or portal upload is not the same as payer receipt, so review confirmation and follow up when the request cannot be located. Do not resubmit repeatedly without identifying whether the payer rejected, lost or misrouted the original request; duplicates can create conflicting records and slower resolution.
Track status with a next action
Use controlled states such as intake incomplete, ready to submit, submitted, payer review, additional information requested, peer review, approved, partially approved, denied, withdrawn or expired. Every open request should show the payer's current status, evidence, owner, next action and follow-up date. Pending alone is not actionable. Record the payer's stated response window and applicable deadline without promising an outcome date the practice does not control. Escalate requests that are missing from the payer system, approaching the planned service date or waiting on a practice dependency. A shared tracker prevents status from living in one inbox or staff member's memory.
Manage payer requests for additional information
Route clinical questions to the appropriate clinician with the exact payer request, secure delivery method and due date. Administrative staff can coordinate the response and confirm receipt, but the clinician should validate clinical content. Track what was sent and avoid disclosing unrelated information. If the payer's request is unclear, ask for clarification and document the conversation. Repeated requests may signal that the original intake checklist or submission route is incomplete. Review the pattern after the immediate case is handled so the workflow improves rather than treating every request as a new emergency.
Capture the complete payer decision
An approval record should identify the authorization number, service, codes when specified, provider, facility or location, approved dates, frequency, units or visits and conditions. A partial approval should make the difference between requested and approved care visible to the clinical team. A denial record should include the reason, notice date, reference, available review or appeal route and deadline. Preserve the written notice rather than relying only on a portal status. Authorization does not guarantee payment because eligibility, documentation, coding and other claim requirements still apply, and the delivered service must match the approval.
Control the scheduling and clinical handoff
Scheduling staff should see whether the service is approved, pending, denied or subject to a documented exception before confirming care that depends on authorization. Clinical teams need the approved scope and remaining units without searching billing notes. Define who may release a hold and how urgent clinical needs are escalated. When the provider, location, date or treatment plan changes, determine whether the existing decision remains valid before care continues. The workflow should support informed decisions without allowing administrative status to replace clinical judgment or emergency-care obligations.
Monitor approved dates and utilization
Track used and remaining visits or units, the authorization period and any review requirements throughout the episode. Connect completed services to the authorization record promptly so the balance is not discovered after the limit has been exceeded. When treatment changes, route the revision to the clinician and payer before relying on the original approval. Build alerts with enough lead time for reassessment and submission. Utilization tracking should reflect actual delivered services and documented payer rules; it should not pressure clinicians to use approved units that are not medically necessary.
Route adverse decisions through the correct path
Review the denial or partial approval, payer reason, evidence and deadline before selecting correction, reconsideration, peer review, appeal or another available route. Confirm who is permitted to act and which clinical participation is required. Submit through the designated channel and retain proof. Avoid generic appeals that do not address the payer's stated reason. Qualified clinical and legal guidance may be needed for complex cases, and patient rights or notices must be handled according to applicable requirements. Track the outcome and whether the cause was preventable, policy-based or dependent on clinical review.
Measure timeliness, completeness and prevention
Track incomplete intake, submission lag, payer requests for additional information, decision turnaround, expiring approvals, authorization-related denials and requests without a next action. Compare by payer, service, provider and location and interpret results against current requirements. The CMS interoperability and prior-authorization rule establishes requirements for certain impacted payers and implementation dates, but practices should verify which provisions and payers apply. Use performance data to update checklists, payer matrices and ownership—not to promise that every request will be approved or decided within one universal time frame.
Prepare for payer and technology changes
Assign owners to monitor official payer notices, portal changes, transaction options and material regulatory implementation dates. Before changing the workflow, confirm which payer products and request types are affected, test the new route and retain the prior process for requests already in flight when needed. Train staff using realistic scenarios and update patient-facing explanations. Technology may reduce manual steps, but it does not eliminate the need to validate clinical information, capture the complete decision and connect it to scheduling and billing. Review access and audit logs whenever a new vendor or interface handles protected health information.
Maintain a quality sample
Periodically review a sample of approved, denied and still-pending requests from requirement check through claim. Confirm that evidence is present, dates and units match, clinical requests reached the right owner and the final decision was visible to downstream teams. Include urgent and changed-service examples rather than reviewing only straightforward approvals. Record defects by workflow stage and assign corrective action. Quality review can reveal that a high approval rate coexists with missing documentation, weak handoffs or avoidable claim denials, giving leadership a more complete view than volume alone.
Working reference
Prior authorization ownership map
Assign one accountable owner at every stage, even when several teams contribute.
| Stage | Primary responsibility | Required output |
|---|---|---|
| Requirement check | Patient access or authorization team | Document whether authorization is required |
| Clinical intake | Ordering clinician and authorization team | Complete order and supporting clinical information |
| Submission | Authorization team | Payer confirmation, reference and submission date |
| Follow-up | Authorization team | Current status, dependency and next follow-up |
| Decision handoff | Authorization team to scheduling and billing | Approved details, denial path or service hold |
| Utilization control | Clinical operations and authorization team | Track approved dates, services and units |
Common questions
Questions practice teams ask
Does prior authorization guarantee payment?
No. Payment still depends on eligibility, benefits, network, documentation, coding and other payer requirements.
Who should provide clinical documentation?
The clinician supplies the clinical record while the authorization team coordinates payer requirements, submission and follow-up.
Can changing the provider or location affect approval?
Yes. Verify whether the authorization is tied to a specific provider, facility, service or setting.
What details should be tracked after approval?
Track the authorization number, approved service, provider, location, dates, units, conditions and payer reference.
What should happen after a denial?
Review the reason and deadline, then determine whether correction, additional documentation, peer review or appeal is available.
Primary references
Sources and further reading
Requirements can change. Use these primary sources to confirm the current rule that applies to the payer, service and date of care.
Ready to turn this guidance into action?
Tell us what is happening in your practice, and we will help you identify the most useful next step.