Adding a new level of care: the operational checklist across licensing, payer contracts, staffing, scheduling, documentation and billing

The space is ready, the group room has chairs, a program director has been hired and the website says IOP is now open. Then the first claim comes back denied because the payer contract only lists outpatient professional services, and the second because the clinician who ran Tuesday's group was never enrolled for the new program. Nothing about the care was wrong. The expansion was planned as a clinical project, and the parts that decide whether it gets paid ran on other people's calendars. This is a reference for owners, clinical directors, billing managers and compliance leads planning to add a level of care: what each workstream involves, who should own it, and which questions need answers before anything is configured.

Why a new level of care is six projects, not one

Most programs plan an expansion around the clinical model: what the day looks like, which groups run, who leads them. That work matters, but it is rarely what delays an opening or what produces the first months of denials. Delays come from licensing, accreditation and payer contracting, which move at the speed of a state agency and a provider relations department. Denials come from the setup work in between: credentialing, scheduling, note types and claim configuration.

Treat the expansion as six workstreams, each with one named owner and a written list of open questions:

• Licensing and accreditation, usually owned by the owner or compliance lead.
• Payer contracting and enrollment, owned by the owner, the billing manager or whoever negotiates contracts.
• Staffing and credentialing, owned by the clinical director with HR and whoever maintains credential files.
• Scheduling and the program day, owned by the program director.
• Documentation, owned by the clinical director.
• Billing setup, owned by the billing or revenue cycle manager.

The sections below take each in turn, then cover the two areas that fall between them: intake and placement, and the handoff when a patient moves from one of your levels of care to another. The article closes with the first 90 days, a hypothetical worked example and a consolidated checklist.

Step zero: write down exactly what you are opening

Every workstream asks the same questions, and they need one answer before anyone calls a state office or a payer. Expansions stall when the license application describes one program, the payer amendment another and the schedule a third. Write a one-page program description that answers:

• Level of care, named the way your state license category and your payers name it. If you use ASAM levels, note which edition your state and payers reference, since sub-level numbering changed between editions.
• Population: adults or adolescents, substance use, mental health or co-occurring. Many licenses and contracts distinguish these.
• Hours and days: how long a program day runs and how many days a week. Licensing rules and payer definitions of a billable day often depend on it.
• Location: the same space as an existing program, the same address with separate space, or a new site.
• Legal and billing entity: whether the program runs under your existing tax ID and NPI or a new one.
• Staffing model: which roles, at what coverage, and who supervises whom.
• Referral flow: step-down from your residential, step-up from your outpatient, outside referrals, or all three, and the census you expect from each.

This page becomes the source for the license application, the payer conversations, the policy manual and the configuration of every system. When a detail changes, change the page first and tell every workstream owner.

Licensing and accreditation

State licensing for behavioral health is generally issued by level of care and often by site, and the agencies, categories and requirements differ from state to state. Some states license substance use and mental health programs through different agencies. An outpatient license generally does not authorize an IOP, and a residential license generally does not authorize a PHP. Confirm what your state requires rather than assuming an existing license stretches to cover the new service.

What the application usually involves

• Policies and procedures specific to the new level: admission and discharge criteria, the program schedule, staffing, emergency procedures, and how the program relates to your other services.
• Physical plant requirements for the space, such as group room size, accessibility, fire and occupancy inspections, and local zoning where it applies.
• A staffing plan showing required roles are filled, or will be by opening.
• A survey or site visit before or after opening, depending on the state.

Accreditation is a separate track

If you are accredited, your accreditor will usually need to know about a new service, and some payers will not contract for a level of care until accreditation covers it. Ask your accreditor how it handles a program added between survey cycles, and ask each payer whether accreditation of the specific service is a condition of contracting. Those two answers decide whether accreditation sits on your critical path or beside it.

Federal layers that may apply

