How to Document Intensive Outpatient Program (IOP) and Partial Hospitalization (PHP) Sessions

A practical guide for clinicians working in IOP and PHP settings. Covers group and individual note requirements, daily attendance tracking, utilization review documentation, higher-frequency treatment plan reviews, and step-down discharge planning for both mental health and substance use disorder programs.

Why IOP and PHP Documentation Is Different

If you have spent most of your career doing outpatient therapy, moving into an intensive outpatient program (IOP) or partial hospitalization program (PHP) will change how you write notes in ways that your outpatient training did not fully prepare you for.

The structural difference starts with frequency. In standard outpatient, a client sees you once a week. You write one progress note. The treatment plan gets reviewed every 90 days or so. In IOP, a client attends three to five days per week, often for three hours per session. In PHP, that becomes five to six days per week, five to eight hours per day. You are writing multiple notes per week for the same client. Each note needs to stand on its own while also connecting to a coherent longitudinal record. That volume compounds fast.

The documentation stakes are also higher. IOP and PHP are higher levels of care that justify significantly higher reimbursement rates than standard outpatient services. Payers, especially Medicaid managed care organizations and commercial insurers, scrutinize these programs closely. Your documentation has to answer one central question on every single note: does this client still medically necessitate this level of care? Not implicitly. Explicitly.

And then there is the setting complexity. Most IOP and PHP programs combine group therapy sessions, individual check-ins, medication management visits, skills training, and psychoeducation blocks. Each service type has its own documentation requirements, and they all have to integrate into a single coherent clinical record.

This guide covers how to handle each of those layers.

Group vs. Individual Session Notes Within IOP/PHP

Most of your documentation time in an IOP or PHP program will be spent on group therapy notes. That is where the bulk of the clinical hours happen, and it is where documentation templates save the most time.

Group Notes in IOP/PHP: What Makes Them Different

Group notes in IOP and PHP carry the same dual-level obligation as group notes in any setting: a group-level record and an individual member addendum. But the IOP/PHP context adds two requirements that standard outpatient group notes often omit.

First, every group note must explicitly address medical necessity. The individual addendum for each member needs to answer: why does this person still need this level of care today? This is not a once-a-week consideration. It is daily (or near-daily) in PHP and multiple times per week in IOP. Clinicians who write vague addenda ("Client participated in today's group and engaged appropriately") without connecting participation to clinical status and level-of-care justification create audit exposure.

Second, daily functional status needs to appear in the record with enough frequency that a reviewer can track the client's trajectory. Are they stable? Declining? Ready to step down? The documentation has to show movement, or justify why there is no movement.

A useful structure for IOP/PHP group note addenda:

Attendance and punctuality (arrived on time, arrived late, left early, no-show with reason)
Presentation at session start (affect, cognition, sobriety/mental status, any acute changes from previous session)
Participation in group content (engagement level, what they contributed or avoided, notable disclosures or behaviors)
Skill practice or psychoeducation engagement (did they complete the in-session exercise? How?)
Symptom status relative to admission criteria (current symptom severity compared to the criteria that qualified them for this LOC)
Level-of-care justification statement (a sentence or two explicitly noting that the client continues to meet criteria)
Plan (next session, any individual follow-up needed)

Individual Check-in Notes

Most IOP and PHP programs include brief individual check-ins or one-on-one therapy sessions alongside the group schedule. These are documented as standard individual progress notes, but they should reference the client's progress in the group component and connect to the unified treatment plan. Do not treat the individual note and the group addendum as siloed documents. They should tell a continuous story.

A Practical Example

Consider Marcus, a 38-year-old with major depressive disorder and co-occurring alcohol use disorder, enrolled in a dual-diagnosis IOP (three days per week, three hours per session). He is in his second week.

The group-level note for Monday's process group covers the session theme (triggers and urges), the group's collective engagement, and any notable dynamics, without naming individual members.

