Multi-site practice

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Define what counts as a site

A site may be a center, office, home-services hub, school-services team, telehealth operation, or another location recognized by law, contract, payer, or internal governance. One street address can contain several entities or payer configurations. One team can operate across several addresses.

Maintain a site master with entity, tax identity, NPI where applicable, licenses, facility approvals, services, hours, payers, providers, systems, clinical leader, emergency routes, and effective dates. Avoid using a marketing location list as the operational source.

Split central and local decision rights

Central teams may own finance, technology, privacy, compliance, contracting, recruiting, and standard policies. Local leaders may own staffing, facility readiness, schedules, emergency execution, and implementation. Qualified clinicians retain case-specific clinical judgment.

A decision matrix should name who recommends, approves, performs, reviews, and stops each action. Ownership alone does not grant professional competence or clinical authority. For covered individuals, the BACB Ethics Code addresses competence, resources, supervision, client involvement, documentation, and continuity; BACB has no separate jurisdiction over organizations or corporations.

Payer readiness is site specific

A group contract or organization enrollment may still require location, rendering-provider, roster, service, taxonomy, and electronic setup. Record each payer, product, entity, provider, location, service, modality, code, and effective date.

The CMS Medicare enrollment page treats practice locations and ownership as reportable enrollment information under Medicare rules. Other payers and states use their own requirements. Never infer a new site’s billing readiness from an existing site’s remittance.

Central staffing can hide local gaps

Count unique workers by site, role, shift, credential, payer eligibility, and supervision. Shared clinicians, float staff, and remote supervisors can appear in several plans while having one calendar.

Include travel, documentation, training, meetings, leave, cancellations, and emergency coverage. A weekly capacity number should stop at the tightest clinical, staff, room, payer, and schedule gate.

Define backup plans for leadership absence, technology outage, severe weather, and sudden staffing loss. A backup name is useful only when authority, competence, availability, and access are current.

Standardize controls while preserving local facts

Common templates can improve consistency, yet each site needs local emergency numbers, licensing sources, payer manuals, facility procedures, access supports, labor rules, and referral pathways. Record approved local variations instead of forcing them into an inaccurate corporate template.

When a policy changes, test implementation at every affected site. Track training completion, access to the current version, scenario results, and overdue corrective actions.

Centralization also creates concentration risk. One payroll vendor, clinical platform, billing queue, or clinical leader can affect every location at once. Maintain tested fallbacks, escalation owners, and workload limits for shared services. Site leaders need enough local authority to protect safety while centralized support is unavailable.

Review concentration by function, site, shift, and qualified role.

Reassess it after every acquisition, opening, closure, or leadership change.

Extend privacy and security across the footprint

For HIPAA covered entities and business associates, HHS risk-analysis guidance covers all ePHI created, received, maintained, or transmitted. New sites add networks, rooms, printers, devices, vendors, and workforce access.

Test identity, role-based access, secure storage, downtime, restoration, device disposal, incident routing, and offboarding. Central systems do not remove physical-site risk.

Compare mature site cohorts

Same-store comparisons should define which sites are old enough to enter the cohort, when they enter, and what happens after relocation, acquisition, closure, or major service change. Keep new sites separate from mature sites.

Pair revenue and utilization with client access, family choice, staff turnover, supervision, incidents, denials, refunds, documentation, and clinical outcomes. A site can grow financially while quality or workforce stability declines.

A fictional site-month review

Harbor Learning has three sites across nine months, producing 27 site-months. Four site-months lack a complete staffing and payer-release record. Site-month readiness is 23 of 27, or 85.2%.

The four misses remain in the denominator and receive owners and due dates. Harbor reports capacity, starts, cancellations, documentation, incidents, and collections only for their defined cohorts; it avoids calling an unverified site-month “zero.”

One center’s referral growth exceeds qualified capacity. The practice pauses new start promises there while adding supervision and access supports. Other sites continue under their own gates.

Use growth guidance as orientation

The SBA growth guide can help frame locations, funding, and operations. It does not establish healthcare licensure, clinical governance, payer readiness, or facility compliance.

End each site review with location-specific actions: release or hold a service configuration, repair staffing or supervision, correct a payer route, improve access, or escalate a shared-service constraint. Preserve site-level denominators and owners so a strong network average never conceals one unsafe or unauthorized operation.