The language you put in a clinical note today will still be doing work ten years from now. Insurance reviewers will read it. Future therapists will read it. Case managers, school psychologists, disability evaluators, and the client themselves will read it. And every single one of those readers will use your language as a shortcut for understanding who this client is and what this client needs. When you write about a client with a PDA profile, the wrong language does not stay in the chart. It shapes every interaction that client has with the health and education systems for the rest of their life.
This is not a theoretical concern. We have watched it happen. A client seen by a previous therapist gets labeled "oppositional" in a note. The next provider reads the note, comes in with expectations of resistance, and structures the session around managing defiance. The client reads the room, recognizes the posture, and shuts down. The provider documents shutdown as further evidence of oppositionality. The chart builds on itself. By the third provider, the client has a documentation history that reads like a behavior problem, and the underlying nervous system pattern has never been named.
If you are treating clients with PDA profiles, you need a different documentation approach. Not because the clinical observations change, but because the words available to describe those observations carry freight that does not fit the mechanism you are actually looking at. This post is about what to write and what to avoid, with specific language you can start using in your notes this week.
The standard vocabulary for describing non-compliant behavior in clinical notes was built for a different population and a different theoretical model. Words like "oppositional," "defiant," "resistant," "manipulative," "noncompliant," and "avoidant" all assume a rational actor who is making a choice to not cooperate. When those words land in a chart, they activate behavioral framings in whoever reads the note next. The next clinician reaches for consequences, limit-setting, behavior plans, and contingency management, because that is what those words call for.
For a client with demand sensitivity, none of those interventions work and most of them cause harm. The non-compliance is not a choice. It is a threat response. The client's nervous system is registering the request as a danger and producing a protective reaction below the level of conscious choice. Writing "the client was oppositional" in this case is not neutral description. It is inaccurate, and the inaccuracy will drive future clinical decisions in the wrong direction.
The task in PDA documentation is to describe the behavior accurately without importing the explanatory framework that comes built into the standard vocabulary. That means naming the observable behavior, naming the nervous system state when you can see it, and leaving out the words that imply intent the client does not have.
Here are some specific swaps. The left-side phrase is what you might be tempted to write. The right-side phrase is what will serve the client better, describe the same observation more accurately, and not prime the next reader to misread the chart.
Instead of
Client was oppositional and refused to engage with the session.
Write
Client demonstrated a threat response to initial session demands, with withdrawal and low verbal output. Session adjusted to reduce demand character.
Instead of
Client was noncompliant with homework assignment.
Write
Client did not complete the between-session task. Clinical pattern suggests the task acquired demand character once assigned, which activated a nervous system response consistent with the client's known demand sensitivity profile.
Instead of
Client is manipulative and uses avoidance to control the session.
Write
Client's presentation is consistent with demand-avoidant responses to perceived pressure. Behaviors described as controlling are more accurately understood as autonomy-preserving strategies in the context of nervous system threat response.
Instead of
Client had a tantrum when redirected.
Write
Client experienced a dysregulation episode (meltdown) in response to a redirection. Presentation included (specific observable features). This is consistent with a fight-flight-freeze cascade, not a volitional outburst.
Instead of
Client refuses to attend school.
Write
Client is unable to initiate school attendance, with somatic and affective presentation consistent with nervous system threat response rather than motivational refusal. School environment currently carries high demand load for this client.
Instead of
Client is avoidant and does not engage in treatment.
Write
Client presents with a demand-sensitive nervous system pattern in which treatment tasks themselves can become demands that activate the avoidance response. Treatment approach has been modified to reduce demand character of session structure.
The pattern across all of these: name the observable, name the mechanism, avoid the words that imply the client is choosing to be difficult. You are still describing what happened. You are not editorializing.
Beyond the direct swaps, there are a few recurring scenarios in PDA documentation that deserve specific language.
Describing meltdowns. A meltdown in a PDA client is not a tantrum, and the distinction is clinically significant. A tantrum is goal-directed behavior intended to produce an outcome. A meltdown is a loss of voluntary regulation when the nervous system exceeds its capacity. In documentation, use "dysregulation episode" or "meltdown" and name the observable features (crying, shouting, motor activation, freeze, shutdown, withdrawal) without adding interpretive language about what the client "wanted." The client did not want anything. The client was past the point of wanting.
Describing task refusal. "Refused" is a loaded word that implies a choice. For PDA clients, what looks like refusal is usually a nervous system response that blocks access to voluntary action. Use "did not complete," "was unable to initiate," or "did not engage" instead. If you have observational data about the nervous system state, include it: "physical signs of activation preceded non-engagement," or "client described feeling unable to move toward the task despite stated intention to do so."
Describing accommodation requests. When a PDA client asks for a change to the session structure (a different chair, a shorter session, no eye contact, permission to draw while talking), the standard clinical framing is "client made unusual requests." A better framing is "client identified environmental modifications to support nervous system regulation." This matters because the first framing invites future clinicians to deny the accommodation. The second framing invites them to honor it.
Describing progress. Progress in PDA treatment does not look like compliance. It often looks like the client being able to name what their nervous system is doing, tolerate being in the room, ask for what they need, or disengage cleanly instead of melting down. Document those as progress. "Client was able to verbalize activation state and request session adjustment" is clinically meaningful progress and it deserves to be in the chart. Otherwise the next reader will see no progress markers and assume the treatment is failing.
Describing the treatment approach. If you are working from a PDA-informed framework, say so in your notes. A one-sentence treatment approach note ("Treatment informed by the RELATE framework for Pathological Demand Avoidance, which prioritizes nervous system safety and autonomy preservation over behavioral compliance targets") tells the next reader what you are doing and why. It also creates a paper trail that justifies your clinical choices if anyone questions why your approach differs from standard behavioral treatment.
If you are taking over a client whose previous records are full of "oppositional" and "manipulative" and "noncompliant," you cannot rewrite the history. But you can reframe it. Your first note with this client should include a paragraph that repositions the previous documentation in light of what you are now observing.
Something like: "Client's prior records describe a history of oppositional and avoidant behaviors. Current assessment suggests these behaviors are more accurately understood as manifestations of a demand-sensitive nervous system pattern (PDA profile). Treatment approach has been adjusted accordingly, and previous intervention strategies targeting compliance are not clinically indicated for this presentation."
That paragraph does three things. It does not attack the previous clinicians, which protects you professionally. It names the reframing so future readers encounter it. And it establishes a new clinical direction in the chart, so that your subsequent notes are consistent with a coherent approach rather than reading as a sudden departure from the established narrative.
PDA is not a standalone diagnosis in the DSM-5 or ICD-11. Current practice uses either an autism spectrum diagnosis with PDA as a descriptive profile, or a combination of codes that capture the presenting concerns (anxiety, OCD, ODD-rule-out, adjustment disorder, depression). This is an ongoing clinical debate, and we are not going to resolve it here. What matters for documentation is that your notes should be diagnostically honest and clinically useful, regardless of which codes end up on the claim.
One practical note: if you end up using an ODD code to get a claim paid, make sure your progress notes and assessment language clarify that the behavioral presentation is driven by nervous system mechanisms and not by the oppositional or conduct-disordered pattern that ODD implies. The code on the claim is not the same thing as the clinical formulation in the chart, and clinicians regularly use codes that are the best available approximation while documenting the actual mechanism in the progress notes.
The clients whose charts you are writing this year will be in treatment with someone else in five years, or ten. The person reading your note at that point will not know you. They will not know what framework you were working from. All they will have is the language. If the language says "oppositional," they will reach for behavior plans. If the language says "demand-sensitive nervous system pattern with protective withdrawal in response to session structure," they will reach for something else. The documentation is an intervention in its own right. It is the intervention you leave behind for the next clinician.
We cover PDA-informed documentation, assessment, and clinical formulation in depth in the RELATE Foundational Training Manual, including sample notes, progress indicators, and a full assessment framework. If you are working with PDA clients and you want a structured approach to all of this, the manual is where the clinical detail lives.