Multi-Authority ABA Supervision Agreement and Register

To build a multi authority ABA supervision agreement and relationship register, list each supervision purpose, governing source, responsible person, supervisee, client or case scope, start and end dates, required contacts, observation, feedback, records, conflicts, access supports, escalation, and transition. Keep client-care supervision, RBT or BCaBA requirements, fieldwork, competency assessment, training, employment management, payer oversight, and licensure duties as linked relationships with separate evidence.

Define Mina's exact supervision relationship

The agreement explains expectations; the relationship register proves who is responsible for which work under which source at a given time. 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 Mina's multi-authority supervision agreement and relationship register

Create one row per relationship rather than one row per person. Record identity, credential and license, organization, purpose, authority, scope, supervision site, clients, duties, qualifying activities, excluded activities, meeting and observation rules, group limits, feedback method, record owner, signatures or attestations when required, retention, compensation, privacy, conflicts, ending conditions, and replacement. Link rows when the same event may serve several purposes, then verify that every source allows the overlap before counting it twice.

Protect clients and supervisees in Mina's workflow

Throughout Mina's multi-authority supervision agreement and relationship 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 Mina's fictional example

Mina's practice inventories 32 proposed or existing relationship rows. Eleven are RBT ongoing-supervision rows, four are BCaBA ongoing-supervision rows, six are fieldwork relationships, three are competency-assessment roles, four are client-care oversight assignments, and four are employment-management relationships. Seven people appear in more than one row. Five proposed overlaps stay held because the activity, participants, time unit, or record would not satisfy every governing source. 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 Mina's denominator without double counting

Register completeness is 27 complete rows divided by 32 reviewed rows, or 84.4%. Five held rows remain visible. A person count would hide multiple obligations, while an event count could double-count one meeting. Report people, relationships, qualifying events, and records as separate units.

Connect Mina's evidence to an accountable decision

The clinical director owns client-care assignments. BACB-designated roles own certification relationships. Human resources owns employment management. Payer and licensing owners verify their rules. Mina receives a plain-language agreement for each relationship and one consolidated view of contacts, access, concerns, and transitions.

Address Mina's main interpretation risk

One agreement can create false confidence when its clauses come from different rules. A meeting that satisfies an employer expectation may fail a BACB, payer, license, or client-care requirement. Keep each controlling source and decision visible.

Place Mina's supervision workflow inside an organization

For Mina's multi-authority supervision agreement and relationship 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 Mina'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. Mina's employer still needs role-specific policy and current legal, licensing, payer, privacy, and client-care controls.

Identify Mina'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 Mina's client-care, RBT, BCaBA, fieldwork, assessment, training, employment, payer, and licensure relationships.

Use the training curriculum as a design aid for Mina

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

In Mina's multi-authority supervision agreement and relationship 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 Mina'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 Mina should be accessible without treating language or disability needs as poor performance.

Keep AAC available throughout Mina's workflow

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. During Mina's multi-authority supervision agreement and relationship 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 Mina

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

Choose Mina's next review trigger

Reopen after a credential, license, payer, employer, case, service, setting, supervisor, supervisee, workload, record system, access need, conflict, or governing source changes. 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 Mina's supervision record carefully

Review the multi-authority supervision agreement and relationship register with Mina, 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.

Build a Multi-Authority ABA Supervision Agreement and Relationship Register