Marcus's individual addendum notes that he arrived on time, appeared mildly fatigued compared to Friday's session, engaged actively in the triggers discussion (shared a recent high-risk situation), completed the relapse prevention worksheet, denied current SI/HI, reported three sober days. The addendum closes with a level-of-care statement: "Client continues to meet IOP criteria given moderate depressive symptoms (PHQ-9: 14 at admission), early recovery phase, and co-occurring diagnosis requiring structured support. Discharge to standard outpatient not yet clinically appropriate."

That last piece is not optional. It is the documentation that defends the billed level of care.

Daily Attendance and Participation Tracking

IOP and PHP programs must maintain a formal attendance log separate from (or integrated with) clinical notes. Payers routinely request this during audits, and it needs to show not just whether the client was present but the exact duration of attendance.

Why duration matters: IOP billing often requires a minimum number of hours within the service day to bill at the appropriate code. If a client arrives 45 minutes late and leaves 30 minutes early from a three-hour session, you may not be able to bill that session as a full IOP unit. Your attendance documentation needs to capture actual time in services, not just presence or absence.

Attendance documentation should include:

Date and scheduled service time
Actual time client arrived and departed
Services attended (e.g., process group, skills group, individual check-in, medication management)
Duration of each service type attended
Reason for any absence or partial attendance (documented as reported by client or caregiver)
Contact attempts for no-shows (if your program policy requires outreach for missed sessions)

For substance use disorder IOP programs, drug screen results (if required by your program) should also be documented on the attendance record or in a daily clinical note, with a reference to the result and any clinical response. A positive screen is a clinical event, not just an administrative notation. It needs a response documented in the chart.

Absences and Level-of-Care Implications

Repeated absences in an IOP or PHP program are themselves a clinical data point. They may indicate that the client is not engaging at the level of care they were admitted to, which has two possible interpretations: either the client is ready to step down, or there is a barrier to attendance that needs to be addressed as part of treatment. Either way, it needs to be addressed explicitly in the record. "Client missed two of three sessions this week without contact" is not sufficient documentation. The clinical response to that pattern needs to appear.

Level-of-Care Assessments and Utilization Review Documentation

IOP and PHP programs operate under utilization review (UR) oversight. Payers authorize a set number of days or sessions and then require clinical documentation that justifies continuing the authorization. This happens on a cycle, often every five to seven business days in PHP and every two to three weeks in IOP, depending on the payer.

Your utilization review documentation is, in many programs, the single highest-stakes documentation task you perform. A UR denial costs the program (and the client) significantly. A well-documented UR request that clearly establishes ongoing medical necessity prevents that.

Level-of-Care Criteria

The most widely used criteria sets for IOP and PHP are the ASAM Criteria (American Society of Addiction Medicine, primarily for substance use disorder programs) and InterQual or MCG criteria (for mental health programs). Many commercial insurers have their own proprietary criteria sets that overlay these standards.

Your UR documentation should directly address the relevant criteria dimensions. For ASAM-based programs, this typically means documenting across six dimensions:

Acute intoxication or withdrawal potential
Biomedical conditions and complications
Emotional, behavioral, or cognitive conditions
Readiness to change
Relapse, continued use, or continued problem potential
Recovery and living environment

You do not need to write a clinical essay for each dimension. But you do need to have enough specific, measurable documentation across your clinical notes that, when you compile the UR summary, you can point to evidence in the record. A UR summary that is not supported by the underlying daily notes is a compliance problem.

What a Solid UR Summary Contains

Current symptom severity (specific scores on validated measures: PHQ-9, GAD-7, AUDIT-C, BASIS-24, or equivalent)
Functional status compared to admission
Response to treatment (what is working, what is not, what has changed in the treatment approach as a result)
Why outpatient level of care would be insufficient (this is the core of the medical necessity argument)
Active barriers to discharge (if client is not yet ready for step-down, what specifically needs to change?)
Anticipated timeline or discharge criteria (what does the client need to achieve to move to a lower LOC?)

