Can a Client Request an ABA Prompt?

Plan an accessible help request

Agree on accessible help messages and the support each message requests. A person might ask for a hint, show me, read it, point, write it down, first step, more time, check my work, or do this part. The form can be speech, AAC, gesture, sign, a help card, a button, or another reliable signal.

A broad help request can lead to a brief clarification when several options exist. The partner should respond within a defined time and avoid requiring a longer or more elaborate message before providing useful help. If the person appears to need immediate safety or access assistance, staff should follow the relevant plan rather than testing whether a more specific request can be produced.

The support following each request should be stated in advance. “Hint” might lead to one clue, while “show me” leads to a model and “do this part” transfers that step to the partner when appropriate. Predictable outcomes make help-seeking useful. A vague promise that support will be available can fail if different staff respond in incompatible ways.

Separate requested help from adult-added prompts

Requested help begins with the client's message. An adult-added prompt begins when staff provide teaching assistance that the client did not request. Both may support a correct response, but they show different forms of participation and need different data categories.

Timing matters. If the client starts a help request and the adult prompts before the message is complete, the record should preserve that sequence. If staff provide a prompt immediately after the cue, the person may have had no practical chance to request help or respond independently. Response timing should account for the client's processing time and communication access.

Ordinary supports are another category. A recipe, calculator, visual schedule, map, spell-checker, mobility aid, or AAC device may be part of how the task is normally completed. Using an ordinary tool independently is different from receiving a teaching prompt, even though both provide information. Families can ask the team to name these conditions before data collection.

Teach the interaction in a useful order

A plain process can look like this:

1. Identify a task where help-seeking serves a real purpose and where help will actually be available.
2. Agree on accessible messages and the specific support attached to each.
3. Make ordinary tools, AAC, and stop or break communication available.
4. Present the natural cue and allow the full response window.
5. Honor a help request promptly, provide only the requested amount when feasible, and record what occurred.
6. Let the person continue, delegate a step, choose another method, pause, or stop according to the plan.
7. Review whether the support solved the problem and whether the person wants a different help option next time.

The partner can offer a small menu if the request is unclear: “Do you want a hint, a demonstration, or help doing this part?” The menu itself is added support and should be recorded when relevant. It should not become an interrogation that delays access.

Help also needs an honest answer. When the partner lacks the information, cannot perform the requested step, or must follow a safety boundary, they can acknowledge the request and explain what help is available. Ignoring the message or pretending to help teaches an unreliable interaction.

Define independence for the real task

Some activities reasonably include asking another person, checking instructions, using a calculator, or opening a map. Decide whether the target is fully unassisted performance, independent tool use, appropriate help-seeking, collaborative completion, or a combination. Report each category plainly.

A person can independently recognize a problem and recruit the exact support needed. That is meaningful problem solving even though the next task step is completed with help. A whole-task “independent” label may still be inappropriate if another person performs part of the work. Step-level categories can show both strengths without inflating authorship.

Goals should reflect daily life. If a coworker is normally available for a two-person lift, requesting assistance may be the safe independent response. If the goal is using a self-check routine before asking, the plan should explain why that sequence matters and which situations allow immediate help. Safety, pain, access, and dignity should never depend on completing an arbitrary independence test first.

Protect communication access

The ASHA AAC portal supports ongoing access to tools or devices. The Ethics Code addresses understandable communication, client involvement, consent and assent when applicable, documentation, risk, and evaluation. A help request should remain available during teaching, probes, transitions, and errors.

Staff should not move, lock, simplify, or edit an AAC system solely to make the target help word easier to find. A separate teaching display or temporary visual may be useful when approved, while the person's full system remains available. Changes to vocabulary, access method, or positioning require the client's input and appropriate AAC or motor-access expertise.

Device outages, missing symbols, poor positioning, inadequate wait time, and partners who do not recognize the message are access or implementation events. They should remain visible rather than becoming client errors. A tested backup should support help, stop, pain, break, and other essential messages.

Fade only unwanted dependence

The team may teach a smaller hint, a self-check routine, or later help-seeking when that change serves the person's goal. Fading can involve offering less information, increasing the pause before help, shifting from a demonstration to a checklist, or teaching the person to select among help types. The client should know the change and retain a reliable way to obtain necessary support.

Repeated help requests may indicate an unclear cue, inaccessible material, missing prerequisite, fatigue, pain, low task value, or a prompt that has become part of the routine. The correct response is assessment, not automatically delaying help. Staff can look at which steps trigger requests, whether the same support works, and how the person describes the task.

Retain help that improves safety, access, dignity, or practical participation. Client preference and task consequences belong in the decision. A support can remain indefinitely when it is an ordinary, efficient part of the person's chosen method.

Use research within its limits

The ABAI basic-principles curriculum and BACB outline include prompts, fading, stimulus control, measurement, and evaluation among foundational or professional concepts. The prompting decision article organizes variables for selecting and evaluating prompting strategies.

The Libby comparison examined two prompting arrangements for a narrow solitary-play task. These sources do not establish one rule for how quickly requested help should arrive, which help type should be faded, or whether strategic help counts as independence in a particular daily task. The team needs an individualized definition and direct evidence.

A practical example

Beck is assembling a camera tripod with a ten-step picture guide. Across five full routines, there are 50 step opportunities. Beck completes 38 independently using the guide, selects show me on AAC for seven, asks a spoken question for four, and encounters one invalid opportunity because a required fastener is missing.

Of the 49 valid step opportunities, the report shows 38 of 49 completed independently with the ordinary guide, 7 of 49 completed after an independently requested demonstration, and 4 of 49 completed after an independently requested verbal answer. Help requests receive the promised support within ten seconds in 11 of 11 opportunities. The missing-fastener event stays outside the performance denominator.

The pattern shows that eight of the 11 requests occur at the same adjustment step. Beck says the diagram for that step is unclear. The team revises that picture with Beck and begins a new material version. It does not simply wait longer before helping, because the recurring requests point to an environmental problem worth repairing.

A family checklist for requested help

• Agree on accessible ways to request a hint, model, explanation, shared step, break, or stop.
• Define exactly what support follows each message and how quickly.
• Keep requested help, adult-added prompts, ordinary supports, and partner completion separate.
• Allow enough time for the person's communication and access method.
• Record whether the partner recognized and delivered the promised support.
• Check repeated requests for unclear materials, pain, fatigue, access problems, or missing skills.
• Preserve essential help during teaching, probes, transitions, and errors.
• Decide with the client which help is worth fading and which should remain.
• Use step-level authorship data when another person completes part of the task.
• Set a clinician, AAC or motor-access reviewer, and review date when changes are needed.

Questions families can use

How can the person ask for help? Which help follows each message? Is requested support different from an adult-imposed prompt? Does the independence definition fit daily life? Which supports remain available? Are repeated requests revealing a problem with the task or materials? Does the partner provide the promised support reliably?

Limits of this guidance

Help-seeking depends on the task, the person's communication and motor access, safety, available partners, and daily goals. This page cannot select a prompt, alter an AAC system, determine the meaning of an ambiguous message, or decide when help should be delayed. A qualified clinician should design and review the process with the client and family and involve AAC, motor, medical, trauma-informed, school, safety, privacy, or legal specialists when applicable.