To audit delay, magnitude, quality, and effort in a contingency, measure Amara's response effort and the consequence delay, magnitude, quality, duration, probability, and accessibility for each relevant alternative. Verify actual delivery and contact, then ask Amara about the experience. A nominally contingent outcome can have little practical effect when it arrives late, is inaccessible, has low quality, or requires far more effort than another option.
Measure response effort
Record time, steps, force, movement, language, device access, waiting, and support required from Amara's perspective. Avoid equating task duration with effort without supporting evidence.
Measure consequence delay
Start the clock at the declared response boundary and end it when the consequence becomes available and accessible. Report distributions when delays vary.
Describe magnitude and duration
Specify amount, intensity, duration, access scope, and any cap or interruption. More is not automatically better, and client preference can change the practical meaning.
Audit quality and accessibility
Record whether the consequence matches the promised form, comes from the expected person, is understandable, works with AAC or assistive technology, and can actually be used.
Compare complete alternatives
List every parameter for each option before attributing allocation to one difference. Preserve client choice, task meaning, history, and naturally occurring consequences.
Use this sequence to audit delay magnitude quality and effort in a contingency
Define Amara's alternatives, measure effort and every consequence parameter, verify delivery and contact, collect client report, compare complete arrangements, repair practical mismatches, and reserve causal claims.
Build Amara's contingency-parameter audit
Create one versioned contingency-parameter audit for the community-volunteer task review. Include Amara'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 Amara's contingency evidence
Confirm Amara's effort definition, feedback content, delay clock, delivery probability, task choice, and access in every cell. Reproduce 8/10, 5/10, 4/10, and 1/10. Review order, carryover, task familiarity, partner, prompts, magnitude, duration, and competing outcomes. Because cells vary on more than one parameter, use the audit to find mismatches and plan a smaller comparison rather than assign a single cause.
Keep Amara'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 Amara 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 Amara's example
Amara has 40 volunteer-task choices across four 10-opportunity cells. A low-effort response followed by high-quality feedback within 10 seconds is selected in 8/10. Low effort with feedback after 5 minutes is 5/10. Higher effort with fast feedback is 4/10. Higher effort with delayed feedback is 1/10. Several parameters change together, so the matrix guides redesign without estimating an isolated delay or effort effect. 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 Amara's main assessment risk
Describing all four cells as response earns feedback hides the experienced contingency. The result could be driven by effort, delay, feedback quality, task preference, order, history, or combinations. 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 Amara
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 Amara.
Treat contingency as more than close timing for Amara
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 Amara, 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 Amara
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 Amara's sampled events while leaving reinforcement, behavioral function, and causality unresolved.
Preserve rules, alternatives, and mixed control for Amara
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 Amara.
Preserve treatment scope, AAC, assent, and access for Amara
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 Amara.
Choose Amara's next bounded action
Amara chooses the lower-effort task setup and immediate specific feedback while the team checks whether the change improves participation in ordinary volunteering. 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 Amara's earlier performance.
Close Amara's contingency review
Review the contingency-parameter audit with Amara, 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 Assess Concurrent Response-Consequence Alternatives
- How to Assess Direct Contingencies Alongside Rules and Prompts
- How to Reassess a Contingency After the Environment Changes
- How to Calculate a Response Versus Nonresponse Contingency Difference
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