How to Document Therapy Sessions Using Collaborative Documentation

A practical guide for therapists who want to write session notes with their clients, covering what to document together, what to keep private, how to adapt SOAP and DAP formats, and how to address the most common objections.

Most therapists write session notes in private, after the client has left. It feels natural. The note is a clinical record, not a conversation. It captures things the client may not be ready to hear framed in clinical language. It uses diagnostic terminology, progress ratings, risk assessments.

But a growing number of therapists are doing something different. They are sitting with the client at the end of a session, or sometimes throughout it, and drafting the note together. Not handing over the record for the client to edit. Not reading diagnostic impressions aloud. Just writing the core of the progress note collaboratively, with the client present and contributing.

This practice goes by several names: collaborative documentation, shared documentation, client-centered note-writing, or, in contexts where the record is formally shared, open notes. The research behind it is more substantial than the practice's relatively low adoption rate might suggest. And for therapists who are spending two to four hours per week writing notes after hours, there is a structural case for trying it.

This guide covers how collaborative documentation actually works in practice, what you write together and what you keep to yourself, how to adapt it to common note formats, how to handle sensitive clinical content, and how to respond to the objections therapists most often raise when they first hear about it.

What Collaborative Documentation Actually Is

Collaborative documentation is not the same as letting clients read their full clinical record. It is not the same as asking clients to sign off on your interpretation of their session. And it is definitely not handing a client a blank DAP form and asking them to fill it out.

It is a structured workflow in which the therapist and client work together, typically in the last 5 to 10 minutes of a session, to identify the key elements of the note. The therapist types or writes while the client talks. The client describes what happened in their own words; the therapist translates that into the appropriate clinical language, often reading sections aloud for accuracy.

The research base comes primarily from community mental health settings. Studies published in the 2010s by David Roe, Nev Jones, and their colleagues in the United Kingdom found that collaborative note-writing improved clients' sense of engagement in their own care, increased their recall of session content between appointments, and reduced no-show rates. A commonly cited finding from the Collaborative Documentation research at the University of Tennessee found that therapists who adopted the practice reported a reduction in after-session documentation time of 20 to 30 minutes per day. For a therapist with a full caseload, that is a meaningful return.

The 21st Century Cures Act (2016) and the subsequent OpenNotes movement pushed this practice further into mainstream healthcare. Since April 2021, most US healthcare providers are required to give patients timely access to their clinical notes. Many therapists now work in systems where clients can read their notes within 24 to 72 hours of a session. Collaborative documentation is, in that context, less a philosophical choice than a practical one: if the client is going to read the note, it is worth writing it in a way that will make sense to them and reflect what actually happened.

What You Document Together

The most useful mental model is to separate the note into two layers: the shared layer and the private layer.

The shared layer is what you build with the client. It covers the factual and functional content of the session:

What the client worked on today (in their own words, then translated into clinical language)
How they described their mood, energy, or symptoms at the start of the session
What interventions were used and how the client responded
Any homework or between-session tasks, with the client's stated intention
Client-identified takeaways or insights from the session
Any changes to goals or treatment focus

This content is typically the core of the Data or Subjective section of a progress note. It is also where client language carries real clinical value. When a client says "I kept rehearsing the conversation in my head for three days and I couldn't let it go," that is more specific and more clinically useful than "client reported rumination." Writing it collaboratively means you capture the actual language.

Fictional Example: Vanessa, 31, GAD

Vanessa is a 31-year-old graduate student working on generalized anxiety disorder using CBT. Her therapist, Dr. Reyes, uses DAP format. Near the end of the session, Dr. Reyes says: "Let's spend a few minutes building the note together. I'll ask you some questions and type while you answer."

Dr. Reyes asks: "What would you say was the main thing we worked on today?"

Vanessa: "The thought record about the thesis deadline. I noticed I was catastrophizing about my committee's reaction."

Dr. Reyes types: Client engaged in cognitive restructuring targeting catastrophic predictions related to academic evaluation (thesis defense timeline). Client identified automatic thought: "My committee will see I'm not good enough and I'll fail." Applied thought record to examine evidence; client rated original belief 75/100, revised to 40/100 following examination of counterevidence.

Dr. Reyes then reads this back to Vanessa and asks: "Does that capture what happened?" Vanessa confirms or adds a detail. The section is complete in 90 seconds.

The homework section is equally quick: Vanessa says she plans to do one thought record before next session. Dr. Reyes types it. No reconstruction required later.

What You Keep Private

Not everything belongs in the collaborative layer. There is clinical content you document on your own, after the session, or in a separate clinical note that the client does not co-write.

Your clinical formulation typically stays private or is translated into plain language before being shared. If you are tracking patterns across sessions, noting that a client's presentation fits a schema-driven avoidance cycle, or refining your diagnostic impression, those clinical inferences belong in the assessment section of the note, which you complete independently.

