Managing Multi-Location ABA Centers Without Spreadsheet Chaos

The second location is where ABA operations break. With one site, a shared spreadsheet, a group text, and a good office manager can hold intake together. Open a second site and the spreadsheet forks. Each location develops its own tab, its own column names, its own idea of what "pending documents" means. By location three, the regional director spends Monday mornings reconciling numbers that were never collected the same way.

Multi-location ABA management is not a scaled-up version of single-site management. It requires a different structure: one organization, many locations, shared definitions, scoped access, and reporting that rolls up automatically. This guide describes that structure and how TargetFlo's platform implements it.

What is multi-location ABA management?

Multi-location ABA management is the set of practices and systems that let an ABA organization operate several therapy sites as one business — consistent intake process, shared clinical and compliance standards, centralized visibility — while giving each location ownership of its own referrals, staff, and families. The defining tension is standardization versus local autonomy. Spreadsheets fail because they force you to pick one: either every site edits one master file, or every site keeps its own.

Six ways spreadsheets fail at the second location

Each of these is a structural property of spreadsheets, not a training issue. The fix is a system built around one organization with location as a first-class attribute.

Principle 1: Define once, operate locally

Intake stages, stage checklists, closure reasons, consent templates, SOPs, and training courses should be authored once at the organization level. Every location then works from the same definitions. This is what makes "cards in Pending Authorization" a meaningful number across sites.

Local operation means each location has its own queue. The North site's intake coordinator opens the intake pipeline and sees North's referrals — the same nine stages as every other site, but only their cards. Local ownership stays intact; the definitions do not drift.

Principle 2: Scope access by role and location

A single-site spreadsheet has one permission model: everyone with the link sees everything. Across locations, that is a HIPAA problem. A front-office coordinator at one site has no need to see the guardian phone numbers of families at another.

Role-based access with location scope solves this cleanly:

• Site coordinator: full access to their location's referrals, clients, tasks, and fax queue
• Site clinical lead: their location's clients plus clinical documents
• Regional director: several locations, with roll-up reporting
• Organization admin: every location, plus templates, courses, and user management

TargetFlo's multi-tenant, multi-location architecture assigns each user one or more locations and a role; the interface shows only what that combination allows. The security overview explains how location scope fits into the platform's four-schema design.

Principle 3: Move referrals between locations without losing them

Families relocate. A site reaches capacity and refers to a sister location. A specific clinician is only available at one site. Transfers between locations are routine in a multi-site organization and are exactly where referrals vanish in spreadsheet operations — deleted from one tab, never pasted into the other.

A transfer should be a single action on the referral card: change the location, assign a new owner at the receiving site, and keep the full history — faxes, eligibility results, documents, notes — attached. The card's timeline should show the transfer as an event, so the receiving coordinator understands where the family has been.

Principle 4: Run one fax intake, route by location

Multi-location centers often have a fax number per site, each landing in a different inbox managed by a different person. Referral sources do not respect those boundaries; a pediatrician faxes whichever number is in their file.

A single fax inbox with location routing is more resilient. Inbound documents from any number land in one triage queue, OCR extracts the referral details, and the triager links the document to a client and assigns a location. Nothing depends on which fax line a referral source happened to use. Details on how the fax inbox handles this are in Fax-to-Intake Automation: A Complete Guide for ABA Operations.

Principle 5: Roll up staffing and compliance, not just intake

Intake is the most visible multi-location problem but not the only one. Training completion, SOP acknowledgments, and consent versions must be consistent across sites, and staff frequently work at more than one location.

Keep the employee directory at the organization level with location assignments, so a BT who covers two sites appears once, with one training history. Assign courses and policies by role, and report completion by location. A regional director should be able to see that one site is behind on the incident-reporting SOP without asking three location managers to check.

Principle 6: Give the regional director a dashboard, not a Monday morning

The weekly reconciliation ritual disappears when every location records the same events in the same system. Dashboard KPIs — referrals per stage per location, average stage age, eligibility verification rate, overdue tasks, fax queue depth — are computed from the operating data rather than assembled by hand.

The valuable view is the comparison: which site converts referrals fastest, which has the longest Pending Documents queue, which has the most overdue follow-ups. Those comparisons drive staffing and process decisions, and they are only possible when definitions are shared. The full KPI list is in 10 Dashboard KPIs Every ABA Operations Leader Should Track.

What to do before you open the next site

1. Write down your intake stages and what "done" means at each. Make that the organization standard.
2. Consolidate consent, SOP, and intake packet templates into single versioned masters.
3. Decide role and location scopes for every job title.
4. Route all fax lines into one triage queue with location assignment.
5. Move the existing site onto the system before the new site opens, so the second location starts on the standard rather than inheriting a spreadsheet.

Opening a location is a growth milestone. It should not double your reconciliation work. One organization, many locations, shared definitions, scoped access — that is the structure that lets ABA centers grow without spreadsheet chaos, and it is the structure TargetFlo is built on.