To define a treatment relapse assessment question, connect Aya's chosen decision to response classes, treatment and comparison histories, contexts, a recurrence event, timing, exposure, integrity, access, health, direct experience, a candidate process, and alternative explanations. Add an immediate safety route, qualified authority, and a result that can change action. Treat relapse language as a testable hypothesis rather than a person trait.

Begin with Aya's practical decision

State what support choice depends on the answer. Immediate restoration of effective, accessible support can proceed while the team considers whether mechanism-specific evidence is necessary.

Define recurrence without naming a process

Describe the response, accepted communication forms, onset, offset, opportunity, time, context, and comparison period. Use recurrence or return until the required history supports a narrower term.

Map the minimum history

Record earlier reinforcement, treatment start and changes, alternative responses, contexts, exposure, integrity, relevant health and access events, and the exact recurrence phase.

Set interpretation and safety boundaries

Protect communication, withdrawal, health care, safety, and emergency action. State that any result applies to the sampled response, phase, and context rather than Aya as a person.

Use this sequence to define a treatment relapse assessment question

Start with Aya's decision, describe recurrence, map history, verify integrity and access, name candidate processes and alternatives, choose safe evidence, and specify action rules.

Build Aya's treatment-relapse question brief

Create one versioned treatment-relapse question brief for the community printing routine. Include Aya's priority, response classes, phases, contexts, treatment versions, reinforcement, exposure, integrity, access, health, recurrence timing, safety action, direct experience, invalidity, missingness, withdrawal, candidate process, alternative explanations, design limits, decision, qualified owner, correction, and reassessment trigger. Store only decision-relevant information with role-limited access.

Validate Aya's recurrence evidence

A second reviewer should locate Aya's priority, response classes, phase history, context, recurrence, timing, exposure, integrity, access, health, experience, candidate process, alternatives, safety route, authority, and decision paths. Trace facts to Aya, dated observation, records, or labeled hypotheses. Predeclare repair, observe, consult, redesign, close, invalid, and withdrawal routes.

Connect Aya's evidence to a decision

Aya's brief will decide whether the recurrence can be described, whether urgent repair is already clear, and whether a process-specific assessment adds practical value. Closure is valid when the history remains incomplete or the likely burden exceeds the decision value. No relapse test is required simply because a chart increased.

Work through Aya's example

Aya's question brief contains 18 required fields. Fifteen are ready. The prior response class pools leaving with requesting help, the treatment phase lacks an effective date, and the recurrence window has no context version. Readiness is 15/18. The team holds the mechanism question while preserving printing access, help, and the option to pause. Preserve every planned and valid unit, response code, phase and context version, treatment component, reinforcement event, exposure, integrity result, access and health state, safety response, withdrawal, direct report, system failure, repair, correction, and unresolved item. This fictional example demonstrates one assessment control. It offers no diagnosis, person trait, universal relapse estimate, treatment effect, legal conclusion, coverage decision, payment promise, or outcome guarantee for Aya.

Address Aya's main interpretation risk

Asking why Aya relapsed assumes both the event and its process. The return of an old response could reflect changed cues, missing support, health, treatment drift, renewal, resurgence, ordinary variability, or a new response definition. Review response and phase definitions, treatment history, reinforcement, exposure, context, integrity, access, health, partner behavior, direct experience, alternative explanations, authority, and design strength separately. A convincing graph cannot repair an unsafe, inaccessible, unwanted, or historically unsupported recurrence assessment.

Keep treatment scope and authority clear for Aya

For Aya's treatment-relapse question brief, the CASP public summary supplies high-level ABA behavioral-health-treatment scope for autistic people, with licensed detail outside this page. The current BACB Ethics Code addresses competence, client involvement, consent and assent when applicable, medical needs, risk, data, documentation, evaluation, discontinuation, and transition for covered people. The BACB outline supplies examination content. These sources create no individualized relapse protocol or practice authority for Aya.

Distinguish early increase from recurrence for Aya

The historical Lerman and Iwata analysis reviewed extinction data and found early increases under a defined burst criterion in a minority of reviewed data sets. An extinction burst describes a time-linked early increase after extinction begins, whereas Aya's later recurrence question requires its own phase history. The study offers no universal prevalence estimate for current care, no safety authorization, and no prediction for the community printing routine.

Use alternative-reinforcement and communication literature within scope for Aya

Athens and Vollmer evaluated differential reinforcement without extinction with seven children and varied dimensions such as immediacy, duration, and quality. The Tiger, Hanley, and Bruzek review discusses FCT assessment, response selection, partner response, schedule thinning, and related risks. These sources support careful history and delivery measurement for Aya; they supply no universal schedule, delay, consequence, or relapse outcome.

Use renewal evidence cautiously for Aya

The Podlesnik renewal review synthesizes basic and translational work on recurrence with context change while extinction or treatment contingencies remain. Much of that evidence comes from controlled laboratory arrangements. Understanding and Reacting to Relapse discusses practice-facing context and recurrence considerations. For Aya, define people, places, cues, treatment continuity, access, and integrity before applying renewal language.

Preserve broad relapse limits and communication access for Aya

Relapse and Its Mitigation distinguishes several recurrence histories and discusses mitigation concepts. It organizes hypotheses rather than proving which process occurred for Aya. ASHA's AAC portal says AAC users should always have access to communication tools or devices. Follow governing sources and preserve Aya's communication, health care, food, water, bathroom use, mobility, rest, relationships, safety, and emergency help throughout review.

Choose Aya's next bounded action

Aya separates an accessible help request from leaving the station and chooses a new context-specific observation after the printer instructions are restored. Record the qualified owner, source evidence, effective date, current phase and treatment version, ordinary supports, access and health state, implementation check, accessible explanation, disagreement route, and reassessment trigger. Preserve the earlier record when responses, people, settings, systems, schedules, health, or priorities change. A repaired arrangement creates a dated phase rather than an error in Aya's prior performance.

Close Aya's relapse review

Review the treatment-relapse question brief with Aya, the qualified behavior analyst, relevant partners, access owners, and specialists named in the manifest. Confirm that observed recurrence remains separate from resurgence, renewal, an extinction burst, treatment drift, access failure, health change, and treatment effect; every denominator is reproducible; AAC and basic access remain protected; urgent needs received action; and conclusions stay bounded to the supported history. Keep this page draft and noindex until every required review is complete.

Related resources

Sources