An ABA scheduling control owner succession plan transfers responsibility when an owner changes roles, takes leave, or leaves the practice. It identifies each control, decision boundary, system, access route, evidence source, open finding, vendor relationship, recurring deadline, backup owner, and acceptance test. The plan preserves accountable scheduling operations without sharing credentials, granting clinical authority through job title, or allowing queues and exceptions to become ownerless.

Inventory owned controls

List schedule release, conflict, capacity, supervision, communication, access, data quality, integrations, vendors, continuity, archives, payroll and billing handoffs, dashboards, procedures, and reviews owned by the departing or unavailable role. Include informal manual checks and spreadsheets. Give each item a stable ID, purpose, system, population, cadence, and consequence.

Separate roles from people

Document business owner, process operator, qualified decision-maker, system administrator, reviewer, backup, and escalation. One person may hold several roles while the duties remain distinct. This makes reassignment possible without giving a successor authority outside licensure, competence, privacy, security, workforce, contract, or payer boundaries.

Map decision boundaries

For each control, record what the owner may decide, what requires clinical or specialist review, what can be delegated, and what must be escalated. Include urgent holds and continuity authority. The successor should understand when to stop and seek a qualified decision rather than treating ownership of the workflow as authority over every case.

Preserve clinical accountability

The BACB Ethics Code supports competence, supervision, continuity, documentation, and qualified clinical accountability for covered people. A succession plan should transfer operational evidence and coordination while assigning clinical duties only to appropriately qualified people under applicable requirements.

Transfer knowledge as evidence

Gather current procedures, source cards, field maps, control definitions, calendars, test results, exception logic, dashboards, known limits, vendor guides, recovery steps, and recent decisions. Label versions and effective dates. Ask the successor to perform representative tasks rather than merely acknowledge documents. Record missing context and update the durable artifact instead of relying on oral history.

Transfer access safely

Inventory applications, roles, groups, service-account relationships, vendor portals, calendars, reports, archives, file shares, support tools, and emergency routes. Grant the successor's own scoped access, test it, then remove the prior owner's access according to the trigger. Avoid shared credentials. Record temporary overlap, approval, expiry, and final revocation.

Classify security scope

Determine entity, data, systems, devices, and vendors. For HIPAA covered entities and business associates, the HHS Security Rule overview frames safeguards for ePHI. Protect handoff exports, credentials metadata, incidents, and client-level queues. Route unexplained or lingering access through security review.

Preserve usable communication

DOJ effective-communication guidance informs suitable aids and services for covered entities. Transfer ownership of interpreter, relay, language, alternate-format, and accessibility escalation workflows. Notify staff, clients, caregivers, and vendors through the appropriate channel when the named contact or response route changes.

Transfer open work

Lock outstanding schedule changes, reconciliation exceptions, failed messages, vendor tickets, access requests, audits, incidents, corrections, and upcoming decisions. Give every row current state, consequence, next action, due date, dependencies, source evidence, and new owner. Keep prior age and history. Avoid closing or recreating work merely to simplify the handoff.

A fictional succession review

Golden Field ABA identifies 36 controls and active workstreams held by one operations lead. Thirty have accepted successors, access, current evidence, and completed task tests. Two vendor routes lack backups, two queues have unclear ownership, one clinical escalation path is outdated, and one old calendar share remains. Readiness is 30 of 36, or 83.3%.

Build the succession register

Use control or work ID, purpose, consequence, former owner, successor, backup, decision boundary, systems, access, sources, procedures, cadence, next deadline, open findings, vendor contact, communication, representative task, test result, former access removal, exception, and acceptance. Link detailed evidence through restricted locations. Keep incomplete rows visible.

Use representative task tests

Have the successor release or hold a fictional visit, review a conflict, find a source version, interpret a dashboard, route a clinical question, contact a vendor, execute a communication fallback, locate recovery instructions, and close a reconciliation case. Define expected evidence and boundaries. Include an unavailable backup and an urgent exception.

Plan leave and sudden departure

Create procedures for planned overlap, extended leave, immediate termination, incapacity, and unreachable contractor. Identify who activates coverage, obtains current work, grants emergency access, contacts vendors, and validates the new owner. Preserve employment and legal decisions with responsible roles. Exercise the sudden path without using another person's credentials or exposing live client data unnecessarily.

Transfer vendor relationships

Record vendor account team, support tier, escalation, active tickets, maintenance, renewals, credentials ownership, data exports, incidents, service levels, and termination obligations. Introduce the successor through approved channels. Verify vendor-side access and contacts change. A name in the internal register does not update a vendor portal or emergency call tree automatically.

Reconcile recurring obligations

Review daily, weekly, monthly, quarterly, annual, release-based, and incident-triggered duties for the next cycle. Confirm calendars, alerts, dashboard subscriptions, queues, and reports reach the successor. Preserve original due dates. Test reminders after the former owner is removed. Assign any unavoidable gap an interim control and expiry.

Close the transition

Require accepted task tests, access confirmation, former access removal, open-work acknowledgment, vendor updates, current procedures, communication, backup coverage, and leadership approval. Record limitations and follow-up dates. Monitor the first operating cycle and sample completed evidence. Reopen the succession item if ownerless work, failed access, or hidden dependencies emerge.

Measure succession readiness

Report controls and workstreams due, successor-assigned, backup-assigned, access-ready, task-tested, open-work transferred, vendor-updated, former-access removed, communication complete, limited, overdue, and accepted. Pair percentages with counts and consequence. Track single-owner dependencies and recurrence. A signed handoff alone does not prove operating continuity.

Monitor the first independent cycle

After formal handoff, observe the successor through the next complete operating cycle without the former owner quietly completing tasks in the background. Sample a routine schedule decision, an exception, a recurring deadline, a vendor interaction, an accessibility route, a control test, and an escalation. Compare the evidence with the documented procedure and decision boundary. Record support requested, missing permissions, hidden contacts, undocumented spreadsheets, unclear ownership, and work that arrived through personal messages. Correct durable systems and procedures instead of creating a new oral dependency on the successor. Leadership should review the cycle, accept any remaining limitation with an owner and expiry, and confirm that the backup can locate the same evidence. The review should also compare planned and actual completion times, confirm that alerts reached both the owner and backup, and inspect whether any decision waited for the former owner. Record the reviewer and review date. When the successor changes a procedure, version the update, explain the reason, test affected controls, and tell downstream users what changed. This step turns succession from a one-day transfer into proof that the control can operate under its new accountable structure.

Related resources

Sources