To assess direct contingencies alongside rules and prompts, record Zain's direct consequences, instructions, rules, models, prompts, feedback, and relevant histories in separate fields. Compare stable and changed arrangements only when safe and useful, and ask Zain what guided each choice. Contingency-shaped, rule-governed, imitative, prompted, and mixed control are functional hypotheses rather than permanent traits or mutually exclusive identities.
Inventory verbal and modeled supports
Record written, spoken, pictorial, modeled, gestural, and device-delivered rules or prompts, including who provided them, when, and whether they accurately described the current consequence relation.
Record direct consequences
Document screen changes, successful task completion, errors, corrections, social feedback, delays, and other outcomes that Zain contacts after each response.
Separate prompt from rule
A prompt increases the likelihood of a response in the current situation. A rule describes part of a contingency. One support can participate in both functions, so record its content and delivery.
Use change carefully
Natural software or policy changes can reveal sensitivity to direct outcomes and rule accuracy. Avoid creating errors, risk, or inaccessible conditions solely to classify control.
Invite Zain's account
Ask which cues, instructions, feedback, and prior experiences influenced the choice. Self-report adds evidence while remaining distinct from a functional demonstration.
Use this sequence to assess direct contingencies alongside rules and prompts
Inventory Zain's rules, models, prompts, and outcomes; version the environment; compare safe arrangements; preserve access and client report; and conclude mixed or unresolved control whenever the evidence demands it.
Build Zain's mixed-control assessment matrix
Create one versioned mixed-control assessment matrix for the ticket-kiosk navigation review. Include Zain's priority, response class, consequence class, learning history, response and nonresponse states, time windows, value, availability, effort, delay, magnitude, quality, duration, rules, prompts, access, health, integrity, agreement, raw cells, invalidity, missingness, withdrawal, direct experience, result, uncertainty, decision, owner, correction, and review trigger. Store only decision-relevant information with role-limited access.
Validate Zain's contingency evidence
Review each of Zain's four 12-opportunity blocks for rule version, prompt level, layout, feedback, consequence, familiarity, order, and access. Reproduce 10/12, 7/12, 4/12, and 9/12. Ask Zain what he used and where the guide conflicted with the screen. Any changed-arrangement probe must remain safe and reversible. Report mixed influence and version mismatch before proposing a source-of-control label.
Keep Zain's dependency, function, and experience separate
Measure response-consequence dependency within eligible response and nonresponse states. Evaluate later functional effects with evidence suited to that question. Ask Zain separately about clarity, effort, comfort, usefulness, burden, and whether assessment should continue. A strong conditional difference can coexist with an unwanted or inaccessible arrangement. Positive experience can also improve while the measured dependency stays unchanged.
Work through Zain's example
Zain completes 12 kiosk opportunities with an accurate visual rule and immediate screen feedback, scoring 10/12. With feedback and no visual rule, he scores 7/12. After the kiosk layout changes while the old rule remains, he scores 4/12. With an updated rule on the changed layout, he scores 9/12. The sequence describes four bundled arrangements and cannot isolate rule or feedback effects. Preserve every planned and valid unit, raw count, denominator, response state, nonresponse state, consequence delivery, contact, value, prompt, rule, access condition, integrity result, withdrawal, direct report, system failure, correction, and unresolved item. This fictional example demonstrates one assessment control. It offers no universal contingency, behavioral function, diagnosis, trait, treatment effect, legal conclusion, coverage decision, payment promise, or outcome guarantee.
Address Zain's main assessment risk
Calling Zain rule dependent can blame him for an outdated support. Calling the first block contingency shaped ignores the accurate visual rule and his prior kiosk history. Review response and consequence definitions, comparison states, timing, base rates, learning history, value, availability, effort, rules, prompts, access, health, context, client experience, authority, and causal scope separately. A large conditional difference cannot repair an inaccessible or ethically unsound arrangement.
Keep contingency concepts and authority clear for Zain
The ABAI Basic Principles page lists behavioral contingencies in higher-education content. The BACB Test Content Outline covers contingencies, reinforcement, schedules, rule-governed behavior, measurement, assessment, and intervention as examination content. The current BACB Ethics Code addresses competence, involvement, consent and assent when applicable, assessment, risk, data, documentation, and evaluation for covered people. These sources do not create licensure, payer approval, or an individualized plan for Zain.
Treat contingency as more than close timing for Zain
Lattal's conceptual review presents contingency as a functional relation with empirical, theoretical, and practical dimensions. Poling and Li critique vague technical use of the word. For Zain, define the response, consequence, dependency, time window, history, and claimed functional effect instead of letting the label carry missing evidence.
Use sequential measures cautiously for Zain
McComas and colleagues discuss challenges in calculating contingencies from natural-environment sequential data. Valid response and nonresponse states, comparable windows, base rates, temporal precision, and raw cells matter. A conditional difference can describe Zain's sampled events while leaving reinforcement, behavioral function, and causality unresolved.
Preserve rules, alternatives, and mixed control for Zain
Tarbox and colleagues discuss rule following and report a small teaching study. Reed and Kaplan explain relative response allocation and obtained reinforcement in matching analyses. These sources help frame rules, prompts, direct outcomes, concurrent alternatives, bias, and effort. They provide no universal protocol or source-of-control conclusion for Zain.
Preserve treatment scope, AAC, assent, and access for Zain
The CASP public summary supplies high-level ABA behavioral-health-treatment scope for autistic people, with licensed detail outside this page. ASHA's AAC portal says AAC users should always have access to their communication tools or devices. Breaux and Smith provide assent-focused guidance in an evolving evidence base. Follow governing sources and keep health care, food, water, bathroom access, communication, mobility, rest, relationships, safety, and emergency help available to Zain.
Choose Zain's next bounded action
Zain chooses a versioned visual guide with a clear correction path and asks the team to keep immediate screen feedback available. Record the qualified owner, supporting evidence, effective date, current supports, health and access state, implementation check, accessible explanation, disagreement route, and reassessment trigger. Preserve the original assessment when people, systems, responses, consequences, or preferences change. A new arrangement creates a dated version rather than an error in Zain's earlier performance.
Close Zain's contingency review
Review the mixed-control assessment matrix with Zain, the qualified behavior analyst, relevant partners, access owners, and specialists named in the manifest. Confirm that close timing stays separate from response dependency and later functional effect, raw cells and denominators are reproducible, AAC and basic access remain protected, health questions stay with qualified professionals, and conclusions remain bounded to the sampled response, consequence, time, and context. Keep this page draft and noindex until every required review is complete.
Related resources
- How to Audit Delay, Magnitude, Quality, and Effort in a Contingency
- How to Calculate a Response Versus Nonresponse Contingency Difference
- How to Assess Concurrent Response-Consequence Alternatives
- How to Define and Verify a Consequence Class
Sources
- Association for Behavior Analysis International, Basic Principles in Behavior Analysis
- Behavior Analyst Certification Board, BCBA Test Content Outline, 6th edition
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts
- Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary
- Lattal, Contingency and Behavior Analysis
- McComas and colleagues, Calculating Contingencies in Natural Environments
- Poling and Li, Commit Heresy: Stop Using Contingency
- Tarbox and colleagues, Rule-Governed Behavior
- Reed and Kaplan, The Matching Law: A Tutorial for Practitioners
- Breaux and Smith, Assent in Applied Behaviour Analysis and Positive Behaviour Support
- American Speech-Language-Hearing Association, Augmentative and Alternative Communication