Speech-generating device

The device is part of a system

Hardware and software produce output, while communication also depends on vocabulary, symbols, motor or alternative access, positioning, mounting, carrying, partners, environments, and backups. A functioning screen alone does not create usable communication.

The current ASHA AAC portal describes aided and unaided AAC, assessment, implementation, partner support, and continuous tool or device access.

Dedicated and integrated devices differ

A dedicated SGD is designed primarily for communication. An integrated system may run on a tablet or computer that also supports other activities. Each option creates tradeoffs involving durability, restrictions, portability, distraction, funding, updates, accessories, privacy, and repairs.

Record the actual configuration and approved uses. Avoid turning communication off because a general-purpose device is also used for recreation or schoolwork.

Access should not wait for prerequisites

A person should not need to prove speech, imitation, matching, pointing, or a particular cognitive score before receiving communication access. Assessment identifies how the person can make selections and which supports improve use.

Possible access methods include direct touch, switches, eye gaze, head tracking, keyguards, scanning, partner-assisted strategies, and other adapted input. Qualified professionals should assess fit with the user.

Vocabulary supports more than requests

The system should support refusal, comments, questions, opinions, humor, relationships, pain, privacy, consent, assent, emergencies, self-advocacy, and topic changes. Include personally meaningful people, places, routines, and languages.

Plan who may add or reorganize vocabulary and how the user participates. Unannounced layout changes can disrupt motor learning and access. Preserve a change history and test updates with the person.

Partners model and respond

Partners can model communication on the system without requiring imitation, wait for a message, recognize other modes, and respond to meaning. They need training on positioning, charging, volume, access, troubleshooting, and backup communication.

Measure partner readiness separately from user behavior. A device placed out of reach or a message ignored by staff is a system gap.

Build a backup and repair plan

Name the backup board, low-tech symbols, writing, sign, gesture, or other reliable form available during charging, damage, updates, transport, water exposure, or vendor repair. Test the backup in each important setting.

Record who contacts support, authorizes repairs, supplies loaner equipment, restores vocabulary, and informs partners. A backup stored in an office offers little help during a community activity.

Run a transition-readiness check

Before each important transition, verify the primary device, charge, unlock state, position, access method, vocabulary, volume, mount, carrying method, backup, and trained receiving partner. Name the person responsible for each system item. The SGD user should not become responsible for fixing every support failure.

Test arrival at school, home, transportation, community activities, appointments, and emergency locations. Include a dead battery, lost network, broken mount, software update, and absent primary partner. Record how quickly usable communication returns and whether the backup supports urgent messages. Review the results with the user and prioritize gaps they identify. Repeat the check after hardware, software, vocabulary, schedule, partner, or setting changes.

Keep the readiness checklist with the device support plan. It should include current contacts, account recovery, warranty or repair details, vocabulary backup date, and the last successful restore test. Limit access to sensitive credentials while ensuring authorized people can act during an outage. Test access during transport, charging, and sleep routines as well.

A fictional transition example

Camila uses an SGD across school and home. During 16 observed transitions, the primary device is present, charged, positioned, and unlocked in 13 of 16. An agreed backup is available in 16 of 16.

Report primary readiness as 13 of 16 and backup availability as 16 of 16. Camila's messages receive a partner response in 11 of 12 observed communications. Keep system and partner denominators separate from Camila's communication.

Protect ownership, access, and privacy

Clarify device ownership, passwords, cloud accounts, message history, location tracking, remote management, recordings, data sharing, and transition rights. The user needs a meaningful voice in these choices.

Never remove the SGD as punishment, a reward condition, or a route to force speech. If hardware presents an immediate hazard, provide accessible backup communication and restore the device promptly. The current BACB Ethics Code addresses competence, collaboration, client involvement, risk, confidentiality, and evaluation for covered professionals. The BACB Test Content Outline does not create device-selection authority.