Distinguish Response-Dependent From Time-Based Delivery

To distinguish response-dependent from time-based delivery, define Jonas's response rule, timer, delivery event, reset, response and nonresponse states, competing schedules, actual timing, access, and current value. Response-contingent delivery depends on a response. Fixed-time or variable-time delivery follows elapsed time without that dependency. Fixed-interval and variable-interval schedules require the first eligible response after the interval, creating a different arrangement.

Write the dependency rule

State whether the consequence requires a defined response. Record which response forms qualify, the delivery window, prompts, and partner action.

Write the timer rule

Define fixed or variable time, timer start, duration distribution, pause, reset, and delivery. Response-independent describes the dependency, not whether behavior happens nearby.

Separate interval schedules

Under fixed or variable interval schedules, elapsed time creates eligibility and a later response produces delivery. The timer alone does not produce the consequence.

Code overlaps prospectively

Specify how to record a response close to a time-based delivery, competing schedule events, timer resets after contingent delivery, and multiple responses in one window.

Protect basic access

Avoid using communication, food, water, bathroom use, mobility, pain response, prescribed care, safety, or emergency help as restricted consequences. Free access can be the appropriate arrangement.

Use this sequence to distinguish response dependent from time based delivery

Define Jonas's response and timer rules, preserve separate due-event cohorts, audit actual timing and overlap, verify access and value, and report schedule identity before analyzing response effects.

Build Jonas's response-dependency and timer comparison

Create one versioned response-dependency and timer comparison for the quiet-space access review. Include Jonas's priority, response, consequence, programmed schedule, obtained schedule, count or clock, distribution, reset, signal, value, availability, delay, magnitude, quality, effort, prompts, access, health, exposure, integrity, agreement, raw sequence, invalidity, missed delivery, extra delivery, withdrawal, direct experience, benefits, side effects, result, uncertainty, decision, owner, correction, and review trigger. Store only decision-relevant information with role-limited access.

Validate Jonas's schedule evidence

Reproduce Jonas's 12 response-dependent and eight time-based due events, 11/12 and 8/8 delivery results, one miss, and three close coincidences. Verify timer starts, response windows, resets, actual delivery, value, access, and any overlapping rules. Preserve essential regulation and safety access outside experimental comparisons. Report dependency from the programmed and obtained rule, then analyze later behavior with separate evidence.

Keep Jonas's implementation, outcomes, and experience separate

Measure programmed-versus-obtained schedule integrity with due events. Measure Jonas's response and client-priority outcome with their own units. Ask separately about clarity, effort, comfort, usefulness, burden, and whether assessment should continue. Accurate implementation can coexist with poor fit or unwanted effects. Better experience can also occur without evidence that the schedule caused an outcome change.

Work through Jonas's example

Across 20 planned quiet-space deliveries, 12 are scheduled after Jonas's accessible request and eight by a ten-minute timer. Staff deliver 11/12 response-dependent events after a valid request and all 8/8 time-based events regardless of responding. One requested event is missed. Three timer events also happen shortly after a request by coincidence and remain time-based because the programmed dependency and actual rule did not change. Preserve every planned and valid unit, raw count, denominator, eligible response, due event, count or clock, reset, signal, delivery, delay, miss, substitution, extra, access state, integrity result, withdrawal, direct report, system failure, correction, and unresolved item. This fictional example demonstrates one assessment control. It offers no universal schedule effect, behavioral function, diagnosis, trait, treatment effect, legal conclusion, coverage decision, payment promise, or outcome guarantee.

Address Jonas's main assessment risk

Classifying the three close timer deliveries as request reinforcement based on timing alone changes the obtained schedule on paper. Conversely, calling all access noncontingent can hide the one missed response-dependent event. Review response and consequence definitions, programmed and obtained rules, count or clock, reset, signal, value, availability, delay, effort, prompts, access, health, context, client experience, authority, and causal scope separately. High integrity cannot repair an inaccessible, burdensome, or ethically unsound schedule.

Keep schedule concepts and authority clear for Jonas

The ABAI Basic Principles page lists reinforcement schedules in higher-education content. The BACB Test Content Outline covers continuous and intermittent reinforcement, ratio and interval schedules, time schedules, compound schedules, maintenance, and schedule thinning as examination content. The current BACB Ethics Code addresses competence, involvement, consent and assent when applicable, positive reinforcement, medical needs, risk, data, documentation, and evaluation for covered people. These sources do not create an individualized schedule for Jonas.

Interpret ratio and interval patterns cautiously for Jonas

Baum analyzes interval and ratio performance from a molar perspective. Staddon and Cerutti review operant conditioning and schedule research. These sources support careful attention to programmed relations, obtained outcomes, time, and response allocation. Textbook schedule patterns are common findings rather than promised signatures for Jonas.

Measure ratio pauses without assigning character for Jonas

Lattal and colleagues review decades of research on pausing under ratio schedules. Pauses can vary with upcoming and prior ratios, reinforcer conditions, histories, and procedures. For Jonas, define the pause boundary, requirement, consequence, effort, and context before interpreting the observation. A pause is not proof of unwillingness or one mechanism.

Scope schedule-thinning evidence carefully for Jonas

Hagopian, Boelter, and Jarmolowicz reviewed schedule thinning following functional communication training and found 19 of 76 reviewed FCT studies described thinning. Falligant and colleagues provide an updated review addressing recurrence, pacing, reinforcer dimensions, competing activities, signals, and other design variables. These FCT-focused reviews do not create a universal schedule, delay ladder, or clinical result for Jonas.

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

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

Choose Jonas's next bounded action

Jonas chooses free quiet-space access whenever possible and keeps an accessible request route for times when logistical help is needed. 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 responses, consequences, people, systems, schedules, or preferences change. A new arrangement creates a dated version rather than an error in Jonas's earlier performance.

Close Jonas's schedule review

Review the response-dependency and timer comparison with Jonas, the qualified behavior analyst, relevant partners, access owners, and specialists named in the manifest. Confirm that programmed and obtained schedules stay separate, due-event and response denominators are reproducible, AAC and basic access remain protected, health questions stay with qualified professionals, and conclusions remain bounded to the sampled response, consequence, schedule, time, and context. Keep this page draft and noindex until every required review is complete.

How to Distinguish Response-Dependent From Time-Based Delivery