Build Baseline and Disruption Windows for Persistence

To build baseline and disruption windows for persistence assessment, define Omar's response unit, observation time, stimulus context, baseline exposure, obtained reinforcement, disruption onset and duration, recovery, sequence, invalid periods, ordinary supports, missingness, and stop rules. Each disruption window should be compared with the same response's relevant baseline. Unmatched contexts or observation lengths need separate reporting rather than one pooled persistence percentage.

Choose Omar's response and clock

Define one completed check-in, acceptable forms, the window start and end, pauses, staff-completed steps, help, withdrawal, invalidity, and missingness. Use the same observation unit across phases.

Establish a relevant baseline

Sample the same garden station under the ordinary support arrangement. Record response rate, obtained reinforcement, exposure, time of day, people, tools, and any trend or instability that affects comparison.

Describe the disruption as an event

Record the handoff onset, duration, staff behavior, access effect, recovery, and stop condition. An event name alone cannot show whether the disruption was delivered consistently.

Retain sequence and recovery

Number every window and preserve carryover, repeated exposure, fatigue, weather, practice, and recovery. A later test may reflect what happened in earlier tests.

Use this sequence to build baseline and disruption windows

Lock Omar's unit, match time and context, measure obtained reinforcement, define the handoff, preserve invalid windows, calculate within-response change, inspect recovery, and bound the conclusion.

Build Omar's baseline-and-disruption window record

Create one versioned baseline-and-disruption window record for the community-garden tool check-in. Include Omar's priority, response class, accepted forms, context, baseline, obtained reinforcement, disruption, recovery, sequence, absolute rate, relative persistence, ordinary supports, access, health, exposure, integrity, agreement, invalidity, missingness, withdrawal, direct experience, burden, alternative responses, causal limits, decision, owner, correction, and review trigger. Store only information needed for the stated decision and limit access by role.

Validate Omar's persistence evidence

Reproduce Omar's baseline mean of 34/4 = 8.5 per 15-minute window, disruption mean of 21/4 = 5.25, and 5.25/8.5 = 61.8%. Confirm four baseline, four matched disruption, one invalid, and two recovery windows. Audit sequence, reinforcement, partner, materials, weather, access, and Omar's report while keeping one rate unit throughout.

Connect Omar's evidence to a decision

Omar's record should show the release rule for another window. Continue only when the same station, time unit, access conditions, and ordinary handoff are available. Hold during rain, equipment loss, changed staffing, or requested pause. Close once the result is precise enough for the stated garden decision rather than collecting repeated disruptions indefinitely.

Work through Omar's example

Omar completes 34 check-ins across four 15-minute baseline windows, a mean of 8.5 per window. During four matched windows containing a routine two-minute staff handoff, he completes 21 check-ins, a mean of 5.25 per window. The disrupted rate retains 61.8% of baseline. One rain-shortened window is invalid and stays in planned coverage. Two recovery windows yield 16 check-ins across 30 minutes. Preserve every planned and valid unit, raw count, time denominator, context version, obtained consequence, disruption event, integrity result, access state, recovery window, withdrawal, direct report, system failure, correction, and unresolved item. This fictional example demonstrates one assessment control. It offers no diagnosis, trait, universal persistence estimate, treatment effect, legal conclusion, coverage decision, payment promise, or outcome guarantee for Omar.

Address Omar's main interpretation risk

Comparing 34 baseline check-ins with 21 disrupted check-ins as raw totals obscures equal or unequal time. Pooling the rain-shortened period changes exposure. Treating recovery as baseline can also conceal order and carryover effects. Review response and context definitions, baseline quality, obtained reinforcement, disruption integrity, sequence, recovery, health, access, effort, partner behavior, direct experience, authority, and design strength separately. A precise percentage cannot repair an unwanted, inaccessible, unsafe, or conceptually mismatched assessment.

Keep concepts and authority clear for Omar

For Omar's baseline-and-disruption window record, the ABAI Basic Principles page supplies higher-education context. The BACB Test Content Outline covers measurement, schedules, stimulus control, motivating operations, experimental design, and interpretation as examination content. The current BACB Ethics Code addresses competence, client involvement, consent and assent when applicable, medical needs, risk, data, documentation, and evaluation for covered people. These sources create no individualized momentum protocol or practice authority for Omar.

Use the translational account narrowly for Omar

In the community-garden tool check-in, Nevin and colleagues describe resistance to change as a relative measure comparing disrupted responding with its own baseline. Their translational review separates baseline response rate from persistence and discusses the role of the stimulus-reinforcer context. It supplies hypotheses and measurement logic for Omar, while individual clinical conclusions still require direct, accessible, context-specific evidence.

Treat applied persistence models cautiously for Omar

The Mace applied review discusses behavioral persistence, alternative reinforcement, and treatment relapse. For Omar's decision, these models can organize questions about context and history. They do not identify a response function, prescribe a treatment, authorize a disruption, or predict relapse for one person. Preserve direct assessment, safety planning, treatment integrity, and model limitations.

Keep reinforcement quality and request sequences distinct for Omar

In research reviewed for Omar, Mace and colleagues examined reinforcer quality, high-probability sequences, and resistance to change across applied and basic experiments. The findings show why obtained consequence quality and context deserve measurement. They also support keeping an applied request-sequence result separate from a formal persistence analysis in the community-garden tool check-in.

Preserve scope, AAC, assent, and access for Omar

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 preserve Omar's communication, health care, food, water, bathroom use, mobility, rest, relationships, safety, and emergency help.

Choose Omar's next bounded action

Omar approves the handoff comparison because it occurs during ordinary gardening. He asks the team to track whether the interruption delays tool access and to stop the comparison if the routine becomes frustrating. Record the qualified owner, source evidence, effective date, context version, ordinary supports, access and health state, implementation check, accessible explanation, disagreement route, and reassessment trigger. Preserve the original assessment when response classes, cues, people, systems, reinforcement, disruptions, health, or priorities change. A new arrangement creates a dated version rather than an error in Omar's earlier performance.

Close Omar's persistence review

Review the baseline-and-disruption window record with Omar, the qualified quantitative behavior analyst, relevant partners, access owners, and specialists named in the manifest. Confirm that baseline rate remains separate from resistance to change; every denominator and time unit is reproducible; obtained reinforcement and context are documented; AAC and basic access remain protected; health questions stay with qualified professionals; and conclusions remain bounded to the sampled response, context, and disruption. Keep this page draft and noindex until every required review is complete.

How to Build Baseline and Disruption Windows for Persistence Assessment