Getting Initial Authorization to Admit

Prior authorization for admission is the payer's approval to admit a specific patient, at a specific level of care, on a specific timeline. It is the last gate between a verified, committed patient and the bed. The verification of benefits told you what the plan covers; the authorization is the payer agreeing that this admission, for this person, right now, is approved. Miss it, and everything upstream — the call, the pre-screen, the VOB, the yes — is standing on nothing.

It is also the gate most admissions content skips. Authorization sits awkwardly between admissions and billing: too payer-facing for the marketing playbooks, too front-door for revenue cycle. So nobody writes about it, and on plenty of floors nobody clearly owns it. This piece covers the initial authorization only — the approval to admit. Concurrent review and continued-stay authorization happen after admission; they belong to utilization review and the revenue cycle, and they are out of scope here.

One caveat before the detail: payer requirements vary, by carrier, by plan, and by level of care. Treat everything below as operational guidance, not billing or legal advice. And if the step before this one is still fuzzy ground, start with what a verification of benefits actually confirms and come back.

Key takeaways

• An initial authorization is the payer's approval to admit this patient at this level of care. It is not the VOB, and neither one is a guarantee of payment.
• The clinical picture payers ask for in an initial authorization is the same picture a structured ASAM 6-Dimension pre-screen captures on the admissions call — captured structured, it never has to be reassembled from memory.
• Start the authorization during the call or immediately after it. An authorization that waits for tomorrow adds a day to the gap between yes and arrival, and that gap is where admissions die.
• The initial authorization needs a named owner inside admissions. "Whoever is free" is how approval requests sit in a queue overnight.
• When a payer pushes back on level of care, the structured pre-screen is the defensible starting point for the conversation, because every answer behind the read is on the record.

What an initial authorization to admit actually is

Three different questions get collapsed into the word "insurance" on an admissions floor, and the collapse causes real damage. Confusing them is how a center admits a patient it believed was covered.

Check	The question it answers	What it is not
Eligibility check	Is this policy active today?	Not a statement of what the plan covers
Verification of benefits	What does this plan cover for this care, at what cost to the patient?	Not the payer's approval to admit
Initial authorization	Does the payer approve this admission, at this level of care, now?	Not a guarantee of payment

Not every admission requires prior authorization: some plans want approval before arrival, some only notification within a set window, some neither — it depends on the payer, the plan, and the level of care. The time to find out which you are dealing with is during the VOB. A real-time verification of benefits that comes back in minutes gives you that answer inside the call instead of a day later.

The sequence, then, is short and unforgiving: verify, authorize, admit. Each step has an owner and a clock, and admissions owns all three.

What payers need to hear before they approve an admission

The specifics differ by payer, but the shape of an initial authorization request is remarkably consistent. The reviewer on the other end needs four things.

Who the patient is. Demographics and policy details — the part the VOB already collected.

What is happening right now. The presenting picture: what the person is using, how much and how recently, prior treatment episodes, withdrawal risk, medical and psychiatric complications, and what the home environment looks like. This is where thin requests fail.

What you propose. The requested level of care and the planned admission date. Payers approve admissions, not intentions — "sometime next week" is not a request.

Why. The clinical rationale connecting the picture to the level of care. Residential rather than intensive outpatient because of the withdrawal history and the environment the person would go home to every night. This is the part the reviewer is paid to test.

How the request travels varies too — a payer portal, a phone review with a payer clinician, sometimes still a fax. The channel matters less than the case. A complete, specific clinical picture moves through any channel; a vague one stalls in all of them.

The pre-screen is the authorization case

Read that list again. Withdrawal risk. Medical complications. Emotional and behavioral picture. Readiness. Relapse history. The environment the person is living in. That is the ASAM six dimensions — the same ground a structured pre-screen covers on the admissions call to produce a level-of-care read.

This is the linkage most centers miss. The structured answers that produced the level-of-care read are the clinical picture the authorization conversation needs. Not similar to it. The same material.

Which means the difference between centers is not clinical skill, it is capture. One center works through the pre-screen in structured fields during the call. When the authorization opens — that afternoon, or first thing the next morning — the person making the case is reading from the record: every dimension answered, timestamped. The other center took narrative notes, something like "detox probably, call Cigna tomorrow," and the next morning someone is reassembling a clinical case from memory, fragments, and a coordinator who is on another call.

Same patient. Same payer. One case is defensible on contact; the other is a reconstruction. The read itself is a starting point for staff, not a clinical determination — but a starting point with every answer behind it on the record is exactly what an authorization conversation is built from.

Start the authorization while the yes is still warm

