How to Document Exposure and Response Prevention (ERP) Therapy for OCD

Related reading:

• How to Write a Good Clinical Narrative
• Progress Note Best Practices for Therapists
• Common Documentation Mistakes Therapists Make

---

Why ERP Documentation Is Different from General Therapy Notes

Most progress notes for individual therapy rely on narrative description: what the client brought to the session, what themes came up, what interventions were used, and how the client responded. This approach works well for modalities like psychodynamic therapy, CBT for depression, or supportive counseling, where the structure of the session is flexible and the key clinical content is often relational and verbal.

Exposure and Response Prevention (ERP) does not work that way. ERP for obsessive-compulsive disorder (OCD) and related anxiety disorders is a structured, protocol-driven treatment. Sessions follow a progression. Each exposure is planned, conducted, and measured. The client's distress level is tracked in real time using standardized scales. Whether the client performed or avoided response prevention (refraining from compulsions during exposure) is itself a clinical outcome that belongs in the record.

This means your ERP notes have to carry more structural information than a standard therapy progress note. A note that says "client practiced exposure to contamination fears and reported anxiety" is missing most of what a complete ERP record needs. It does not tell you where this exposure sits in the hierarchy, what the starting and ending distress levels were, whether habituation occurred, whether the client was able to refrain from compulsions, or how this session compares to the preceding ones.

This guide covers how to document each major phase of ERP treatment: the initial fear hierarchy construction, session-by-session SUDS tracking, response prevention adherence, habituation patterns over time, and how to write progress notes that serve both clinical purposes and insurance documentation requirements.

---

Documenting the Initial Fear Hierarchy Construction

What the Hierarchy Is and Why It Belongs in the Record

The fear hierarchy (also called an exposure hierarchy) is the foundational planning document for ERP. It is a collaboratively constructed ordered list of feared situations, objects, or thoughts, ranked from least to most distressing. The hierarchy guides the sequence of exposures throughout treatment and serves as a baseline against which progress is measured.

Because the hierarchy is built with the client and shapes every subsequent session, it belongs in the clinical record as its own document, not just as a passing reference in a session note. Many therapists include it as a structured attachment to the intake or initial treatment planning documentation.

What to Include in Hierarchy Documentation

A well-documented fear hierarchy includes:

• The specific feared stimulus or situation for each item, described concretely. "Touching a doorknob" is more useful than "contamination fears." "Writing a sentence and not checking it" is more useful than "fears about making mistakes."
• The initial SUDS rating assigned to each item. SUDS (Subjective Units of Distress Scale) is typically scored 0-100, where 0 represents no distress and 100 represents the most distress the client can imagine. Document whether you used a 0-100 or a 0-10 scale and stay consistent throughout treatment.
• The associated obsession and compulsion pair for each item, where applicable. This connects the hierarchy item to the OCD cycle: the intrusive thought or feared consequence, and the compulsion or ritual that has functioned as the client's relief strategy.
• The client's stated feared outcome, not just the triggering stimulus. "Client fears touching doorknobs because of belief that doing so will cause illness to a family member" tells the clinical story that "doorknob touching" alone does not.
• The date the hierarchy was constructed and any subsequent updates, since hierarchies evolve as treatment progresses.

Fictional Example: Initial Hierarchy Documentation

Client: Daniel, 28-year-old male presenting with contamination OCD. Assessment completed over two intake sessions. Initial hierarchy constructed in session 3.

Note: Hierarchy was reviewed with client and confirmed. Client agreed to begin exposures at the 30-50 SUDS range in session 4. Hierarchy will be updated as items are mastered or as new items are identified.

---

Tracking SUDS Ratings Across Sessions

Why SUDS Documentation Matters

SUDS ratings are one of the clearest outcome measures available in outpatient therapy. In ERP, they serve two functions: they guide the therapist's real-time decisions during an exposure (when to move on, when to hold, when to stop), and they provide longitudinal data that demonstrates treatment progress over time.

For insurance and clinical supervisors, SUDS data is particularly valuable because it is quantitative. A note that says "client showed significant progress" is difficult to evaluate. A note that shows starting SUDS of 70, ending SUDS of 30 during the third exposure to the same stimulus, compared to a starting SUDS of 70 and ending SUDS of 65 during the first exposure to that stimulus, tells a clear and defensible clinical story.

What to Capture for Each Exposure in a Session

For every exposure conducted in a session, your documentation should include:

• The specific exposure item, matched to the hierarchy item by name
• The starting SUDS rating at the beginning of the exposure
• Peak SUDS reached during the exposure, if it differs meaningfully from the starting rating
• Ending SUDS rating at the point of discontinuation (ideally when habituation has occurred or after the planned exposure duration)
• Duration of the exposure
• Whether response prevention was maintained throughout (see the next section)
• Therapist observations of the client's behavioral responses (avoidance behaviors, safety behaviors, escape attempts) that SUDS scores alone do not capture