If the new service is substance use disorder treatment in a federally assisted program, 42 CFR Part 2 applies to those records. Review consent forms and disclosure workflows for the new program, particularly where consents name specific programs or where records will move between levels of care. Opening an opioid treatment program adds federal certification and regulation under 42 CFR Part 8 on top of state requirements, a much larger project than this checklist covers. For Part 2 in practice, see 42 CFR Part 2, explained for operators.

Payer contracting and enrollment

This workstream is the one most likely to set your real opening date. Not the day the doors open, but the day services become billable.

Read the contracts you already have

Pull every active payer agreement and find the services exhibit or rate schedule. Contracts generally list the services, codes and rates the payer has agreed to pay you for. A level of care that is not listed is usually not covered by your agreement, even if the payer covers that level of care for its members at other providers. Look also for clauses requiring notice of new services or locations, and for the process to request an amendment.

What to get in writing

• The level of care as the payer names it, and the service codes, revenue codes and modifiers you will bill.
• The rate and its structure: per diem, per service or another methodology.
• The claim form. Some payers expect an institutional claim for PHP or IOP, others a professional claim. Do not guess.
• Authorization requirements: whether the level needs prior authorization, how the payer's initial approval is expressed, and how concurrent review works.
• Any minimum service requirement for a billable day or unit.
• Requirements for rendering and supervising providers, including credential types.
• The effective date. Services delivered before it are not covered by the amendment.

If a payer will not amend before you open, decide whether you will admit that payer's members to the new program. Some programs use single case agreements in the meantime; they are negotiated one patient at a time and are not a substitute for a contract. Make this a written policy before intake starts taking calls, not a decision made during one.

Enrollment, identifiers and taxonomy

Depending on your state Medicaid program and commercial payers, a new level of care may require a new enrollment, a new location on an existing enrollment, a separate NPI for the program or site, or updated taxonomy codes. A new billing entity may also need its own electronic claim and remittance enrollment. Each has its own processing time. Ask every payer which identifiers it expects on claims for the new program, and record the answer beside the contract so billing configures what the payer actually expects.

Staffing and credentialing

A new level of care almost always needs roles the current program does not: more group facilitators for IOP, medical and nursing coverage for PHP, a program director accountable for the day. State licensing rules typically specify required roles and sometimes coverage or supervision arrangements, and payer contracts can add their own requirements for who may render a billed service.

Hire against the rules, not the org chart

Start from the staffing requirements in the license rules and the payer contracts, then map existing staff against them. A clinician fully qualified for outpatient individual therapy may need supervision, an additional credential or a separate payer enrollment to render services in the new program. Gaps found now are hiring decisions; gaps found after opening are denials.

Credential for the new program, payer by payer

Enrollment status is per payer and sometimes per location or program. Before the first patient is scheduled, confirm for every clinician who will render or supervise, and for every payer whose members you will admit: license active, enrollment effective for the new program, supervision documented where required. Record effective dates rather than a single status, because any questioned claim will be judged against the date of service. Provider credentialing for a past date of service covers how to keep that history.

Train on the new workflows

Staff moving from outpatient to IOP, or residential to PHP, need training on the new program's attendance recording, note types and schedule, plus the transition workflow described below. Schedule it close to opening, record completion per person, and include anyone who will cover groups when the regular facilitator is out.

Scheduling and the program day

Outpatient scheduling is built around appointments, IOP and PHP around a program day, residential around a census. Adding a level of care usually means running two scheduling models side by side.

• Build the program calendar: which groups run when, who facilitates each, which room, and where individual sessions, psychiatric visits or medication management fit around groups.
• Define attendance states before day one: present, late, left early, excused, absent. Documentation and billing will both depend on which one was recorded.
• Check the day against payer minimums: if a payer defines a minimum for a billable day, the schedule should make it achievable with room for a late arrival.
• Plan coverage: who facilitates when the scheduled clinician is out, and whether the substitute is credentialed for every payer represented in the room.
• Set capacity: maximum group sizes from your license or policy, and the census at which you need a second track.
• Plan the logistics outpatient never needed: meals for a full PHP day, transportation, somewhere to wait between groups.