Risk assessments require careful handling. When safety concerns arise, you need to document your clinical reasoning, the specific questions you asked, the client's responses, and your risk stratification. Some of this can be done collaboratively and transparently: "I want to document the safety check we did. I'm going to write that you reported no current suicidal ideation, no plan, no intent, and that your safety plan is in place. Is that accurate?" But the clinical reasoning behind your risk stratification (why you assessed low versus moderate risk, what factors you weighed) typically goes in the assessment portion, which you write independently.

Third-party information stays out of the collaborative note. If a client's spouse called between sessions, or a collateral contact shared something relevant, that information belongs in a separate contact note, not in the collaborative portion of the session note.

Psychotherapy process notes (sometimes called private process notes) remain entirely private. If you keep notes on the therapeutic relationship itself, your countertransference, or process observations that you would not want disclosed even in litigation, those are not part of the collaborative documentation workflow.

The practical boundary looks like this: the collaborative portion of the note covers what happened in the session and what the client said. The independent portion covers your clinical interpretation of what it means and what you plan to do about it.

Format Adaptation: DAP, SOAP, and BIRP

Collaborative documentation works with all common note formats. The key is knowing which sections to build with the client and which to complete alone.

DAP (Data, Assessment, Plan)

This is probably the most collaborative-friendly format because the structure maps cleanly onto the two-layer model described above.

Data section: Build this with the client. Data is the factual record of the session: what was discussed, how the client presented, what interventions were used, what the client said and did. This is where client language is most valuable.

Assessment section: Write this independently, after the client leaves. Assessment is your clinical interpretation: how the client is progressing, whether they are meeting treatment goals, your reasoning about diagnosis or treatment response, and your clinical risk determination. This requires clinical judgment, not collaboration.

Plan section: This can be a hybrid. The between-session tasks and next session agenda are collaborative. Your clinical reasoning about treatment direction (why you are shifting from behavioral activation to cognitive restructuring, for example) is yours to add afterward.

SOAP (Subjective, Objective, Assessment, Plan)

Subjective: Build with the client. This is the client's own account of how they are doing and what happened today.

Objective: Partially collaborative. Behavioral observations (client appeared alert and engaged, speech was normal rate and rhythm, mood was described as 6/10) can be verified with the client. Mental status elements that are your clinical observation (psychomotor retardation, flat affect) are yours to add.

Assessment: Write independently.

Plan: Hybrid, same as DAP.

BIRP (Behavior, Intervention, Response, Plan)

Behavior: Build with the client. What did the client present with today? This is observable and factual.

Intervention: This can be co-written, though the therapist often leads. "We used a thought record today" is something the client can confirm and describe.

Response: Build with the client. How did the client respond to the intervention? The client's description of their own response is more specific than your inference.

Plan: Hybrid, as above.

Ethical Considerations and Sensitive Content

Collaborative documentation raises real ethical questions that deserve honest treatment, not just enthusiasm.

Before introducing collaborative documentation, explain what it involves and give the client a genuine choice. Some clients will find it empowering. Others will find it anxiety-provoking, particularly those with trauma histories or significant shame about their presenting concerns. A client who fears having their struggles "written down in front of them" may have real reasons for that fear, and those reasons are worth exploring clinically.

Document the conversation about collaborative documentation in the intake record or early session notes, including the client's response and agreement.

Diagnostic Language

Most clients are not prepared for clinical diagnostic language. If you write "client exhibits features consistent with BPD-spectrum dysregulation" in front of a client who did not know that was part of your formulation, that is a clinical rupture waiting to happen, not a therapeutic moment.

The practical solution is to complete the assessment section, including diagnostic reasoning, privately. If your formulation is something the client needs to know, address it as a clinical conversation during the session itself, not as a disclosure moment while you are typing notes together.

Sensitive Disclosures

If a client disclosed something significant in a session (a trauma memory, a relational betrayal, a secret they have held for years), collaborative documentation of that content requires care. Some clients will find it meaningful to have you acknowledge and record what they shared. Others will feel exposed. Read the room. It is always acceptable to say: "I'm going to note what you shared today, but I want to be thoughtful about how I word it. Can we check in about that next week?"

The Coercive Documentation Risk

There is a subtle but real risk that collaborative documentation, done poorly, can feel coercive. If a client feels they must agree with how the therapist is framing the note, they may comply without actually consenting. Mitigate this by explicitly inviting pushback: "Does this sound right to you? Is there anything I'm missing or anything you'd want me to say differently?"

If a client says "I'd rather you just write it yourself," that is a legitimate clinical preference, not a failure of the approach. Respect it.

Addressing Common Objections

