What Breaks at Two Locations — and How to Fix It Before You Sign

The second location rarely fails on demand. The waitlist was real, the referrers asked for it, and the market analysis holds up afterward. What fails is quieter: a front desk that double-books because nobody decided who owns the calendar at site two, an assistant treating across town from a supervisor who was always “down the hall” until suddenly she wasn’t, a clinician covering at the new site who cannot see the chart she needs. None of these is a growth problem. Each is a system that never actually existed — the owner’s physical presence was the system, and presence is the one thing that cannot be in two buildings.

This article is about those systems. It names the three that break first — scheduling authority, supervision coverage, and cross-site chart access — shows what each one looks like when it is quietly held together by proximity, and gives you a sequence to run before the lease starts. The order matters: every one of these is cheap to fix while there is still one building and expensive to fix after families are booked at two. There is also an administrative clock you do not control, because adding a location is a reportable event for Medicare enrollment and usually for your commercial payers too, and those timelines start whether or not your operations are ready.

A single-site practice can operate for years without written rules because the owner is a walking rulebook. Scheduling conflicts get resolved because the owner overhears them. Supervision happens because the supervisor and the assistant share a hallway. Chart questions get answered by turning a screen around. None of this feels like infrastructure, which is exactly why it does not survive the split: the day you open site two, roughly half of every workday’s decisions now happen somewhere the rulebook is not standing.

The failure mode is rarely dramatic. It is a slow accumulation of small inconsistencies — the two front desks develop different cancellation habits, the new site’s clinicians invent their own documentation shortcuts, make-up sessions get promised at one location that the other location’s calendar cannot honor. Each inconsistency is minor; together they produce the thing multi-site owners actually complain about, which is that site two “runs differently” and nobody decided it should. The fix is not more oversight. It is converting the three proximity-dependent systems into written, software-enforced ones before the proximity disappears.

Each row below is the same pattern: a function that looked like a system at one site but was actually a person — usually you — being nearby. The third column is the test to run while everything still works, because a system that only works when you are in the building will tell you so the moment you imagine yourself out of it.

Work the steps in order. The first five cost almost nothing while you still have one building — they are writing-things-down work — and each becomes dramatically harder once two teams have invented their own habits. The administrative steps have external clocks attached, so they are sequenced where those clocks demand it, not where they are convenient.

1. 01

   Write the scheduling authority map at site one

   Before anything else, write down how scheduling actually works today: who may book, move, and cancel appointments; who approves a make-up session and against which rules; what happens when two requests collide; who owns the waitlist. You will discover most of it lives in one or two heads. Converting it to a one-page authority map is the cheapest step in this entire sequence, and every later step depends on it.

2. 02

   Decide what is local and what is central — and name a site lead

   Go through the authority map and mark each decision L or C: local decisions the site lead makes without asking (a same-day room swap, a front-desk coverage gap), central decisions that stay uniform across sites (cancellation policy, fee handling, documentation standards, who gets added to the schedule). Then name the site-two lead and put the map in their hands. A second site without a named decision-maker does not escalate less — it escalates everything, to you, at both sites.

3. 03

   Consolidate both sites onto one scheduling system with location-aware views

   Two calendars is how double-bookings become structural. Both sites belong in one system where every appointment carries a location, every clinician’s view spans both sites, and the front desk at either site can see — but not necessarily edit — the other’s calendar according to the authority map. Test the cross-site cases deliberately: a clinician who splits the week, a family that attends whichever site has the earlier opening, a make-up offered at the other location.

4. 04

   Redesign supervision as scheduled, documented contact

   List every supervisee — assistants, clinical fellows, new graduates — and write a supervision plan per person that would hold up with the supervisor across town: how often direct observation happens and where, how indirect contact is delivered and logged, and who covers questions when the named supervisor is at the other site. Build each plan against your state practice act and your payers’ conditions for billing assistant-delivered services, because those two rulebooks differ and the stricter one governs. The compliance section below covers where the rules actually live.

5. 05

   Set chart access by role and relationship, not by building

   Define access in terms that survive the split: treating clinicians see their caseload wherever it is scheduled, covering clinicians get access through the coverage assignment, supervisors see their supervisees’ documentation, and front-desk roles see scheduling and demographics without clinical notes beyond what their job requires. HIPAA’s minimum necessary standard expects exactly this — access matched to role — and the move to two sites is when “everyone sees everything” stops being a shortcut and starts being a finding.

