Utilization review in behavioral health: a complete guide from first authorization to appeal

Most programs treat utilization review as a phone call. A coordinator dials the payer, reads from the chart, and writes the number of approved days on a sticky note or into a spreadsheet. That works until the reviewer asks for something the chart does not say, the coordinator who knew the patient takes a week off, or a denial letter sits in the mail tray past the appeal deadline. Utilization review is better understood as a documentation discipline with a calendar attached. Every stage, from the first authorization to an external appeal, is answered by the same record. This guide covers each stage in order: what the payer is deciding, what the reviewer typically wants to see, where requests fail, and what your team can change this week so the record carries the argument.

What utilization review is, and why it is really one question

Utilization review is the process payers use to decide whether services are medically necessary, delivered at the appropriate level of care, and consistent with the plan's criteria. It is usually described as three types, distinguished by timing:

• Prospective review, usually called prior authorization: the payer decides before the service starts whether it will cover the requested level of care for a set number of days, units or visits.
• Concurrent review: while the patient is still in treatment, the program presents current clinical information to justify more authorized days or units.
• Retrospective review: after care is delivered, the payer reviews the records, sometimes because no authorization was required up front, sometimes because it was obtained late, and sometimes as part of a post-payment audit.

The question behind all three is the same: does the record show that this patient needs this level of care at this time? Only the tense changes. Before admission the answer rests on the assessment. During the stay it rests on progress notes, the treatment plan and the discharge plan. After discharge it rests on everything, read by someone who never heard your phone call. A program that understands this stops treating each review as a separate performance and starts making sure the chart answers the question continuously.

Who is on the other end of the call

The rules that govern a review depend on what kind of coverage the patient has. Fully insured commercial plans are shaped by state insurance law. Many employer plans are self-funded and governed by ERISA, often administered by a third party. Medicaid managed care organizations operate under federal Medicaid managed care rules and their state contracts. Medicare and Medicare Advantage have their own processes. Many health plans also delegate behavioral health utilization management to a separate vendor, so the company on the member's card is not always the company reviewing the stay.

The person you speak with is often a nurse or licensed clinician working from criteria. In many arrangements a denial has to be made or reviewed by a physician or other appropriate clinical reviewer; the applicable regulation and plan documents set who that must be. That distinction matters later, because it determines who your clinician should expect on a peer-to-peer call.

The practical step is a payer UR profile: one page per payer, or per payer and product line, kept where every coordinator can find it. Record:

• The UR entity, the phone line or portal, and whether reviews are telephonic, written, or both.
• The criteria set the payer applies to each level of care, and the edition.
• The review cadence by level of care, as stated in the contract or the payer's provider manual.
• What the payer wants submitted: a clinical update form, recent notes, the treatment plan, or a verbal summary only.
• Decision timeframes and how determinations are communicated.
• The peer-to-peer process: how to request it, who may participate, and any window after a determination.
• Appeal addresses, levels and filing methods for member appeals and for provider disputes under the contract.
• The internal owner for that payer.

None of this should be written from memory. Pull it from the contract, the provider manual and the payer's published UM policies, and date the sheet so you know when it was last checked.

The criteria the reviewer is reading against

Every review is a comparison between your record and a criteria set. For substance use disorder treatment, the ASAM Criteria is widely referenced by payers and states, and many organize their reviews around its six dimensions. Some payers license proprietary criteria, some use criteria they developed, and mental health levels of care are often reviewed against a different set from SUD levels. The fourth edition of the ASAM Criteria, published in 2023, revised the sub-levels, so a payer still using the third edition may describe levels differently from your program's licensing or your clinicians' training. Confirm the edition before matching level numbers.

This matters for documentation because the reviewer is looking for evidence organized the way the criteria are organized. That is not an invitation to stuff notes with criteria language. It means that when a clinician observes something relevant to withdrawal risk, biomedical conditions, emotional or behavioral conditions, readiness, relapse potential or the recovery environment, the observation should be written plainly enough that a reviewer can find it and connect it to the dimension it supports.

Ask each payer for the criteria it applies. Many will share them or the specific guideline on request, and in some circumstances plans are required to disclose the criteria behind an adverse determination. Confirm what applies against the plan documents and the governing regulation. A coordinator who knows exactly which guideline the reviewer is reading from prepares differently from one who is guessing.

Stage one: the initial authorization

