Utilization Review Process: Steps, Best Practices, and Denial Prevention

Table of Contents

Get in touch

Ready to amplify your business?
Let's transform potential into performance together.
Talk to Sales

Quick Summary

Utilization review (UR) can make or break authorizations, continued-stay approvals, and revenue in behavioral health. This guide walks you through a practical UR process, from benefits verification to concurrent reviews and appeals, so your documentation consistently proves medical necessity. 

Why Payers Cut Days Even When Care Is Clinically Appropriate

Utilization review can determine whether a payer approves, delays, shortens, or denies care. You can have the right level of care, the right clinical work happening, and real patient progress, but still get hit with “not medically necessary” because the chart doesn’t clearly prove why the patient still requires that level of care today.

In this article, we’ll explain how the utilization review process works in behavioral health and how to run it to protect authorized days. You’ll learn what payers look for, what strong medical necessity support sounds like, and how to reduce denials without disrupting clinical care.

Why Listen to Us

We work directly with behavioral health and rehab programs across detox, residential, PHP, and IOP. Through hands-on utilization review support, we see what payers expect, what triggers denials, and what documentation gaps cost programs covered days. That real-world experience puts us in a strong position to explain how UR works and how to run it effectively to protect authorizations and reduce payer pushback.

What Is the Utilization Review Process?

The utilization review (UR) process is how you confirm and document that a patient meets the payer’s medical necessity criteria for a specific level of care. 

Think of it as your roadmap for proving a patient truly needs the level of care you’re providing at admission and throughout their stay. UR helps clearly demonstrate to the payer why the current level of care is medically necessary and eligible for coverage.

A solid UR process includes three main pieces: initial authorization, ongoing concurrent reviews, and continued-stay justification. Each step documents symptoms, risk factors, functional impairment, and treatment response in a way that payers understand. When done consistently, it supports admission decisions and protects reimbursement by proving the right care is happening at the right time.

How to Improve the Utilization Review Process

Step 1: Confirm Payer Coverage and Benefits (VOB/Eligibility)

Before you submit an authorization, make sure the coverage actually exists. This prevents situations in which a patient appears clinically appropriate but has no plan, likely because coverage is inactive, out-of-network, or limited.

Here’s what to do: 

  • Verify in real time. Don’t rely on what the patient reports. Call or check the payer portal to confirm:
    • The plan is active for the exact dates of service
    • Member ID is correct
    • Patient is assigned to the correct policyholder and product type
  • Check the level-of-care rules. For the level of care you’re admitting, confirm whether:
    • Prior authorization is required
    • There are strict visit or day limits
    • Certain services are excluded
  • Document everything. Log the confirmation source, reference number, and the payer rep’s name/department. This record can save hours or days if questions arise later.

For example, you’re admitting a patient to residential care. The plan portal shows active coverage, but daily limits are capped at 14 days. You note this in the chart and flag the team: the authorization request will cover the first 14 days, with concurrent review planned for 15+ days. 

When the payer questions the stay, you have the documented proof to avoid delays.

Step 2: Identify the Required Level of Care and Payer Medical Necessity Criteria

Ensure the patient’s clinical presentation matches both the right level of care and the payer’s definition of medical necessity. Even if your clinical judgment is spot-on, a mismatch here is the fastest way to lose approved days.

Do this instead;

  • Start with objective drivers, not diagnostic labels. Lead with clarity and risk, then functional impairment, then evidence of failed lower-level care. Diagnosis alone rarely convinces payers.
  • Anchor to measurable, payer-relevant evidence. Document current symptoms, safety concerns, and the patient’s ability, or inability to function. Ask yourself: “Could this patient safely step down to PHP or IOP today?” If the answer is no, write exactly why.
  • Translate your clinical picture into payer language. Use cause-and-effect reasoning and time-bound details. Show what’s changed recently, what interventions were tried, and why the current intensity of care is required now.
  • Pressure-test your rationale. Before submitting, consider the lower levels of care: outpatient, IOP, and PHP to see if they meet the patient’s needs. If they don’t, state it clearly and support it with evidence.
  • Create a repeatable workflow checklist. This ensures logic stays consistent across charts and during concurrent reviews.

For example, a patient presents with severe alcohol withdrawal, repeated failed attempts at IOP, and an inability to manage ADLs safely. Your note might read: 