Fictional Example: In-Session SUDS Tracking

Client: Daniel, session 7.

Session goal: Continue contamination exposures at mid-range hierarchy items. Target item: touching shared office surfaces (keyboard, desk, door handles) without handwashing.

Habituation across trials observed. Client was able to reduce starting SUDS from 55 to 45 across three trials of the same item with progressive loading. Ending SUDS at or below 50% of peak for all trials. Client reported surprise at the third trial: "I thought it would just keep building but it didn't."

---

Documenting Response Prevention Adherence

Why Response Prevention Documentation Is Its Own Category

ERP is not just about conducting exposures. The therapeutic mechanism depends equally on response prevention: the client's decision to refrain from performing compulsions during and after exposure, allowing natural habituation to occur rather than using compulsions to artificially reduce distress.

A client who engages with exposures but continues to perform compulsions immediately afterward is not receiving the full benefit of ERP, and may be inadvertently reinforcing the OCD cycle. Response prevention adherence is therefore a primary clinical outcome that deserves specific documentation, not a footnote to exposure data.

What to Document for Response Prevention

For each session, document:

• Which compulsions were targeted for response prevention during the session
• Whether the client maintained response prevention during the in-session exposure period
• Whether the client reported performing compulsions after the session (at home, following between-session exposures), and the approximate frequency and nature of those compulsions
• Any safety behaviors that may have functioned as covert compulsions during the exposure (mental rituals, seeking reassurance, distraction as avoidance)
• The client's ability to tolerate the urge to ritualize and any self-report of what made that possible or difficult

Documenting Mental Compulsions

Mental compulsions are particularly important to document explicitly because they are less visible than behavioral rituals. A client who looks as though they are completing an exposure while internally performing a neutralization ritual (mentally "undoing" a feared thought, counting, praying to cancel out harm) is engaging in a covert compulsion that undermines the exposure work.

When a client reports mental compulsions, document:

• The nature of the ritual (neutralization, mental checking, reassurance-seeking through rumination)
• The approximate frequency during or after exposures
• Whether the client has been able to identify and resist the mental ritual at any point
• How this is being addressed in treatment (often requires additional psychoeducation and graduated fading of the mental ritual as an explicit hierarchy item)

---

Documenting Habituation and Progress Over Time

Session-Level vs. Across-Session Habituation

There are two types of habituation that ERP documentation should track: within-session habituation (SUDS decreasing within a single exposure trial) and between-session habituation (the starting SUDS for a given exposure decreasing across multiple sessions as the trigger becomes less threatening through repeated non-reinforced contact).

Both types of habituation are clinically significant, and both should be visible in the record:

• Within-session habituation is visible in the SUDS tracking table for each session (starting SUDS to ending SUDS within a trial).
• Between-session habituation is visible when you compare starting SUDS for the same hierarchy item across sessions. If a client's starting SUDS for touching shared surfaces was 55 in session 7, 45 in session 9, and 30 in session 11, that is measurable progress that belongs in the record and in any treatment plan review.

Progress Notes That Show Habituation

A well-structured ERP progress note in the Assessment section should address:

• The specific exposure item(s) addressed this session
• Habituation observed (whether within-session, between-session, or both)
• Comparison to previous sessions for the same item or hierarchy level
• The client's self-report of generalization: Has the client noticed reduced distress outside of sessions when encountering the same or similar stimuli?
• Barriers to habituation, if progress has stalled: avoidance, covert compulsions, insufficient exposure duration, over-reliance on therapist presence

Fictional Example: Progress Note Excerpt

Client: Daniel, session 11.

Assessment: Client continued contamination exposures targeting mid-to-upper hierarchy items. Starting SUDS for public surface contact (the target from session 7) was 30 today, down from 55 when this item was first attempted. Within-session habituation occurred across all three trials, with ending SUDS between 20-25. Client reported that at work this week he touched shared office equipment without difficulty and did not feel the urge to wash. This represents the first spontaneous generalization to a naturalistic context he has reported for this item. Client continues to report difficulty with compulsions following unexpected encounters with vomit-related stimuli, which remain in the upper hierarchy and have not yet been targeted. No mental compulsions reported for contamination targets this session; client described catching himself beginning a mental checking sequence once, stopping, and not completing it.

---

Documenting In-Session vs. Between-Session Exposures

Why the Distinction Matters

ERP treatment involves two types of practice: in-session exposures conducted under the therapist's guidance, and between-session exposures assigned as practice homework. Both need to be documented, but they serve different clinical and documentation functions.

In-session exposures are where you establish proof of concept, conduct the most difficult items that the client cannot yet approach independently, and gather real-time SUDS data under controlled conditions. Between-session exposures are where generalization happens, the work moves into the client's real life, and the client begins to develop self-efficacy as their own exposure therapist.