Specificity is everything in UR documentation. "Client continues to struggle with mood symptoms" will not support continued authorization. "Client's PHQ-9 score remains 16, with active passive suicidal ideation without plan or intent, poor sleep maintenance, and inability to sustain sobriety in unstructured time without intensive daily support" gives the reviewer something to work with.

Treatment Plan Reviews at Higher Frequency

In standard outpatient therapy, treatment plan reviews happen every 90 days. In IOP, the typical requirement is every 30 days. In PHP, it is often every two weeks or even weekly in some programs. The exact schedule depends on your payer contracts, your state licensing regulations, and your accreditation body (CARF, Joint Commission, or state-specific standards).

This frequency is not bureaucratic excess. Clients in IOP and PHP are in intensive treatment precisely because they need active adjustment, not maintenance. A treatment plan that goes unchanged for eight weeks in a PHP program is a documentation problem and a clinical one.

What IOP/PHP Treatment Plan Reviews Must Cover

Current diagnosis (confirm, update, or add as clinically indicated)
Progress toward each goal and objective since the last review (use measurable indicators: scores, behavioral observations, self-report, collateral input)
Modifications to goals or interventions based on treatment response
Current level-of-care appropriateness (is this client still in the right program?)
Discharge planning status (what is the current discharge target, and what has changed in that estimate?)
Client participation in the review (most payers and accreditation bodies require documented client involvement in treatment planning)

For multi-disciplinary programs, the treatment plan review may involve input from the prescriber, case manager, group facilitators, and individual therapist. Document who participated in the review and in what capacity. If the client was present (or why they were not), document that too.

The Two-Week Review in PHP: Avoiding Documentation Fatigue

Writing a full treatment plan review every two weeks in a PHP program, while also writing daily or near-daily group note addenda and individual check-in notes, is genuinely demanding. The clinicians who manage it best tend to do two things: keep treatment plan goal language specific enough to be measurable without being so granular that every minor shift requires a full rewrite, and use their daily notes to do continuous documentation of progress so that the review is a summary, not a reconstruction.

Step-Down and Discharge Planning Documentation

One of the most important things IOP and PHP documentation communicates is movement: the client is getting better (or worse), and the treatment intensity should change accordingly.

Step-down planning should appear in the chart before the client is actually stepped down. A discharge from PHP to IOP, or from IOP to standard outpatient, should be visible in the preceding documentation as a planned transition, not a sudden administrative event.

What Discharge and Step-Down Documentation Should Include

When documenting a step-down or discharge, the record should contain:

Clinical rationale for the transition (which criteria or indicators justified moving to a lower LOC)
Symptoms at discharge with validated scores compared to admission scores
Skills and competencies demonstrated that support functioning at a lower level of care
Continuing care plan (who will provide outpatient follow-up, what frequency, any medication management continuation)
Referrals made and confirmation of appointment scheduling (documented in chart)
Client's response to the step-down (did they agree with the clinical assessment? Are there concerns?)
Relapse prevention or crisis plan that applies to the lower-care environment
Emergency contact and crisis resources reviewed with client

For substance use disorder programs, the discharge summary must also document the client's sobriety status, relapse risk factors, and recovery support resources (peer support, mutual aid groups, sober living if applicable).

When Clients Step Up Instead of Down

Not every IOP or PHP episode ends with successful step-down. Some clients deteriorate during treatment and require a higher level of care, including inpatient hospitalization. When this happens, the documentation should show the decision-making process: what changed clinically, what interventions were attempted at the current LOC, why step-up was indicated, and what referral and transfer actions were taken.

This documentation protects the clinician and the program. A well-documented step-up decision reflects appropriate clinical judgment. An undocumented sudden transfer raises audit questions about whether the program was monitoring the client adequately.

Documentation Differences Between Mental Health and SUD IOP

