To audit ABA supervision records across certification payer license and employer rules, define one cohort for each authority and verify relationship identity, source version, dates, eligible time, contacts, observation, individual and group units, goals, feedback, signatures or attestations when required, records, retention, client safeguards, corrections, holds, and reconciliation. Keep missing and ineligible work visible. Never infer one rule's compliance from another rule's record.
Define Vera's exact supervision relationship
The audit asks whether the record proves the exact requirement under the exact source. It does not convert documentation quality into a claim about care quality or competence. 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 Vera's multi-authority supervision-record audit
Create a field-level audit map that names the source, population, unit, clock, expected record, owner, system of record, retention, and exception handling. Lock the cohort before sampling. Trace each summary value back to the original record and each correction through its audit history. Compare unique people, supervisor relationships, organizations, months, service minutes, qualifying contacts, observations, groups, records, and client cases without pooling unlike units. Validate portal status and local records separately.
Protect clients and supervisees in Vera's workflow
Throughout Vera's multi-authority supervision-record audit, 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 Vera's fictional example
Vera audits 40 supervisor-organization-months. Thirty-four have complete relationship, time, contact, observation, and record evidence. Six stay open: two lack a service-observation link, one includes professional-development time as ongoing supervision, one group exceeds the applicable size, one relationship date conflicts across systems, and one correction lacks a preserved original. Five of the six receive documented correction or exclusion before the cutoff; one remains unresolved. 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 Vera's denominator without double counting
Initial complete-month rate is 34 of 40, or 85%. Resolved audit status is 39 of 40 after five repairs, reported as a separate post-correction measure. Record completeness, rule compliance, client-care quality, and supervisee competence remain different conclusions.
Connect Vera's evidence to an accountable decision
The auditor reports evidence and exceptions. Qualified credential, clinical, payer, licensing, employment, privacy, and records owners decide findings within scope. Vera's team corrects the record transparently and protects current clients while any material uncertainty remains.
Address Vera's main interpretation risk
A polished monthly total can hide double counting, ineligible activity, missing observation, unregistered relationships, group errors, or corrections that overwrite history. Audit the definitions and source records behind every total.
Place Vera's supervision workflow inside an organization
For Vera's multi-authority supervision-record audit, 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 Vera'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. Vera's employer still needs role-specific policy and current legal, licensing, payer, privacy, and client-care controls.
Identify Vera'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 Vera's certification, client care, payer, licensure, employer, privacy, and records requirements.
Use the training curriculum as a design aid for Vera
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 Vera, 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 Vera
In Vera's multi-authority supervision-record audit, 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 Vera'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 Vera should be accessible without treating language or disability needs as poor performance.
Keep AAC available throughout Vera's workflow
The ASHA AAC portal says AAC users should always have access to their communication tools or devices. During Vera's multi-authority supervision-record audit, 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 Vera
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 Vera, HIPAA is only one layer; verify consent, recording, employment, licensure, payer, school, state privacy, and contract rules separately.
Choose Vera's next review trigger
Repeat after each monthly or contract cycle, source update, system migration, relationship change, correction, complaint, missed contact, external review, or recurring exception. 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 Vera's supervision record carefully
Review the multi-authority supervision-record audit with Vera, 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
- Build a Multi-Authority ABA Supervision Agreement and Relationship Register
- How to Transfer ABA Supervisory Responsibility Without Losing Continuity
- How to Verify an ABA Supervisor Across Certification, Licensure, Payer, Employer, and Case Rules
- Build an ABA Performance-Remediation Plan That Protects Clients
Sources
- Council of Autism Service Providers, Organizational Guidelines public overview
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts
- Behavior Analyst Certification Board, Supervision, Assessment, Training, and Oversight
- Behavior Analyst Certification Board, Supervisor Training Curriculum Outline (2.0)
- Behavior Analyst Certification Board, RBT Handbook, June 2026
- U.S. Department of Justice, ADA Requirements: Effective Communication
- American Speech-Language-Hearing Association, Augmentative and Alternative Communication
- U.S. Department of Health and Human Services, Guidance on Audio-Only Telehealth and HIPAA