How to Document Peer Support Specialist and Recovery Coach Sessions
A practical guide for certified peer support specialists and recovery coaches on what to document, what to avoid, how to meet Medicaid billing requirements, and how to navigate 42 CFR Part 2 in SUD settings.
Peer support specialists and recovery coaches occupy a unique position in behavioral health. They bring something no licensed clinician can replicate: lived experience with mental health challenges, addiction, or both. That relational authenticity is the foundation of the role. But increasingly, programs that employ peer specialists also expect structured documentation, Medicaid-billable notes, and supervisor-ready session logs.
The result is a genuine tension. You are trained to be a peer, not a clinician. Your power comes from mutuality, not authority. And yet the system asks you to write notes that sound structured, meet billing requirements, and survive audits.
This guide walks through what peer support documentation actually requires, what you must avoid writing, how privacy rules apply in different settings, and how to write session notes that protect you, your organization, and the people you support.
What Makes Peer Support Documentation Different
Before getting into format, it helps to be clear about what peer support work actually is. A certified peer support specialist (CPSS) is someone with personal experience of mental health challenges or addiction who has been trained and certified to support others in their recovery. A recovery coach (sometimes called a peer recovery coach or recovery support specialist) typically works specifically in substance use settings, though roles vary by state.
Neither role involves clinical assessment, diagnosis, or treatment. That distinction shapes everything about documentation.
Licensed clinicians document clinical observations, diagnostic impressions, symptom severity, and treatment interventions. Peer specialists document something different: the content and quality of a supportive relationship, practical recovery tasks, progress toward self-defined goals, and the person's own report of their experience.
When peer specialists write notes that sound clinical, they create problems. Notes that include language like "client presented with depressed affect" or "SI denied" or "adjusted coping skills for anxiety" cross into clinical territory that peers are not trained or licensed to assess. This is not a technicality. It is a scope-of-practice boundary that protects the person being served and protects you.
What to Document
Peer support documentation should focus on three categories: what you did, what the person you supported said or reported, and what the plan is going forward.
Contact information is always documented: date, start and end time, location or service modality (in-person, phone, telehealth), and the name of the individual served. For Medicaid billing, units of service are calculated from start and end times, so precision here is not optional.
Service activities describe what actually happened during the encounter. This is where you document the nature of your peer support work: sharing relevant personal experience to normalize recovery challenges, working through barriers to treatment engagement, helping someone prepare for an appointment with their prescriber, practicing how to ask for what they need from a case manager, accompanying someone to a community resource, or reviewing their self-care plan. Be specific about the activity, not vague. "Provided peer support" tells an auditor nothing. "Reviewed individual's relapse prevention plan; individual identified two early warning signs she had not previously recognized" tells an auditor exactly what happened.
Individual's self-report captures what the person told you in their own words. You are not interpreting it clinically. You are recording it as their self-report. "Individual reports feeling more confident about upcoming court date after reviewing what to expect" is appropriate. "Individual appears anxious about court date" is not. The second phrasing is a clinical observation you are not qualified to make.
Progress toward goals documents movement (or lack of it) toward the recovery goals the individual set, not goals a treatment team assigned. Peer support centers on self-determination. If Marcus set a goal of attending three community AA meetings per week, you document how many he attended, what he said about them, and what he wants to do differently next week.
Next steps or plan closes the note with what you and the individual agreed on for the next contact or between sessions.
What NOT to Document
This section matters as much as the section above.
Do not document clinical observations. You cannot and should not record mood, affect, cognition, behavior, or symptom status the way a clinician would. If someone you are supporting is in visible distress, your note can say "individual reported feeling overwhelmed and tearful during session" (their self-report) rather than "individual presented with depressed mood, tearful, psychomotor slowing" (a clinical assessment).
Do not document diagnoses. You may know from the individual's own disclosure that they have been diagnosed with bipolar disorder. That disclosure is part of their story. It is not yours to record in your note unless the documentation system explicitly asks for it as a program-required field populated from clinical records.
Do not document treatment recommendations. You can note that someone expressed interest in trying a new medication and that you encouraged them to bring it up with their prescriber. You cannot note that "medication adjustment may be warranted."
Do not document speculation about reasons for behavior. "Individual did not show for appointment; possible relapse" is speculation. "Individual did not appear for scheduled meeting; left voicemail to reschedule" is a fact.
Do not document detailed disclosure content that goes beyond what is needed. If someone shared a traumatic incident from their past in the context of processing their recovery narrative, you do not need to record the specifics of that trauma. The relevant documentation is that the individual shared personal history related to their recovery journey and what recovery-focused meaning they drew from it.
Medicaid-Billable Peer Support Notes
In most states, peer support services are a Medicaid-billable service under a specific benefit category. The exact requirements vary by state, but there are consistent elements that most programs require.
A Medicaid-compliant peer support note typically needs:
- Member identifying information: name, Medicaid ID, and date of service
- Service code and modifier: your state program will specify which HCPCS or CPT code applies (common codes include H0038 for self-help/peer services)
- Start and end time (not just duration): most billing systems require actual clock times
- Place of service code: 11 for office, 99 for home, 02 for telehealth
- Description of service activity: what peer support activity was provided, in the peer support scope of practice
- Documentation of medical necessity: many states require language connecting the peer support service to the individual's behavioral health diagnosis and treatment goals. This is written at the program level (it references the clinical diagnosis from their treatment record), not diagnosed by you.
- Signature and credentials: your name, CPSS certification number, and the date you signed the note
Programs typically use a structured note template that prompts you for these fields. If your agency provides a template, use it exactly. The consistency protects you and the agency in audits.
A Medicaid Note Example
Here is a realistic fictional example. Latanya is a CPSS working for a community mental health center. She sees Marcus, a 34-year-old man in recovery from opioid use disorder who is also managing depression.
A compliant note for a 45-minute in-person session might read:
Date of service: April 10, 2026. Start: 10:00 AM. End: 10:45 AM. Service: H0038, HQ modifier. Place of service: 11 (office). Member: Marcus R., Medicaid ID 00000000.
Service activity: Met with individual in office. Individual reported completing three NA meetings this week as planned and described feeling less isolated. Reviewed individual's personalized recovery plan; individual identified goal of restarting gym membership as a recovery support activity. Peer shared personal experience with the role of physical activity in sustaining recovery. Assisted individual in identifying logistical barriers (transportation, cost) and explored solutions. Individual expressed interest in the YMCA's sliding-scale membership program; provided referral information. Discussed upcoming clinical appointment and individual's plan to raise medication side effects with prescriber.
Plan: Individual will contact YMCA before next session. Next peer support contact scheduled April 17, 2026.
Signature: Latanya W., CPSS #00000, April 10, 2026.
Notice what is not in that note: no clinical assessment of Marcus's mood, no diagnostic language, no speculation about relapse risk, and no treatment recommendations.
42 CFR Part 2 and Peer Support in SUD Settings
If you work in a substance use disorder (SUD) program that receives any federal funding, your records are governed by 42 CFR Part 2, a federal privacy regulation that is stricter than HIPAA for substance use records specifically.
Under 42 CFR Part 2, records that identify a person as having or having had a substance use disorder, and that are created by a federally assisted program, cannot be disclosed without the patient's written consent, even to other providers, even in emergencies (with limited exceptions). This is more restrictive than the HIPAA treatment, payment, and operations (TPO) carve-outs.
What this means for peer support documentation in SUD settings:
Your notes are Part 2 records if you work within or are employed by a Part 2-covered program. That means they carry all the restrictions of Part 2, including restrictions on sharing with other providers within the same health system without specific patient authorization.
The 2024 Final Rule (effective February 2026) aligned 42 CFR Part 2 more closely with HIPAA for some TPO disclosures, allowing a single consent to cover ongoing TPO sharing within integrated care settings. This reduces some of the friction that previously prevented peer support records from being integrated into shared care records. However, the core rule still applies, and programs must have their consent infrastructure updated to reflect the new rule.
In practice: your program's compliance officer or supervisor should be guiding you on what consent forms are in place and what the sharing rules are. Your job as a peer specialist is to document accurately and flag any situations where you are uncertain whether sharing information is permitted. When in doubt, do not share and do ask.
Documentation discipline matters more in Part 2 settings because notes that contain unnecessarily detailed SUD-related disclosures increase risk if those notes are ever disclosed improperly. Write what is needed. Do not write what is not.
Supervisor-Required Session Logs
Many peer support programs require session logs in addition to, or separate from, billing notes. These serve a supervisory purpose: they help your supervisor understand what you are doing, flag situations that need clinical consultation, and document your professional development over time.
Session logs are typically less formal than billing notes and may include:
- A brief narrative of how the session went (your own reflective perspective, not a clinical assessment)
- Any situations that felt challenging or that you want to bring to supervision
- Whether there are any concerns that warrant clinical staff awareness (without crossing into clinical assessment yourself)
- Questions or learning needs you have identified
These logs belong in your own practice development records, not in the member's clinical file. The clinical file contains only the member-facing service documentation.
The Core Tension: Peer and Practitioner
The hardest part of peer support documentation is not learning a format. It is holding two realities at once.
You came into this role because you have been where the people you serve have been. That history gives you credibility that no degree can. But the system that employs you operates on documentation, billing codes, and audit trails. It does not run on human connection alone.
The risk is that documentation pressure gradually shifts your self-perception from peer to provider. When that happens, peers sometimes begin writing like clinicians, speaking like clinicians, and eventually seeing themselves as clinicians in all but credential. That is a loss for everyone: for the individuals served, who lose access to the distinctive gift of peer mutuality, and for the peer specialist, who has traded the most powerful part of the role for a paperwork identity.
Good documentation practice holds both sides. You write clearly enough to satisfy billing requirements. You write specifically enough to be useful to supervisors and treatment teams. And you write truthfully enough to remain a peer: recording what the individual said, what you did together, and what comes next, without clinical framing that does not belong in your role.
Practical Strategies
Write your notes the same day. Peer support encounters are relational and often feel less formal than clinical sessions. That can make it easy to defer notes. Do not. Memory fades and details blur. Accurate notes require same-day documentation.
Use your program's template. If your agency provides a structured note template, fill it out completely every time. Templates exist because they reflect what your program's billing system and state Medicaid requirements actually need. Improvising your own format creates gaps.
When something significant happens, document it plainly. If an individual expressed thoughts of suicide or overdose, you are responsible for documenting that you heard it, that you took it seriously, and that you followed your program's protocol (which almost certainly means immediately notifying a licensed clinical staff member). Your note documents what you did: "Individual disclosed thoughts of self-harm during session. Per program protocol, immediately consulted supervising clinician [name] and remained with individual until clinician arrived." You do not assess the risk level. You document the fact and the action.
Ask your supervisor when you are uncertain. No guide covers every situation. Peer support is delivered in diverse settings, by people with different certifications, under different state regulations, in different program structures. When something comes up that you do not know how to document, the right move is to ask.
Keep personal disclosure out of the member's record. When you share your own recovery experience with an individual, that is a peer support intervention. It is appropriate to note briefly that you shared personal experience related to [topic] to normalize the individual's challenge. It is not appropriate to record the details of your own history in the member's chart. Your story is yours.
If your program uses a documentation tool like NotuDocs, you can build a peer support session template that prompts for the right fields and keeps you within scope automatically. A template-first approach means you fill in what happened rather than writing from a blank page each time.
Peer Support Documentation Checklist
Use this before signing any session note.
Contact and administrative
- Date, start time, and end time recorded
- Place of service documented (in-person/telehealth/phone/community)
- Service code and modifier included if required by your program
- Member name and ID included
Service content
- Specific peer support activities described (not "provided support")
- Individual's self-report reflected in their own words (not clinical interpretation)
- Progress toward individual's own recovery goals documented
Scope of practice
- No diagnostic language or clinical symptom assessment
- No treatment recommendations
- No speculation about causes of behavior
- No unnecessary detail about trauma or sensitive disclosures
Compliance
- For SUD settings: 42 CFR Part 2 consent and sharing rules followed
- Any urgent safety situations documented with actions taken and clinical staff notified
- Note signed and dated
Supervisor logs (if required)
- Reflective log submitted separately from member's clinical file
- Supervision topics flagged if applicable
Peer support documentation is not about proving you did clinical work. It is about showing that you showed up, that the encounter was meaningful, and that the individual is moving toward the recovery life they want. When you write with that frame in mind, the paperwork stops feeling like a threat to the relationship and starts feeling like a record of it.
Related articles:
