Compare Programmed and Obtained Reinforcement Schedules

To compare programmed and obtained reinforcement schedules, write Farid's schedule rule first, then audit every eligible response or interval and actual consequence. Classify on-time correct delivery, delay, omission, substitution, extra delivery, inaccessible outcome, reset, and pause. Report the programmed due-event denominator and the obtained sequence separately. Implementation drift belongs to the system record rather than Farid's performance score.

Freeze the programmed version

Record the approved schedule, response definition, count or interval, variability rule, reset, signal, consequence, timing target, owner, effective date, and exceptions before auditing delivery.

Create a due-event denominator

List every response or interval that should have produced the consequence. Keep missed events in the denominator and exclude only prospectively defined invalid units.

Classify actual delivery

Use mutually exclusive states for on-time correct, delayed, omitted, substituted, inaccessible, and data missing. Record extra deliveries outside due events separately.

Preserve sequence and partner

Show the order of obtained outcomes, pauses, resets, people, shifts, and settings. The same aggregate percentage can represent very different experiences.

Repair before evaluating effect

Implementation drift can obscure both benefit and harm. Restore the intended arrangement or approve a new version before attributing Farid's response pattern to the schedule.

Use this sequence to compare programmed and obtained reinforcement schedules

Version Farid's rule, identify due events, classify every delivery, retain extras and access failures, display the obtained sequence, repair drift, and evaluate client outcomes separately.

Build Farid's programmed-versus-obtained schedule audit

Create one versioned programmed-versus-obtained schedule audit for the supported-employment feedback review. Include Farid'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 Farid's schedule evidence

Reproduce Farid's 30 due events and the 24, 2, 1, 2, and 1 mutually exclusive classifications. Confirm that the four extra events are outside the due denominator. Verify response eligibility, partner, timestamp, delay target, consequence form, device access, reset, and pauses. Compare the written schedule with each observed sequence. Fix implementation gaps before interpreting the schedule's relation to Farid's outcomes.

Keep Farid's implementation, outcomes, and experience separate

Measure programmed-versus-obtained schedule integrity with due events. Measure Farid'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 Farid's example

Farid has 30 programmed feedback events due during the review. Twenty-four occur on time and in the defined form. Two are delayed, one is substituted, two are missed, and one is delivered but inaccessible because the device audio is off. Staff also give four extra feedback events outside the programmed rule. Report 24/30 on-time integrity and all six due-event deviations, with extras in a separate count. 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 Farid's main assessment risk

Calling the plan a variable schedule because staff deliver feedback unpredictably converts missed delivery and drift into a technical design. The obtained schedule may also differ across partners, shifts, or response forms. 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 Farid

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

Interpret ratio and interval patterns cautiously for Farid

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

Measure ratio pauses without assigning character for Farid

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

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

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

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

Choose Farid's next bounded action

Farid chooses a visual confirmation option and asks supervisors to review missed and extra deliveries by shift before changing the clinical rule. 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 Farid's earlier performance.

Close Farid's schedule review

Review the programmed-versus-obtained schedule audit with Farid, 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 Compare Programmed and Obtained Reinforcement Schedules