Plan a Request-to-Retain-Support Goal in ABA Care

To plan a request-to-retain-support goal in ABA, identify the useful support the client wants to keep. Separate support use from goal performance, verify authority and safety, and define an accessible request plus partner response. Avoid arbitrary fading based on age, appearance, or independence labels. Measure support availability, request access, participation, experience, burden, and unwanted effects before any change.

Define the support and value

Record the device, visual, prompt, person, schedule, sensory, mobility, language, environmental, or other support and what Petra says it enables.

Describe how the support works in Petra's actual routine. A visual schedule may help her anticipate transitions, correct a missed step, reduce memory load, communicate a change, or participate with less stress. Record where it is available, who prepares it, the version or format, and which activities depend on it. Avoid treating every prompt, accommodation, aid, supervision requirement, and teaching cue as the same kind of support.

Ask Petra what she wants to retain and why, using her preferred communication form. She may value reliability, privacy, comfort, communication access, safety, speed, or choice even when a standard performance score looks similar without the support. Include a way to say that only part of the support remains useful or that she wants to compare a different format.

Separate use from performance

Measure participation, communication, safety, burden, and experience with the support instead of subtracting success because support remains present.

Define success around the activity and Petra's priorities. If the goal is participating in class, report access to the schedule, participation, completed opportunities, communication, errors, distress, time, and experience. Do not mark a correct response as less independent merely because Petra used an approved support. The support may be the condition that makes authentic participation possible.

When the team wants to understand whether needs changed, use a qualified review rather than routinely withholding the support. Compare representative conditions only with Petra's involvement, retained backup, and a stop rule. A single unsupported success does not prove that the support is unnecessary across people, tasks, settings, or periods of fatigue.

Set change safeguards

Require a client-informed reason, qualified owner, current evidence, accessible discussion, consent or assent when applicable, trial, stop rule, and restoration path.

Identify who can change each support. A clinician, speech-language pathologist, occupational or physical therapist, medical professional, school team, payer, legal representative, accessibility owner, or another qualified party may control part of the decision. Record current evidence and any external requirement. Age, appearance, convenience, or a broad expectation of independence is not a complete rationale.

Before a proposed reduction, tell Petra what would change, why it is being considered, what alternatives exist, and how she can object, pause, or request restoration. State the trial setting, length, measures, interim backup, and restoration owner. If the change affects AAC, mobility, medical safety, or another specialized support, involve the relevant professional and preserve access while review occurs.

Keep support access independent of requesting

Petra should not have to demonstrate a new request skill to keep an already useful support. Record routine availability and request access as separate states. If the schedule is missing, provide or restore it under the existing support plan, then document the system failure. A request trial can measure communication access, but it cannot turn staff readiness into Petra's responsibility.

Test proposed changes reversibly

When Petra wants to compare a different format or the qualified team proposes a change, define the setting, duration, retained backup, stop signal, outcome measures, and restoration owner before the trial. Compare participation, errors, effort, stress, and Petra's account under each condition. Preserve the original support during review so a poor trial does not create an avoidable access gap.

Measure retained-support fit

Report availability, requests, partner response, participation, distress, errors, generalization, unwanted effects, burden, and Petra's account.

Use separate denominators for sessions in which the support should be ready, sessions where it was available, review opportunities Petra could access, requests to retain or change it, partner responses, trials completed, and restorations made on time. Report missing support as a system failure. Close a retention request only after the active plan and staff instructions agree, Petra confirms the result, and she knows how to reopen the decision. Recheck availability promptly after staff, classroom, device, schedule, or plan-version changes because earlier access does not prove continuing implementation.

Build Petra's support-retention request plan

Create one versioned support-retention request plan for the classroom participation. Include the request, direct communication, privacy, consent and assent when applicable, AAC and retained supports, authority, source evidence, interim protection, partner duties, eligible opportunities, client and partner measures, experience, burden, decisions, owners, dates, and review triggers.

Work through Petra's example

Across eight classroom sessions, Petra's visual schedule is available in six. She requests that it remain in 3 of 3 review conversations, and the team honors 2 of 3 pending decisions. Report 6/8 availability, 3/3 requests, and 2/3 response. Missing access remains a system failure. Keep every opportunity, readiness state, client action, partner response, system failure, numerator, denominator, exclusion, support, and experience measure visible. This fictional example supplies no universal goal, legal conclusion, payer result, or outcome guarantee.

Address Petra's main fit risk

A higher unsupported score can coexist with more stress or lower participation. Petra's plan evaluates outcomes with the support present. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Petra's next action

The team restores the missed availability, resolves the open decision, and asks Petra whether the format still fits. Record the qualified owner, authority, interim support, evidence needed, due date, client communication, correction route, disposition, and next review.

Apply current professional sources to Petra's plan

For Petra's plan, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, confidentiality, assessment, risk, documentation, and evaluation for covered people. BACB has no separate organizational jurisdiction. The BCBA outline is examination content and supplies no practice authority. The CASP public summary gives high-level context for ABA treatment of autistic people. An evidence-based ABA framework supports integrating research, clinical expertise, client values, and context.

Use implementation and access evidence for Petra

In Petra's plan, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit procedures, representative evidence, and cautious interpretation. They create no universal response threshold. Breaux and Smith offer assent-focused practice guidance in an evolving evidence base. ASHA supports continuous access to AAC tools or devices.

Close Petra's review

Review the support-retention request plan with Petra, the responsible clinician, affected partners, and the specialists named in the manifest. Preserve direct communication, ordinary supports, disagreement, system duties, versions, decisions, limits, and open gaps. Keep this page draft and noindex until all required reviews are complete.

How to Plan a Request-to-Retain-Support Goal in ABA