6. 06

   Start the enrollment and credentialing clocks deliberately

   Adding a practice location is a reportable event, not an FYI. For Medicare, practice location additions must be reported to your Medicare contractor within 30 days under 42 CFR §424.516(d). Commercial payers and state Medicaid programs set their own notice and credentialing requirements per location, and some will not pay for services at an address they have not enrolled. Sequence this against your opening date — the payers’ clocks, not the landlord’s, decide when site two can actually bill.

7. 07

   Pilot the split while you can still fix it cheaply

   For two weeks before opening, operate as if you were already at two sites: the owner works deliberately offsite on set days, the site lead runs the authority map without appeal, supervision happens only through the scheduled plan, and coverage is requested through the new access process. Every failure this surfaces — and it will surface several — is a failure you get to fix without families booked at the second address.

8. 08

   Set the first-90-days review cadence before opening

   Put three reviews on the calendar now: at two weeks, at six weeks, and at ninety days. At each one, review the same short list — scheduling conflicts and how they were resolved, supervision logs against each plan, access requests and whether the roles held, and anything site two invented that site one does not do. The goal is not zero drift; it is deciding on purpose which site-two inventions become practice-wide standards and which get rolled back.

The operational work above is on your schedule; the administrative work is not. Medicare treats a practice location as part of your enrollment record, and the regulation is specific: under 42 CFR §424.516(d), physicians, nonphysician practitioners, and their organizations must report a change, addition, or deletion of a practice location to their Medicare contractor within 30 days, while most other enrollment changes get 90. Build the enrollment update into the opening plan itself — alongside the lease and the buildout — rather than treating it as a post-opening errand.

Commercial payers and state Medicaid programs each handle new locations their own way: some extend your existing contract to the new address on notice, others require credentialing or a contract amendment per location, and their timelines range from days to months. The only safe generalization is that none of them move on your opening date. Ask every payer you bill, in writing and early, what it requires for a second location and how long it takes — and ask your state licensing boards and registration authorities the same question, because facility-level registration requirements vary by state and by discipline. The expensive version of this lesson is a fully staffed site delivering sessions a payer will not pay for at that address.

Supervision is where a second location most often turns an informal habit into a compliance question, because the rules are written in terms — direct, general, on-site, immediately available — that suddenly matter when the supervisor is across town. For Medicare, the ground shifted recently in your favor: in the CY 2025 Physician Fee Schedule final rule, CMS moved supervision of physical therapist assistants and occupational therapy assistants in private practice from direct supervision, which required the therapist to be physically on site, to general supervision, effective January 1, 2025. Under general supervision the service is furnished under the therapist’s overall direction and control without requiring their physical presence — which is precisely the flexibility a two-site practice needs.

That change does not end the analysis, for two reasons. First, Medicare’s rule does not override your state practice act: where a state still requires on-site or direct supervision of assistants, the stricter state rule governs, so the two-site supervision plan has to be built state-first. Second, for speech-language pathology the picture is more state-driven still — SLPA supervision requirements, including how much contact is required and how much must be direct, are set state by state and can differ substantially from ASHA’s own guidance. ASHA, AOTA, and APTA each maintain current state-by-state requirements; treat those pages and your state board’s rules as the authority, and write each supervisee’s plan against them by name.

Cross-site chart access fails in two opposite directions, and both are avoidable with the same design. The first failure is the locked-out covering clinician: a therapist picks up a session at the other site and cannot see the plan of care, so the session runs on a verbal handoff and memory. The second is the overcorrection: to make sure that never happens, every account is granted access to every chart, and the practice quietly abandons any relationship between role and access. HIPAA’s minimum necessary standard points at the middle path — covered entities are expected to identify who in the workforce needs access to protected health information, which categories they need for their duties, and to limit access accordingly. Role-based access is not an enterprise luxury; it is the written expectation, and it scales to two sites better than either failure mode.

In practice, the design is relational: access attaches to the treating relationship, the coverage assignment, and the supervision relationship, wherever those happen to be scheduled. When a clinician is assigned to cover at site two, the coverage assignment carries chart access for those patients for that period; when the assignment ends, so does the access. Front-desk roles at both sites see schedules, demographics, and balances without open-ended clinical access. Review the grants on the same first-90-days cadence as everything else — access lists only ever grow unless someone owns shrinking them.

The readiness test for a second location is not a revenue threshold; it is a dependence test. If the practice runs for two consecutive weeks with the owner deliberately absent — decisions made by the authority map and the site lead, supervision happening on the documented schedule, access requests resolved by role — then the systems exist, and a second site is an expansion. If those two weeks produce a queue of texts to the owner, the systems do not exist yet, and a second site would simply split the queue across two buildings. “Not yet” is a cheap answer before the lease and an expensive one after it; the sequence above is how a motivated practice converts not-yet into ready in a quarter rather than discovering it in month two.