Reassess a Contingency After the Environment Changes

To reassess a contingency after the environment changes, begin with Cyra's report and a defined trigger. Review people, setting, schedule, policy, technology, response effort, consequence availability, delay, magnitude, quality, access, health, prompts, and preference. Version the old, changed, and repaired arrangements, restore essential supports, and collect only the new evidence needed for the current decision.

Set practical change triggers

Open review when a person, setting, policy, schedule, technology, response step, consequence, delay, access feature, health condition, or preference changes enough to affect the decision.

Ask Cyra what changed

Use Cyra's preferred communication to identify missing, confusing, effortful, helpful, or unwanted features. Maintain a way to pause or decline assessment.

Version the complete arrangement

Record response steps, prompts, people, screens, effort, consequence delivery, delay, quality, access, dates, and locations for old, changed, and repaired versions.

Restore access first

Repair AAC, screen-reader, language, vision, hearing, motor, mobility, connectivity, or partner-access failures before interpreting performance. Keep failures visible in coverage.

Use minimal new evidence

Choose a short natural comparison or targeted probe that resolves the decision. Preserve ordinary support and stop once the change is adequately understood.

Use this sequence to reassess a contingency after the environment changes

Start with Cyra's report, verify the trigger, version the arrangement, restore access, compare only decision-relevant features, report each version separately, and update the hypothesis without assigning blame.

Build Cyra's contingency change review

Create one versioned contingency change review for the updated workplace-check-in review. Include Cyra'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 Cyra's contingency evidence

Confirm that Cyra's response, opportunity, and consequence definitions remain comparable across all three versions. Reproduce 12/15 in the old system, 5/15 across all planned changed-system opportunities, 5/12 among access-ready changed-system opportunities, 10/15 after repair, and the three access failures. Keep the all-planned and access-ready denominators side by side so the record shows both system coverage and Cyra's performance when the response was accessible. Document screens, effort, delay, confirmation quality, device, labels, prompts, partner, schedule, and workload. Ask Cyra which changes mattered. Preserve the old evidence and attach each conclusion to its dated environment version. Repeat the repaired version only when Cyra agrees and the decision still needs evidence.

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

Cyra completes the check-in response in 12/15 old-system opportunities. After a software change adds two screens and delays confirmation, completion is 5/15 across all planned opportunities. Three of those 15 opportunities lack screen-reader labels, leaving 12 access-ready opportunities and an access-ready completion result of 5/12. After accessibility repair and a shorter confirmation path, completion is 10/15. Report the all-planned measure, the access-ready measure, all three environment versions, and the access failures separately. The uncontrolled sequence identifies a practical change without proving one cause. 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 Cyra's main assessment risk

Calling the drop noncompliance places a system and access change inside Cyra. Calling the later increase proof of the repair also exceeds a sequence where practice, familiarity, workload, and partner support changed. 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 Cyra

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

Treat contingency as more than close timing for Cyra

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

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

Preserve rules, alternatives, and mixed control for Cyra

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

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

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

Choose Cyra's next bounded action

Cyra approves the accessible shorter path and asks the employer to keep a human check-in route during future software releases. 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 Cyra's earlier performance.

Close Cyra's contingency review

Review the contingency change review with Cyra, 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.

How to Reassess a Contingency After the Environment Changes