How should multi-site ABA practice operations work? A multi-site ABA operating system defines the standards shared across locations, the decisions retained locally, the evidence required before each site operates, and the route for exceptions. Strong multi-site ABA practice operations give every location clear accountability while preserving clinical judgment, local legal and payer requirements, workforce context, facility conditions, and client access needs.
Create a common core and local overlay
The enterprise common core contains requirements and methods intended to apply across the organization. A local overlay records jurisdiction, payer, facility, workforce, emergency, transportation, language, access, and market differences for one site or service area.
Common-core candidates include document control, data definitions, decision logging, incident intake, access provisioning, vendor review, financial reconciliation, and enterprise reporting. Local overlays may govern building approvals, emergency contacts, labor rules, service settings, payer configurations, local resources, staffing patterns, and site schedules.
The CASP Organizational Guidelines public overview describes guidance across business, clinical, and risk-management areas. Detailed guidance is sold. The common-core and local-overlay structure is an editorial operating model.
Assign enterprise and site decision rights
| Decision | Enterprise role | Site role | Required evidence |
|---|---|---|---|
| Open or materially change a site | Approves investment and release framework | Verifies local readiness and conditions | Current authority, facility, staffing, payer, safety, and access gates |
| Adopt a common workflow | Owns design, controls, system configuration, and training | Tests local fit and executes approved process | Versioned procedure, test results, exceptions, and effective date |
| Schedule daily services | Defines scheduling rules and capacity controls | Assigns local resources within cleared parameters | Staff, setting, client, authorization, and clinical readiness evidence |
| Respond to a site interruption | Maintains continuity framework and escalation | Activates local plan and reports status | Client and staff accounting, safe-stop decision, communication, recovery evidence |
| Change clinical content | Provides governance and qualified review structure | Case clinician makes case-specific decisions within scope | Current assessment, data, client involvement, and required approvals |
The current BACB Ethics Code applies to covered certificants and applicants. It addresses competence, resources, client involvement, assessment, intervention, supervision, documentation, and evaluation. BACB has no separate organization or corporate jurisdiction. Enterprise standards should support professional duties without predetermining individual clinical conclusions.
Use a site release gate
Before a new site markets or schedules a service, verify the requirements that actually apply:
- entity, professional, facility, zoning, occupancy, fire, accessibility, and local authority
- service model, population, setting, modality, and hours
- payer participation, provider and location records, authorization routes, and billing configuration
- qualified staff, supervision, onboarding, payroll, workers' compensation, and training
- clinical leadership, case assignment, safety information, communication access, and consultation
- privacy and security risk analysis, devices, networks, access, vendors, and downtime route where applicable
- insurance territory and conditions
- emergency contacts, evacuation, continuity, incident, complaint, and record procedures
Record the source, owner, evidence, effective period, exception route, and recheck trigger. An enterprise approval cannot substitute for local authority.
Standardize data definitions before comparing sites
Define a referral, assessment release, active client, scheduled hour, rendered hour, cancellation, open authorization issue, vacancy, incident, complaint, claim, and payment once. Record local source mappings and known differences.
A site with a different payer mix, service setting, travel pattern, client population, maturity, or staffing model can produce different results without weaker execution. Compare rates with counts, denominators, cohorts, and context.
The HHS OIG General Compliance Program Guidance is voluntary and nonbinding. Its guidance on leadership, risk assessment, auditing, reporting, corrective action, and board or owner oversight can help a multi-site organization create a common review structure. Actual duties remain source-specific.
Design shared services with local service levels
For each shared function, define what the site submits, what the central team returns, response targets, acceptance criteria, escalation, coverage, and reconciliation. Common shared services include provider data, authorization operations, billing, payroll, technology, compliance coordination, recruiting, purchasing, and reporting.
Track both directions. A central team cannot meet a target when site inputs arrive incomplete, and a site cannot act when central work lacks a clear status. Report sender readiness, receiver acceptance, hold reasons, and original-cohort completion.
Give site leaders a clear operating charter
A site leader needs authority to manage daily staffing, facility readiness, local vendors within limits, family communication, ordinary schedule exceptions, and escalation. The charter should list reserved enterprise and clinical decisions, spending limits, emergency authority, required records, meeting cadence, and measures.
OSHA's management leadership guidance recommends goals, resources, management visibility, and accountability within a safety and health program. It is general guidance. Multi-site owners can apply the principle by giving local safety responsibilities adequate authority and resources while verifying federal or state-plan requirements.
A fictional three-site comparison
Summit Bridge ABA is a fictional three-site practice. It defines 20 site-release controls. Site A clears 20, Site B clears 18, and Site C clears 15. The organization reports 20 of 20, 18 of 20, and 15 of 20 separately.
Site C has two open facility controls, one untested downtime route, one payer-location mismatch, and one vacant backup role. Leaders hold the affected service release and assign owners. They avoid averaging the sites into 53 of 60 because the site-specific stop conditions matter.
During the next month, shared authorization services receive 48 site submissions. Forty-one meet sender criteria, and 37 are accepted on first review. Sender readiness is 41 of 48, or 85.4%. Receiver acceptance is 37 of 41, or 90.2%. Original-cohort first acceptance is 37 of 48, or 77.1%.
Measure enterprise and local performance
Track site-release controls complete, common workflows operating on the current version, local overlays reviewed by target, shared-service sender readiness, receiver acceptance, open exceptions by age, unresolved high-consequence issues, and corrective actions that pass effectiveness tests.
Review variation for learning. A site with a useful local method can propose a common-core change through change control. A local exception should carry an owner, reason, safeguards, expiration, and review.
Maintain a site-specific source register for every location. The register should name the current board, agency, payer, contractor, facility, labor, privacy, insurance, and emergency sources that affect the site. Multi-site ABA practice operations become unreliable when a central procedure silently assumes that one state's or payer's rule applies everywhere. Review the register before copying a workflow to another location. Record which common-core steps remain valid, which need a local overlay, and which require qualified review before service release. Index the framework under the terms staff actually use for sites, locations, shared services, and local operations so they can find it when work changes.
Scale in controlled stages
Before adding another site, test whether the enterprise can support the current locations. Review clinical leadership capacity, shared-service backlogs, source freshness, financial runway, vendor limits, data quality, emergency coverage, and leadership succession.
Open the site in stages when appropriate: authority and facility readiness, staff onboarding, limited service release, evidence review, then broader capacity. Record each gate and stop condition. A target opening date should never override a missing authority or safety control.
Related resources
- ABA Practice Change Control: Approving and Rolling Out Operational Changes
- ABA Practice Policy Library: Structure, Ownership and Review
- ABA Practice Operating Model: Centralized vs Site-Level Responsibilities
- ABA Practice Handoff Design: Intake, Clinical, Authorization and Billing
