OCD ERP Treatment Plan Template (With Progress Note Example)

Why an ERP Treatment Plan Needs Structure

An OCD ERP treatment plan turns a complex, distressing presentation into a workable clinical roadmap. ERP — Exposure and Response Prevention — is the structured psychological treatment for obsessive-compulsive disorder, and a written plan keeps the work organized: clear goals, a hierarchy of exposures, concrete response prevention rules, and a measurement plan you can actually track.

A good plan is a scaffold, not a script. It documents the route, but the clinician still owns readiness, pacing, and safety at every step. This post is a clinician tool — it is not patient treatment advice, and it does not diagnose or prescribe care for any individual.

What ERP Is (and Isn't)

ERP has two halves that work together. Exposure means deliberately confronting a feared trigger, intrusive thought, image, or situation. Response prevention means resisting the compulsion, ritual, avoidance, or reassurance seeking the person normally uses to relieve the distress. Doing one without the other is incomplete; exposure with the ritual still running is closer to ritual practice than treatment.

ERP is considered the first-line psychological treatment for OCD because of its very strong evidence base (IOCDF). On average, patients achieve about a 60% reduction in OCD symptoms, and hundreds of clinical trials have studied ERP in adults, adolescents, and children since the 1960s (IOCDF). The APA practice guideline likewise recommends cognitive behavioral therapy in the form of ERP, and/or an SSRI (or clomipramine), as first-line treatment, with ERP-focused CBT having the strongest evidentiary support (APA Practice Guideline for the Treatment of Patients With OCD).

One framing note worth a single sentence: many clinicians now design exposures around the inhibitory-learning or expectancy-violation model — where a new, safer association competes with the original fear — rather than relying only on within-session habituation (Jacoby & Abramowitz, 2016, Clinical Psychology Review).

A scope note: ERP for OCD is not the same as trauma-focused exposure or EMDR. The frames, targets, and contraindications differ. Don't conflate them when you write the plan.

The 6 Components of an OCD/ERP Treatment Plan

A complete plan usually covers six parts. The hierarchy mechanics are only one of them — building the fear ladder itself is covered in our companion post, Exposure Hierarchy Worksheet for ERP. Here we focus on the whole plan and the documentation around it.

1. Presenting Problem and Diagnosis Context

Document the clinician-determined diagnostic picture and the presenting OCD symptoms: primary obsessions, the compulsions and avoidance that maintain them, frequency, triggers, and functional impact. Note any subtype framing (for example, contamination, checking, symmetry, or unacceptable-thoughts presentations) you are using to organize targets. Diagnosis is a clinical judgment, not something a template confers.

2. Measurable Goals

Tie goals to both symptom reduction and functional recovery. Strong ERP goals are specific and trackable rather than vague. Examples of the shape of a goal:

• Reduce time spent on washing or checking rituals to a target range
• Reduce a baseline Y-BOCS total into a lower severity band over a defined window
• Restore a specific avoided activity (return to a feared room, resume a daily task)
• Reduce reassurance-seeking frequency to an agreed level

Pair each clinical goal with a functional one. "Lower Y-BOCS" matters more when it is paired with "return to cooking dinner without decontamination rituals."

It also helps to write objectives beneath each goal — the smaller, observable steps that show movement toward it. A goal might be "reduce checking rituals"; the objectives under it could be "complete three in-session checking exposures with response prevention" and "reduce evening lock-checking to one check." Goals describe the destination; objectives describe what you will actually document along the way. Keep both client-collaborative and revisable, because ERP targets shift as treatment uncovers new triggers and avoidance.

3. Baseline Measurement — Y-BOCS / CY-BOCS

The Yale-Brown Obsessive Compulsive Scale (Y-BOCS) is the standard severity measure for adult OCD. It scores 10 items, each rated 0-4, producing a 0-20 obsession subtotal and a 0-20 compulsion subtotal across five dimensions — time, interference, distress, resistance, and control — for a total of 0-40 (Goodman et al., 1989; see Y-BOCS overview).

Commonly used severity ranges (present these as widely used bands, not a single authoritative cutoff — exact labels vary by source, and some collapse 24-40 into a single "severe" range):

Y-BOCS total	Commonly used band
0-7	Subclinical
8-15	Mild
16-23	Moderate
24-31	Severe
32-40	Extreme

For children and adolescents (roughly ages 6-17), the CY-BOCS is the pediatric adaptation. It keeps the same 0-40 structure (0-20 obsessions + 0-20 compulsions) with a symptom checklist plus severity scale, and is typically clinician-rated with child and parent collaboration (Scahill et al., 1997, JAACAP; psychometric properties of child- and parent-report formats described in Storch et al., 2006). You can administer the pediatric scale through CoralEHR's free CY-BOCS assessment.

4. Exposure Hierarchy (Fear Ladder) with SUDS

The exposure hierarchy is the ranked list of feared situations the client will work through. Each item gets a predicted SUDS rating — the Subjective Units of Distress Scale developed by Joseph Wolpe (1969), traditionally scored 0-100 where 0 is absolute calm and 100 is the worst anxiety imaginable (SUDS overview). Some clinicians use a 0-10 SUDS variant instead; either is fine as long as you are consistent within a plan.

Order items from easier to harder by predicted SUDS so there is a shared starting point and a sense of progression. A useful hierarchy item is specific enough to practice — it names the trigger, the behavior, and the response prevention rule, not just a vague theme like "deal with contamination."

Within an inhibitory-learning framing, the hierarchy is less a staircase to climb in strict order and more a menu of expectancy-violation tests: the aim of each exposure is to disconfirm a specific feared prediction, not simply to wait for distress to drop (Jacoby & Abramowitz, 2016). Many clinicians still find predicted SUDS useful for ordering and pacing while treating the falling of distress as a byproduct rather than the goal.

To build and sort the ladder itself, use the free Exposure Hierarchy Builder and the Exposure Timer, and see the step-by-step mechanics in the Exposure Hierarchy Worksheet for ERP. This post does not repeat that how-to; it folds the hierarchy into the larger plan.

5. Response Prevention Rules

The response prevention half deserves its own line in the plan, written concretely and per exposure. A vague rule like "do not neutralize" is clinically accurate but too abstract for homework. Concrete rules travel better:

• No handwashing for 10 minutes after the exposure
• No rechecking the lock more than once
• No reassurance question after sending the message
• No mental reviewing or silent counting during the exposure
• No avoidance of the feared bodily sensation

Each exposure should name what the client is practicing not doing, not just what they are confronting.

6. Reassessment Cadence and Relapse Prevention

Decide up front when you will re-administer the Y-BOCS or CY-BOCS — for example, at a set interval or at defined milestones — so progress is measured, not guessed. Close the plan with relapse-prevention and maintenance planning: identifying early warning signs, keeping a short self-directed exposure routine, and scheduling booster contact if symptoms creep back.

Sample OCD/ERP Treatment Plan Template

The block below is a fill-in template using a fictional, non-PHI contamination-subtype example. Replace every field with clinician-documented information for a real client; nothing here describes or advises any actual person.

Field	Description	Example (fictional)
Presenting subtype	Clinician-documented OCD presentation	Contamination / washing
Diagnosis context	Clinician-determined dx and key symptoms	OCD; washing rituals after perceived contamination, ~3 hrs/day
Baseline Y-BOCS	Total + band at intake	26/40 (severe band)
Goal 1 (symptom)	Symptom-reduction target	Reduce daily washing time toward a defined lower range
Goal 2 (measure)	Measurement target	Move Y-BOCS toward the moderate band over the treatment window
Goal 3 (function)	Functional-recovery target	Resume preparing meals without decontamination rituals
Goal 4 (rituals)	Reassurance/ritual target	Reduce reassurance-seeking to an agreed lower frequency
Hierarchy excerpt	A few ordered steps (see below)	See table
Response prevention	Plan-level RP framing	No washing immediately after exposures; delay and shorten over time
Reassessment cadence	When measures repeat	Re-administer Y-BOCS at clinician-defined intervals
Relapse prevention	Maintenance plan	Self-directed exposures + early-warning-sign review

A short hierarchy excerpt for the same fictional example:

Step	Trigger	Predicted SUDS	Response prevention rule
1	Touch own office doorknob	30/100	Delay washing 5 minutes
2	Set bag on the office floor	45/100	No wiping the bag afterward
3	Touch a public stair railing	65/100	Delay washing 15 minutes, no sanitizer
4	Touch trash can lid, then eat a snack	85/100	No washing before eating; no reassurance question

ERP Progress-Note Example

A progress note should tie the session to clinical reasoning, not to the worksheet. Below is a fictional, non-PHI note modeled on a DAP-style entry, showing peak versus ending SUDS, response prevention, and homework.

Therapist and client reviewed the contamination-focused ERP hierarchy and selected a mid-range in-session exposure (touching a stair railing) with a response prevention rule of delaying washing for 15 minutes and using no sanitizer. Client completed the exposure with SUDS starting at 60/100, peaking at 72/100, and ending at 41/100. Client noted the feared prediction of "I will get sick" did not occur and reported the urge to seek reassurance decreased with repetition. Therapist assessed readiness, reviewed safety and response prevention parameters, and assigned the same exposure as homework. Plan: re-administer Y-BOCS at the next scheduled interval and advance to the next hierarchy step pending tolerance.

Notice the note records a clinical decision (the therapist selected and assessed), not an automated one. Avoid documentation that hands the decision to a tool:

Hierarchy generated the ERP plan automatically.

The plan and hierarchy organize the work. The clinician determines readiness, safety, pacing, homework fit, and treatment adaptation — and signs the note.

Clinical Guardrails

ERP should be collaborative, consent-based, and clinically supervised. Slow down or reassess when there are active safety concerns, unmanaged medical risk, severe dissociation, acute substance-use concerns, high dropout risk, or trauma material that needs a different treatment frame.

The goal is not to flood the client. It is to create meaningful learning — disconfirming feared predictions and reducing rituals and avoidance — in a clinically appropriate, well-paced way. A template can hold the structure; it cannot replace clinical judgment.

How CoralEHR Helps

CoralEHR is an AI-first, HIPAA-compliant EHR built for private-pay behavioral-health therapists, and it signs BAAs. For ERP work, it keeps planning, measurement, and documentation in one record.

Here is how the AI fits, stated plainly: CoralEHR drafts treatment-plan suggestions that you review, edit, and sign. There is no auto-sign and no auto-accept — nothing enters the record until a licensed clinician signs it. Validated instruments like the Y-BOCS, CY-BOCS, and PHQ-9 are attached verbatim from a catalog, so the scale you administer is the real, unmodified instrument. AI documentation is included on the Professional plan with no per-seat add-on. Your data trains nothing — under Anthropic's BAA and commercial terms, patient data is not used to train models. Treatment-plan drafts auto-delete after 30 days, and no session recording is required — drafts come from the notes you type, not a live recording.

The takeaway isn't "use the AI." It's that the clinician stays the author of record, the instruments stay valid, and your data trains nothing — the safeguards that let you save documentation time without giving up the signature or the responsibility behind it.

Try CoralEHR free for 30 days, no credit card. See pricing, review our BAA, or explore CoralEHR.

Takeaways

• An ERP treatment plan organizes six parts: presenting problem, measurable goals, baseline measurement, the exposure hierarchy with SUDS, response prevention rules, and a reassessment and relapse-prevention plan.
• Measure progress with the Y-BOCS (0-40) for adults or the CY-BOCS for kids, and track SUDS on hierarchy items session to session.
• Keep response prevention rules concrete and per exposure, and write progress notes that tie the session to clinical decisions.
• The template is a clinician tool, not patient treatment advice — readiness, safety, and pacing stay with the clinician.

Build the ladder with the free Exposure Hierarchy Builder and Exposure Timer, administer the CY-BOCS, and read the companion Exposure Hierarchy Worksheet for ERP. When you're ready to connect planning, SUDS tracking, assessments, homework, and progress notes in one record, try CoralEHR free — 30 days, no credit card.