To define a response-consequence contingency assessment question, connect Uzo's chosen decision to one response class, one consequence class, and a credible response-versus-nonresponse comparison. Specify the time window, learning history, consequence availability and value, effort, prompts, access, health, and result that could change action. Close timing can generate a hypothesis, while a functional contingency claim needs comparative evidence and later behavior change.

Begin with Uzo's decision

Ask which garden activity, communication opportunity, or support decision matters to Uzo. Describe current access, safety, natural consequences, and why a response-consequence relation could change the plan.

Define the response class

List accessible forms with the same intended relation, including speech, AAC, gesture, movement, writing, or tool use. Specify onset, offset, opportunity, prompt, effort, omission, and invalidity.

Define the consequence class

Describe the actual environmental change, source, quality, amount, delay, duration, and accessibility. Staff attention, help, break, or access labels require observable boundaries.

Build response and nonresponse states

Create mutually exclusive, comparable opportunities. The nonresponse state needs its own start, window, eligibility, and consequence measure rather than leftover time.

Name the inference

Decide whether the assessment asks about delivery dependency, conditional probability, later response change, or a treatment effect. These questions require different designs and evidence.

Use this sequence to define a response consequence contingency assessment question

Start with Uzo's priority, define the response and consequence, build comparable states and windows, verify access and authority, state alternative explanations, and collect only decision-changing evidence.

Build Uzo's response-consequence question brief

Create one versioned response-consequence question brief for the community-garden participation review. Include Uzo'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 Uzo's contingency evidence

A second reviewer should identify Uzo's response class, consequence class, response state, nonresponse state, window, history, availability, value, and decision from the brief alone. Trace each element to direct report, record, observation, or labeled hypothesis. Predeclare stronger, weaker, mixed, invalid, and withdrawn result paths. Confirm that the question can be answered without removing ordinary help or manufacturing failure before any structured comparison is released.

Keep Uzo'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 Uzo 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 Uzo's example

Uzo's brief contains 17 required fields. Fourteen are ready. The nonresponse comparison is undefined, watering help sometimes occurs before any response, and the consequence window has no end point. Report 14/17 readiness and hold quantitative contingency analysis until those fields close. Existing observations can still guide a clearer question without being recoded as proof. 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 Uzo's main assessment risk

A question such as what reinforces Uzo can pool requests, gestures, task steps, staff praise, help, and garden access into one vague relation. Broad labels make a positive result almost impossible to interpret. 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 Uzo

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 Uzo.

Treat contingency as more than close timing for Uzo

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 Uzo, 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 Uzo

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 Uzo's sampled events while leaving reinforcement, behavioral function, and causality unresolved.

Preserve rules, alternatives, and mixed control for Uzo

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 Uzo.

Preserve treatment scope, AAC, assent, and access for Uzo

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 Uzo.

Choose Uzo's next bounded action

Uzo chooses whether an accessible request reliably changes the timing of tool assistance as the first practical question. 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 Uzo's earlier performance.

Close Uzo's contingency review

Review the response-consequence question brief with Uzo, 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

Sources