Prior authorization is the single most operationally disruptive element of behavioral health revenue cycle management. For programs operating at higher levels of care — partial hospitalization, residential, and detoxification — the combination of initial authorization requirements, concurrent review obligations, and level-of-care change authorizations creates an administrative burden that, when managed poorly, produces significant revenue loss through expired authorizations, medical necessity denials, and authorization-to-billing mismatches.
The programs that manage authorization most effectively treat it as a revenue cycle function — not a clinical administrative task. Authorization management requires defined workflows, accountable ownership, real-time tracking systems, and documentation practices that are built around payer requirements, not clinical convenience.
What Is Prior Authorization in Behavioral Health?
Prior authorization (also called prior approval, pre-authorization, or pre-certification) is a requirement by payers that providers obtain approval before delivering certain behavioral health services in order for those services to be covered. The authorization requirement exists primarily for higher-intensity services — residential treatment, partial hospitalization, intensive outpatient at some payers, detoxification, and psychiatric inpatient — where payers exercise utilization management to validate medical necessity before committing to payment.
Outpatient behavioral health services (individual therapy, medication management, standard outpatient SUD treatment) typically do not require prior authorization under most commercial payer plans. However, as payers have expanded utilization management programs, authorization requirements have extended to services that previously didn't require approval — including telehealth behavioral health at some payers and applied behavior analysis (ABA) services for autism spectrum disorder treatment.
The Most Common Prior Authorization Failures in Behavioral Health
Authorization failures that result in revenue loss fall into several predictable categories:
Authorization not obtained before services begin. Programs that admit clients before confirming authorization status — or that assume authorization has been granted based on a phone verification — routinely generate claims for services that were never authorized. Payers deny these claims as unauthorized services, and appeals for retroactive authorization are granted inconsistently and infrequently.
Authorization expiration before claim is filed. Authorizations are granted for specific date ranges. When billing processes are delayed — due to documentation backlogs, staffing gaps, or billing system failures — claims are sometimes submitted after the authorization period has expired. Most payers deny expired authorization claims, and retrospective authorization requests are rarely approved.
Services billed don't match the authorized level of care. When a client transitions from one level of care to another — from PHP to IOP, or from residential to PHP — a new authorization for the new level of care must be obtained before the transition. Programs that bill the new level of care under the old authorization generate level-of-care mismatch denials that are time-consuming and inconsistently successful on appeal.
Concurrent review documentation doesn't meet payer standards. For authorized services, payers require periodic clinical documentation demonstrating continued medical necessity. Documentation that doesn't substantiate ongoing medical necessity at the level being billed results in authorization denial at the concurrent review stage — cutting off authorization for future dates of service and potentially triggering recoupment of previously paid claims.
Building an Authorization Management System
Effective authorization management requires three components working together: a tracking system, a documentation workflow, and defined accountability.
Authorization tracking. Every client's authorization status must be visible in real time — including what's authorized, the date range of authorization, the number of authorized units remaining, and the deadline for the next concurrent review submission. Programs that manage this in spreadsheets or rely on staff memory produce authorization failures at predictable rates. An EMR configured to surface authorization status at the point of service, or a dedicated authorization tracking system, is necessary for programs with more than a handful of authorized clients.
Concurrent review documentation workflow. Concurrent review submissions must be scheduled, assigned, and tracked as a defined operational process. The documentation submitted for concurrent review — typically a clinical summary or treatment update — must be prepared by clinical staff who understand what payers are looking for: current ASAM dimensional severity, active treatment plan goals, clinical progress, and a continued stay rationale. Programs that submit generic progress summaries that don't address payer utilization management criteria consistently experience higher concurrent review denial rates.
Authorization accountability. Someone in the organization must own authorization management — tracking expiration dates, initiating re-authorization requests in advance, coordinating concurrent review submissions, and managing denials when they occur. At programs with significant authorized census, this is a dedicated role. At smaller programs, it's a defined responsibility of an existing staff member with protected time for the function.
Concurrent Review and Medical Necessity Documentation
The documentation submitted for concurrent review is the primary determinant of whether authorization continues for ongoing services. Payers conducting utilization management for behavioral health — particularly for residential and PHP levels of care — evaluate documentation against specific criteria that align with ASAM dimensional severity.
Effective concurrent review documentation demonstrates: current presenting problems and symptoms at a severity level that justifies the level of care; active, individualized treatment plan goals directly tied to those presenting problems; clinical progress (or documented lack of progress with clinical rationale); barriers to stepping down to a lower level of care; and a specific plan for the remainder of the treatment episode including anticipated discharge criteria.
The most common concurrent review documentation failure is progress notes that describe what happened in treatment — groups attended, topics covered, client engagement — without documenting the clinical severity and treatment plan alignment that payers are specifically evaluating. Building progress note templates and clinical documentation standards that produce utilization-review-ready records as standard clinical practice is one of the highest-leverage investments a behavioral health program can make in its authorization performance.
Managing Authorization Denials
When concurrent review results in authorization denial, programs have defined appeal rights under their payer contracts and under state and federal parity laws. The appeal process for authorization denials typically involves: a peer-to-peer review request (a direct clinical conversation between the treating clinician and the payer's medical director), a formal written appeal with additional clinical documentation, and — if the internal appeal is unsuccessful — an external independent review.
Peer-to-peer reviews, when conducted by clinicians who understand ASAM criteria and can articulate dimensional severity in clinical terms, overturn initial denials in a significant percentage of cases. Programs that escalate to peer-to-peer consistently — rather than accepting initial concurrent review denials — recover meaningfully more authorization revenue than those that don't.
Frequently Asked Questions: Behavioral Health Prior Authorization
What behavioral health services require prior authorization?
Prior authorization requirements vary by payer and plan. Generally, higher-intensity behavioral health services — residential treatment, partial hospitalization, detoxification, and psychiatric inpatient — require prior authorization. Some payers also require authorization for intensive outpatient, ABA services, and certain medication-assisted treatment protocols. Outpatient therapy and medication management typically don't require prior authorization under most commercial plans, though this varies.
What happens if I provide services without prior authorization?
Payers typically deny claims for services provided without required prior authorization. Retroactive authorization is available from some payers in limited circumstances — usually for emergency situations or administrative errors — but is not routinely granted and should not be relied upon as a billing strategy. Services provided without authorization in non-emergency situations generally result in permanent revenue loss.
How far in advance should I request prior authorization?
Authorization requests for planned admissions should be submitted as early as possible — ideally 2–5 business days before the anticipated admission date for non-urgent situations. For urgent or emergent admissions, most payers allow concurrent authorization requests submitted within 24–72 hours of admission. Re-authorization for ongoing services should be initiated at least 5–7 business days before the current authorization period expires to allow for processing time and to avoid gaps in authorization coverage.
Authorization readiness and fast insurance verification also directly influence how many inquiries convert to admits. For a complete view of how front-end operations affect census, see our guide on growing behavioral health census through a better admissions process.
Saint Health Group builds authorization management systems for behavioral health programs — from tracking infrastructure through concurrent review documentation workflows and denial management processes. Learn more about our behavioral health revenue cycle management services or contact us to discuss your organization's authorization challenges.