To run ABA group supervision while preserving individual oversight, use the group only for eligible shared learning and verify the governing participant, activity, size, time, and record rules. Protect client confidentiality, AAC, access, and psychological safety. Track each person's attendance and participation. Maintain required individual contact, client-specific observation, feedback, competence decisions, concern routes, and follow-up outside the group when the work or risk is personal.

Define Ravi's exact supervision relationship

Group supervision is a defined learning format. It cannot absorb every individual obligation simply because several people attend the same meeting. 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 Ravi's group-supervision participation and individual-oversight register

Publish the purpose, eligible participants, facilitator, agenda, case-redaction rule, technology, access options, attendance method, participation choices, time allocation, individual follow-up, concern route, and record. Never treat silent attendance as competence or agreement. Avoid discussing identifiable client or personnel details beyond the authorized purpose. If the group identifies a case risk or individual performance need, move that work to the qualified private route while protecting immediate safety.

Protect clients and supervisees in Ravi's workflow

Throughout Ravi's group-supervision participation and individual-oversight 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 Ravi's fictional example

Ravi's organization audits ten group contacts involving its eight-RBT cohort. Nine contacts keep the interactive group within the applicable 2-to-10-RBT limit. At one contact, three RBTs from another team join, bringing the group to 11 RBTs, so that contact is excluded from qualifying RBT group-contact evidence. Across the month, each of the eight audited RBTs also receives an individual contact and a service observation. Two people request private follow-up, and both meetings occur by the agreed date. 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 Ravi's denominator without double counting

Eligible group-contact integrity is nine of ten. Individual-contact completion is eight of eight RBTs, and observation completion is eight of eight. Those figures cannot be pooled because their units differ. The excluded group contact stays in the operational record and is never relabeled as individual supervision.

Connect Ravi's evidence to an accountable decision

The supervisor decides which material is suitable for shared learning. Ravi can participate accessibly and request private discussion. Client-specific and employment decisions move to their accountable owners. The practice protects time for individual oversight before scheduling another group event.

Address Ravi's main interpretation risk

A lively group can mask uneven participation, fear of speaking, confidentiality risk, inaccessible discussion, or missing individual feedback. Review whose cases and questions shape the agenda and who receives follow-up.

Place Ravi's supervision workflow inside an organization

For Ravi's group-supervision participation and individual-oversight 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 Ravi'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. Ravi's employer still needs role-specific policy and current legal, licensing, payer, privacy, and client-care controls.

Identify Ravi'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 Ravi's eligible group learning, individual meetings, service observation, case review, confidentiality, and follow-up.

Use the training curriculum as a design aid for Ravi

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 Ravi, 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 Ravi

In Ravi's group-supervision participation and individual-oversight 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 Ravi'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 Ravi should be accessible without treating language or disability needs as poor performance.

Keep AAC available throughout Ravi's workflow

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. During Ravi's group-supervision participation and individual-oversight 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 Ravi

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 Ravi, HIPAA is only one layer; verify consent, recording, employment, licensure, payer, school, state privacy, and contract rules separately.

Choose Ravi's next review trigger

Reassess after a group-size error, confidentiality concern, access barrier, missed individual contact, missed observation, new participant, remote-platform change, performance concern, or rule update. 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 Ravi's supervision record carefully

Review the group-supervision participation and individual-oversight register with Ravi, 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