“Patient requires 24-hour medical monitoring for CIWA ≥15, demonstrates persistent functional impairment, and continues unsafe behaviors at home. IOP or outpatient care is unsafe due toinsufficient monitoring and relapse risk.”

This shows exactly why residential care is required today, using language the payers recognize.

Step 3: Complete Intake Assessment with Objective Severity, Risk, and Impairment Evidence

Your intake sets the baseline for defending the stay and makes ongoing reviews significantly easier. If severity, risk, and functional impairment are vague on day one, every concurrent review becomes harder because you don’t have a clear baseline to defend the ongoing level of care.

To prevent this, here’s what to do; 

  • Document objectively: Use time anchors like “past 72 hours” or “last two weeks,” to quantify frequency and intensity, and capture what the patient cannot safely or consistently do because of symptoms.
  • Make risk explicit and current. Don’t just list history; describe active risks. Depending on the risk levels, cite protective factors or describe why lower-level care is unsafe.
  • Translate impairment into real-life function. Show how symptoms disrupt work, school, parenting, sleep, medication adherence, self-care, or the ability to engage in treatment without intensive structure.
  • Include failed or insufficient lower-level care attempts. Payers notice patterns: escalating symptoms, repeated ED visits, missed outpatient appointments, inability to stabilize, or rapid decompensation after step-down.

For example, 

“Past 72 hours: Patient reports daily cravings with 3 episodes of unprotected drinking, unable to maintain ADLs independently, missed two outpatient appointments last week. Previous IOP failed due to persistent withdrawal symptoms and sleep disruption. Requires 24-hour supervision and structured interventions.”

This creates a clear, defensible baseline. Future progress notes can now focus on how treatment is working, not rewriting the admission story mid-stay.

Step 4: Submit Initial Authorization with a Clear Level-of-Care Rationale

The initial authorization is where you win or lose your first block of covered days. Only submit it when your chart can stand on its own with a clear diagnosis, current risk, measurable impairment, and a direct explanation of why a lower level of care isn’t enough today.

Here’s what to do before submitting the authorization:

  • Think like the payer, not the clinician. Start with the acute drivers, what’s happening right now, then explain why the current intensity of care is medically necessary. Avoid vague phrases like “needs structure” unless you define what happens if it’s missing.
  • Make your level-of-care rationale clear. If this is residential or PHP, show why IOP won’t suffice. If this is IOP, explain why outpatient isn’t enough. Tie everything to objective evidence and recent changes, not just historical problems.
  • Check your chart before submission. Make sure it answers predictable payer questions such as:
    • What is the patient’s current symptom severity and safety risk?
    • What is the measurable functional impairment today?
    • What skilled services are delivered at this intensity?
    • What is the expected clinical focus for the next authorization period?
    • Why is step-down care inappropriate right now?

For example, “Patient demonstrates daily unsafe alcohol use with CIWA scores 12–15, unable to maintain ADLs independently, missed previous IOP attempts. Residential care provides 24-hour monitoring, structured withdrawal management, and daily skill-building groups. Step-down to PHP or IOP is unsafe due to ongoing withdrawal and functional deficits.”

Send the authorization on time, log the payer reference number, and set the next review date. A strong initial authorization prevents rework and sets up a smoother concurrent review cycle.

Step 5: Run Concurrent Reviews on Schedule with Updated Evidence

Concurrent reviews are where programs often lose approved days. The goal is to demonstrate, using current clinical evidence, that the patient still meets the criteria for this level of care today.

Follow these steps to update your documentation ahead of the reviews;

  • Update what’s changed. Start by noting differences since the last authorization, including symptom severity, safety risks, and functional impairment. Use clear timeframes, such as “past 48 hours.”
  • Document cause-and-effect. Progress notes should link intervention → patient response → clinical decision. Avoid “activity-only” notes. Saying “attended group” isn’t enough unless you explain how it affected symptoms, functioning, or risk.
  • Explicitly justify the continued stay. Show why step-down is premature: ongoing withdrawal risk, incomplete stabilization, inability to function independently, or unresolved barriers.
  • Keep discharge planning visible throughout the stay. Document remaining clinical barriers and what must occur before transition.

Here’s an example: 

“Over the past 5 days, the patient’s CIWA scores have remained 10–12, continues to miss meals due to nausea, requires staff assistance with ADLs, and exhibits unsafe coping behaviors. Group skill practice addressed craving management, but continued 24-hour monitoring. Step-down to PHP is unsafe at this time. Discharge planning focuses on ADL independence and relapse-prevention sessions over the next week.”