If a patient might receive services at two of your levels of care on the same day, decide in advance whether that is allowed. Same-day services across levels can create billing conflicts depending on payer rules, so confirm with each payer before it appears on a schedule.

Intake, eligibility and placement

Admissions now has a routing decision on every call. Update the intake workflow before opening:

• Pre-screening questions that help route a caller toward the right level of care, with the placement decision itself made by a clinician.
• Eligibility and benefits checked for the specific level of care, not behavioral health benefits in general. Coverage, cost-sharing and authorization requirements can differ by level. See verification of benefits.
• A placement assessment documented in a way your payers accept as supporting medical necessity, often structured around the ASAM criteria for substance use treatment.
• Consent forms, financial agreements and patient materials updated to name the new program.
• A script for what intake says when a payer's contract for the new level is not yet effective, consistent with the policy you set in contracting.

Documentation

The record for a new level of care is not the outpatient record with more notes in it. Licensing rules, accreditation standards and payer contracts each describe what must be documented at that level, and those requirements should drive the note types you build before the first patient arrives.

Build the note types before you need them

• Admission assessment and placement documentation for the new level.
• Group notes that separate shared session content from each participant's individual participation and response. See why identical group notes are a problem.
• Individual, psychiatric and medical notes as the program model requires.
• Daily or weekly progress documentation, if your license or payers require it at this level.
• Treatment plan templates with review intervals matching the requirements for the new level, which may differ from your existing program.
• Discharge and transition summaries.

Set the documentation window

Decide how soon after a session a note is due, who is reminded and when a late note is escalated. A new program staffed partly by new hires is exactly where documentation lag starts, and it is far easier to correct in week two than at the first records request.

Audit the first patients

Take the first several patients through the program and review their records end to end after their first week: assessment, plan, attendance, notes and signatures. You are testing whether the templates capture what the license and the payers require, while changing a template still affects a handful of charts instead of hundreds.

Billing setup

Billing turns every answer above into configuration. Expect to set up:

• The new program or service location, linked to the correct billing entity, NPI and taxonomy.
• Service codes, revenue codes and modifiers per payer, exactly as each contract amendment states.
• Contracted rates per payer, so every remittance can be compared against what you agreed.
• The claim form for each payer: professional or institutional.
• Place of service and any program-specific claim fields.
• Authorization tracking for the new level, by days or units and by date range.
• Pre-submission checks for the new program: rendering provider enrollment, authorization windows and attendance-based billability.
• Rules for when an incomplete note or missing attendance holds a claim.

Before the first live claim, walk one test day through every step: a patient scheduled, attended, documented and billed. Check the resulting claim against the contract line by line. Then send the first real claims to each payer in a small batch and wait for the responses before releasing the rest. A setup error caught on three claims is an afternoon; caught on three hundred, it is a month.

For the program-day detail, see what has to be true before an IOP day is billable; for day-based residential billing, see per-diem and case-rate billing.

Transitions between your own levels of care

Once you run two levels of care, a new event appears: a patient moving from one of your programs to the other. Inside the building, step-down from residential to PHP feels like continuity of care. To a payer it is often a new level with its own medical necessity, its own authorization and sometimes its own claim form. Build one transition workflow with one owner, covering:

1. Transition documentation from the sending level explaining why the patient no longer needs that intensity.
2. Placement documentation at the receiving level supporting why this level is now appropriate.
3. A new or updated authorization where the payer requires one. An approval for residential days should not be assumed to cover PHP days.
4. A treatment plan reviewed and updated for the new level rather than carried forward unchanged. See treatment plan reviews.
5. Eligibility re-checked for the new level.
6. Billing switched over on the correct date, with no day billed at both levels.

