To plan a request-for-less-prompting goal in ABA, identify prompts the client wants reduced and preserve safety plus useful support. Define accessible stop, wait, different-prompt, show me, and try-alone messages. Teach the partner to pause and review the prompt plan. Measure prompt exposure, requests, honoring, client action, errors, distress, burden, and experience with the client and partner units separated.

Inventory prompts and supports

List verbal, visual, gestural, model, physical, positional, environmental, time, technology, and partner supports plus who selects or authorizes each one.

Observe the complete task before changing the plan. Record the prompt type, exact task step, timing, who delivered it, whether it was planned, and which support Rafael already had. Separate a teaching prompt from an instruction, safety cue, AAC access, environmental arrangement, mobility support, or supervision requirement. Calling every form of help a prompt can lead the team to remove an essential accommodation while chasing a lower prompt count.

Ask Rafael which parts feel intrusive, rushed, repetitive, confusing, or unnecessary and which supports he wants to keep. He may want more wait time before a verbal prompt, a visual instead of spoken direction, help only at a hazardous step, or the option to request a demonstration. Record his preferred changes by task and setting rather than assuming one fading rule fits the whole routine.

Define client messages

Accept stop, wait, try alone, different prompt, show me, help, repeat, move back, and restore the prior support through Rafael's communication forms.

Make every message available before the task starts through speech, AAC, gesture, card, switch, or another established form. Teach partners to recognize existing signals rather than requiring Rafael to use one new phrase perfectly. Include uncertainty and correction. He may begin by asking to try alone, then request help or restore a support without that change being scored as failure.

Check privacy and power. A request for less physical or verbal prompting may be difficult to make to the person delivering it. Provide a route to review the plan with another trusted person and a way to report prompts delivered after a stop signal. Preserve ordinary access and avoid making preferred activities contingent on accepting a prompt.

Teach the partner response

Specify pause, safety check, acknowledgment, prompt change, observation window, reoffer, documentation, escalation, and how Rafael confirms the result.

The partner should pause long enough for the selected message to matter, acknowledge it without debate, check the predeclared safety rule, and follow the agreed branch. That branch might allow Rafael to try alone, extend wait time, switch prompt type, receive a demonstration, or stop the step. If a qualified safeguard limits the request, explain the specific boundary and offer the least intrusive ready alternative.

Practice the partner response across the people and settings that use the plan. Record missed acknowledgments, repeated prompts, shortened wait time, and unauthorized prompt changes. A client-focused goal cannot be considered implemented when Rafael communicates clearly but partners continue the old prompting pattern.

Protect essential safeguards

Classify each prompt or support before changing it. A teaching cue, communication aid, approved safety procedure, mobility support, equipment instruction, and legally or clinically required supervision can have different owners and change rules. If Rafael asks to reduce an item that carries a current safety function, pause the activity when needed and route the request to the qualified owner. Give him an accessible explanation and an interim option while review continues.

Measure the prompting environment

Count prompts delivered by type, timing, source, and task step along with Rafael's requests. Record unplanned repeats, prompts delivered after a stop message, partner wait time, and whether the selected change occurred. A lower prompt count can reflect missing teaching or inaccessible instructions, so interpret it with task opportunity, accuracy, safety, effort, and Rafael's experience.

Measure both sides

Report prompt opportunities and type, accessible messages, requests, partner response, latency, client action, errors, safety events, distress, burden, and experience.

Use task-step denominators for planned prompt opportunities, message access, requests made, partner responses matched, and steps completed under each condition. Keep errors, near misses, safety events, effort, distress, duration, and Rafael's account visible. Review whether less prompting improved fit without reducing instruction clarity or essential support, then document the continue, revise, or restore decision and update every partner copy. Retest after any material procedure change.

Build Rafael's less-prompting request plan

Create one versioned less-prompting request plan for the meal-preparation teaching. 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 Rafael's example

Across twelve eligible meal-preparation steps, Rafael can access his prompt-choice message in ten. He requests less prompting in five of those ten, and the partner honors 4 of 5. Report 10/12 access, 5/10 requests, and 4/5 partner response. Two inaccessible steps stay visible. 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 Rafael's main fit risk

Reducing prompts without checking safety or Rafael's chosen support can create risk. The plan changes only the prompt he identifies and preserves the approved safeguard. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Rafael's next action

The partner repairs the missed response, Rafael reviews prompt options, and the clinician checks error and burden patterns. Record the qualified owner, authority, interim support, evidence needed, due date, client communication, correction route, disposition, and next review.

Apply current professional sources to Rafael's plan

For Rafael'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 Rafael

In Rafael'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 Rafael's review

Review the less-prompting request plan with Rafael, 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.

Related resources

Sources