Treat each concurrent review as a focused reassessment. If your documentation clearly answers why now, why this level, and why continued care is required, you protect days without rework.

Step 6: Manage Denials and Appeals Using Documentation-Backed Arguments

When you receive a denial, don’t treat it like a billing issue; you can just resubmit. Think of it as a documentation issue you can fix, defend, and prevent from happening again.

Here are better ways to handle this; 

  • Map the denial to the missing evidence. Look at the payer’s reason: was it a level-of-care rationale, risk assessment, functional impairment, progress, or discharge planning? Identify exactly what they said is lacking.
  • Build the appeal around objective facts. Don’t vent frustration; show the evidence. Pull specific progress notes, CIWA scores, functional assessments, or structured treatment plan entries that prove medical necessity for the denied dates.
  • Follow a clear, repeatable logic:
    • Denial reason: what the payer flagged
    • Chart evidence: what’s already documented
    • Rationale: why the current level of care was necessary right then

Here’s a typical example of how to handle denials; 

Denial: “Residential care not medically necessary 1/10–1/16.”

Appeal note: “During 1/10–1/16, patient required 24-hour monitoring for withdrawal (CIWA 11–14), unable to perform ADLs independently, unsafe coping behaviors observed daily, and IOP would not provide sufficient supervision. Daily skill-building groups and medical monitoring are provided at the residential level to stabilize risk and functional impairment.”

How Prosperity Behavioral Health Can Help (Consulting or Managed Services)

Utilization review only works when your documentation, timelines, and payer communication are well-documented. Prosperity Behavioral Health helps programs build a UR process that protects authorization days and reduces denials. 

Here’s how we do it; 

1. Verification of Benefits (VOB) + Eligibility Support

We confirm coverage details upfront so admissions don’t get delayed or disrupted by avoidable eligibility issues, plan limitations, or missing payer requirements.

2. Authorization Management (Initial + Concurrent)

We manage the authorization workflow across detox, residential, PHP, and IOP, so reviews proceed as scheduled, documentation is aligned and accurate, and you don’t lose covered days due to missed deadlines.

3. Utilization Review + Medical Necessity Support

We support the UR workflow by organizing clinical evidence, staying ahead of review timelines, and strengthening documentation of the logic behind the chosen level of care, so initial and continued days are easier to secure.

4. Denials Management + Appeals

When denials happen, we help resolve them faster using documentation-backed arguments, corrections, and appeal workflows that reduce A/R aging and prevent avoidable write-offs.

5. Consulting + Gap Analysis

We identify operational weak points (documentation drift, review inconsistency, missed requirements) and implement fixes that improve reimbursement performance without adding chaos to your team. 

Best Practices for Your Next Utilization Review

  • Write for the next reviewer, not the last clinician. Assume the payer reviewer has never met the patient and will only read a few pages before making a decision. Your documentation should stand alone without requiring “see prior note” references or interpretation. 
  • Track “why not a lower level of care” every week. Payers approve continued stay based on current need, not intake history. Each week, explicitly state why step-down care is not appropriate, yet using specific evidence, and show your structure for continued care. 
  • Quantify change, not participation. “Attended group and participated” doesn’t tell a payer whether the patient is stabilizing, deteriorating, or stuck. Replace attendance-based notes with measurable change, such as symptom frequency/intensity, sleep stability, cravings, mood regulation, etc
  • Treat payer deadlines like clinical deadlines. Build a system that makes deadlines predictable. This involves knowing the standard review days by payer, coverage planning for weekends/holidays, and clear handoff processes when staff are out. When UR timelines are included in your workflow, your team can document more proactively. 
  • Use denials as process data. Track denial reasons by payer, level of care, and clinician, then use that data to update templates, coaching, and QA scoring. The goal isn’t to win one appeal; it’s to prevent the same denial from happening again next week with a different patient.

Build a UR Process That Payers Can’t Tear Apart

A robust utilization review process protects your patients, authorizations, and revenue by ensuring your documentation is accurate for the payer from intake through continued stay. When your UR process is consistent, you can prevent denials. Think of it as building a documentation system that consistently holds up under payer review. 

Prosperity Behavioral Health supports behavioral health programs across detox, residential, PHP, and IOP with utilization review, authorization management, and denial support to strengthen medical necessity documentation and reduce payer friction.Book a call today to discuss improving your UR process.

Related Post