A PHP note needs more structure than a standard therapy progress note
Partial hospitalization program documentation often has more moving parts than a weekly outpatient therapy note. A PHP clinician may need to document daily therapeutic contact, safety concerns, group participation, medication coordination, treatment plan updates, discharge planning, and measurable progress toward goals.
A strong PHP note template gives clinicians a repeatable structure for capturing those details without rewriting the format after every service. It also helps keep documentation consistent across providers when multiple clinicians contribute to the same client’s care.
This guide gives you a practical PHP note template, sample documentation language, format comparisons, AI-assisted note guidance, privacy considerations, and a clear explanation of how AutoNotes can help create editable PHP note drafts faster while keeping the clinician responsible for review and final approval.
What “PHP note” usually means in behavioral health documentation
In behavioral health settings, PHP commonly refers to a partial hospitalization program. PHP services are typically more intensive than routine outpatient care and less restrictive than inpatient hospitalization. Clients may attend programming several days per week and receive a mix of individual therapy, group therapy, psychiatric services, psychoeducation, care coordination, and discharge planning.
Some organizations use similar abbreviations differently, and older documentation may refer to psychiatric history and physical documentation as “PHP” in local workflows. Before building a template, confirm what PHP means in your setting. For most therapy and behavioral health practices, this article focuses on partial hospitalization program notes.
A PHP note should connect the service provided to the client’s presenting problems, treatment plan goals, risk status, interventions, response, and next steps. It should not read like a generic attendance record. The note should show why the level of care remains clinically appropriate or why a transition in care is being considered.
Core sections to include in a PHP note template
A PHP note template should be detailed enough to support clinical continuity, but not so bloated that clinicians avoid using it. The best templates guide documentation without forcing repetitive or irrelevant text.
Use these sections as a starting point:
- Client and service details: Client name or identifier, date, program name, service type, location or delivery method, start and end time, and provider name.
- Reason for PHP level of care: Presenting symptoms, functional impairment, safety concerns, recent crisis, or step-down from a higher level of care.
- Current clinical status: Mood, affect, behavior, thought process, orientation, engagement, symptom changes, and risk indicators.
- Interventions provided: Individual therapy, group therapy, skills training, safety planning, medication coordination, psychoeducation, family contact, or care coordination.
After the intervention section, the note should shift from what the provider did to how the client responded. This is where many PHP notes become too thin. “Client participated” is usually not enough. A stronger note describes the client’s engagement, insight, barriers, skills practiced, and connection to treatment goals.
- Client response: Participation level, affective response, statements made, skills used, resistance, insight, or difficulty applying the intervention.
- Progress toward goals: Link the session or program day to specific treatment plan goals or objectives.
- Risk and safety update: Suicidal ideation, self-harm, homicidal ideation, substance use risk, protective factors, safety plan review, and supervision needs when applicable.
- Plan: Continued PHP attendance, treatment focus for next contact, referrals, medication follow-up, family session, discharge planning, or level-of-care review.
Free PHP note template you can adapt
You can copy and adapt the template below for your own documentation workflow. Adjust it to match your payer requirements, program policies, licensure rules, and electronic health record fields.
PHP progress note template
Client: [Client name or identifier]
Date of service: [Date]
Program/service: Partial Hospitalization Program
Service type: [Individual therapy / group therapy / psychiatric follow-up / family session / care coordination / treatment plan review]
Time: [Start time–end time]
Provider: [Name and credentials]
Presenting focus for today: [Brief description of symptoms, stressors, treatment goal, or program focus addressed during the service.]
Clinical presentation: [Mood, affect, behavior, thought process, orientation, engagement, speech, insight, judgment, and relevant symptom changes.]
Interventions: [Document specific clinical interventions used. Examples: CBT cognitive restructuring, DBT distress tolerance practice, motivational interviewing, relapse prevention planning, psychoeducation, grounding skills, safety planning, medication coordination, family communication support.]
Client response: [Describe how the client responded. Include participation, verbalizations, emotional response, skills practiced, barriers, insight, and readiness for change.]
Progress toward treatment goals: [Connect the service to one or more treatment plan goals. Include observed progress, lack of progress, or barriers.]
Risk/safety assessment: [Document current risk status, relevant denials or endorsements, protective factors, safety plan use, and actions taken if risk increased.]
Plan: [Next PHP service, continued interventions, referrals, medication follow-up, family contact, discharge planning, or level-of-care recommendation.]
Clinician signature: [Signature, credentials, date]
PHP note example for an individual therapy session
The following example is fictional and should be adapted to the client, service, and setting. Avoid copying sample language into a real chart unless it accurately reflects the session.
Presenting focus for today: Client attended PHP individual therapy focused on anxiety management, recent panic symptoms, and use of coping skills outside program hours. Client reported increased anxiety the previous evening after an argument with a family member but denied current suicidal or homicidal ideation.
Clinical presentation: Client was alert and oriented. Mood was anxious with congruent affect. Speech was normal in rate and tone. Thought process was coherent and goal directed. Client appeared tired but engaged, maintained appropriate eye contact, and was able to identify triggers related to family conflict and perceived criticism.
Interventions: Clinician used CBT interventions to help client identify automatic thoughts related to “I can’t handle this” and “everyone is disappointed in me.” Clinician supported client in generating alternative thoughts and practiced paced breathing during session. Clinician reviewed the client’s safety plan and reinforced use of crisis supports if symptoms increase.
Client response: Client participated actively and was able to identify two cognitive distortions with prompting. Client reported that paced breathing reduced anxiety from “8 out of 10” to “5 out of 10” during session. Client expressed concern about applying the skill during family conflict but agreed to practice before evening check-in.
Progress toward treatment goals: Client made partial progress toward the treatment goal of improving anxiety management by practicing one coping skill and identifying thought patterns that intensify panic symptoms. Continued PHP level of care remains clinically appropriate due to recent symptom intensity, need for daily skills practice, and ongoing monitoring.
Risk/safety assessment: Client denied current suicidal ideation, homicidal ideation, and intent to self-harm. Client identified sibling and crisis line as supports. Safety plan reviewed without changes.
Plan: Client will continue PHP programming tomorrow, practice paced breathing before and after family contact, and discuss barriers to skill use in next group session. Clinician will monitor anxiety symptoms and reassess safety at next contact.
PHP group note example
PHP programs often rely heavily on group services. A group note should describe the group’s clinical purpose, the intervention provided, and the client’s individual participation. Avoid documenting every client with identical language.
Group topic: Distress tolerance and crisis coping skills
Intervention: Clinician provided psychoeducation on short-term distress tolerance skills and facilitated discussion on using grounding, paced breathing, and sensory-based coping during acute emotional activation. Group members completed a written coping plan for high-risk evening hours.
Client participation: Client arrived on time and participated with moderate prompting. Client shared that isolation after dinner increases urges to use substances and identified taking a walk with a family member as a safer alternative. Client practiced a grounding exercise during group and reported mild reduction in emotional intensity.
Progress and plan: Client demonstrated increased awareness of evening triggers and identified one coping action aligned with the relapse prevention goal. Client will bring completed coping plan to tomorrow’s individual check-in for review.
SOAP, DAP, BIRP, and GIRP formats for PHP documentation
PHP notes can be written in several formats. The right choice depends on your program, payer expectations, EHR setup, and clinical preference. The format matters less than whether the note clearly documents medical necessity, clinical interventions, client response, progress, risk, and plan.
SOAP notes
SOAP stands for Subjective, Objective, Assessment, and Plan. It works well when a PHP program wants a clear split between client report, clinician observations, clinical assessment, and next steps.
- Subjective: Client report of mood, symptoms, stressors, cravings, sleep, medication concerns, or safety issues.
- Objective: Observable presentation, participation, behavior, affect, and group engagement.
- Assessment: Clinical interpretation, progress, risk status, and level-of-care rationale.
- Plan: Continued PHP schedule, interventions, referrals, safety actions, or discharge planning.
DAP notes
DAP stands for Data, Assessment, and Plan. It is often faster than SOAP because subjective and objective information are combined under Data. This can work well for busy PHP clinicians documenting several contacts in one day.
For example, the Data section may include the client’s report, observed affect, group participation, and intervention details. The Assessment section then explains clinical meaning, and the Plan section documents next steps.
BIRP and GIRP notes
BIRP stands for Behavior, Intervention, Response, and Plan. GIRP stands for Goal, Intervention, Response, and Plan. These formats are useful when the program wants documentation to stay tightly connected to treatment goals and client response.
For PHP services, GIRP can be especially helpful because it begins with the treatment goal addressed that day. This makes it easier to show how a group, individual session, or care coordination contact connects to the client’s plan of care.
Common PHP documentation mistakes to avoid
PHP documentation problems usually come from vague language, missing clinical reasoning, or notes that do not distinguish one service from another. A template can help, but the clinician still needs to document the actual service and clinical judgment.
- Using copy-forward language without updates: Repeated wording can make it unclear what happened during the specific service.
- Listing interventions without client response: A note should show how the client engaged, struggled, declined, improved, or used the intervention.
- Leaving risk status vague: If risk is clinically relevant, document what was assessed, what the client reported, protective factors, and the plan.
- Not connecting to the treatment plan: PHP notes should reflect active treatment goals, not just attendance.
Another common issue is documenting too much non-clinical detail. For example, “client discussed argument with partner for 30 minutes” is less useful than documenting the symptom pattern, intervention, response, and treatment relevance connected to that conflict.
How AI-assisted PHP notes can reduce after-hours documentation
AI-assisted notes are not a replacement for clinical judgment. They are draft-generation tools. The clinician provides session details, reviews the output, edits for accuracy, and finalizes the note according to the clinical record requirements.
For PHP documentation, AI can be helpful because the same clinician may need to complete several notes after a full program day. A structured AI note tool can turn brief clinical inputs into an organized draft with sections for interventions, client response, progress, safety, and plan.
Generic AI writing tools may produce polished text, but they are not built around behavioral health documentation workflows. A therapy-specific platform is more useful when it supports common clinical formats, service types, and treatment language while leaving the provider in control.
AI-assisted drafting can help with:
- Turning brief post-session details into a structured PHP note draft.
- Keeping language consistent across SOAP, DAP, BIRP, and GIRP formats.
- Reducing the blank-page problem after a full day of PHP services.
- Helping clinicians document interventions, response, progress, and plan in a repeatable structure.
Privacy, security, and clinician review for AI-generated PHP notes
PHP notes often include sensitive information about safety, trauma history, substance use, family conflict, psychiatric symptoms, and medication concerns. Any AI-assisted documentation workflow should be evaluated carefully before client information is entered.
Clinicians and practice owners should review how a documentation tool handles protected health information, account access, storage, permissions, audit practices, and vendor agreements. HIPAA responsibilities can vary by role and setting, so practices should follow their own policies and seek qualified guidance when needed.
Clinician review is non-negotiable. AI may misinterpret context, overstate progress, omit a risk detail, or use wording that does not match the service provided. The final note should reflect the clinician’s assessment and the actual care delivered.
Before saving an AI-assisted PHP note, check:
- Does the note accurately describe the service type, date, duration, and provider?
- Are interventions specific enough to support the clinical purpose of the service?
- Does the client response match what occurred?
- Are risk, safety, and plan details clinically accurate?
Editing is part of responsible use. AI should give the clinician a faster starting point, not remove clinical accountability.
How AutoNotes supports PHP documentation workflows
AutoNotes is built for behavioral health documentation, including progress notes, therapy notes, intake documentation, treatment planning, assessments, group notes, and other common clinical workflows. For PHP services, AutoNotes can help clinicians create structured, editable drafts from session details rather than starting from a blank note.
A PHP clinician can enter key details from an individual session, group, care coordination contact, or treatment plan review. AutoNotes then generates a draft organized around the selected service type and note format. The clinician reviews, edits, and finalizes the note before placing it in the clinical record.
This matters because PHP documentation is often high-volume and time-sensitive. If a clinician sees multiple clients, facilitates groups, and coordinates care in one day, even a few saved minutes per note can reduce late-evening paperwork. The benefit is not that AI “does the note” independently. The benefit is a structured draft that helps the clinician move faster while preserving review and control.
Where AutoNotes fits compared with other documentation options
A blank document gives maximum flexibility, but it also requires the clinician to build the structure every time. A static template improves consistency, but it still leaves the clinician writing most sections manually. A generic AI chat tool may create text quickly, but it may not follow behavioral health note conventions without repeated prompting.
AutoNotes is designed around clinical documentation tasks. Clinicians can use templates for specific services and generate note drafts that include clinically relevant sections such as interventions, client response, treatment plan progress, and next steps. The draft remains editable, so the provider can adjust tone, detail, risk language, and clinical reasoning before finalizing.
If you want a faster way to create PHP, SOAP, DAP, BIRP, GIRP, intake, and treatment planning drafts, you can start your free trial and test AutoNotes with your own documentation workflow.
Practical checklist for stronger PHP notes
Use this checklist after drafting a PHP note, especially when documenting high-acuity clients, safety concerns, or level-of-care decisions.
- Confirm the note identifies the correct service, provider, date, duration, and delivery method.
- Document the client’s current clinical presentation, not only the topic discussed.
- Name the interventions used and connect them to the treatment plan.
- Describe the client’s response with specific behavioral or verbal examples.
Then review the clinical reasoning. The note should show why the service was appropriate and what happens next.
- Include progress, limited progress, or barriers related to treatment goals.
- Address risk and safety when clinically relevant.
- Document coordination with psychiatry, family, school, work, or outside providers when applicable.
- End with a clear plan for continued PHP care, discharge planning, or level-of-care review.
Frequently asked questions about PHP note templates
What should a PHP note include?
A PHP note should include service details, presenting focus, clinical presentation, interventions, client response, progress toward treatment goals, risk or safety updates when relevant, and a plan. The exact fields may vary by program, payer, EHR, and provider discipline.
Is a PHP note the same as a regular therapy progress note?
Not usually. A PHP note may need more detail about level of care, safety monitoring, group participation, treatment intensity, coordination, and discharge planning. A standard outpatient therapy note may be shorter and focused on one weekly session.
Can I use SOAP for PHP documentation?
Yes. SOAP can work well for PHP notes because it separates client report, objective presentation, clinical assessment, and plan. DAP, BIRP, and GIRP can also work if they capture the required clinical details.
How detailed should a PHP group note be?
A PHP group note should document the group topic, clinical intervention, and the client’s individual participation and response. Avoid using the same participation language for every client unless it is truly accurate.
Can AI write PHP notes for me?
AI can help create a structured draft, but the clinician should review, edit, and finalize the note. The final documentation should reflect the actual service, the client’s presentation, and the clinician’s judgment.
How does AutoNotes help with PHP notes?
AutoNotes helps behavioral health professionals create structured, editable note drafts from clinical details. For PHP workflows, it can support individual therapy notes, group notes, care coordination documentation, treatment plan updates, and other service-specific drafts.
Do I still need to edit an AutoNotes draft?
Yes. AutoNotes is designed to give clinicians a faster starting point. You should review the draft for accuracy, adjust clinical language, confirm risk and plan details, and finalize the note yourself.
Where can I try AutoNotes for PHP documentation?
You can try it free and test AutoNotes with your own PHP note format, service types, and documentation preferences.
Start with a PHP template, then improve the drafting process
A PHP note template can make documentation more consistent, especially when clinicians need to document multiple services across a high-intensity program day. The template should capture the clinical reason for care, interventions, client response, treatment progress, safety updates, and next steps.
If the template helps but the writing still takes too long, AI-assisted drafting can provide a more efficient starting point. AutoNotes helps clinicians create structured, editable PHP note drafts while keeping review, edits, and final approval in the provider’s hands. Start your free trial to see how it fits your documentation workflow.
