EMDR Progress Notes: Documenting Desensitization Phases and SUD Levels

EMDR documentation has a problem that other modalities do not share: the clinical work is highly structured, phase-specific, and data-driven, but the tools therapists use to document it are none of those things.

An EMDR desensitization session generates a wealth of specific clinical data. SUD levels at start and end. VOC ratings. The target memory, the negative cognition, the positive cognition. Number of bilateral stimulation sets. Channels of association that emerged. Blocking beliefs encountered. Whether the target was fully processed or requires continuation.

Try capturing all of that in a SOAP note. Subjective: "Client discussed a traumatic memory." Objective: "Client appeared distressed." Assessment: "Processing is occurring." Plan: "Continue EMDR."

That note is useless. It does not tell you where you stopped, what SUD level the client reached, which channels opened, or whether the positive cognition installed. Next session, you will be guessing instead of continuing precisely where you left off.

EMDR documentation needs to track the protocol. Here is how to do it well.

Why EMDR Documentation Is Protocol-Specific

EMDR is one of the most structured therapeutic modalities in practice. Shapiro's eight-phase protocol provides a session-by-session roadmap: history taking, preparation, assessment, desensitization, installation, body scan, closure, and reevaluation. Each phase has specific procedures, specific measurements, and specific decision points.

This structure is a documentation advantage -- if your tools support it. The challenge is that most EHR templates and AI note tools do not understand EMDR's protocol structure. They treat an EMDR session like any other therapy session: somebody talked, the therapist did something, and they plan to continue.

What makes EMDR documentation distinct:

• SUD and VOC tracking. Subjective Units of Disturbance (0-10) and Validity of Cognition (1-7) are quantitative measurements taken at specific points in the protocol. They need to be recorded with precision.
• Phase identification. Which phase of the protocol was the session in? This determines what procedures were used, what measurements were taken, and what comes next.
• Target and cognition tracking. The target memory, negative cognition, positive cognition, and emotion identified during the assessment phase persist across sessions. They need to be consistently documented.
• Bilateral stimulation parameters. Type (eye movements, tapping, audio), speed, and number of sets. These are part of the clinical record.
• Channel tracking. During desensitization, associations emerge in channels -- new memories, sensations, emotions, or insights that connect to the target. These need to be documented because they inform processing direction.
• Incomplete processing indicators. If a session ends before the target is fully processed (SUD at 0), the closure procedure used, the client's state at session end, and the plan for continuation need to be captured.

None of this maps cleanly to Subjective/Objective/Assessment/Plan. EMDR notes need a protocol-native format.

The Protocol-Native Note Format

A Protocol-Native format organizes documentation around EMDR's phase structure. It captures the data points that the protocol requires without forcing them into categories designed for talk therapy.

Format Structure

Phase and Target: What phase of the protocol was this session in? What was the target memory or issue being addressed? For desensitization sessions, what were the original assessment data points (NC, PC, emotion, SUD, VOC, body location)?

Processing Summary: What happened during bilateral stimulation? What channels of association emerged? How did SUD levels change across sets? Were there any blocking beliefs, feeder memories, or abreactions?

Measurements: SUD at start and end of processing. VOC at start and end (during installation). Body scan results. These are the quantitative backbone of EMDR documentation.

Clinical Observations: Therapist observations during processing -- affect changes, somatic responses, cognitive shifts, spontaneous verbalizations. These are the qualitative complement to the measurements.

Closure: How was the session closed? Was the target fully processed (SUD = 0, VOC = 7, clean body scan) or was processing incomplete? If incomplete, what containment or stabilization technique was used? What is the client's state at departure?

Plan: Reevaluation targets for next session. Any between-session instructions (container exercise, safe place practice, journaling). Treatment plan status.

This format is not mandatory. But it captures the clinical data that EMDR requires without the translation overhead of generic templates.

EMDR Progress Note Examples

Example 1: Desensitization Session -- Active Processing with Channel Tracking

This example shows a mid-treatment desensitization session for a client processing a motor vehicle accident.

What makes this note strong: It tracks SUD across sets, documents the channel that emerged (feeder memory), captures the spontaneous cognitive shift, and records bilateral stimulation parameters. The closure section documents an incomplete session with specific containment procedures. The plan connects to the target sequence and treatment goals.

Example 2: Installation and Body Scan -- Completing a Target

This example shows a session where the target reaches SUD = 0 and the therapist moves through installation and body scan.

What makes this note strong: It documents the transition across three phases (4, 5, 6) within a single session, tracks both SUD and VOC at each measurement point, and records the body scan result. The plan includes reevaluation and the next target in the sequence.

Example 3: What Generic AI Produces vs. Protocol-Native Documentation

Here is what a typical AI note tool generates from the session described in Example 1:

This note loses nearly everything that matters clinically. No SUD levels. No set-by-set tracking. No channel documentation. No distinction between desensitization and other phases. No closure procedure. No target sequence planning. "Eye movement exercises" reduces bilateral stimulation to a generic descriptor. "Relaxation techniques" replaces a specific container exercise and safe place protocol.

A therapist reading this note before the next session would not know where to resume processing, what channels were active, or what SUD level was reached. They would be starting from scratch.

