To plan a communication-support preference goal in ABA, identify the interpreter, language, AAC, modality, pace, positioning, or partner support the client wants for a defined setting. Assign access-provider duties separately from client action, preserve direct communication and refusal, and verify privacy and qualifications. Measure support readiness, preference communication, partner response, fit, burden, and experience.

Inventory support preferences

Ask about language, interpreter, AAC, speech, sign, writing, captioning, visuals, pace, wait time, positioning, lighting, sound, privacy, partner, and backup.

Map preferences by activity and topic. Hugo may want captions for a lecture, an interpreter for discussion, AAC for questions, written instructions for later review, more wait time during decisions, or a private channel for sensitive information. Record the primary and backup support, placement, vocabulary or language needs, and the conditions that make it usable.

Ask what Hugo wants to avoid as well as what he prefers. A familiar partner may help in one setting and reduce privacy in another. Fatigue, lighting, sound, device position, topic complexity, and group pace can change fit. Treat the preference as current information that Hugo can revise.

Assign provider duties

Identify who arranges, funds, verifies, schedules, positions, tests, updates, secures, and replaces each support under applicable access and service requirements.

Separate Hugo's communication from system readiness. The program, provider, school, employer, payer, technology owner, interpreter service, or another authority may control procurement and setup. Record who confirms each gate, the due date, backup, and current status. Do not score Hugo down because a captioner was absent, a device lacked needed vocabulary, or staff placed it out of reach.

Plan maintenance and change control. Identify charging, connectivity, updates, vocabulary changes, interpreter confirmation, secure storage, infection precautions, and partner training. Preserve the working version during upgrades and provide a tested backup. A support plan should survive staff absence and ordinary equipment failure.

Test the support before the activity

Readiness means the selected support works where it will be used. Check device charge and vocabulary, interpreter or captioning connection, sight lines, sound, seating, lighting, privacy, partner knowledge, and the agreed backup. Let Hugo confirm the setup through his usual communication. Record a failed check as an access or system result, even when the activity later proceeds through a workaround.

Treat preference as current

Communication needs can vary by topic, setting, fatigue, privacy, sensory conditions, and communication partner. Ask at defined transition points and after a support failure instead of treating one prior choice as permanent. Keep the original preference, later change, partner response, and outcome as separate facts. A switch to the backup shows that the backup was used; it does not establish that the preferred support was ready.

Define preference messages

Accept select, change, decline, reposition, slow down, repeat, different partner, private channel, backup, stop, and complaint through Hugo's accessible forms.

Make these controls available through Hugo's established system before the activity begins. Partners should acknowledge, adjust the environment or support, and confirm the result. If a requested change cannot happen immediately, explain the reason and offer a ready alternative without requiring Hugo to continue through inaccessible communication.

Provide a route outside the immediate partner for repeated failures, privacy concerns, or discrimination. Preserve direct communication and label proxy observations separately. A support person can assist with access without becoming the author of Hugo's preference.

Measure access and fit

Report support readiness, eligible adjustments, client messages, partner response, latency, missed access, direct communication, burden, and Hugo's experience.

Track planned activities, preferred supports ready, backups used, adjustment opportunities, Hugo's messages, partner responses, access failures, and qualified corrections. Report the primary support and backup separately. Review direct communication, participation, effort, privacy, and experience before deciding that the arrangement fits, then update every affected partner and test again after material changes.

Build Hugo's communication-support preference plan

Create one versioned communication-support preference plan for the adult education program. Include the request or choice, direct communication, consent and assent when applicable, privacy, AAC and retained supports, authority, source evidence, system and partner duties, eligible opportunities, client and partner measures, experience, burden, decisions, owners, dates, and review triggers.

Work through Hugo's example

Across eight classes, Hugo's preferred communication support or agreed backup is ready in seven. He communicates a support adjustment in 3 of 3 eligible moments, and staff respond in 3 of 3. Report 7/8 readiness plus separate 3/3 client and partner measures. 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, dose, independence standard, legal conclusion, payer result, or outcome guarantee.

Address Hugo's main fit risk

A goal that scores Hugo's participation can hide a missing interpreter or poorly positioned AAC. His plan measures support readiness first. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Hugo's next action

The program corrects the missed support, Hugo confirms the backup, and staff review positioning before the next class. Record the qualified owner, authority, affected setting, interim support, evidence needed, due date, client communication, correction route, disposition, and next review.

Test the correction before instruction resumes. Verify the preferred support and backup in the actual room, platform, seating, lighting, sound, and privacy conditions; confirm that current vocabulary or language access is available; and have Hugo approve the setup through his ordinary communication. Record every failed gate and the responsible repair owner.

During the next class, check whether partners responded to adjustment messages, whether direct communication reached the intended people, and whether use of the backup added effort or lost information. Reconcile staff instructions after the trial and keep the issue open until Hugo receives an accessible disposition. Repeat readiness testing after interpreter, device, software, room, schedule, partner, or topic changes that could affect access.

Apply current professional sources to Hugo's plan

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

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

Review the communication-support preference plan with Hugo, 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