Say a hospital calls on a Tuesday afternoon to refer a patient for residential treatment. Admissions verifies benefits, confirms that the plan requires authorization for the level, and a coordinator calls the payer. The reviewer is trying to decide whether the patient meets criteria for this level of care, today, and for how long to approve before looking again.

What the reviewer typically wants:

• The diagnosis and how it was established.
• Current presentation and risk: withdrawal, medical, psychiatric and safety concerns as they stand now, not only the history.
• Why a less intensive level of care would not be adequate: prior treatment episodes and how they went, the living environment, supports, and what happened the last time the patient tried a lower level.
• What this level provides that a lower one would not.
• Initial goals and early thinking about discharge and expected length of stay.
• Collateral information from the referring provider, family or prior records, where the patient has consented to its use.

The documentation that supports it

The initial request is supported by the intake assessment, the biopsychosocial, the multidimensional assessment against the criteria set, withdrawal or other standardized scales where relevant, the nursing or medical assessment, and any prior records obtained. The aim is for those documents to be complete enough before the call that the coordinator is summarizing the chart rather than filling gaps with recollection. If the program routinely calls for authorization before the assessment is finished, look at whether the intake sequence can be reordered.

Where initial requests fail

• The assessment describes history in detail but says little about current risk.
• Nobody answers the question of why a lower level would not work, so the reviewer answers it for you.
• The diagnosis on the request does not match the diagnosis in the assessment.
• Information was given verbally on the call but never written into the chart, so it does not exist for later reviews.
• The level requested does not match what the program is licensed or contracted to deliver at that site.

Whatever the outcome, record it on the chart the same day: the authorization reference number, the level of care, approved days or units, the date range, the reviewer's name, and the next review date. Our piece on tracking authorizations covers the operational side of watching both the date range and remaining utilization once approval is in hand.

Stage two: concurrent review

Concurrent review happens while the patient is still in treatment. Days delivered past the last authorized date without an approved review are at risk of going unpaid. How often reviews occur depends on the payer, the level of care and the contract, and it can change mid-stay if the reviewer shortens the next approval.

The question at concurrent review is narrower than at admission. The reviewer already accepted that the patient met criteria. Now they want to know whether the patient still needs this intensity and whether treatment is working or being adjusted. What they typically ask for:

• Specific progress since the last review, in clinical terms rather than attendance.
• Current severity in the dimensions or domains the criteria use.
• Changes to the treatment plan, and the reasons for them.
• Barriers to progress and what the team is doing about them.
• Participation and engagement, including missed sessions and why.
• Medication changes and their effects.
• The discharge plan, the target date, and the next level of care.
• Family or collateral involvement, where the patient has consented.

The no-change problem

Reviews often stall in one of two ways. In the first, the patient has not improved, and the treatment plan has not changed either. The reviewer reasonably asks why the payer should keep funding an approach that is not working. In the second, the patient has improved noticeably, and the reviewer asks why the patient is not stepping down. Both are answered the same way: a treatment plan that was revised when the clinical picture changed, and notes that explain the reasoning. If the patient is stuck, the record should show what the team tried differently. If the patient is better, the record should show what specifically still requires this level and what has to be true before a step-down is safe.

Documentation that supports concurrent review

Progress notes that describe the patient's response, not just that the session happened. A treatment plan that was updated between formal review dates when something changed. Nursing and medical notes. Outcome scores trended against baseline, where the program collects them. Incident reports and safety events. Our pieces on treatment plan reviews and using outcome scores cover those records in more depth, and the guide to preparing for the continued-stay call walks through the call itself.

Timing the preparation

Work backward from the last authorized day, not forward from the last call. Set a preparation date far enough ahead that the treatment team can discuss the patient before the review, the clinician can update the plan if needed, and the coordinator can submit on time. A coordinator assembling the update from the chart on the morning of the review is reading whatever happens to be there, and finding the gaps too late to fix them honestly.

Step-down and other level-of-care transitions

A step-down moves a patient to a less intensive level: residential to PHP, PHP to IOP, IOP to outpatient. Sometimes the program plans it. Sometimes the payer proposes it at concurrent review. Either way it is three things at once:

• A clinical transition. The treatment plan needs to be revised for the new setting, because priorities in a residential stay differ from those in IOP.
• A new authorization. An authorization for one level of care should not be assumed to cover another. Many payers treat the new level as a new request, reviewed against different criteria.
• An administrative change. The claim form, billing structure, rate, place of service and patient cost-sharing can all change with the level. Confirm each against the payer contract and the plan.

