ABA Operations Glossary

Route demand before promising service

A referral source records where an inquiry originated. It can help a practice understand communication quality and access, while leaving clinical fit and payer status unresolved.

An intake workflow gathers decision-relevant information and routes a next step. Waitlist management keeps people informed when a suitable next event cannot yet be offered. Define contact attempts, accessibility, voluntary choice, aging, reprioritization, closure, and referral options.

Client onboarding begins after a conditional offer or other defined disposition and prepares the next authorized event. Intake, onboarding, assessment, treatment scheduling, payer authorization, and first service have distinct prerequisites.

The CASP Organizational Guidelines public overview describes business operations, clinical operations, and risk-management scope for autism service organizations. CASP sells the detailed guidelines. This page uses its public framing and presents the workflows as editorial controls.

Define where and how care can operate

A service area is a versioned location set for a specified service, setting, modality, team, and payer or financial path. Marketing reach can be broader than bookable capacity.

A care delivery model describes how services are organized across settings, roles, modalities, schedules, and supports. Community-based ABA takes place in everyday community settings and requires planning for privacy, access, travel, safety, payer rules, and the person's goals.

For covered public accommodations, the DOJ Title III overview addresses equal opportunity, effective communication, reasonable modifications, and physical access subject to the law's standards and defenses. Treat access needs as implementation work, with clinical suitability evaluated separately by a qualified clinician.

Make handoffs and standard work visible

An operational handoff transfers defined responsibility, evidence, deadlines, and unresolved risks between people or teams. A message sent is one event. Receipt, acceptance, clarification, and completion are separate states.

A standard operating procedure describes repeatable work, decision points, roles, evidence, and exceptions. It should identify the current source and version. A procedure cannot grant clinical, legal, privacy, employment, or payer authority that the assigned role lacks.

Suppose a fictional practice reviews 18 intake-to-scheduling handoffs whose due date passed in July. Fifteen contain the required authority, access, payer, clinical-decision, and scheduling fields, so completeness is 15 of 18, or 83.3%. Of those 15, twelve are accepted by the next owner within the target, so timely acceptance is 12 of 15, or 80%. The three incomplete records remain visible with age, reason, owner, and next action.

Respond to incidents and disruption

Incident management receives, triages, responds to, documents, reviews, and closes safety, clinical, privacy, security, workplace, facility, and billing events. One event can require several routes and clocks.

A business continuity plan explains how critical functions will continue or safely pause during disruption and recover in a controlled order. The Ready.gov continuity suite offers general business-impact, recovery, and exercise templates. It is not ABA, HIPAA, clinical, payer, or legal authority.

For a HIPAA covered entity or business associate, HHS risk-analysis guidance requires assessment of potential risks and vulnerabilities to all ePHI the regulated entity creates, receives, maintains, or transmits. New sites, devices, vendors, interfaces, and access routes can change that analysis.

Close services and preserve records

A discharge workflow coordinates a client request, clinical recommendation, payer action, service-end authority, continuity work, and operational closure without treating them as one decision.

A record retention schedule assigns each record type its governing source, retention period, trigger, hold, owner, access, storage, and destruction method. Clinical, payer, corporate, tax, employment, privacy, security, and facility records can follow different rules.

Closure should reconcile future appointments, authorizations, records, claims, payments, property, system access, referrals, incidents, and open tasks. Preserve client access and any required custody or transfer route after the last service date.

Measure each stage on its own terms

Report inquiry response, intake review, conditional offer, onboarding, assessment release, first service, handoff, incident closure, and discharge as separate cohorts. Define the event that starts each clock and the evidence that ends it. Keep pending records visible by count and age.

Pair speed with accuracy, accessibility, family understanding, clinical appropriateness, safety, staff burden, and correction rates. A fast intake can still produce preventable holds downstream. A low open-work count can reflect premature closure unless the final disposition and contact evidence are reviewed.

Build an operations register

For each workflow, record:

• purpose, entry rule, current state, owner, and due date
• governing source, evidence, decision authority, and exception route
• access need, communication channel, privacy classification, and safety route
• numerator, eligible denominator, clock, maturity, exclusions, and open-item aging
• validation, corrective action, effective date, and next review

This register helps an owner see where work waits and which role can resolve it. Software can surface evidence and conflicts. Qualified people still make the clinical, legal, privacy, payer, employment, and safety decisions assigned to their roles.

Start or grow your ABA practice with Finni. Confirm current operational support, product capabilities, implementation duties, security terms, and fit during diligence.