How to Coordinate AAC Across School and ABA Services

Make access continuous

ASHA's AAC portal says users should always have access to their communication tools or devices and notes the importance of use across contexts such as school. Define who transports and charges the device, where it is positioned, how it follows the person, and which tested low-tech or other backup is available during repair, transport, water activities, or outages.

Coordinate vocabulary and partner response

The AAC user should guide priorities and changes. Record who can add or hide vocabulary, how changes are communicated across settings, and how partners recognize speech, signs, gestures, writing, and aided messages. Define the response to help, stop, pain, bathroom, break, yes, no, uncertainty, and emergency messages without requiring eye contact or speech first.

Measure system performance separately

Track whether AAC and backup were available, charged, positioned, and functional in every observed session. Separately track whether partners noticed and honored defined messages within the agreed window. The person's message count has a different denominator. Missing access is a partner or system failure rather than a failed communication opportunity for the student.

Build a two-system coordination record

Create a restricted cross-setting AAC access plan for primary AAC, backup, ownership, transport, charging, positioning, access method, vocabulary, message recognition, partner response, change, and repair. Record the student and authorized decision-maker, school and ABA contacts, each source and effective date, the exact event, pending questions, next action, due date, and closure evidence. Preserve original records and label summaries, copies, corrections, and professional interpretations.

In the cross-setting AAC access plan, keep education decisions, private clinical recommendations, consent, disclosure authority, payer states, meeting participation, scheduling, and emergency duties in separate fields. A shared goal, signature, email, portal account, or meeting does not give either organization authority over every decision.

Protect the student's voice and access

Use the cross-setting AAC access plan to show how the student participated. Offer plain language, the student's ordinary AAC, interpreters or other communication support, enough response time, and a way to agree, question, pause, object, or ask for private help. Do not remove communication access to simplify a meeting, observation, or data collection.

For the cross-setting AAC access plan, the BACB Ethics Code addresses understandable communication, client and stakeholder involvement, consent and assent when applicable, confidentiality, assessment, documentation, and risk for covered professionals. ASHA says AAC users should always have access to their communication tools or devices. Apply the governing school and clinical sources to the actual roles.

Ask nine coordination questions

When coordinating AAC across school and ABA, use these nine questions:

• What exact meeting, observation, record, decision, or support is proposed?
• Who maintains each source record and in what role?
• Which FERPA, IDEA, HIPAA, state, school, or provider rule applies?
• What consent, authorization, exception, or invitation supports the action?
• How will the student communicate preference, assent, dissent, pain, or need for help?
• Which definitions, dates, settings, and denominators travel with the data?
• Which school, clinical, privacy, payer, or safety owner decides each issue?
• Which system, recipient, and transmission path will be tested?
• What change, deadline, error, or conflict triggers recheck?

Mark each item complete, failed, pending, or inapplicable with a reason. Pause the affected handoff when required while safe and authorized school and clinical supports continue.

Verify before the handoff occurs

Before the cross-setting AAC access plan releases a record, guest, observation, meeting, plan comparison, or system connection, confirm the exact purpose, holder, recipient, source, effective period, student access, and assigned decision owners. Verify that the data packet contains the definitions and dates needed to avoid a misleading comparison.

A pending item in the cross-setting AAC access plan blocks only the unsupported path. Send the next owner the source, exact question, evidence already collected, and deadline. Recheck when the student, school, provider, service, record category, invited person, consent, setting, or system changes.

Make the handoff usable

Summarize the cross-setting AAC access plan in language the student and authorized adult can use. State what will happen, which organization owns each action, what information will move, what will remain separate, and when the next review occurs. Attribute every statement to student report, family report, school record, provider record, direct observation, or professional interpretation.

The joint FERPA and HIPAA guidance explains that record coverage depends on who maintains the information and in what capacity. Apply that boundary to the cross-setting AAC access plan; avoid calling all school health information HIPAA data or all provider data an education record. Offer a correction path for a wrong summary or recipient.

A fictional school-ABA example

Cam is fictional and involved in school and clinic transitions with a speech-generating device. The team locks 26 AAC access and partner-response fields before review and completes 20 of 26 by the due date. Every missing, disputed, expired, or failed field stays in the denominator with an owner, age, source request, and next action.

The cross-setting AAC access plan reports documentation completeness separately from lawful disclosure, educational quality, clinical quality, safety, and Cam's experience. The team preserves original school and clinic data, tests the affected route, and asks Cam whether communication and support worked as explained.

Any mismatch remains open in the cross-setting AAC access plan. The affected transmission, meeting action, observation, plan change, or access permission waits for the proper owner. Unrelated safe and authorized services continue under their existing plans.

Measure without losing pending work

Measure the cross-setting AAC access plan with locked units: complete handoffs divided by all handoffs due; correct permissions divided by permissions tested; records carrying source, date, definition, and denominator divided by records reviewed; AAC available divided by student observations due; and corrections validated by deadline divided by corrections due. Publish counts, time window, and exclusions.

Segment cross-setting AAC access plan results by school, provider, record type, legal route, event, and owner. Pair process results with student and family feedback, access failures, privacy events, safety conflicts, complaints, and recurrence. These measures show workflow performance. They do not establish educational benefit, clinical effectiveness, compliance, or causation.

Recheck the source and the relationship

Review the cross-setting AAC access plan when consent or authorization changes, the student reaches the applicable age, a school or provider changes, a new record or purpose appears, definitions drift, AAC changes, a safety plan changes, or a transmission fails. Preserve the source, version, effective date, repair, and test history.

For the cross-setting AAC access plan, the CASP organizational overview supplies broad business, clinical-operations, and risk framing. IDEA sources describe federal special-education requirements; the joint guidance explains FERPA and HIPAA at a federal level. School policy, state law, contracts, and case facts can add requirements. Keep this page draft and noindex until every named reviewer completes review.