1. Write the transition note or discharge summary from the current level, including the clinical reasons for the move.
2. Update the assessment so the new request reflects the patient's current presentation.
3. Revise the treatment plan for the new level.
4. Request authorization for the new level before the patient's first day there.
5. Confirm the program is in network and contracted for the new level with this payer.
6. Re-verify benefits, because deductible, copay or coinsurance may differ by level. See our guide to verification of benefits.
7. Schedule the patient into the new program and tell them what changes, including any change in what they may owe.

When the payer proposes a step-down the team disagrees with

Write down the clinical reasoning in the chart: what specific risk the team expects at the lower level and what in the record supports it. Request a peer-to-peer if the payer offers one. Talk with the patient about what coverage looks like and what their options are. Two things to avoid: discharging or transferring a patient simply because authorized days ran out, without a clinical plan, and continuing to deliver and bill care as if it had been approved. Whether care continues is a clinical decision. Whether the payer covers it is a separate one, and the record should show both.

Step-ups

Transitions run in both directions. When a patient in IOP deteriorates, the request for a higher level rests on documentation of the deterioration: dated notes describing what changed, safety concerns, failed attempts to stabilize at the current level. A step-up request built on a single crisis note with nothing before it is harder to support than one where the decline is visible over several days.

Peer-to-peer review

A peer-to-peer is a conversation between a clinician from your program and the payer's reviewing physician or clinical peer, usually after an adverse determination or before one is finalized. Whether it is available, who may participate, and how long you have to request it vary by payer and contract. The notice letter or the provider manual usually says. Check both the day a denial arrives.

Who should make the call

The treating psychiatrist, medical director or attending clinician who knows the patient. A coordinator reading from the chart rarely moves a physician reviewer, and in many processes the payer expects a licensed provider. The coordinator's job is to prepare the clinician and sit in on the call to take notes.

A one-page brief

• The authorization reference and the minimum identifying information the payer needs.
• The level of care and dates requested.
• The criteria the determination cited, quoted from the letter or the call notes.
• The specific dimension or area where the team disagrees, with dated chart evidence for each point.
• What the team expects would happen at a lower level, stated concretely.
• The current plan, the target discharge date and the next level of care.
• What you are asking for: the full request, fewer days, or a modified level.

On the call

• Ask which criterion the reviewer believes was not met, and answer that point first.
• Use what is in the chart. If something is not documented, the reviewer cannot rely on it later, and nobody should describe a finding that was not observed.
• Ask whether a partial approval or a modified level is possible if the full request is not.
• Before hanging up, confirm the outcome, any new reference number, approved days, and what happens next.

After the call

Record the peer-to-peer in the chart or the UR log: date, time, participants, the reviewer's name, what was discussed, and the outcome. If the denial was upheld, the appeal clock is already running, and the call notes become part of the appeal.

Appeals and external review

If an adverse determination stands, the written notice generally explains the appeal rights, the deadlines and how to file. Federal rules set requirements for many plans: the ERISA claims procedure regulation for employer-sponsored plans, the internal claims, appeals and external review requirements for many group and individual plans, and the Medicaid managed care rules for MCOs. State law adds its own layer. Timeframes and rights differ across those rules, so do not work from a general rule of thumb. Read the letter and confirm against the regulation that governs the patient's coverage.

• Expedited or urgent appeals generally exist for situations where the standard timeframe could seriously jeopardize the patient. Check the criteria in the notice and the plan.
• A member appeal and a provider dispute under your contract are different processes with different addresses and deadlines. Know which one you are filing.
• If the program files on the patient's behalf, the plan may require an authorized representative designation. Get it signed early.
• External review by an independent organization may be available after internal appeals are exhausted, depending on the plan and applicable law.

1. A copy of the adverse determination.
2. A letter that addresses each reason cited, one by one.
3. The relevant records for the dates in question: assessment, notes, treatment plan, medical documentation.
4. References to the criteria the payer applied.
5. Your record of the peer-to-peer, if one happened.
6. A letter from the treating physician explaining the clinical reasoning.

Keep an exact record of what was sent, when, how and by whom. Our piece on assembling an audit packet covers that discipline, and it applies equally to appeals.

Retrospective review

Retrospective review happens after care is delivered. It may be the payer's standard process for some services, a consequence of an authorization obtained late, or part of a post-payment audit. The reviewer reads the same records with none of the context your coordinator supplied on the phone. That is the strongest argument for writing call content into the chart: a verbal explanation that persuaded a concurrent reviewer in March is gone by the time a retrospective reviewer opens the file in October. Our payer audit playbook covers post-payment reviews in detail.