Documenting Between-Session Exposures

For between-session exposure practice, your documentation should include:

• The specific practice assigned at the end of the previous session (the hierarchy item, the approximate duration or number of repetitions, the response prevention instructions)
• What the client actually completed, as reported at the start of the next session
• Self-reported SUDS during home practice, even if approximate
• Whether response prevention was maintained during home practice
• Any obstacles encountered (situational, motivational, or related to symptom fluctuation)
• The client's interpretation of the home practice experience and what, if anything, it taught them about the OCD cycle

Do not accept a summary response ("I did the homework and it went fine") without some detail. The quality of between-session practice data is a useful clinical signal. A client who consistently reports perfect, distress-free practice may be avoidantly completing homework at a level that does not challenge the OCD cycle. A client who consistently avoids home practice despite in-session readiness is giving you information about barriers to generalization that needs to be addressed directly.

Fictional Example: Between-Session Documentation

Session 11, opening review of between-session practice:

Assigned practice (from session 10): Touch shared surfaces at work (door handles, shared keyboard) twice daily without handwashing for 20 minutes following contact. Response prevention: no washing, no cleaning with hand sanitizer, no avoidance of eating after contact.

Client report: Completed practice on 4 of 7 days. Skipped 3 days due to increased work stress. On days completed: starting SUDS typically around 40-45, ending SUDS around 25-30. Maintained RP on all days completed; reported one instance of using a small amount of hand sanitizer on day 2 after touching elevator button ("it was just once"). Client noted that by day 4 of practice he was "barely thinking about it at the elevator." No washing rituals during the practice period on completed days.

Assessment of home practice: Partial completion with good quality on days practiced. The one breach of RP (hand sanitizer use) noted and explored without judgment. Reduction in anticipatory anxiety by day 4 suggests early between-session habituation. Incomplete adherence (4/7 days) likely reflects genuine situational stress rather than avoidance; will monitor.

---

Documentation for Insurance Purposes

Why ERP Is Well-Positioned for Insurance Documentation

ERP has one of the strongest evidence bases in outpatient psychotherapy for OCD and related disorders. Multiple randomized controlled trials and meta-analyses support its efficacy. This means that, when you document ERP well, you are writing notes that support authorization, justify continued treatment, and demonstrate medical necessity in terms that insurance reviewers recognize.

The core components that insurance documentation requires are the same components that good ERP clinical documentation produces naturally:

• Diagnosis and clinical need: OCD (or another anxiety disorder or OCD-spectrum disorder) with documented functional impairment
• Individualized treatment rationale: Why ERP specifically, and how the treatment plan was tailored to this client's specific symptom presentation and hierarchy
• Measurable goals: SUDS reduction targets, reduction in compulsion frequency, functional improvement goals tied to specific life areas
• Progress data: Session-by-session SUDS data, habituation documentation, and response prevention adherence records provide objective progress metrics that most insurers find compelling
• Medical necessity: Continued treatment can be justified by identifying remaining hierarchy items not yet addressed, barriers to generalization, relapse prevention work, or ongoing functional impairment in specific domains

What to Emphasize in Authorization Requests and Treatment Plan Reviews

When submitting treatment plan reviews or authorization requests for continued ERP, frame the documentation around:

• Current level of functional impairment using measurable examples (time spent on rituals per day, areas of life being avoided, impact on work or relationships)
• Progress relative to the hierarchy: how many items have been mastered versus remaining
• Between-session generalization: evidence that exposure learning is transferring to the client's real-world functioning
• Remaining clinical need: specific items or domains that still require treatment

Avoid vague language like "client is making progress" or "therapy continues to be beneficial." Replace these with specific data: "Client's starting SUDS for mid-range contamination items has decreased from a mean of 60 to a mean of 30 over the past four sessions, with consistent within-session habituation and initial generalization to workplace context. Upper-range hierarchy items (SUDS 85-95) have not yet been addressed."

CPT Code Documentation for ERP

ERP is typically billed under individual psychotherapy CPT codes (90834, 90837) depending on session length. Some providers also use 90875 or 90876 for biofeedback as part of anxiety treatment, though this is less common. Document the time spent in session accurately, as the CPT code selected should correspond to the actual face-to-face time. If you are providing ERP intensively (multiple sessions per week or extended sessions), document the clinical rationale for the frequency in the treatment plan.

---

Common Documentation Mistakes in ERP

Mistake 1: Narrative Notes Without SUDS Data

Writing "client engaged in exposure to contamination stimuli and tolerated distress well" without capturing numerical SUDS ratings discards the most objective clinical data ERP produces. SUDS ratings are the primary outcome measure for ERP. Notes without them are incomplete.

