To plan a communication-technology backup goal in ABA, keep the person's primary AAC and communication system available. Define battery, network, software, access, mount, audio, or device failures and the backup modes the person chooses. Assign technical and partner duties, practice without withholding the primary system, and measure backup readiness, failure recognition, access, use, partner response, recovery, and experience.

Inventory communication dependencies

List primary device, mount, access method, vocabulary, battery, charger, cable, network, app, account, audio, positioning, backup modes, partner knowledge, and repair contacts.

Complete the inventory with Uma in every setting covered by the plan. Record the exact device and access setup she uses, where charging equipment and backups are stored, and which features depend on a network or account. Include low-tech communication that already works, plus partner knowledge, positioning, volume, visual access, and privacy conditions. A device that powers on but cannot be reached or understood is not ready.

Test the chain in ordinary use. Confirm that the mount fits, the correct vocabulary opens, audio can be heard when Uma wants it, and the backup travels with her rather than staying in another building. Document serial numbers or account details only in an approved secure channel. The clinical goal record needs the responsible contact and recovery route, not reusable credentials.

Define failure states

Distinguish low battery, dead device, frozen software, lost network, damaged access method, missing mount, unavailable vocabulary, lost device, privacy incident, and partner failure.

Define each failure in observable terms and pair it with the action that protects communication. A low battery may trigger charging while the primary system still works; a frozen app may require immediate backup access; a lost device may require security, location, and replacement procedures. A partner who fails to bring or recognize the system is a partner or operational event, not a device failure and never a client error.

Add escalation conditions for urgent communication and suspected privacy events. The appropriate technical, organizational, clinical, or legal role decides those responses. Partners need enough information to activate the route promptly while avoiding improvised troubleshooting that could erase vocabulary, disclose data, or make the device unavailable longer.

Choose backups with the user

Record which paper, board, sign, gesture, text, speech, partner-supported, or alternate-device routes Uma accepts for each failure and where each backup is stored.

Uma may choose different backups for different contexts. A paper board might work in a quiet classroom but expose private communication in the community, while an alternate tablet may be useful only if it contains current vocabulary and the right access settings. Let her try options while the primary system remains present, then record her preference, declined options, and how she signals that a backup is inadequate.

Backups should support more than task answers. Include stop, help, health, pain, bathroom, privacy, consent, people, places, and other messages Uma identifies as essential. Provide a route for novel communication rather than limiting her to a small emergency card whenever the primary device fails.

Assign system duties

Name who charges, updates, secures, transports, tests, repairs, replaces, restores, documents, and trains partners. A client goal cannot repair missing infrastructure.

Use named roles and time points. The morning staff member may perform the readiness check, school technology may own repair, the speech-language pathologist may advise on communication-system fit, and an administrator may handle privacy or procurement. Define a backup owner when the primary contact is absent and a method for confirming that restoration is complete.

Partner training should include locating the backup, presenting it without taking over, recognizing Uma's communication, protecting privacy, and reporting the failure. A checklist completion is useful only when representative observation shows the procedure works. Repeated uncharged devices or missing boards call for operational correction, not extra client practice.

Measure readiness and recovery

Report primary-or-backup readiness, natural failures, recognition, backup access and use, partner response, recovery time, lost communication time, privacy events, and Uma's experience.

Readiness uses all covered sessions as its denominator. Failure recognition and backup use apply only to naturally occurring failures or safe simulations that Uma chose. Partner response begins when a failure or backup message is identified. Report restoration separately, since successful backup use can coexist with a device that remains unrepaired for days.

Record the minutes in which Uma lacked an effective communication route, the messages affected, any privacy concern, and the effort required. Ask her whether the backup was acceptable and whether partners listened to it. Review patterns by setting, failure type, and owner so the team can fix weak infrastructure instead of celebrating a high backup-use percentage.

Build Uma's communication-technology backup plan

Inventory each communication failure Uma wants the plan to cover and pair it with a backup she accepts. Record primary-device availability, charging and mounting, vocabulary, network and software, paper or alternate-device location, privacy, partner recognition, repair owner, restoration evidence, and urgent communication route. Keep the primary AAC system continuously available. Practice uses device checks, tabletop review, or naturally occurring failures with consent and assent when applicable rather than creating loss of communication for a trial.

Work through Uma's example

Across eight class sessions, Uma's primary system or tested backup is ready in seven, or 87.5%. Two natural primary-system failures occur during ready sessions. Uma uses the selected backup in both, and partners recognize it in both, producing separate 2 of 2 measures. The unready session remains a system gap. Two successful recoveries cannot establish readiness outside the seven sessions where a communication route was available.

Address Uma's main fit risk

Removing Uma's primary device to create practice weakens communication access. Her plan uses device checks, tabletop practice, and naturally occurring failures. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Uma's next action

The assigned technology or access owner repairs the charging gap, Uma confirms the paper backup vocabulary, and partners retest recognition. 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 Uma's goal

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

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

Review the communication-technology backup plan with Uma, 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