How documentation supports each stage

The same chart answers every stage, but each stage leans on different parts of it:

• Initial authorization: intake assessment, multidimensional assessment, medical and nursing assessment, prior treatment history, and a clear statement of why a lower level would not be adequate.
• Concurrent review: progress notes that describe response, an updated treatment plan, trended scores where collected, incidents, and a discharge plan with a date.
• Step-down: transition note, updated assessment, revised plan for the new level, and a new authorization request.
• Peer-to-peer: dated chart evidence for the specific criterion in dispute, and the treating clinician's reasoning.
• Appeal: everything above for the dates in question, plus the determination, the peer-to-peer record and a physician letter.
• Retrospective review: the complete record, read without your explanation.

The common thread is that the records are dated, signed, specific, and consistent with each other. A note that says the patient is ready for discharge, next to a plan that says the patient needs four more weeks, will be read by every reviewer at every stage.

Habits that help in every review

• Write current severity, not only history.
• Record why a decision was made, not only what was done.
• Update the treatment plan when the clinical picture changes, not only on the scheduled review date.
• Treat the discharge plan as a working document from the first week.
• Keep the UR record in the chart, not in a coordinator's notebook or inbox.
• Avoid copy-forward. A reviewer who sees the same paragraph in five consecutive notes will conclude nothing changed. See cloned notes and medical necessity.

Who owns utilization review inside a program

Utilization review crosses departments, which is why it breaks at the handoffs. A workable division:

• UR coordinator: the review calendar, submissions, calls, the UR log, and chasing documentation before a review.
• Clinicians: notes and plan updates that support the clinical case.
• Medical director or attending: level-of-care judgment and peer-to-peer calls.
• Clinical director: treatment team meetings, plan review oversight, and escalation when a patient is stuck.
• Admissions: the clinical and benefits information for the initial request.
• Billing: authorization data on every claim, and flagging services delivered outside an approved range.
• Compliance: consent for disclosures to payers, and what records go out.

The failure to plan for is the departure. Say your UR coordinator leaves in March. If the review dates, reference numbers and call outcomes lived in their email and a personal spreadsheet, the next person starts by calling every payer to find out where each patient stands. If they lived on the patient record, the next person starts by reading.

Building a UR log that holds up

Every review event deserves a row, or better, an entry on the episode of care. Fields worth capturing:

• Patient episode, payer, plan and level of care.
• Authorization reference number.
• Approved days, units or visits, and the date range.
• Review type: initial, concurrent, step-down, retrospective.
• Submission or call date, and the reviewer's name.
• Criteria cited, especially on any adverse determination.
• Outcome and next review date.
• Peer-to-peer requested, held, and its outcome.
• Appeal filed, level, deadline and status.
• Internal owner.

Run a weekly list of reviews due in the coming days and walk it in a short meeting with the coordinator and the clinical lead. The list should show which patients have documentation gaps before the review, not after.

Internal measures worth running

There is no universal target for any of these, and your payer mix will shape them. They are useful because they point to where your own process leaks:

• Review outcomes by payer and by level of care.
• Days delivered outside an approved authorization, and why.
• Peer-to-peer calls requested against those that changed the outcome.
• Adverse determinations grouped by the criterion cited.
• How close to the last authorized day reviews are being submitted.

If most determinations cite the same dimension, the fix is usually in how the assessment or progress notes describe it, which is a training conversation with clinicians rather than a phone script for the coordinator.

Where software fits, and where it does not

A spreadsheet holds a UR log adequately until the program grows, a coordinator leaves, or billing needs to know whether a service was inside an approved range without asking. What helps is having authorization data on the same record everyone works from, with approaching limits visible where scheduling and documentation happen. In Unisona Health, prior authorizations track visits, units, dollars, remaining utilization and expiration dates against the services being delivered, so a review date is visible to the coordinator, the clinician and the biller at once.

The concurrent review argument also depends on a treatment plan that keeps pace with the patient. Treatment plan reviews surface before they are due, which gives the team a prompt to revise the plan ahead of the payer asking what changed. Neither feature decides medical necessity. That stays with your clinicians and, for coverage, with the payer.

The programs that handle utilization review well are rarely the ones with the most persuasive coordinators. They are the ones whose charts answer the reviewer's question at every stage, whose review dates are known before they arrive, and whose denial letters are read the day they land. Start with the payer profile sheets and the UR log. Both can be built this week.

Frequently asked questions