What is an ABA practice operating model? An ABA practice operating model defines where recurring work, decisions, evidence, and accountability live across the owner, shared services, clinical leadership, and each service site. A useful model identifies the responsible role, final decision owner, required inputs, backup coverage, escalation route, and proof of completion for every important workflow.

Start with work rather than titles

An operating model is a map of recurring work. Begin with the activities that must happen reliably: referral intake, clinical review, credential verification, authorization tracking, scheduling, supervision, documentation, claims, payroll, incidents, complaints, facility checks, privacy response, and policy maintenance.

For each activity, record six fields:

  1. the person responsible for completing the work
  2. the person accountable for the final decision or result
  3. the source that defines the requirement
  4. the evidence produced when the work is complete
  5. the backup when the primary role is unavailable
  6. the trigger for escalation, pause, or reassignment

The CASP Organizational Guidelines public overview describes guidance spanning business operations, clinical operations, and risk management for autism service organizations. CASP sells the detailed guidelines. The allocation method on this page is an editorial operating framework rather than a CASP requirement.

Separate four layers of accountability

Many practices struggle because enterprise governance, site management, clinical authority, and shared services appear in one undifferentiated chart. Define them separately.

LayerTypical accountabilityBoundary to record
Owner or governing bodyStrategy, resources, risk oversight, leader appointment, and material operating decisionsOwnership does not create clinical competence, licensure, or payer authority
Shared servicesFinance, people operations, compliance coordination, payer operations, technology, and common systemsEach function acts within assigned authority and current source requirements
Site leadershipDaily staffing, facility readiness, local service execution, family communication, and exception routingSite leaders use approved standards and elevate reserved decisions
Clinical leadershipClinical standards, case assignment, supervision quality, escalation, and reviewQualified clinicians retain case-specific clinical judgment within scope

The current BACB Ethics Code applies to BCBA and BCaBA certificants and people who completed an application for either credential. BACB states that it has no separate jurisdiction over organizations or corporations. A practice therefore needs entity-level policy while preserving each covered professional's duties.

Decide which work belongs at the center

Centralization works well when one team can apply a common rule with better expertise, consistency, or control. Common candidates include payroll administration, system access, contract storage, provider-data maintenance, source monitoring, revenue-cycle configuration, and enterprise reporting.

Site ownership works well when local context changes the decision quickly. Daily staffing adjustments, room readiness, local emergency contacts, transportation conditions, and same-day family communication often need a named site owner.

Some workflows use a shared design with local execution. The enterprise team can define an intake checklist while a local coordinator gathers information. A centralized authorization team can maintain payer requirements while the case clinician supplies and approves clinical content. A common incident route can send a report to clinical, safety, privacy, workforce, and insurance owners according to its facts.

Use three questions for every allocation:

  • Does the role have the authority and competence to decide?
  • Can the role see the information needed at the time of decision?
  • Can the practice verify completion and provide backup coverage?

Preserve clinical, payer, and legal boundaries

An operations team may surface missing evidence, a deadline, or a conflict. An appropriately qualified clinician decides whether clinical goals, dosage, procedures, risk controls, or rationale should change. A payer controls its coverage and authorization decision under the applicable product and sources. Legal, privacy, workforce, and accounting questions go to the responsible qualified role.

The HHS OIG General Compliance Program Guidance is voluntary and nonbinding. It offers useful design prompts for leadership, policies, training, reporting, auditing, investigations, corrective action, and adaptations for small entities. Use those prompts to build accountability, then map every actual duty to the source governing the practice.

Build the model from a workflow inventory

Create one row for each recurring workflow and add columns for state, site, payer product, service, setting, role, system, current source, effective date, accountable owner, responsible worker, backup, completion evidence, exception route, and review trigger.

Mark a workflow red when authority, ownership, or evidence is absent. Mark it yellow when the assigned role lacks capacity, backup, or a tested escalation. Green means the source is current, the owner accepts responsibility, the work product is defined, and a recent sample passed review.

The SBA guide to managing a business provides general orientation across finances, employees, taxes, compliance, marketing, and emergencies. It supplies no ABA clinical, payer, or healthcare authority. The practice's register must connect each workflow to current domain-specific sources.

A fictional two-site example

Cedar Point ABA is a fictional practice with two centers and a small home-based program. Its leaders inventory 38 recurring workflows. Twenty-two are assigned to shared services, ten remain site-owned, and six use shared design with local execution.

The first review finds that 30 of 38 rows have a named accountable owner, backup, current source, and completion artifact. Operating-model completeness is 30 of 38, or 78.9%. The eight incomplete rows stay visible. Four concern facility inspections, two concern authorization exceptions, one concerns after-hours family contact, and one concerns access removal after staff separation.

The team assigns owners and due dates instead of averaging the gaps away. It also tests one absence scenario. When the authorization manager is unavailable, the named backup can retrieve the current payer source, identify expiring cases, and route clinical questions without editing clinical content.

Measures that reveal whether the model works

Track counts beside rates and define the cohort before the period begins.

  • ownership completeness: workflows with owner, backup, source, artifact, and escalation divided by workflows in scope
  • exception aging: elapsed time from a defined exception event to disposition
  • rework rate: completed workflows reopened because required evidence or authority was missing divided by completed workflows reviewed
  • backup test success: backup scenarios completed within target divided by backup tests due
  • site variation: local exceptions by type, source, and site, with the underlying counts

Review the model after a new location, state, payer, service, system, role, acquisition, material incident, or source change. A stable organization still needs change-triggered review.

A 30-day build sequence

During week one, inventory recurring workflows and current owners. During week two, separate enterprise, site, shared-service, and clinical decisions. During week three, define artifacts, backups, and escalation thresholds. During week four, test five high-risk workflows using realistic absence, outage, deadline, and conflict scenarios.

Finish with a signed responsibility register and an unresolved-gap list. The model becomes useful when staff can identify who acts, who decides, what evidence is required, and what happens when the ordinary path fails.

Give each unresolved gap a consequence label, interim safeguard, accountable owner, and target date. Review the highest-consequence gaps weekly until the permanent control passes a realistic test.

Related resources

Sources