The usual failure looks like this: the patient steps down on a Friday afternoon, attends PHP on Monday, and nobody requested the authorization because utilization review thought the clinical team had it and the clinical team thought billing did. A single owner and a written checklist prevent most of it. For the review side, see utilization review from first authorization to appeal.

The first 90 days

Opening day starts the riskiest stretch, not the end of the project. Review weekly:

• Rejections and denials for the new program, grouped by payer and reason. Early denials usually point to a setup error, such as a code, identifier or enrollment, that will repeat on every claim until fixed.
• Payments compared against the contracted rate. A wrong rate loaded on either side shows up here first.
• Authorization utilization, with continued-stay requests started before approved days or units run out.
• Documentation timeliness by clinician.
• Census against capacity and staffing.

Hold formal reviews at 30 and 90 days with all six workstream owners. Bring the denial list, a sample of records and the authorization log. Revenue cycle KPIs covers how to count the numbers consistently so the 90-day review compares like with like.

A worked example (hypothetical)

Say a 30-staff outpatient substance use practice decides to add an adult IOP at its current address, under its existing tax ID.

In week one the owner writes the program description: a few hours a day, several days a week, adults with substance use and co-occurring conditions, two group tracks. The compliance lead takes it to the state licensing agency and learns the IOP needs its own license category and a site visit. The billing manager pulls the five largest payer contracts. In this example, two list outpatient professional services only, one already lists IOP with a per-diem rate on an institutional claim, and two require both an amendment and accreditation covering IOP.

That reorders the plan. The accreditation extension and the two amendments become the critical path. The clinical director maps staff against the license rules and finds one more facilitator is needed, and credentialing for that hire starts as early as each payer allows. Note types, the program calendar and the claim setup are built in parallel. The program opens for members of the already-contracted payer first, adds the others as amendments take effect, and intake is scripted to explain this to callers honestly.

None of the timing in this example should be read as typical; it depends on the state and the payers. The point is the order: the questions with the longest answers get asked in week one.

Where your systems fit

If your current system was built around appointments, a program day is where it shows: attendance on a sign-in sheet, authorizations in a spreadsheet, and a census nobody trusts. On Unisona Health, PHP and IOP attendance is the billing record, per-diem minimums are checked on the day and continued-stay authorizations surface before they expire, on the same chart as the outpatient or residential record. Contracted rates per payer and per code can be loaded in contracts and rates so each remittance line is compared against them. Whatever system you use, run the new level of care end to end in it before the first patient arrives.

The consolidated checklist

1. Program description: level of care, population, hours, location, entity, staffing model and referral flow written on one page.
2. Licensing: state category confirmed, application submitted, policies written, space inspected, survey scheduled.
3. Accreditation: accreditor notified; each payer asked whether accreditation of the new service is a contracting condition.
4. Federal rules: Part 2 consents and disclosure workflows reviewed if the program treats substance use disorder.
5. Payer contracts: every agreement read; amendments in writing with services, codes, rate, claim form, authorization rules and effective date.
6. Enrollment: NPI, taxonomy, location and electronic claim enrollment confirmed with each payer.
7. Out-of-contract policy: written rule for admitting members of payers not yet contracted.
8. Staffing: roles mapped against license and contract requirements; gaps hired.
9. Credentialing: every rendering and supervising clinician enrolled for the new program with each payer, with effective dates recorded.
10. Training: role-based training completed and recorded close to opening.
11. Schedule: program calendar, attendance states, coverage plan, capacity and logistics set.
12. Intake: routing questions, level-specific eligibility checks, placement assessment and updated forms in place.
13. Documentation: note types, treatment plan templates, documentation window and escalation built.
14. Billing: location, codes, rates, claim forms, authorization tracking and pre-submission checks configured; a test day walked through.
15. Transitions: one workflow and one owner for moves between your levels of care.
16. First 90 days: weekly denial, payment, authorization and documentation review; formal reviews at 30 and 90 days.

Frequently asked questions