To plan a break-access goal in ABA, protect ordinary rest, food, water, bathroom use, medication, pain care, and emergency help before teaching. Define any additional break decision the person wants, make the request accessible, specify the partner response, and preserve choice about returning. Measure break availability, message access, partner response, wait time, retained supports, burden, and the person's experience.

Separate essential and chosen access

List scheduled rest, bathroom, water, food, medication, pain, mobility, communication, and emergency access separately from an optional communication goal.

Start with an access audit of Priya's actual shift. Compare the written schedule with time records, coverage, location access, and her account of what happens on busy days. A break listed on paper is not available if she is expected to finish a task first, cannot reach the break area, lacks bathroom coverage, or loses access to communication or mobility support. Correct those conditions through the responsible workplace or service role before interpreting request data.

Name essential access in the plan as a standing duty, not a reward for communication. Priya does not need to demonstrate a new response before receiving water, using the bathroom, addressing pain, taking authorized medication, or obtaining emergency help. The optional goal begins only with additional moments she identifies as worth communicating about.

Define the break decision

Record the situations Priya wants covered, accepted message forms, possible locations, length or review point, privacy, support, return choice, and help route.

Ask Priya what “break” means in each covered situation. She may want a quiet space, a brief change of task, time without conversation, access to a support person, or an end to the activity. Write those outcomes separately so the partner does not approve a break while delivering an unwanted substitute. Include speech, AAC, gesture, movement, and agreed contextual signals, along with a way to clarify an uncertain message.

Define what happens near a handoff or time-sensitive step. The solution might be immediate relief with another worker covering, a client-approved interim action, or escalation to a supervisor. Any limit should be specific, lawful, and reviewed by the proper authority. It should never be invented in the moment because staffing is inconvenient.

Assign partner duties

Specify who receives the request, confirms it, changes coverage or workload, preserves safety, avoids repeated demands, and records any delay or exception.

Provide partners with a short response sequence: acknowledge Priya, confirm the requested break outcome if needed, arrange coverage, state when the break begins, and avoid negotiating her back to work. When a response is delayed, the partner records the operational reason and activates the named escalation route. Priya should not carry the burden of repeatedly asking multiple people for the same result.

Return is also a decision. At the agreed review point, offer accessible choices about returning, changing the task, extending the break within applicable boundaries, or contacting the designated support. Score the partner's faithful presentation of those options separately from Priya's selection.

Use representative opportunities

Teach across actual low-risk situations with ordinary supports. Keep inaccessible or partner-unavailable moments visible in the system data.

Begin where coverage and communication are already reliable. Priya can rehearse with a chosen partner or use naturally occurring low-pressure moments without waiting until fatigue or distress is high. Retain any schedule, AAC, coworker support, or environmental adaptation she ordinarily uses. Prompting may support the chosen communication step, but it should not become a prerequisite for access.

Expand across workload levels and supervisors only after the response procedure is stable. An opportunity with no available receiver or no feasible coverage stays in the denominator for system readiness, while it is excluded from the client-response denominator. That distinction directs correction toward staffing rather than Priya.

Measure access and burden

Report scheduled access, eligible moments, message availability, requests, partner latency, honored breaks, return choices, workload, distress, Priya's experience, and corrections.

Set denominators before reviewing the results. Scheduled-break availability uses all breaks owed under the relevant plan or workplace rule. Request access uses the additional moments Priya and the team defined as eligible and ready. Partner response uses recognized requests. Report the number and reason for exclusions, and show results by supervisor or shift when combined data could conceal a recurring gap.

Pair the counts with Priya's assessment of privacy, effort, and whether the break actually helped. A fast response that sends her to an inaccessible or overstimulating location is not a successful outcome. Continue, revise, or close the goal based on access quality and her priorities, not a request percentage alone.

Build Priya's break-access plan

Create one versioned break-access plan for the supported employment shift. Include the chosen outcome, direct communication, consent and assent when applicable, privacy, primary AAC and retained supports, medical and safety authority, system and partner duties, eligible opportunities, teaching scope, client and partner measures, experience, burden, decisions, owners, dates, and review triggers.

Work through Priya's example

Priya receives all eight scheduled rest periods, so ordinary break availability is 8 of 8. During three additional eligible moments, she uses her chosen request in 3 of 3. A supervisor responds within one minute in 2 of 3. These are separate 8/8, 3/3, and 2/3 measures. Keep every opportunity, readiness gate, client action, partner response, system failure, numerator, denominator, exclusion, support, and experience measure visible. This fictional example supplies no universal goal, dose, independence standard, medical or legal conclusion, payer result, or outcome guarantee.

Address Priya's main fit risk

A request percentage can conceal a workplace that misses scheduled rest or delays responses. Priya's plan measures ordinary availability before request performance. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Priya's next action

The supervisor resolves the delayed response, Priya reviews the return-choice language, and the team checks whether workload predicts access failures. Record the qualified owner, authority, affected setting, interim support, evidence needed, due date, client communication, correction route, disposition, and next review. Software may coordinate workflow while qualified people make decisions within scope.

Apply current professional sources to Priya's goal

For Priya's goal, the BACB ethics hub identifies the current Ethics Code, which addresses client involvement, consent and assent when applicable, assessment, medical needs, risk, intervention, 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 planning 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 Priya

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

Review the break-access plan with Priya, 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