Fix: Build SUDS tracking into your session template so it is impossible to forget. Document starting and ending SUDS for every exposure trial, every session.

Mistake 2: Not Distinguishing In-Session and Between-Session Work

A note that blurs in-session exposures and home practice into a single narrative makes it impossible to evaluate what happened where, and whether generalization is occurring outside the clinical setting.

Fix: Use clear headings or sections: "In-Session Work" and "Between-Session Practice Review." Document them separately with their own SUDS data where available.

Mistake 3: Treating Response Prevention as Binary

Response prevention is not simply "maintained" or "not maintained." Clients often maintain RP partially, delay compulsions, perform modified or reduced rituals, or engage in mental compulsions that do not count as behavioral RP failures. Documenting only whether RP was "yes" or "no" obscures this clinical detail.

Fix: Document the quality of response prevention: full maintenance, partial maintenance with description, delayed ritual (how long the delay was), or substitution of a different compulsion. This gives you the granularity to shape the treatment plan accurately.

Mistake 4: Missing the Comparison to Previous Sessions

A progress note that describes today's session without referencing prior sessions leaves the reader with no sense of trajectory. The clinical value of ERP documentation is cumulative: it shows a pattern of habituation building over time.

Fix: Every Assessment section should include at least one direct comparison to a prior session. Reference the previous starting SUDS for the same item, the previous response prevention quality, or the previous level of generalization.

Mistake 5: Losing the OCD Cycle in Hierarchy-Focused Notes

As sessions focus on moving through the hierarchy, it is easy for notes to become a series of SUDS tables without any narrative connecting the work to the client's specific OCD presentation. Insurance reviewers and supervisors need to see that you understand the relationship between this client's specific obsessions, compulsions, and the exposures you are targeting.

Fix: Every few sessions, include a brief narrative paragraph in the Assessment section that names the obsession being targeted, the feared consequence, and how the current exposure work challenges that feared consequence. This does not need to be long. Two or three sentences anchors the data in the clinical context.

---

ERP Documentation Checklist

Use this after each session before closing the chart.

Session Basics

• Date, time, and session duration
• Client identifier and session number within ERP course
• Presenting diagnosis (OCD or OCD-spectrum disorder) with ICD-10 code
• Phase of treatment (psychoeducation, hierarchy construction, active exposure, maintenance/relapse prevention)

Hierarchy Status

• Current hierarchy version on file and up to date
• Hierarchy items addressed this session, referenced by name
• Any new hierarchy items added or existing items modified based on session data

In-Session Exposure Data

• Starting SUDS for each exposure trial
• Peak SUDS for each trial (if meaningfully different from starting)
• Ending SUDS for each trial
• Duration of each exposure trial
• Whether within-session habituation was observed
• Any safety behaviors or partial avoidance observed during exposure

Response Prevention Documentation

• Compulsions targeted for RP during session
• Whether RP was fully maintained, partially maintained, or not maintained
• Any covert or mental compulsions identified
• Client's self-report of RP difficulty or ease
• Any RP breaches explored without judgment, with updated clinical note

Between-Session Practice

• Assigned practice from previous session documented at start of note
• Client's self-report of completion rate for home practice
• Self-reported SUDS during home practice
• RP adherence during home practice
• Obstacles to home practice identified and addressed

Habituation and Progress

• Within-session habituation documented (start to end SUDS change)
• Between-session habituation documented (comparison to prior sessions for same item)
• Client self-report of generalization to naturalistic contexts
• Updated functional impairment estimate if treatment plan review is due

Assessment and Plan

• Connection to at least one measurable treatment goal
• Next hierarchy item(s) planned for upcoming session
• Any modifications to treatment plan based on progress or barriers
• Clinical rationale for continuing at current pace vs. advancing or pausing

Insurance and Administrative

• CPT code matches documented session length
• Progress framed in measurable terms (not "continues to improve" without data)
• Medical necessity supported by documented functional impairment and remaining clinical need
• Authorization timeline noted if review is approaching

---

If you are documenting ERP alongside other anxiety disorder treatments, How to Write a Good Clinical Narrative covers how to write the interpretive sections of a note with the specificity that ERP's structured data requires. For broader note format decisions, Progress Note Best Practices for Therapists addresses the structural elements that apply across modalities. And if you want to tighten your documentation before an audit or insurance review, Common Documentation Mistakes Therapists Make addresses the patterns that most often create problems.

ERP documentation rewards structure. The more systematically you capture SUDS ratings, response prevention adherence, and habituation data, the more clearly your notes tell the clinical story of a client moving through the hierarchy. NotuDocs lets you build an ERP-specific progress note template with built-in SUDS fields, response prevention checkboxes, and between-session practice prompts, so the structure is consistent across every session and you are not rebuilding it from scratch each time.