All how-to guides
Modality skill

How to do ERP (Exposure & Response Prevention) for OCD

Build the hierarchy, run the exposure, prevent the ritual, repeat.

8 min read·6 steps· Updated June 10, 2026
Use the tool
OCD / ERP Tool
An in-session ERP tool for OCD work: map the obsession-compulsion cycle (overt + mental rituals, feared outcome, reinforcer), build a SUDS-ranked exposure hierarchy, run a live exposure with a habituation curve drawn from logged SUDS readings, set the response-prevention plan, and assign repeat homework with a confidence rating.

ERP is the gold-standard psychotherapy for OCD. It works through inhibitory learning — the brain stores a new 'this is safe' memory alongside the old fear memory. The mechanics matter; here's how to deliver it cleanly.

Quick answer

Exposure and Response Prevention (ERP) treats OCD by deliberately triggering obsessions while preventing the compulsions that normally relieve them. Effective ERP builds a hierarchy of feared situations, works from moderate to high SUDS items, and stays in each exposure until distress drops by half or for at least 45 minutes — without reassurance, checking, or mental rituals.

Key takeaways

  • Psychoeducation: Explain the OCD cycle (obsession → anxiety → compulsion → relief → reinforcement) and how ERP breaks it.
  • Build the hierarchy: List feared situations, rate SUDS 0–100.
  • Set the exposure: Specific, repeatable, time-bound.
  • Prevent the response: No physical or mental compulsions.
  • Track expectancy violation: Predict the feared outcome (e.g.

When to use this

  • Diagnosed OCD or clearly OCD-spectrum presentations (BDD, health anxiety with ritual).
  • After psychoeducation and motivational work — ERP is harder than it sounds.
  • Generally NOT a fit for primary trauma without stabilization first.

Steps

  1. 1

    Psychoeducation

    Explain the OCD cycle (obsession → anxiety → compulsion → relief → reinforcement) and how ERP breaks it.

  2. 2

    Build the hierarchy

    List feared situations, rate SUDS 0–100. Start at a 40–60 rung — challenging but workable.

  3. 3

    Set the exposure

    Specific, repeatable, time-bound. In vivo > imaginal when possible.

  4. 4

    Prevent the response

    No physical or mental compulsions. Reassurance-seeking counts.

  5. 5

    Track expectancy violation

    Predict the feared outcome (e.g. 'I'll be contaminated for 3 days'), then notice what actually happens.

  6. 6

    Generalize

    Vary contexts, times, locations so the new learning travels.

Example

Sample exposure plan (contamination OCD)
Rung: touch doorknob in public bathroom without immediate handwashing.
Prediction: 'I'll feel disgusted for hours and probably get sick within 3 days' (SUDS 70; expectancy 85%).
Response prevention: no washing for 2 hours, no sanitizer, no mental review.
Generalize: repeat at gym, coffee shop, library across the week.
Outcome to discuss: did the feared thing happen? what surprised you about the curve of distress?

Quick checklist

  • Hierarchy ≥ 10 items, SUDS-rated.
  • Each exposure has an explicit prediction.
  • Response prevention covers covert (mental) rituals.
  • Variability built in (location, time, context).
  • Family accommodation addressed.

Common variations

Imaginal exposure

For situations that can't be staged (e.g. moral-scrupulosity obsessions): write a 1–2 paragraph script, read on loop.

I-CBT

Inference-based CBT — alternative for clients who can't tolerate classic ERP; works on the obsessional doubt itself.

Evidence base

ERP has Class I evidence (APA, NICE) for OCD with effect sizes routinely d = 1.0–1.5 across RCTs; response rates of 60–80% in well-delivered protocols.

Deep dive

Why response prevention is the active ingredient

Exposure alone produces transient anxiety reduction but does not cure OCD. The compulsion — the checking, the washing, the mental review, the reassurance-seeking — is what teaches the brain that the feared outcome was prevented by the ritual. Preventing the response is the corrective learning experience. Modern inhibitory learning models (Craske) downplay habituation as the mechanism and emphasize expectancy violation: the client predicts catastrophe, prevents the ritual, and the catastrophe does not occur. That mismatch is the therapeutic event.

Building a hierarchy that gets used

Hierarchies fail when they are abstract. 'Touch contaminated things' is not an exposure; 'touch the doorknob of the public bathroom for 30 seconds, then prepare a sandwich without washing' is. Each item should specify the trigger, the duration, the location, and the prevented compulsion. SUDS-rate each item at design time, then re-rate before and after each exposure session. Start at the 40–60 SUDS range — too low and there is nothing to learn from, too high and the client abandons treatment.

Reassurance, the invisible compulsion

Most OCD treatment failures involve undetected reassurance loops — the client googles symptoms after session, asks the partner 'are you sure I locked the door,' or mentally reviews the day to confirm nothing bad happened. Reassurance is a compulsion and must be on the response-prevention list. This includes therapist reassurance: 'You probably did not have a stroke' feels supportive and is, in fact, treatment-undoing. The ERP-consistent response is 'I notice the urge for me to reassure you — let's sit with the uncertainty together.'

Tips

  • Modern ERP focuses on inhibitory learning, not habituation — variability and surprise matter more than 'staying until anxiety drops'.
  • Family accommodation often maintains OCD; loop in supports.

Common pitfalls

  • Allowing covert rituals (mental review, reassurance from self) — they sabotage the exposure.

Related tools

Frequently asked questions

How many sessions does ERP take?

12–20 weekly sessions for typical OCD; more for complex or comorbid presentations.

People also search for

  • erp therapy for ocd examples
  • ocd exposure hierarchy template
  • intrusive thoughts ocd treatment
  • response prevention compulsions
  • inhibitory learning ocd

Related how-to guides