The Protocol-Native note from Example 1 captures precisely where processing paused, what emerged, and what comes next. That is the clinical utility of documentation that matches the protocol.

Common EMDR Documentation Mistakes

Not recording SUD/VOC at each measurement point. SUD and VOC are the quantitative spine of EMDR treatment. If you only record start and end numbers without documenting changes during processing, you lose the trajectory that informs clinical decision-making. Was the SUD drop gradual (normal processing) or did it spike mid-session (new channel or blocking belief)? The pattern matters.

Describing bilateral stimulation as "EMDR techniques." Document the modality (eye movements, tapping, auditory), the speed, and the approximate number of sets. These are clinical parameters, not minor details.

Failing to document incomplete processing. Most desensitization sessions end before the target is fully processed. Your note needs to specify: what SUD level was reached, what closure technique was used, what the client's state was at departure, and exactly where to resume next session. Without this, the next session starts with uncertainty.

Not tracking feeder memories and channels. When a new memory or association emerges during desensitization, it may be a feeder memory that needs separate targeting or a channel that resolves within the current target's processing. Document it either way -- it informs your target sequence and your understanding of the trauma network.

Mixing phases without documenting the transition. If a session moves from desensitization (Phase 4) to installation (Phase 5) to body scan (Phase 6), each transition should be documented with the relevant measurements at each point. Collapsing everything into a single narrative obscures the protocol structure.

Over-relying on narrative at the expense of data. EMDR generates quantitative data (SUD, VOC, number of sets) that should be recorded as data, not embedded in paragraphs. "SUD: 6 → 2" is clearer and more useful than "the client's distress appeared to decrease over the course of the session."

Writing EMDR Notes Efficiently

EMDR's structured protocol actually makes documentation easier if you set up the right system. The data points are predictable -- you know you will need SUD, VOC, phase, target, and bilateral stimulation parameters every session.

Use a structured template with fill-in fields. Pre-build your note template with fields for Phase, Target, NC, PC, SUD (start/end), VOC (start/end), BLS type/sets, and Closure status. Filling in values is faster than composing paragraphs.

Track SUD in real time. After each set of bilateral stimulation, record the SUD rating immediately. A simple list -- "S1: 6, S2: 5, S3: 5, S4: 4, S5: 6, S6: 5, S7: 4, S8: 3, S9: 3, S10: 2, S11: 2, S12: 2" -- takes seconds to maintain and provides the full processing trajectory for your note.

Note channel content in shorthand during processing. When a new channel emerges, jot one phrase: "feeder: bike fall, parent yelled, self-blame" or "somatic: chest → hands → release." These anchors expand into full documentation in the note.

Document the session map before the narrative. Start with the measurements and phase transitions, then add clinical observations. The data points are the note's skeleton; the narrative is the muscle. Most EMDR notes can be written in three to five minutes this way.

TherapyDesk's modality-aware AI understands EMDR's phase structure and generates Protocol-Native notes that track SUD levels, document bilateral stimulation parameters, identify feeder memories, and distinguish between desensitization, installation, and body scan phases. If you want to see what that looks like for your own EMDR sessions, try the demo.

Adapting Documentation Across EMDR Phases

Not every EMDR session is a desensitization session. Your documentation emphasis should match the phase:

• Phase 1 (History and Treatment Planning): Document the trauma history, target sequence, and selection rationale. This is the roadmap for treatment.
• Phase 2 (Preparation): Document resource installation (safe place, container, other stabilization resources), client's readiness indicators, and informed consent for processing.
• Phase 3 (Assessment): Document the target image, negative cognition, positive cognition, emotion, SUD, VOC, and body location. This is the baseline data that anchors all subsequent processing.
• Phase 4 (Desensitization): SUD tracking, channel content, set-by-set processing, blocking beliefs, and abreaction management. This is the data-heaviest phase.
• Phase 5 (Installation): VOC tracking for the positive cognition. Document any strengthening or modification of the PC.
• Phase 6 (Body Scan): Result of the head-to-toe scan. Note any residual disturbance and its location.
• Phase 7 (Closure): Complete or incomplete? Containment used? Client state at departure? Between-session instructions.
• Phase 8 (Reevaluation): Has processing held? New disturbance? Target sequence update.

Each phase has different data requirements, but all of them are protocol-specific. Your documentation should reflect the phase you are in, not a generic summary of "did EMDR."

Conclusion

EMDR documentation is protocol documentation. The data points are built into the model: SUD, VOC, phases, targets, cognitions, bilateral stimulation parameters, channels, and processing outcomes. When your notes capture this data with precision, they serve you clinically -- you know exactly where to resume, what has processed, and what comes next.

When your notes are generic summaries, you lose the protocol thread. Next session becomes a partial reconstruction rather than a precise continuation.

The format you use matters less than whether it captures EMDR-specific data. But if your current template asks for Subjective/Objective/Assessment/Plan and you are spending five minutes translating desensitization phases into those categories, a Protocol-Native format will save you time and produce better documentation.

Want to see what EMDR documentation looks like when the AI understands the protocol? Try the TherapyDesk demo and see how modality-aware notes track SUD levels, phases, and bilateral stimulation automatically.