Documenting Behavior Reduction Programs

When implementing a Behavior Intervention Plan (BIP), the RBT's documentation has higher stakes than typical skill-acquisition data. Behavior reduction documentation drives clinical decisions about plan continuation, modification, or fading — and supports the agency's defense if a family questions the methods used.

What to Record for Each Targeted Behavior

  • Operational definition: The exact, observable definition as written in the BIP (the RBT records using this definition, not their own)
  • Each instance: Time of onset, duration if relevant, intensity if defined
  • Antecedent: What was happening immediately before
  • Function in evidence: Does this instance suggest the hypothesized function (sensory, escape, attention, tangible)?
  • Intervention used: Which procedure from the BIP was implemented (e.g., extinction, redirection, DRA prompt)
  • Client response to intervention: Did the behavior decrease, escalate, stay the same?
  • Recovery time: How long until client returned to baseline functioning

The Difference Between Following the Plan and Deviating

Follow the BIP exactly as written. If you deviate — even with good reason (an unusual antecedent, safety concern, missing materials) — document the deviation clearly: what you did instead, why, and that you'll relay it to the BCBA. Deviations aren't violations IF they're documented and reported. Deviations without documentation are.

Documenting Antecedent Modifications

BIPs often include antecedent strategies (NCR, visual schedules, environmental modifications) designed to prevent behavior. Note whether these were available and used. If the visual schedule wasn't set up at the start of session, the data tells the BCBA why a behavior count is higher than expected.

Documenting Replacement Behavior

Most BIPs target the reduction of an unwanted behavior AND the increase of a replacement (DRA target). Document both: count of the target behavior AND opportunities/instances of the replacement. The ratio matters more than either count alone.

Sessions Where Crisis Occurred

If the behavior reached crisis level during the session, link the session note to the separately-filed crisis incident report by reference number. Do not duplicate the crisis details in both documents — but ensure both can be cross-referenced.

What NOT to Write

  • Diagnostic language: "client was being manipulative" — interpretive, not observable
  • Pejorative descriptions: "client had a meltdown" — use behavior topography instead
  • Reasons that go beyond observed antecedents: "client did this because she's tired of the program"
  • Personal opinions about the plan: "this intervention isn't working" — raise concerns with the BCBA in supervision, don't document them in session notes