Report Stimulus-Control Assessment Results and Limits

To report stimulus control assessment results and limits, document Jiro's priority, response, antecedent features, comparison, consequence history, design, access, prompts, trial order, exposure, integrity, observer agreement, raw condition data, invalidity, missingness, client experience, and context. State whether evidence supports differential responding, a candidate feature, a compound, transfer, or uncertainty. Avoid trait, diagnosis, comprehension, function, and universal-control claims the design never tested.

Open with Jiro's question and scope

State Jiro's priority, decision, qualified lead, contributors, dates, settings, consent route, assent when applicable, and method rationale. Explain what stimulus-control evidence can and cannot answer.

Describe the tested relation

Define response forms, opportunities, antecedent features, comparison, relevant consequence history, effort, access, prompts, feedback, and ordinary supports. List material differences among conditions.

Show design and coverage

Report planned, completed, valid, invalid, declined, stopped, and missing trials or sessions. Describe order, exposure, balancing, probes, replication, deviations, and context. Present raw counts before percentages.

Report integrity and agreement

Show whether stimuli, opportunities, prompts, and consequences followed the protocol and how observer agreement was sampled. Keep integrity, agreement, and Jiro's performance as separate measures.

State a bounded conclusion

Identify differential responding and the feature, compound, context, or uncertainty supported by the comparison. Preserve alternative features and untested settings. Avoid converting performance into a diagnosis or fixed ability.

Use this sequence to report stimulus control assessment results and limits

Lead with Jiro's decision, document the tested relation and design, show raw coverage and condition data, report access and integrity, state scope, record client experience and next action, and preserve a reassessment trigger.

Build Jiro's scope-bounded stimulus-control report

Create one versioned scope-bounded stimulus-control report for the post-assessment clinical review. Include Jiro's priority, response, opportunity, antecedent feature, compound, comparison, consequence history, setting, partner, effort, prompts, feedback, order, exposure, access, health, motivation, integrity, agreement, raw data, invalidity, missingness, withdrawal, direct experience, result, uncertainty, decision, owner, correction, and review trigger. Store only decision-relevant information with role-limited access.

Validate Jiro's stimulus-control evidence

Before release, a second reviewer should trace every summary statement to raw trials, reproduce both condition denominators, and verify prompts, order, exposure, integrity, agreement, invalidity, and withdrawal. The qualified clinical reviewer checks the functional and causal scope. Jiro reviews the plain-language version and correction route. Version control preserves the original assessment when later cues, supports, contexts, or preferences change. Recommendations name owners and review triggers without predicting universal performance.

Keep Jiro's response and experience separate

Measure the defined response under eligible target and comparison opportunities, and ask Jiro separately about clarity, effort, comfort, usefulness, burden, and whether the assessment should continue. Differential responding can coexist with inaccessible materials or an unwanted goal. Enjoyment or confidence can also change without evidence of the tested stimulus relation. Report both evidence streams with their own units, timing, and decision role.

Work through Jiro's example

Jiro's report covers 48 planned opportunities. Forty-four are valid, with 22 in the target condition and 22 in comparison. The response occurs in 18/22 target and 6/22 comparison opportunities. Four invalid trials involve two display failures, one prompt error, and one withdrawn opportunity. Report 44/48 valid coverage, both 22-opportunity condition results, and every invalid reason. The conclusion stays attached to the tested materials and setting. Preserve every planned and valid unit, raw count, denominator, feature state, comparison, prompt, access condition, integrity result, withdrawal, direct report, system failure, correction, and unresolved item. This fictional example demonstrates one assessment control. It offers no universal stimulus function, diagnosis, ability, treatment effect, legal conclusion, coverage decision, payment promise, or outcome guarantee.

Address Jiro's main assessment risk

A conclusion such as Jiro understands the cue can hide the response, consequence, comparison, access, and setting that produced the evidence. A scope-bounded report prevents later readers from inheriting a broader claim. Review response definition, feature access, comparison, consequence history, motivation, prompts, position, order, effort, health, setting, partner, exposure, integrity, client experience, authority, and causal scope separately. High accuracy never repairs a confounded or inaccessible assessment.

Keep stimulus-control concepts and authority clear for Jiro

The ABAI Basic Principles page lists stimulus control in higher-education content. The BACB Test Content Outline covers stimulus control, simple and conditional discrimination, prompting and fading, generalization, and related concepts 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. For Jiro, these sources do not create licensure, payer approval, or an individualized protocol.

Anchor Jiro's interpretation in comparison and history

Lattal's contingency review supports careful analysis of response-consequence relations beyond close timing. Saini and colleagues reviewed 31 applied multiple-schedule studies and described uses of correlated signals across applications. These sources illustrate history and differential responding. They do not establish that one color, card, display, schedule, or procedure will control Jiro's response or improve a clinical outcome.

Plan generalization explicitly for Jiro

Stokes and Baer organized nine historically influential generalization tactics. Osnes and Lieblein analyze generalization through stimulus control and relevant environmental features. For Jiro, define the intended performance universe, trained set, reserved probes, common stimuli, natural supports, and context-specific results. Historical frameworks guide questions rather than supply a universal modern protocol.

Read gradient evidence narrowly for Jiro

Lalli and colleagues systematically varied therapist distance in one applied assessment and observed different response levels. The study illustrates an ordered stimulus dimension and a case-specific gradient. It does not prescribe exposing Jiro to distress, identify a diagnosis, or predict another gradient. The CASP public summary supplies high-level ABA treatment scope for autistic people, with licensed detail outside this page.

Preserve AAC, assent, and basic access for Jiro

ASHA's AAC portal says AAC users should always have access to their communication tools or devices. Breaux and Smith provide assent-focused practice guidance in an evolving evidence base. For Jiro, follow governing consent and assent sources, honor accessible refusal and withdrawal, and keep adequate food and water, bathroom access, communication, mobility, prescribed care, pain response, rest, safety, relationships, and emergency help available.

Choose Jiro's next bounded action

Jiro corrects one feature description, approves the accessible summary, and chooses a community probe as the next step. Record the qualified owner, evidence, effective date, current supports, access and safety state, implementation check, accessible explanation, disagreement route, and reassessment trigger. Preserve the original assessment when materials or contexts change. A new cue version creates a dated record rather than an error in Jiro's earlier performance.

Close Jiro's stimulus-control review

Review the scope-bounded stimulus-control report with Jiro, the qualified behavior analyst, relevant partners, access owners, and specialists named in the manifest. Confirm that stimulus presentation stays separate from functional control, target and comparison denominators are reproducible, AAC and basic access remain protected, health and sensory questions stay with qualified professionals, and conclusions remain bounded to the tested response and context. Keep this page draft and noindex until every required review is complete.

How to Report Stimulus-Control Assessment Results and Limits