3.4 Functional Assessment Support: Descriptive and Functional Analysis

Functional assessment is about variables, not blame

Functional assessment procedures are used to identify environmental events that may be related to behavior. The focus is not on blaming the client, caregiver, teacher, or RBT. The focus is on observable relations: what happens before behavior, what the behavior looks like, what happens after, when it is more or less likely, and what setting events may influence it. RBTs may participate by collecting data and implementing assigned components, but they do not independently conclude the function.

Common functions discussed in behavior analysis include access to attention, access to tangibles or activities, escape or avoidance of demands or situations, and automatic reinforcement. Those are concepts the RBT should recognize, especially because they appear in behavior reduction content as well. However, recognition is not the same as confirmation. If a client screams after a math worksheet is presented and the worksheet is removed, escape may be a hypothesis for the supervisor to evaluate. The RBT should record the sequence, not announce that escape is proven.

Descriptive assessment support

A descriptive assessment observes behavior in natural or typical contexts without systematically manipulating antecedents and consequences the way a functional analysis does. The RBT may record ABC data during classroom work, meals, transitions, play, bedtime routines, or community outings. The value comes from repeated, accurate observation. One ABC note rarely establishes a reliable pattern. Many well-collected observations can help the supervisor decide what additional assessment or intervention is appropriate.

Good descriptive data include enough context to be useful. Antecedent does not mean only the last adult instruction. It may include transition warnings, task difficulty, noise, denied access, waiting, peer interaction, change in staff, or absence of a usual item. Consequence does not mean only formal reinforcement. It includes what others did after the behavior: attention, reprimands, comfort, removal of demands, access to items, blocking, redirection, planned ignoring, or no obvious change.

Setting events such as poor sleep, illness, medication change reported by caregiver, substitute teacher, or schedule disruption should be documented and reported according to workplace rules.

Descriptive observation workflow:

1. Review the target behavior definition and data sheet before the observation.
2. Position yourself to observe without disrupting the routine more than necessary.
3. Record the exact behavior when it occurs, including count, duration, intensity code, or other assigned measure.
4. Record what happened before and after using neutral language.
5. Include relevant context such as activity, people nearby, materials, and time.
6. Mark uncertainty instead of filling gaps with guesses.
7. Notify the supervisor about safety events, repeated data gaps, or patterns requested by the plan.

Functional analysis support

A functional analysis, often shortened to FA, is different because conditions are arranged to test relations between behavior and consequences. For example, the supervisor may design attention, demand, tangible, alone or ignore, and play or control conditions. The conditions are not casual role play. They involve planned antecedents, planned consequences, measurement, safety protections, and decision rules. An RBT should participate only after training and only within the assigned procedure.

Functional analysis can involve evoking problem behavior. That raises the importance of safety and dignity. The RBT must know the target behavior definition, precursor behavior if included, protective procedures, reinforcement delivery rules, session length, termination criteria, and who is supervising. If the client engages in behavior that meets stop criteria, the RBT should follow the stop procedure and contact the supervisor, not push through to finish a data sheet. If the RBT does not understand a condition, the RBT should ask before starting.

Scenario: In a demand condition, the written procedure says to present work tasks and remove the task for 30 seconds contingent on the target behavior. During the session, the client begins crying softly but does not meet the target behavior definition. The RBT should follow the written condition and any distress or precursor instructions. The RBT should not change the consequence based on personal theory. The RBT records crying if the data sheet includes it or notes it as context if directed, then reports concerns to the supervisor.

Scenario: During descriptive ABC observation in a home session, a caregiver says the client always hits for attention. The RBT should not write attention function confirmed. A better note is that the caregiver reported the statement, then the RBT records direct observations separately. Stakeholder reports can be useful, but they are different from direct observation and must be handled objectively.

The exam logic is boundary logic. Functional assessment is important, but the RBT role is controlled by training, written procedures, supervision, and objective documentation. When a scenario asks what the RBT should do, choose the action that preserves data integrity, follows safety criteria, and routes interpretation to the supervisor.