"It will disrupt the therapeutic relationship."

This is the most common concern, and it is not unreasonable. Introducing any new activity in the last minutes of a session changes the texture of the ending. For some clients, this is disruptive. For many, particularly those in longer-term treatment who have a stable therapeutic alliance, it is not.

The evidence from collaborative documentation research is actually in the opposite direction from this objection. Clients who participate in writing their own notes report feeling more respected, more engaged in their care, and more empowered in the therapeutic relationship. The act of being asked "what would you say we worked on today?" can itself be therapeutic, requiring the client to articulate and consolidate what happened in the session.

Introduce it carefully, explain the rationale honestly, and monitor the client's response over several sessions.

"I work with trauma survivors who cannot engage with this."

For some trauma clients, particularly those in early-stage trauma work where stabilization is the priority, collaborative documentation is not appropriate. Asking a client to help document a session in which they accessed traumatic material can feel retraumatizing or can interrupt the necessary post-session integration process.

This is a clinical judgment call, not a categorical rule. Collaborative documentation can work with trauma clients in later stages of treatment, when the alliance is strong and the client has developed sufficient regulation capacity. It is simply not a good fit for every client at every stage.

"My notes include things the client cannot see."

This objection often rests on a conflation of the collaborative layer and the full clinical record. You are not showing the client everything. You are building one section of the note together, then completing the rest privately. The distinction matters. The client does not read your assessment of their diagnostic formulation. They help you capture what happened in the session today.

"I use a specialized format that requires clinical judgment in every section."

Some therapeutic modalities (EMDR, IFS, PCIT) have documentation structures where every section involves clinical interpretation. In those cases, collaborative documentation may be limited to a briefer check-in portion: "Here's what I'm going to note about today's session. Let me read it to you and see if it sounds accurate." That is not full collaborative documentation, but it still captures the client's perspective on accuracy and maintains transparency.

Integration with AI Documentation Tools

If you use a template-based documentation tool in your practice, collaborative documentation integrates naturally into the workflow. The collaborative portion of the session produces the raw material: the client's words, the named interventions, the described responses. You then enter that material into your documentation tool immediately, while it is fresh, completing the independent clinical sections (assessment, risk analysis, treatment direction) separately.

Tools that work from structured templates, where you fill specific fields rather than generating text from a session recording, align well with this approach because the template fields map cleanly onto the collaborative and private layers described in this guide. NotuDocs, for example, lets you define your own note structure and fill each section from your post-session notes, which works whether you wrote collaboratively with the client or reconstructed the session on your own.

Common Mistakes

Starting collaborative documentation without informed consent. The client needs to understand what you are doing and why before you open a laptop and start typing while they speak.

Documenting the client's full diagnostic formulation in front of them. Assessment is your clinical layer. Keep it private.

Using clinical jargon while writing with the client present. If you type "client exhibited labile affect with signs of object constancy disruption," and the client can see the screen, you have a clinical conversation to have that you did not plan for.

Abandoning the approach after one uncomfortable session. Many clients need two to three sessions to get comfortable with collaborative documentation. One awkward attempt is not data; it is a learning curve.

Treating the collaborative note as the complete clinical record. The note you build together is part of your documentation. Your assessment, clinical reasoning, and treatment planning reflections are added independently. The full record includes both layers.

Forgetting to document the client's response to collaboration itself. If a client expresses hesitation, discomfort, or enthusiasm about the practice, that belongs in the record. It is clinically relevant information about how the client engages with their own care.

Checklist

Before Introducing Collaborative Documentation

Reviewed the client's clinical presentation and history to assess fit (trauma stage, severity, readiness)
Planned how to explain collaborative documentation to the client in plain language
Determined which sections of your note format will be built collaboratively and which will remain private
Prepared to document the consent conversation itself

In the Session

Explained the purpose and process to the client before the first collaborative session
Invited the client's genuine input, not just confirmation ("Is there anything I'm missing?")
Avoided clinical jargon in the collaborative portion of the note
Read collaborative sections aloud to the client for verification
Maintained awareness of the client's emotional state and pacing during the documentation portion
Respected any client preference to not participate

After the Session

Completed the assessment section (clinical formulation, risk determination, treatment direction) independently
Added any third-party information or collateral contact notes in a separate entry
Documented the client's response to collaborative documentation if clinically relevant
Signed and dated the complete note, not just the collaborative portion

For Specific Client Populations

Trauma clients: assessed stage of treatment and stabilization level before introducing
Clients with significant shame or stigma concerns: paced introduction carefully, monitored for discomfort
Clients who can access notes digitally: ensured the independently completed sections use language appropriate for client review
Minor clients: clarified with guardian about the collaborative documentation process and documentation access

If you are building a more efficient documentation workflow, these guides cover adjacent topics: