How to Plan a Request-for-More-Time Goal in ABA

To plan a request-for-more-time goal in ABA, identify the decisions or tasks where additional processing or decision time matters. Provide ordinary wait time first, make requests accessible, define the partner response, and distinguish a real deadline from avoidable pressure. Preserve refusal, support, and access. Measure time availability, requests, honored extensions, response latency, decisions, experience, and burden separately.

Define when more time matters

Identify choices, questions, transitions, communication, reading, motor actions, health decisions, or unfamiliar tasks where Asha wants added time.

Observe where the current pace creates a real barrier. Asha may need time to read, use AAC, compare options, recover from a transition, complete a motor step, formulate a question, consult a support person, or decide after receiving new information. Record the task stage, setting, current wait, interruption pattern, and what Asha says would help. Do not assume every pause reflects the same need.

Separate processing time from teaching delay, avoidance, fatigue, pain, inaccessible information, or an unresolved clinical concern. The plan can protect ordinary time while the qualified team reviews other causes. Asha should not need to demonstrate distress before partners provide the agreed window.

Set the default window

Specify ordinary wait time, how the window starts and ends, visible timing when useful, interruptions, reminders, and who may change a true deadline.

Define the default partner behavior before requiring a request. State when the clock begins, what counts as an interruption, whether Asha wants a visible timer, and how partners know she is ready. Give reminders only in the form and frequency she selects. Repeatedly asking whether she is finished can erase the extra time on paper.

Identify genuine deadlines and their sources. Emergency, medical, legal, payer, workplace, school, transportation, or operational limits may have different owners and consequences. Explain the deadline and available alternatives accessibly. Label flexible staff preferences as flexible rather than presenting them as fixed requirements.

Build an accessible request

Accept speech, AAC, gesture, movement, a time card, a selected duration, or a request to return later. Keep refusal and clarification available.

Offer choices that fit the situation: a few more minutes, a named return time, a break, information to review later, another person, or postponement of the decision. Preserve refusal and a request for clarification as distinct messages. Asha may need more time and later decide against the activity.

Teach the partner response alongside the message. The partner should acknowledge, state the revised time, preserve the option, avoid pressure, and follow up through the agreed channel. If the requested extension cannot be granted, the qualified owner should explain why and offer the least burdensome ready alternative.

Measure time and response

Report ready windows, eligible requests, partner grants, latency, repeated prompts, missed deadlines, completion chosen by Asha, stress, burden, and experience.

Track eligible situations, default windows available, accessible request forms, extensions requested, extensions honored, return contacts completed, and decisions reached without counting a particular outcome as success. Include interruptions, repeated prompts, expired options, and burden. Review whether the process gave Asha meaningful time and whether any fixed deadline needs earlier preparation next time.

Build Asha's more-time request plan

For each job-training decision, identify the ordinary processing window, any genuine deadline and its source, who may change it, and the additional time Asha can request. Record visible timing if useful, AAC and accepted request forms, privacy, reminders, interruptions, refusal or clarification, partner acknowledgment, revised return time, and follow-through. Keep workplace or legal deadlines under their applicable authority. Audit whether time was available before measuring Asha's request and whether the trainer honored it afterward.

Work through Asha's example

Across eight training decisions, Asha's agreed processing window is available in six, or 75%. Four of those six situations include an eligible need for more time; Asha requests it in all four, and the trainer grants three, or 75%. The two rushed prompts remain system failures, while the missed extension remains a partner-response gap. Each denominator follows the stage that created the opportunity and says nothing about Asha's ability under an unavailable window.

Address Asha's main fit risk

A fluent request cannot repair a process that withholds ordinary wait time. Asha's plan audits time availability before her response. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Asha's next action

The trainer corrects the missed extension, Asha reviews the reminder method, and the team separates fixed deadlines from flexible prompts. Record the qualified owner, authority, affected setting, interim support, evidence needed, due date, client communication, correction route, disposition, and next review.

Practice the corrected response with each regular trainer before relying on Asha to use it during a high-pressure decision. Verify that the agreed wait begins at the right point, reminders follow her selected schedule, AAC remains available, and a request to return later produces a specific contact time. Record partner errors and repair ownership.

When a window is missed, restore a meaningful opportunity whenever the choice remains open. If the deadline passed, explain the actual consequence, identify whether earlier preparation could have prevented it, and route any correction or review. Compare conditions before interpreting latency: unfamiliar material, device access, interruptions, pain, fatigue, and partner behavior can all affect time used. Close the plan review only after Asha confirms that the revised timing works across the settings that matter. Retain the original and revised timing instructions so supervisors can identify which partner used an outdated rule. Recheck the full window promptly after task, device, setting, health, or staffing changes, and let Asha freely revise the chosen reminder method without losing ordinary processing time.

Apply current professional sources to Asha's plan

For Asha's plan, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, confidentiality, assessment, medical needs, 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 Asha

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

Close Asha's review

Review the more-time request plan with Asha, 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.