12.1 Using Individual & Group Data to Increase Positive Behavior

12.1 Using Individual & Group Data to Increase Positive Behavior

Quick Answer: Increasing positive behavior starts with collecting the right kind of data for the behavior in question. Discrete behaviors get counted (frequency/event recording), behaviors that vary in length get timed (duration recording), response-time concerns get measured from cue to onset (latency recording), and high-rate or continuous behaviors get sampled across intervals. Layered on top of these individual measures, ABC anecdotal data captures context, and schoolwide/group data (like office discipline referrals) shows whether systems — not just individual students — are working. The FTCE ESE exam expects you to match a measurement method to a behavior's dimension and to read a simple data pattern to decide whether an intervention should continue, change, or fade.

Why Data Comes Before Intervention Decisions

Teachers and behavior specialists cannot reliably judge whether a behavior is improving from memory or impression alone — perception is biased by the most recent incident, by how tired the adult is, or by how disruptive a single episode felt. Systematic data collection replaces impression with evidence: it establishes a baseline (how often, how long, or how quickly the behavior occurs before any intervention), documents change once a support is introduced, and creates a paper trail that satisfies IDEA's requirement for data-based decision-making in intervention and IEP planning.

Matching Measurement to the Dimension of Behavior

Not every behavior should be measured the same way. Choosing a measurement system starts with asking what dimension of the behavior actually matters for the intervention goal.

Event/frequency recording works only when a behavior has a clear beginning and end and does not vary much in length — counting "number of times out of seat" is meaningless if some episodes last three seconds and others last ten minutes, which is exactly when duration recording becomes the better tool. Latency recording is especially useful for compliance concerns, where the question is not whether a student eventually follows a direction but how quickly. Interval recording trades some precision for feasibility: instead of counting every instance of a very frequent behavior, an observer marks whether the behavior occurred during short, consistent intervals (e.g., every 30 seconds), producing an estimate of occurrence that is far easier to collect reliably in a busy classroom.

ABC Anecdotal Recording

ABC recording is a narrative, real-time log of three columns: the Antecedent (what happened immediately before the behavior), the Behavior (an objective, observable description of what the student did), and the Consequence (what happened immediately after, including how adults and peers responded). Unlike frequency or duration data, ABC records do not just quantify a behavior — they begin to reveal patterns: does the behavior reliably follow a transition, a difficult academic demand, or a peer's comment? Does it reliably produce adult attention, escape from work, access to a preferred item, or simply feel good to the student regardless of anyone's reaction? ABC data collected across several occurrences is the raw material a team later uses to build a hypothesized function during a Functional Behavior Assessment (covered in the next section).

Individual-Student Data vs. Group/Schoolwide Data

Data serves two different questions depending on its scope, and ESE professionals need to read both.

A school team might notice from schoolwide ODR data that referrals spike in the cafeteria between 12:00 and 12:30 — a systems-level pattern suggesting more staff supervision or a revised transition routine, not an individual behavior plan. At the same time, a case manager tracking individual frequency data for one student's out-of-seat behavior needs a completely different lens: is this particular student's rate trending down since the intervention started three weeks ago? Both data streams matter, and confusing them leads to mismatched solutions — treating a systems problem with an individual plan, or treating an individual student's need as if reteaching schoolwide expectations alone will resolve it.

Turning Data Into a Decision: Visual Analysis

Once data is collected, teams typically graph it and look for three features before making a decision:

1. Level — Is the overall amount of behavior high or low compared to baseline?
2. Trend — Is the line moving up, down, or staying flat across sessions?
3. Variability — Is the data bouncing around unpredictably, or is it stable enough to interpret?

A single bad day should never trigger a plan change; a consistent trend across three to five consecutive data points in the undesired direction is the generally accepted threshold for concluding an intervention needs adjustment. Just as important, teams should confirm the intervention was actually implemented as designed (treatment fidelity) before assuming the plan itself failed — a good plan delivered inconsistently will produce disappointing data that has nothing to do with the plan's underlying logic. Establishing a stable baseline phase (data collected before any change) is what makes this comparison possible at all; without it, a team has no way to know whether behavior change followed the intervention or would have happened anyway.