Utilization management
Utilization management is the payer process that controls if, when, and how much care is approved as medically necessary and covered. Utilization management drives prior authorization, concurrent review, and continued-stay decisions that can override clean billing data.
What it means
What utilization management is
Utilization management is the payer's gatekeeping process for medical necessity and level of care. It covers activities like prior authorization, admission review, concurrent or continued-stay review, and discharge planning, all against the payer's clinical criteria and policies.
UM teams are usually separate from claims-processing teams. A claim can be perfect from a coding and data perspective, but if UM has not approved the level of care, service dates, or units, the claim still denies or pays at a lower rate.
In behavioral health, UM is often driven by criteria sets like ASAM, LOCUS, or CALOCUS, combined with payer-specific policies about what services and lengths of stay they consider necessary.
Why utilization management matters operationally
UM decisions control revenue long before a claim hits the 837 file. If a pre-cert is missed, concurrent review is late, or documentation does not match UM criteria, you see denials like CO-197 or CO-50, shortened authorized stays, or downgraded levels of care.
Operationally, weak UM management shows up as:
- High authorization-related denials and avoidable write-offs
- Shortened stays that leave unused bed-days or empty group slots
- Long, uncertain AR tails while your team chases retro auth or appeals
- Clinical staff pulled into back-and-forth with payers instead of treatment
Strong coordination with UM reduces preventable denials, stabilizes census, and makes your appeals effort more strategic instead of frantic case-by-case firefighting.
How utilization management shows up in daily workflows
For revenue cycle and program leaders, UM is not just a clinical or UR department issue. It touches multiple workflows:
- Intake and benefits verification: Confirm if services require prior authorization, which UM vendor handles BH, what criteria they use, and how many days or units they typically approve on the first request.
- Admission and initial auth: Match presenting symptoms and risk to an appropriate level of care, then obtain an authorization that covers the right dates, setting, and units. Capture auth details in the EHR or billing system in structured fields.
- Concurrent or continued-stay review: Track when each case is due for review and what documentation the payer expects. If concurrent UM is late, days past the last approved date are at high risk for CO-197 denials even if you later get clinical agreement.
- Discharge planning and step-down: Align discharge timing and step-down level of care (PHP, IOP, OP) with UM approvals, so you are not providing non-authorized days or levels of care that will be written off.
- Denials and appeals: When UM drives denials, your team needs to spot the pattern quickly, coordinate peer-to-peer reviews, and prepare appeals that speak to the UM criteria used, not just coding rules.
Clean claims and accurate coding cannot fix a broken UM process. If you do not treat UM as a core part of revenue cycle, you leave cash on the table and increase audit and recoupment risk when documentation does not support what UM approved.
Common mistakes
- Letting UM live entirely in the clinical or UR team, so admissions get authorized verbally but no one enters the auth number, auth span, or unit limits into the billing system. Claims then hit CO-197 or CO-32, even though someone technically got an approval.
- Assuming a single authorization number means the entire residential or PHP episode is covered, instead of tracking the specific start and end dates and max days. Days 21 through 30 bill out, but UM only approved through day 20, so those units deny as not authorized.
- Sending concurrent review packets without tying them to specific requested dates, so the payer cuts the approval short or only approves partial units. Billing then submits all days and has to manage partial denials and complex recoups mid-episode.
- Ignoring the payer's stated criteria set, such as ASAM or LOCUS, when building documentation templates. Progress notes look clinically solid but do not hit the boxes UM reviewers need, and you see repeated medical-necessity or level-of-care downgrades.
- Treating all UM denials as one bucket in your denial reporting, so you cannot separate true medical-necessity denials from preventable misses like late concurrent review or using the wrong UM vendor for a behavioral-health carve-out plan.
Why it matters in behavioral health
In behavioral health, utilization management is especially aggressive due to high-cost levels of care and long episodes. Payers often use ASAM or LOCUS-based criteria to continually question whether a member still needs residential, PHP, or IOP, and they may shorten stays even when you have capacity and clinical buy-in.
Carve-out behavioral-health plans add another layer. A member's medical benefits might sit with a major commercial payer, while a separate behavioral-health vendor runs UM, prior auth, and concurrent review. If intake only checks the medical plan, you can admit and treat for days before anyone realizes a separate UM team should have been authorizing care.
State Medicaid and Medicaid managed care organizations rely heavily on UM for SUD and MH services. For withdrawal management, residential, and intensive outpatient, they may require tight concurrent review schedules and state-specific criteria that differ from commercial payers. Miss a review by even a day, and per-diem claims for that span can deny as non-authorized or medically unnecessary, with limited appeal rights.
Per-diem residential and PHP/IOP claims multiply the impact of UM mistakes. One missed or shortened authorization can impact weeks of daily billing. That is why BH providers often need closer coordination between UR, clinical, and billing teams than a typical medical specialty.
How AI can help with Utilization management
AI can help with utilization management by keeping track of the maze of payer rules and the timing details humans usually manage in spreadsheets. An agent can read eligibility responses and payer policies, flag when a level of care requires prior auth, track when concurrent review is due for each patient, and cross-check scheduled services against what UM has actually approved.
Supabill's agents can pull in benefits and authorization details during intake, tie auth spans to specific episodes, and monitor 835 remits to classify UM-related denials like CO-197 or CO-50. That frees your human team to focus on higher-value tasks, such as preparing strong clinical summaries and handling peer-to-peer reviews. Judgment calls about whether to push for continued stay, how to frame an appeal, or when to step a patient down in level of care still sit squarely with clinical and UR leaders, not the AI.
FAQ
How is utilization management different from utilization review?
Utilization management is the broader program payers use to control use of services, including policies, criteria, and workflows. Utilization review is the case-level activity of reviewing a specific admission, continued stay, or service against those UM rules.
Who should own utilization management in a behavioral-health facility?
Clinically, UM is usually owned by a UR or clinical team, but revenue cycle leaders need a tight partnership. Ideally, UR manages clinical discussions with payers and criteria, while RCM tracks auth numbers, spans, and denials so missed UM steps do not quietly erode revenue.
Can I bill if the payer's utilization management team has not approved the stay yet?
You can submit a claim, but there is a high risk the claim will deny for no authorization or medical necessity if UM has not signed off. For high-cost BH levels of care, billing before UM approval usually just pushes costs to denials and appeals.
What documentation helps with utilization management approvals in behavioral health?
Documentation that clearly ties symptoms, risk, and functioning to a specific level-of-care standard, such as ASAM or LOCUS, is most effective. Detailed risk assessments, failed lower levels of care, and measurable progress or lack of progress tend to carry more weight with UM reviewers than narrative alone.
Why do I still get denials if I have an authorization number?
An authorization number only covers what the payer approved: certain dates, levels of care, and units. If you bill outside those limits, use the wrong UM vendor for a carve-out plan, or your documentation does not support medical necessity, payers can still deny or downgrade the claim.
Related terms
Prior authorization is a payer requirement to obtain approval before delivering specific services, confirming that planned care is medically necessary and covered under the member's benefit. Prior authorization is typically required for higher-cost, high-utilization, or ongoing treatment and is a common denial trigger when missing or expired.
Utilization review (UR) is the clinical and administrative process payers and providers use to decide whether services are medically necessary, at the right level of care, and for how long. Utilization review drives prior authorizations, concurrent reviews, day limits, and many medical-necessity denials.
Continued stay review (CSR) is a payer-required clinical and utilization review used to decide whether days or units beyond the initial authorization will be approved. CSR determines if a patient can remain at the same level of care, step down, or be denied further covered days.
Authorization denial is a payer decision to deny some or all claim lines because required prior authorization, precertification, or continued-stay approval was missing, expired, exceeded, or not documented correctly. Authorization denial can be technical, administrative, or clinical and often uses CARC codes such as CO-197 or CO-50.
Related denial codes
Precertification, authorization, or notification absent
Not deemed a medical necessity
Patient not eligible as subscriber dependent
Refer to plan benefit documents for coverage details
