To transfer ABA supervisory responsibility without losing continuity, inventory every client-care, RBT, BCaBA, fieldwork, employment, payer, licensure, and system relationship owned by the departing or unavailable supervisor. Verify the replacement's authority, competence, capacity, conflicts, dates, cases, records, observations, hours, deadlines, and portal relationships. Obtain explicit handoff acceptance, notify affected people accessibly, and hold work that lacks qualified coverage.

Define Uri's exact supervision relationship

Transition ends when the responsible person has authority, evidence, access, capacity, and accepted work, not when the outgoing supervisor disappears from the calendar. Record the purpose, source, accountable supervisor, supervisee or trainee, client or case scope, dates, setting, qualifying work, excluded work, communication, evidence, escalation, and transition before the relationship begins.

Build Uri's supervisory-responsibility transition register

Start before leave or departure when possible. Use one transition row per responsibility with outgoing owner, incoming owner, client or supervisee, purpose, source, effective dates, current plan, risk, pending decision, last contact, next observation, hours or records, portal status, access, payer or license action, notification, acceptance, and unresolved item. Preserve original records and avoid backdating. A human-resources transfer or portal change cannot silently establish clinical or certification responsibility.

Protect clients and supervisees in Uri's workflow

Throughout Uri's supervisory-responsibility transition register, keep immediate safety, competent case decisions, required supervision, informed consent where required, assent when applicable, dissent, AAC, disability and language access, privacy, ordinary care, complaint routes, nonretaliation, employment rights, and lawful transition protected. The relationship cannot create authority beyond the supervisor's verified credential, license, competence, payer, employer, case, relationship, and jurisdiction scope.

Work through Uri's fictional example

Uri's organization inventories 14 transition rows. Ten receive verified replacement authority and accepted handoffs before the outgoing supervisor's end date. Two are temporarily covered under a verified route with dated limits. Two remain held because the proposed replacement lacks case competence and a required portal relationship is incomplete. Sessions or certification activity that depend on those rows do not proceed as if coverage exists. Preserve each planned, released, held, excluded, completed, corrected, transitioned, and unresolved unit with its relationship, source version, person, case, organization, date, owner, evidence, access, risk, decision, and follow-up.

Use Uri's denominator without double counting

Permanent handoff readiness is 10 of 14. Covered continuity is 12 of 14 when the two valid temporary routes are included. The remaining two holds stay visible. Client-care, RBT, BCaBA, fieldwork, payer, and employment transitions are reported separately when their authorities differ.

Connect Uri's evidence to an accountable decision

The outgoing supervisor supplies an accurate handoff. The incoming supervisor accepts only verified work. Clinical leaders protect client continuity. Credential, payer, licensing, system, and employer owners complete their routes. Uri and affected clients or staff receive accessible notice and a current contact.

Address Uri's main interpretation risk

A name on a schedule, email thread, portal, or organization chart can create the appearance of coverage without actual acceptance or authority. Verify both the relationship and the work transferred.

Place Uri's supervision workflow inside an organization

For Uri's supervisory-responsibility transition register, the CASP Organizational Guidelines public overview provides high-level business, clinical-operations, and risk-management scope for autism service organizations. CASP sells the detailed guidelines. The workflow on this page is Finni's editorial design, not a CASP-prescribed supervision procedure, accreditation standard, payer rule, or legal conclusion.

Apply the current ethics code to Uri's covered work

The current BACB Ethics Code applies to BCBA and BCaBA certificants and people who completed an application. Its supervision section addresses competence, supervisory volume, delegation, performance monitoring and feedback, documentation, evaluation, and transition. BACB has no separate jurisdiction over organizations or corporations. Uri's employer still needs role-specific policy and current legal, licensing, payer, privacy, and client-care controls.

Identify Uri's exact BACB supervision role

The BACB supervision and training page distinguishes supervising RBTs, assessing or training RBTs, supervising BCaBAs, and supervising fieldwork. Its role table points to different handbooks, packets, or curricula and identifies which roles require the eight-hour training. A BACB role does not itself establish licensure, employer authority, payer recognition, case responsibility, or payment for Uri's client-care, RBT, BCaBA, fieldwork, employment, payer, licensure, portal, leave, and departure transitions.

Use the training curriculum as a design aid for Uri

The May 2026 Supervisor Training Curriculum Outline 2.0 includes preparation, capacity, contracts, goal setting, performance skills, feedback, evaluation, documentation, and transition topics. It is a curriculum outline rather than a complete practice rule or authorization. For Uri, translate the relevant topic into current source-specific duties and page-specific evidence instead of treating the outline as a universal checklist.

Keep the current RBT rule boundary visible for Uri

In Uri's supervisory-responsibility transition register, the June 2026 RBT Handbook governs an RBT example only when its relationship and date scope apply. It defines ongoing-supervision structure, percentage, contact, observation, individual or group, organization, record, and retention requirements. It also separates ongoing supervision from professional development so one event cannot cover both. Verify the current handbook and do not generalize its figures to BCaBA, fieldwork, payer, licensure, or employer rules.

Make Uri's supervision communication accessible

For covered title II or title III entities, DOJ effective-communication guidance explains that aids and services depend on the communication's nature, length, complexity, context, and the person's usual method. Apply the actual entity and rule. Agreements, observation explanations, feedback, remediation, complaints, and transitions for Uri should be accessible without treating language or disability needs as poor performance.

Keep AAC available throughout Uri's workflow

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. During Uri's supervisory-responsibility transition register, preserve the client's or supervisee's communication system, backup, vocabulary, positioning, wait time, privacy, and authorship. A supporter can facilitate access while the person retains the ability to ask, decline, pause, correct, report concern, and describe experience.

Protect remote and recorded evidence for Uri

For HIPAA covered entities, HHS audio-only telehealth guidance explains reasonable privacy safeguards and Security Rule risk analysis and management for technologies transmitting ePHI. It identifies recordings and transcripts as risk considerations and distinguishes vendors that act as business associates from mere conduits. For Uri, HIPAA is only one layer; verify consent, recording, employment, licensure, payer, school, state privacy, and contract rules separately.

Choose Uri's next review trigger

Recheck at acceptance, effective date, first contact, first observation, portal update, record reconciliation, temporary-route expiry, unresolved hold, return from leave, or source change. Record what changed, which relationship and source are affected, immediate client protection, the qualified owner, revised capacity or evidence, communication, any hold, and the next validation date.

Close Uri's supervision record carefully

Review the supervisory-responsibility transition register with Uri, the accountable supervisors and clinical leaders, clients and chosen or legally authorized supporters as applicable, and the specialists named in the manifest. Confirm that certification, clinical, payer, licensing, employment, privacy, and record decisions remain separate; every denominator is reproducible; access and safety remain protected; ineligible work stays excluded; and responsibility has an accepted endpoint or transition. Keep this page draft and noindex until every required review is complete.

Related resources

Sources