/ Single-Case Design Graphs

Overview › Visual analysis › Lesson 2

Lesson 2 of 7About 15 minutes

Experimental control

Seeing a change is not the same as showing that the intervention caused it. Experimental control, also called a functional relation, requires the effect to appear repeatedly, exactly when the conditions change.

You will be able to

  • Tell an effect from a functional relation, and say how many demonstrations a functional relation needs.
  • Explain how prediction, verification, and replication show control, and where each design gets its demonstrations.
  • Decide whether a graph from any design shows experimental control, reaching 8 of your last 10 in the practice.

An effect versus a functional relation

An effect is a change in behavior that lines up with a change in conditions. A functional relation is shown when that effect is demonstrated at least three times, at three different points in time (Horner et al., 2005). Three is a professional convention, and more demonstrations increase confidence (Kratochwill et al., 2010). Each demonstration reduces the chance that something other than the intervention is responsible.

Non-effects weaken the case. A non-effect is a phase change where behavior should have changed and didn't, such as a tier that doesn't respond or a reversal that doesn't reverse. The WWC pilot standards rate three demonstrations with no non-effects as strong evidence. Three demonstrations plus a non-effect, such as a fourth tier that doesn't respond, is moderate evidence. A non-effect that leaves fewer than three demonstrations, such as one of three tiers not responding, means no functional relation is shown (Kratochwill et al., 2010).

Baseline logic

Single-case designs rely on baseline logic, which has three elements (Cooper et al., 2020):

  1. Prediction. Stable baseline data predict what behavior would do without intervention.
  2. Verification. Evidence that the prediction was accurate, such as behavior returning toward baseline when the intervention is withdrawn in a reversal, or untreated tiers staying at their baseline level in a multiple baseline.
  3. Replication. The effect appears again when the conditions change again.

The step that links prediction to the intervention data is called affirmation of the consequent: if the intervention controls the behavior, behavior should change when the intervention starts, and it does. On its own this proves little, because something else could have changed at the same time. That is why verification and replication must follow. Some courses teach affirmation as a fourth step between prediction and verification. The logic is the same, and the figure below labels that step “Affirmation.”

Reversal graph of percentage of intervals on task. Baseline is near 30 percent; a dashed predicted line continues at 30 percent through the first intervention phase, where data rise to 60 to 85 percent. Data return to 30 to 45 percent in the second baseline and rise to 80 to 92 percent when the intervention is reintroduced. Labels mark prediction, affirmation, verification, and replication.
Baseline logic in a reversal design. The predicted level (dashed) didn't happen in the first intervention phase (affirmation). Behavior returned to the predicted level when the intervention was withdrawn (verification) and changed again when it was reintroduced (replication).

Questions to ask of any graph

Worked example: reading a reversal graph

This is the reversal graph from Excel Lessons 1 to 4, the one you build there with the graph type set to Reversal (ABAB): on-task behavior across baseline and a token economy. The model answer follows the order an assignment asks for: within phases, between phases, then a conclusion about control.

Experimental control Reversal graph of percentage of intervals on task across Baseline, Intervention, Baseline, and Intervention phases. Both baselines are low, near 25 to 45 percent; both intervention phases are high, 60 to 92 percent.
The tutorial reversal graph. Baseline sessions 1–5 and 11–15; token economy sessions 6–10 and 16–20.

Within phases. Baseline 1 (sessions 1–5) is stable with no trend: mean 30%, range 25–35%. Intervention 1 (sessions 6–10) is higher (mean 75%, range 60–85%). It rises over the first four sessions and then levels off. Baseline 2 (sessions 11–15) falls to a mean of 35% (range 30–45%), starting at 45% and settling near 30–33%. Intervention 2 (sessions 16–20) is high and stable (mean 87%, range 80–92%).

Between phases. Each change is immediate. The mean of the last three points of one phase and the first three of the next goes from 32% to 70%, then from 82% to 38%, then from 31% to 86%. No point falls within the range of the adjacent phase, so there is no overlap. Similar phases are consistent: both baselines are low (30% and 35%), and both intervention phases are high (75% and 87%).

Conclusion. The effect appears three times, at three different points in time, with no non-effects. The graph demonstrates experimental control: a functional relation between the token economy and on-task behavior. Every phase has five data points, so the design meets the WWC pilot standards' minimum of five points per phase without reservations.

Compare a graph that falls short:

No experimental control Reversal graph where on-task behavior rises from about 30 percent to 60 to 85 percent in the first intervention phase and stays at 80 to 88 percent in the second baseline and second intervention phases.
Model answer. On-task behavior rose from a mean of 30% to 75% when the intervention began, but stayed high (mean 84%) when it was withdrawn. Without a return toward baseline there is no verification, and the second intervention phase has nothing to replicate. With only one demonstration, history, maturation, or another variable could explain the change. The graph does not demonstrate experimental control.

How each design gets its three demonstrations

DesignDemonstrations come fromCommon reason control fails
ABOnly one comparisonOne demonstration at most, so never enough on its own
ReversalIntroduce, withdraw, reintroduceBehavior doesn't reverse; baseline trend
Multiple baselineStaggered starts across tiersUntreated tiers change too; a tier doesn't respond
Alternating treatmentsRepeated alternationPaths overlap; carryover between conditions
Multielement (functional analysis)Each test condition compared with Play in every cycleUndifferentiated: no test condition consistently above Play
Changing criterionEach criterion changeBehavior jumps or drifts instead of tracking steps

A functional analysis asks its own question. It is a multielement design: test conditions such as Attention, Demand, Tangible, and Alone alternate with Play, the control condition. The analysis is differentiated when responding is consistently higher in at least one test condition than in Play. A differentiated analysis points to a function, or to more than one: escape, attention, or tangibles when that test condition stays above Play, or automatic reinforcement when only Alone is elevated. An undifferentiated analysis doesn't identify a social function, whether responding is high in every condition (which can point toward automatic reinforcement) or near zero in every condition (examples of each).

Visual analysts don't always agree. Agreement between experienced raters is far from perfect, especially for graphs with variability or trend. That is why structured aids and explicit criteria help (Lesson 4), and why clear graphing matters.

Practice

Graphs come from every design in the table above. If a design is new to you, read its page first (linked in the table): each one shows what control looks like in that design and the common ways it fails. Decide whether each graph shows experimental control, or, for a functional analysis, whether it is differentiated. Most graphs then ask a second question. When a graph doesn't show control, or a functional analysis isn't differentiated, choose why. When an alternating treatments graph shows control, choose which treatment produced less responding. When a functional analysis is differentiated, choose which test conditions are consistently above Play. An item with two questions counts only when both answers are right.