The structural documentation requirements above apply across both mental health and substance use disorder IOP and PHP settings. But there are some practical differences worth noting.

Mental health IOP/PHP programs typically use diagnostic criteria from the DSM-5-TR as the primary framework for level-of-care justification. Common presenting diagnoses include major depressive disorder, bipolar disorder, anxiety disorders, and PTSD. Documentation should reflect current symptom severity using validated measures (PHQ-9, GAD-7, PCL-5, MADRS, as appropriate) and track functional impairment.

Substance use disorder IOP programs (sometimes called ASAM Level 2.1) must document across the ASAM dimensions, track substance use status, document any drug screen results, and address co-occurring mental health conditions as an integrated part of the treatment plan. The relapse prevention plan and the recovery environment dimension (ASAM Dimension 6) are particularly important in SUD documentation because they directly address the payer's concern: will this client be able to maintain gains in a lower-care environment?

Dual-diagnosis programs, which treat both a primary psychiatric diagnosis and a co-occurring SUD, are the most documentation-intensive. The notes need to address both diagnostic frameworks, track symptoms and sobriety status simultaneously, and show integration of the dual-diagnosis treatment approach, not just parallel tracks.

Common Documentation Mistakes in IOP/PHP

Knowing what to avoid is as useful as knowing what to include.

Generic participation language. Notes that say "client was present and engaged" without specifics about what they engaged with, how they presented, or what their clinical status was that day do not meet utilization review standards and do not tell a clinical story.

Missing level-of-care justification. Every group note addendum in IOP or PHP should contain something that answers the question: why today? Routine notes that never address this are a payer audit waiting to happen.

Treatment plans that never change. A treatment plan that looks identical at the four-week review as it did on admission suggests either that the client has made no progress (which should be reflected in the documentation) or that the clinician is not actually reviewing the plan.

Attendance records that only show presence or absence. Payers need to see actual service hours to validate billing. Time-stamped attendance matters.

Discharge documentation written after the fact. Step-down documentation that appears to have been completed in a single sitting on the final day, rather than building over time through the clinical record, looks fabricated in an audit and may not survive review.

IOP/PHP Documentation Checklist

Daily Group Note Addendum

Session date, group type, duration attended
Client's clinical presentation at session start (affect, status, any acute changes)
Participation in group content (specific, not generic)
Symptom status relative to admission criteria
Explicit level-of-care justification statement
Drug screen result documented if applicable
Plan and any individual follow-up needed

Attendance Tracking

Date and scheduled session time
Actual arrival and departure time
Services attended with duration by service type
Reason for any absence or partial attendance
Contact attempts documented for no-shows
Drug screen results with clinical response if applicable

Utilization Review Documentation

Current validated symptom scores compared to admission scores
Response to treatment with treatment modifications noted
Specific clinical rationale for continued LOC (not just "ongoing symptoms")
Active barriers to step-down clearly stated
Anticipated discharge criteria documented

Treatment Plan Review

Review completed on required schedule (30 days IOP, 14 days PHP, or per payer)
Progress toward each goal with measurable indicators
Modifications to goals or interventions
LOC appropriateness addressed
Discharge timeline updated
Client participation in review documented

Step-Down and Discharge

Clinical rationale for LOC transition
Symptom scores at discharge vs. admission
Continuing care plan with confirmed appointments
Relapse prevention or crisis plan reviewed with client
Emergency resources documented
For SUD programs: sobriety status and recovery support resources

The documentation demands of IOP and PHP are real, and they are heavier than standard outpatient work. The volume of notes is higher, the stakes per note are higher, and the reviews are more frequent. Building a consistent system for each note type, including a structured template for group addenda that prompts the level-of-care justification language you need, is the most reliable way to keep documentation manageable without cutting clinical corners.

If you use NotuDocs, you can build separate templates for your IOP group addenda, PHP individual check-ins, and UR summaries, each with the specific structural prompts your program requires, so the documentation system supports your clinical work instead of dragging behind it.