Before outsourcing prior authorization, ask how a revenue cycle partner will handle your payer mix, clinical documentation, security, urgent cases, performance reporting, and handoffs. Define responsibilities before a staffing problem becomes a new operational risk.
What should you check before outsourcing prior authorization?
Define the partner's scope, payer and specialty experience, clinical handoffs, EHR access, security controls, escalation process and reporting. Put transition and exit responsibilities in writing. Outsourcing administrative tasks does not transfer clinical decisions to the vendor or guarantee payer approval or claim payment.
A vendor says it can take prior authorization off your team's hands. Before you discuss price, ask whose hands will handle the work, what those people can access, and when a request comes back to your clinicians.
Our revenue cycle leakage article looks at the broader financial picture. Prior authorization needs a closer operational review. Outsourcing can shift administrative work, but an unclear handoff can leave your practice chasing the same missing information through another organization.
Use these seven questions to test a revenue cycle management (RCM) partner's proposal before signing.
1. What exactly will you own, and what stays with us?
Ask the partner to walk through one request from the order to the documented payer decision. Does its scope include identifying authorization requirements, assembling submissions, checking status, answering administrative follow-ups, and recording authorization dates and approved units? Are renewals, changed orders, and administrative appeals included or separately priced?
Put ownership in writing. Your practice still needs a named person for scheduling and patient communication. Decide who checks whether an authorization matches the planned service and who handles unresolved requests near the appointment. Treat authorization as one prerequisite, not a guarantee of claim payment.
2. Can you demonstrate experience with our payers and specialties?
A general billing background does not establish fit for your authorization workload. Share your largest payers, common procedures, locations, and request volumes. Ask how the partner tracks plan-specific requirements and distinguishes requirements that vary within the same insurer.
Request a de-identified walkthrough for a service your practice actually orders. An imaging request and a surgical request may need different supporting records and follow-up. Check references from comparable practices, and ask about services the vendor will not support. Specify whether drug authorizations are excluded from your engagement rather than assuming they are covered.
3. How will you obtain complete medical documentation without making clinical decisions?
Ask how staff identify missing records and route questions to the ordering team. The answer should cover clinical notes, relevant results, prior treatment history, and payer-specific documentation requests without promising that software can supply clinical facts missing from the record.
The partner can organize existing documentation and coordinate requests. Your clinicians remain responsible for clinical judgments, accurate documentation, treatment choices, and participation in peer-to-peer reviews. Establish who schedules those reviews and alerts the clinician before a deadline. Reject promises of automatic medical approval: the payer makes the authorization decision, and an administrative vendor cannot guarantee it.
4. How will the workflow fit our EHR and protect patient information?
Have the partner demonstrate where requests, attachments, statuses, and payer responses appear in your electronic health record (EHR). Identify duplicate entry and interfaces requiring separate implementation. Review the HIPAA business associate agreement (BAA), subcontractors, named-user access, multifactor authentication, audit logs, incident notification, and access removal with your privacy and security leads. A signed BAA does not replace that review.
CMS-0057-F applies to specified payers, including Medicare Advantage, Medicaid and CHIP programs and plans, and qualified health plans on federally facilitated exchanges, not all commercial insurers. Its prior authorization provisions exclude drugs. Operational requirements generally began January 1, 2026; application programming interface (API) compliance dates generally begin January 1, 2027, with timing varying by payer type.[1] Ask about actual payer connectivity and your EHR's readiness, not a blanket compliance guarantee.
5. What happens when volume rises or an urgent request stalls?
Ask for staffing assumptions tied to your workload, including coverage hours, absences, seasonal peaks, and limits on backlog acceptance. A sales commitment is not a capacity plan. Identify the supervisor who can reassign work when the queue grows.
Agree on escalation triggers for unanswered payer requests, missing clinical records, and approaching service dates. Define how clinically urgent cases reach your clinical team promptly; vendor staff should not independently decide clinical urgency. Record who contacts the patient and who has authority to change scheduling. Request a fallback process for portal outages and unavailable staff.
6. Which metrics will show whether the arrangement works?
Start with a baseline from your own operation. Request reporting by payer and service type on submission timeliness, incomplete submissions, pending-request age, authorization-related rescheduling, and denials attributable to authorization issues. Define the denominator and start and stop points for each measure.
Separate time awaiting practice documentation from time awaiting the payer. Otherwise, a fast average can hide a growing unresolved queue. Ask for case-level drilldowns and a regular review of exceptions. Include team turnover, training, and account handoffs in those conversations. Staff replacement can affect continuity even when headline metrics look stable.
7. How will we maintain continuity and leave the contract safely?
Review implementation and exit together. Specify who works existing requests during transition, when the partner assumes new work, and how duplicate submissions will be prevented. Keep a practice owner accountable for monitoring the handoff.
The contract should address fees, scope changes, service commitments, termination notice, transition support, and data export. Require a usable record of open requests, attachments, authorization identifiers, expiration dates, and next actions. Set responsibility for returning or deleting patient information and revoking access, including subcontractor access. Have counsel review the terms before your existing process is dismantled.
A five-point due diligence checklist
- Document task ownership and exclusions.
- Test payer and specialty fit with real workflows.
- Review documentation handoffs, the BAA, and security controls.
- Agree on capacity, escalation, and measurable reporting.
- Set continuity and contract exit responsibilities.
Conduit Bridge Advisory connects organizations with partners rather than operating a billing department. Explore our healthcare advisory focus and available solutions, then schedule an advisory consultation to discuss your requirements before evaluating vendors.