How an Adult Can Change or Remove an ABA Support Person

Confirm the adult's current instruction

Speak with the adult using ordinary communication supports and without the support person present when feasible. Ask which roles should end, which should continue, when the change starts, and whether another person will help. Record the adult's own message and any immediate privacy or retaliation concern through the appropriate safety route.

Audit linked permissions

Search meeting invitations, text and email recipients, portal proxies, standing authorizations, directed-record destinations, payer permissions, billing notices, transportation, pickup, emergency contacts, and care-team notes. A person may lose meeting permission while retaining a separately valid legal or emergency role. Route that distinction to the proper owner.

Test the changed configuration

Remove obsolete access, send the adult an accessible confirmation, and test each system. HHS family guidance bases routine directly relevant communication on the adult's agreement or lack of objection in the stated circumstances. HHS restriction guidance may apply when the adult asks for a formal restriction. Preserve the exact route used.

Build a source-controlled record

Create a restricted support-person change log for adult request, affected support tasks, meeting access, disclosures, portal, records, payer, transport, separate legal authority, removal test, and replacement. Record the request or event, the adult's own communication, controlling source, qualified reviewer, source version, effective date, expiration or review date, exact scope, restrictions, clinical owner, privacy owner, operations owner, payer contact when applicable, system changes, verification test, open question, due date, and final disposition. Preserve superseded evidence as history while removing obsolete operational access.

For this support-person change log, label personal-representative authority, involved-person communication, written authorization, directed record access, financial authority, clinical recommendation, payer decision, daily support, and emergency action separately. One relationship label, signature, payment, or meeting invitation cannot safely stand in for all of them.

Protect the adult's communication and choices

Use the support-person change log to keep the adult's voice visible. Offer plain-language explanations, ordinary AAC, interpreter access, enough response time, private communication, several real options, and a way to agree, question, pause, object, or change a supporter. ASHA says AAC users should always have access to their communication tools or devices.

Throughout review of the support-person change log, preserve food, water, bathroom access, mobility, medication, prescribed care, ordinary relationships, rest, and emergency help. The BACB Ethics Code addresses understandable communication, client and stakeholder involvement, consent and assent when applicable, confidentiality, documentation, risk, and evaluation for covered professionals. It does not interpret state law or create organizational authority.

Ask the questions that release the next step

A request to change or remove an ABA support person should trigger a scoped access review rather than an all-or-nothing family label.

• What exact action or disclosure is proposed?
• Which current source governs it, and who is qualified to interpret that source?
• Is the adult acting directly, receiving support, or represented under a verified legal route?
• Which information, decision, person, setting, and date are within scope?
• Which rights and choices remain with the adult?
• What accessible communication and private response opportunity were offered?
• Which clinical, payer, financial, privacy, and operations decisions remain separate?
• What changes in the portal, messages, meetings, records, signatures, or billing systems?
• What evidence proves implementation and removal of obsolete access?
• What event triggers recheck, expiration, restoration, escalation, or legal review?

Place only the affected action on hold when safe. Continue undisputed care and essential supports within verified authority. Emergency and mandatory-reporting routes follow their own current law and policy.

Apply a scoped release decision

Before the next assessment, treatment, meeting, disclosure, record transfer, billing action, or access change, the support-person change log should answer five release questions. What action is proposed? Which source permits it? Has the qualified owner reviewed that source? Can the adult understand and respond through ordinary communication? Do system permissions match the decision?

In the support-person change log, mark yes, no, pending, or inapplicable for each question. A pending legal or privacy gate pauses that path while unrelated supports continue when safe and authorized. Repeat the test when the action, person, information, setting, effective date, or controlling source changes.

A fictional family-involvement example

Caleb is a fictional adult involved in a change from sibling support to a trusted friend. The team locks 20 permission and access states due for action before review. It completes 15 of 20, or 75%, by the due date and leaves every missing field in the denominator. Each open item has an owner, source request, age, and next action.

Caleb's team does not call the percentage proof of valid authority or good care. It checks whether the correct person made each decision, the adult's accessible communication was available, the clinical recommendation remained with the qualified clinician, and system permissions matched the verified scope. It reports completed, pending, disputed, expired, and inapplicable states separately.

Before closing the access change, Caleb reviews a plain-language summary of which support roles ended, which continue, who replaces them, and when each update takes effect. Staff test message recipients, portal views, meeting access, signature routing, record destinations, pickup, and transportation. Any mismatch stays open and blocks only the affected path. The practice records Caleb's experience separately from administrative completion.

Measure verification and access

Measure the support-person change log with locked units and dates: completed required fields divided by all fields due; permissions correctly configured divided by permissions tested; obsolete access removed divided by obsolete access identified; and open items resolved by due date divided by items due. For every duration, name the start and end event. For every percentage, publish counts and the eligible denominator.

Segment support-person change log results by route, service, setting, and responsible owner. Report pending and excluded items with reasons. A high completion percentage cannot establish lawful authority, clinical quality, respect for the adult's choice, coverage, claim acceptance, or outcome. Review errors and client-reported access failures individually.

Review changes before access fails

Recheck the support-person change log when the adult requests a change, a document activates or expires, capacity is formally reassessed, a supporter or family member changes, a portal or payer changes, a service moves settings, or staff identify conflicting evidence. Use the current state law, court or legal document, payer rule, and provider policy for the actual case.

For the support-person change log, the CASP organizational overview supplies broad operations, clinical-operations, and risk framing. USAGov links to legal-help resources. These sources do not decide a particular person's authority. Keep this page in draft until the named clinical, adult or family, privacy, and legal reviewers complete their work.