Can a Client Ask Who Will Be in an ABA Session?

Who attends ABA session visits

Provide the expected participant list before the visit when practical. Verify identity at arrival and explain role changes. A trainee's presence, a caregiver's relationship, or an employee's system access does not by itself establish permission to observe every activity or receive every record.

Protect client access and participation

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Provide a reliable way to ask, decline, pause, report discomfort, and correct another person's interpretation.

Keep roles and evidence clear

The CASP public summary supports individualized assessment, planning, implementation, and evaluation for ABA treatment of people diagnosed with autism.

The BACB Ethics Code addresses understandable communication, client involvement, consent and assent when applicable, assessment, intervention, risk, documentation, supervision, and evaluation for covered behavior analysts.

The BCBA Test Content Outline covers assessment, measurement, intervention, and data-based decisions as examination content. These sources do not create one universal session policy.

A practical example

Jordan expects an RBT and supervising BCBA. A trainee arrives for observation. Jordan uses AAC to decline the trainee's presence. Staff move the trainee out, preserve the planned communication supports, and document the response under the practice's applicable process.

Questions families can use

Ask who is expected, who may join remotely, whether any trainee or observer is optional, how the client can decline or pause, what each role may do, and how an unexpected participant is documented.

Build the session-participant roster

Use the session-participant roster to tell the client who is present, why each person is there, what each role may do, and how the client can raise a concern or decline optional participation. Record names, roles, participation purpose, in-person or remote status, expected arrival, access to information, optional or required status, consent and assent route, privacy limits, payer or setting rule, role change, client response, and departure time. Add the source, date, responsible role, current state, and next review to each material entry so the family can tell what is confirmed and what remains open.

For the session-participant roster, use states that fit the work: requested, acknowledged, scheduled, observed, held, corrected, escalated, resolved, or closed with reason. Keep client communication, clinical judgment, operational action, payer status, service delivery, and claim outcome separate because those facts may change at different times.

Start with the client's purpose and access

Ask what the client wants to understand, communicate, change, or avoid through the session-participant roster. Provide the person's usual speech, AAC, sign, gesture, writing, interpreter, sensory, mobility, language, and processing supports. Record a caregiver's observation by source and invite the client to correct another person's interpretation.

The session-participant roster should name who has authority for the decision at issue. Client assent or dissent when applicable, legal consent, privacy permission, clinical authority, payer action, and family involvement are distinct. A relationship or staff title should never be used as a shortcut for all of them.

Work through the process in order

1. Share the expected roster before the visit when practical. Open the session-participant roster with the exact question and owner.
2. Verify every participant's identity and purpose at arrival. Preserve access and record the immediate response.
3. Explain optional observers, trainees, and remote participants. Identify the evidence, governing role, and any hold.
4. Honor the applicable client response and privacy process. Keep what actually happened separate from what was planned.
5. Update the roster when anyone joins, leaves, or changes role. Give the family a dated result and next step.

For this session-participant roster, define every duration and proportion before collecting it. State the start and end event, eligible opportunities, exclusions, missing records, and the person or system that supplied the data. Report raw counts beside percentages and keep declined or invalid events visible under their correct category.

Prepare for a realistic complication

An employee may have system access without permission to observe every activity, and a caregiver relationship does not automatically provide access to every record. Unexpected trainees or observers can also create pressure to agree. Pause long enough to explain the person and apply the actual privacy and participation rule.

When that complication appears, return to the session-participant roster and document the changed condition. Identify which conclusion remains supported, which one is on hold, which alternative is available, and who will gather the next evidence. Do not silently rewrite the earlier plan or observation.

Work through a concrete example

Jordan expects an RBT and supervising BCBA. A trainee arrives to observe. Jordan uses AAC to decline the trainee's presence. Staff move the trainee out, preserve the planned session and communication supports, and document the response without treating it as refusal of ABA services.

The example shows how the session-participant roster can support a real family decision. Its counts and outcome describe only the stated people, events, settings, and dates. They do not prove treatment effect, staff quality across all visits, or a universal rule for another provider.

Questions families can ask about the session-participant roster

• Who is expected in person and remotely?
• Why does each participant need to be there?
• Which participants are optional?
• How can the client decline, pause, or ask someone to leave?
• What happens when a participant arrives unexpectedly?

Request a written answer tied to the session-participant roster when it affects names, roles, participation purpose, in-person or remote status, expected arrival, access to information, optional or required status, consent and assent route, privacy limits, payer or setting rule, role change, client response, and departure time. If the answer is unknown, the session-participant roster should show the owner, current source, next action, and update date rather than treating uncertainty as completion.

Review the result with the client

Review the session-participant roster in a format the client can use. Ask whether it reflects the person's message, what felt helpful or burdensome, and what should change. Correct factual errors while preserving who originally supplied each account. Keep private personnel information outside the family-facing summary while still explaining the effect on care.

The session-participant roster should match the people who actually attended. Preserve the client's response and the reason for any addition rather than assuming a title, relationship, or employment status resolves privacy and choice.

Prepare the family follow-up

Before the next visit or review, use the session-participant roster to list what the family should expect to see, hear, receive, or decide. Include the relevant contact, date, accessible communication route, and any evidence the family has agreed to bring. If the expected step does not occur, the session-participant roster should explain whether the family should contact the clinician, operations team, privacy contact, payer, or another responsible route.

The final session-participant roster entry should state the disposition, evidence limits, follow-up owner, and future review trigger. Give the client and family a concise summary plus a route to report a mismatch between the written result and what occurs next. Preserve that summary as a dated version so a later correction or change remains visible.