Measure Reinforcement-Schedule Integrity and Missed Delivery

To measure reinforcement schedule integrity and missed delivery, create Lior's denominator from every eligible response or interval that makes a consequence due. Classify on-time correct delivery, delay, omission, substitution, extra delivery, inaccessible consequence, and data loss. Retain every due event and system failure in coverage. Report client outcomes, observer agreement, and implementation evidence separately so fidelity never substitutes for benefit or fit.

Define when delivery is due

Write response or interval eligibility, schedule count or clock, reset, signal, delivery window, and exception rules. A reviewer should identify due events without knowing whether staff delivered.

Use exhaustive delivery states

Classify on-time correct, late, substituted, omitted, inaccessible, and missing. Add other mutually exclusive states only when the local decision needs them.

Track extras separately

Record consequences delivered outside due events with timestamp, reason, source, and context. Extra delivery changes the obtained schedule without belonging in the due-event numerator.

Sample agreement and source quality

Check agreement on eligibility, due status, delivery, timing, and consequence form. Video, system logs, and live observation have different coverage and privacy limits.

Segment implementation

Report setting, partner, shift, schedule version, response form, and access where enough data exist. A pooled percentage can hide a concentrated failure.

Use this sequence to measure reinforcement schedule integrity and missed delivery

Define Lior's due events, classify every actual delivery, preserve misses and missingness, separate extras, verify agreement, segment system patterns, and compare client outcomes in their own units.

Build Lior's schedule-integrity due-event ledger

Create one versioned schedule-integrity due-event ledger for the clinic-to-community implementation review. Include Lior'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 Lior's schedule evidence

Reproduce Lior's 31 + 3 + 2 + 2 + 1 + 1 = 40 classifications and 31/40 = 77.5%. Confirm that all categories are mutually exclusive and every due event appears once. Audit response or interval eligibility, delivery clock, consequence form, access, setting, partner, missing-data rule, and five extras. Sample observer agreement across due-event identification and delivery coding. Keep Lior's outcomes and experience in separate measures.

Keep Lior's implementation, outcomes, and experience separate

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

Lior has 40 due events across clinic and community routines. Thirty-one are delivered on time and correctly. Three are late, two are substitutions, two are missed, one is inaccessible, and one has missing delivery data. The seven categories sum to 40. On-time integrity is 31/40, or 77.5%. Five extra deliveries occur outside due events and remain a separate implementation 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 Lior's main assessment risk

Dropping missing, missed, and inaccessible events produces 31/36 and overstates integrity. Adding five extras to the numerator produces a measure with no coherent due-event denominator. 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 Lior

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

Interpret ratio and interval patterns cautiously for Lior

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

Measure ratio pauses without assigning character for Lior

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

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

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

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

Choose Lior's next bounded action

Lior asks the team to separate clinic and community results, fix the inaccessible delivery, and review extra consequences before changing the programmed schedule. 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 Lior's earlier performance.

Close Lior's schedule review

Review the schedule-integrity due-event ledger with Lior, 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 Measure Reinforcement-Schedule Integrity and Missed Delivery