Introduction
The Interview-Informed Synthesized Contingency Analysis (IISCA) represents a significant evolution in the field of Applied Behavior Analysis (ABA), offering a practical, efficient, and highly individualized approach to functional behavior assessment. Practically speaking, when practitioners ask what the IISCA conditions typically are run for, they are essentially inquiring about the specific experimental logic, duration parameters, and decision-making criteria that govern the implementation of the test and control sessions. Unlike traditional functional analyses that isolate single variables (e.g., attention, escape, tangible) across multiple distinct conditions, the IISCA synthesizes the unique contingencies identified during an open-ended interview into a single, personalized test condition. In real terms, this test condition is then compared against a matched control condition where all synthesized reinforcers are available non-contingently. Understanding exactly what these conditions are run for—how long they last, what data they yield, and when they terminate—is critical for behavior analysts seeking to maintain procedural fidelity while maximizing the safety and dignity of the client Simple, but easy to overlook..
Most guides skip this. Don't.
Detailed Explanation
To grasp what the IISCA conditions are run for, one must first understand the architectural difference between a standard Functional Analysis (FA) and the IISCA. On the flip side, in a traditional FA, conditions are "run for" the purpose of isolating a single maintaining variable—testing if attention maintains behavior, then testing if escape maintains behavior, and so on. This often requires numerous sessions across many days. Day to day, the IISCA, developed by Dr. Gregory Hanley and colleagues, flips this logic. The conditions are run for the purpose of validating a hypothesized synthesized contingency derived directly from caregiver or staff interviews.
The process begins with the Open-Ended Interview, where the analyst gathers rich, narrative data about the "when, where, who, and what" surrounding the problem behavior. From this interview, the analyst constructs a Test Condition that combines the specific establishing operations (EOs), discriminative stimuli (SDs), and reinforcers reported by the informants. So naturally, for example, if a parent reports that a child engages in aggression when told to stop playing an iPad (EO: removal of preferred item; SD: vocal demand to transition) and the result is getting the iPad back plus 5 minutes of negotiation (reinforcers: access to tangible + attention + escape), all of these elements are programmed into a single test condition. The conditions are run for the explicit purpose of demonstrating functional control by this specific, idiosyncratic package of variables Most people skip this — try not to..
The Control Condition is run for the purpose of providing a baseline comparison where the exact same reinforcers are delivered freely, on a dense schedule (e.Plus, the conditions are run for a comparison of rates: if the problem behavior occurs significantly more in the Test condition than in the Control condition, the synthesized contingency is validated. , non-contingent reinforcement every 30 seconds), and no demands or EOs are present. g.This comparison is the singular goal for which the sessions are executed Simple as that..
Step-by-Step or Concept Breakdown
The execution of IISCA conditions follows a rigorous, step-by-step protocol designed for efficiency. Understanding these steps clarifies exactly what the conditions are run for at each phase Not complicated — just consistent. That's the whole idea..
1. Designing the Synthesized Test Condition
The analyst does not guess at variables; they are "run for" the specific topography of the client's natural environment. The analyst programs the Establishing Operation (EO) (e.g., dividing attention, removing preferred items, presenting difficult tasks), the Antecedent/SD (e.g., a specific instruction, a look, a transition warning), and the Consequence/Reinforcer (e.g., 30 seconds of escape, high-magnitude attention, return of the item). This condition is run for the purpose of evoking the target behavior under the exact contextual variables reported to be relevant That's the part that actually makes a difference..
2. Designing the Matched Control Condition
This condition is run for experimental control. It mirrors the test condition physically (same room, same materials, same therapist) but removes the contingency. The EO is absent (attention is continuous, tasks are absent/preferred items available), and the reinforcers are delivered on a time-based schedule (NCR) regardless of behavior. This condition is run for the purpose of ruling out non-contingent reinforcement or sensory maintenance as the primary driver.
3. Session Duration and Number
A critical aspect of "what they are run for" involves the termination criteria. Unlike traditional FAs which often run for 10–15 minutes per session regardless of behavior rates, IISCA sessions are typically short (3 to 5 minutes). They are run for a minimum of 3 to 5 sessions per condition (alternating Test/Control). That said, they are also run for stability. The analyst continues running pairs of sessions until a clear differentiation in problem behavior rates is observed (visual analysis) or until a pre-determined maximum (usually 5 pairs/10 sessions total) is reached. They are run for efficiency—to get an answer in a single morning or afternoon rather than weeks The details matter here..
4. The "Shaping" or "Mini-Analysis" Phase
If the initial synthesized test condition does not evoke behavior, or if the control condition shows high rates (false positive), the conditions are run for troubleshooting. The analyst may systematically remove components (e.g., run a test condition with just escape + attention, removing the tangible) to isolate the active ingredient. In this phase, the conditions are run for component analysis within the synthesized framework.
Real Examples
Consider a 7-year-old client, "Leo," who engages in severe self-injury (head-banging). Mom packs a lunch (divided attention/EO). Tablet is freely available. * Control Condition Run For: Mom sits next to Leo, playing with him continuously (NCR attention). In practice, tablet is removed. Now, run for 3 minutes. If Leo engages in SIB, Mom rushes over, soothes him, and gives the tablet back for 30 seconds (Synthesized Reinforcer). That said, this condition is run for 3 minutes. Data shows 15 instances of SIB. Leo bangs his head; Mom rushes over, picks him up, soothes him (high-quality attention), and lets him keep the tablet for 5 more minutes (escape + tangible). Therapist says, "Leo, go play" (SD). Worth adding: if SIB occurs, nothing changes (reinforcers still available freely). Data shows 0 instances of SIB. And * Result: The conditions were run for a clear demonstration of functional control. The synthesized contingency (Divided Attention + Demand + Removal of Tangent -> Attention + Escape + Tangible) is validated. This leads to * Test Condition Run For: The analyst sets up the room. * Interview Data: Mom reports it happens in the morning when she is packing lunches (divided attention), she tells Leo to "go play" (demand/transition), and he loses access to his tablet. No demands placed. Treatment (Skill-Based Treatment / SBT) can now be designed specifically for this contingency.
In a second example, a residential facility uses IISCA for an adult, "Maria," with aggression.
- Run For: Differentiation. If aggression is high in Test and zero in Control, the facility knows exactly which context variables to modify in the treatment plan (e.In real terms, * Control Condition: Peer is quiet, no instructions, staff chats with Maria continuously, free access to preferred snacks. * Test Condition: Peer is loud (EO), Staff gives hygiene instruction (SD), Aggression results in termination of instruction + removal from room + staff conversation (Escape + Attention).
- Interview: Staff report aggression occurs when Maria is asked to do hygiene tasks (showering) while a specific peer is loud nearby. g.
headphones during hygiene routines, scheduling showers during quieter hours) and which reinforcers to deliver for appropriate alternative behaviors (e.Also, g. , escape from the task via a break card, staff attention for compliance) No workaround needed..
Troubleshooting and Component Analysis in Practice
Returning to the logic of the decision model, imagine Leo’s initial test condition produced high rates of SIB, but the control condition also showed moderate levels (e.Now, g. , 5 instances). This false positive in the control signals that the "free access" environment still contained an evocative variable—perhaps the presence of the tablet itself was an EO for SIB, or the therapist’s proximity was insufficiently engaging. The analyst would then run conditions for troubleshooting: perhaps a control condition with the tablet removed but attention continuous, or a test condition removing the "escape" component (allowing Leo to keep the tablet but still delivering attention) to isolate the tangible variable.
Conversely, if Maria’s test condition showed zero aggression, the analyst runs conditions for sensitivity. They might intensify the EO (longer duration of peer noise), increase the demand difficulty, or thin the reinforcement schedule in the control to ensure the test contingency is sufficiently distinct. This iterative process—running conditions not just for a binary "yes/no" but for precision—is the hallmark of a rigorous IISCA.
The "Why" Dictates the "How Long"
A common practical question arises: "How many sessions do I run?" The answer is dictated entirely by the purpose.
- For Demonstration of Functional Control: You run until visual analysis confirms differentiation (non-overlapping data paths between test and control) and replication (typically a minimum of 3–5 sessions per condition showing a consistent pattern). You stop when the functional relation is undeniable.
- For Troubleshooting/Sensitivity: You run until the confound is resolved or the evocative variable is identified. This might take one session or ten; the criterion is diagnostic clarity, not a pre-set session count.
- For Component Analysis: You run systematic permutations (e.g., Test A: Attention+Escape; Test B: Attention+Tangible; Test C: Escape+Tangible) until the minimal effective synthesis is identified. Each permutation is run for differentiation.
Conclusion
The IISCA is not a rigid protocol with a fixed dosage of sessions; it is a dynamic, hypothesis-driven investigative framework. The decision to run a test condition, a control condition, or a component analysis probe is never arbitrary—it is a direct response to the data generated in the prior session and the specific question the analyst is asking at that moment: *Is this the function? Because of that, is the control clean? Which part of the synthesis is doing the work?
By anchoring the decision to run conditions in these distinct purposes—demonstration, troubleshooting, sensitivity, and component analysis—analysts move beyond mechanical implementation. In real terms, they check that every minute of assessment time is spent refining the precision of the functional hypothesis. g.On top of that, , "maintained by attention"), but a nuanced, contextually rich understanding of the contingency maintaining it. In practice, this precision is the prerequisite for compassionate, efficient, and durable Skill-Based Treatment. The result is not merely a label for the behavior (e.When we know exactly why we are running a condition, we know exactly when to stop—and exactly where to start treatment.