An initial authorization that waits for tomorrow adds a day to the gap between yes and arrival. That gap is the most fragile stretch of the whole inquiry-to-admit journey — it is where second thoughts, family objections, and other facilities live. Every hour without a confirmed authorization is an hour the admission stands on a verbal yes and nothing else.

The sequence that protects it is short.

1. Run the VOB during the call, not after it. If your verification still takes hours, fix that first — how to verify benefits faster covers what that takes.
2. Confirm, inside the VOB, whether this plan requires prior authorization for this level of care.
3. Capture the pre-screen in structured form while the caller is on the line.
4. Open the authorization the same day — portal or phone — while the clinical picture is fresh and the patient is committed.
5. Log the reference number, the payer contact, and the status where the whole team can see them.

Payers keep business hours, and some reviews wait for a payer clinician — which is an argument for starting immediately, not for waiting. A request opened at four in the afternoon is first in tomorrow's queue; a request nobody opened is in no queue at all.

A named owner, not whoever is free

Every initial authorization needs a name attached to it — the coordinator who took the call on a small floor, a dedicated authorization role on a larger one. Either works. What does not work is "whoever is free," because whoever is free is also whoever is on the next crisis call, and a request with no owner sits in a queue overnight without anyone noticing.

The second failure mode is location. An authorization that leaves the admissions flow — into a personal email inbox, a fax confirmation folder, a sticky note on a monitor — goes invisible. The admission stalls silently: the family believes they are arriving Thursday, and the payer has not been asked. It is the same species of handoff failure as the VOB mistakes that cost admissions: the work left the system, so the system could not show it was stuck.

The fix is structural, not motivational. The authorization is a step in the admissions pipeline with an owner and a status, on the same record as the lead, the pre-screen, and the VOB. When the status lives next to the lead, a stalled authorization looks like what it is — a stalled admission — and someone is on it before the family calls to ask.

When the payer pushes back on the level of care

Sometimes the payer does not say no; the reviewer says "intensive outpatient" when you requested residential. That conversation is decided by specifics: the withdrawal history, the prior episode at a lower level of care that did not hold, the environment the person would return to every night.

A center with a structured pre-screen walks the reviewer through the dimensions, one at a time, with the caller's actual answers. A center with narrative notes says "we really think residential is appropriate" and hopes. The pre-screen's level-of-care read does not decide the question — it is a read, not a determination — but it makes the case defensible, because every answer behind it was captured when the caller gave it.

If the pushback holds, most payers have escalation paths, typically including a clinician-to-clinician review; the processes vary enough that your team should know each major payer's before it needs them. And sometimes the honest outcome is that the reviewer is right and a different level of care is the right admission. A structured picture makes that call cleaner too — you are agreeing based on the record, not conceding because the case was thin.

How Census CRM keeps the initial authorization inside admissions

Census CRM does not submit authorizations to payers. The payer conversation is your team's. What Census does is make sure the person having that conversation is reading from the record instead of reconstructing it — and that the request never leaves the flow.

The pieces are already in place by the time the authorization opens. The ASAM 6-Dimension pre-screen is captured as structured answers during the call inside the guided admissions workflow, and the level-of-care read is auto-computed from those answers — so the clinical picture the payer needs exists the moment the call ends. The VOB has already come back in real time, flagged HIGH, MEDIUM, or LOW risk, across carriers including BCBS, Aetna, Cigna, UHC, and Humana, so the team knows how hard the road is likely to be before anyone dials the payer.

Then the authorization lives where the admission lives. Every lead moves through one pipeline — Qualification, Approval, Commitment — and the authorization work sits in Approval, on the record, with an owner and a status the whole floor can see, not in a fax queue nobody watches. At admission, the record hands off to the EMR, including Kipu and Sunwave, which is where utilization review picks up concurrent and continued-stay work. That process was shaped by 60,000+ admissions calls a month and 1,200+ placements a month, and the boundary is deliberate: admissions owns the initial authorization, and nothing after it.

Where to begin with initial authorization

Pull your last ten admissions and ask three questions of each. When did the authorization start, relative to the family's yes? Who owned it, by name? And where was its status visible? If the honest answers are "the next morning," "whoever was free," and "in someone's inbox," you have found a full day you can give back to every admission — and with each admission carrying about $10,000 of value, a day of silent drift is an expensive habit.

Fix ownership first, because it costs nothing. Then fix timing, which mostly means starting the same day. Then fix capture, so the case the owner argues from is structured instead of remembered.

If you want to see the pre-screen produce the level-of-care read on a live call, and the authorization sit in a pipeline where nothing goes invisible, watch it run with a scenario from your own floor.