The second branch is where every therapy center owner discovers how fragile their first branch's workflows were. What ran on messages and memory now needs structure. This playbook covers the four operational systems that make a 2β5 branch therapy center sustainable: shared scheduling, per-branch finance, cross-branch supervision, and role-based access.
Shared scheduling without double-bookings
A therapist who works at two branches needs one calendar, not two. If branch A books her at 4 PM and branch B books her at 4 PM, nobody wins. BloomTalkx models this with TherapistClinic β a therapist's availability is per-branch, but her bookings are global, so a slot taken at one branch disappears from the other.
Per-branch finance that owners can trust
- Revenue by branch, by therapist, by discipline β same report, three slices
- Hospital cut per therapist (configurable per link) β and per-patient override when the deal is non-standard
- Discounts and custom charges reflected in effective revenue, not list price
- Receptionist cash collection reconciled against appointment bills
Supervision across branches: therapist-wise vs client-wise
Two valid supervision models exist and most owners pick the wrong one. Therapist-wise supervision assigns each therapist a supervisor who reviews all of that therapist's clients. Client-wise supervision assigns each client (usually a child in ABA) a supervising clinician who oversees them across every therapist who works with them. BloomTalkx lets you pick at onboarding and switch if your model matures.
Role-based access β the escalation you did not plan for
A single-branch clinic can run on three roles (owner, therapist, receptionist). A multi-branch center cannot. You need a hospital owner with full control, delegated managers with scoped permissions (finance only, HR only, roster only), and staff grants that let a receptionist book without seeing your P&L. BloomTalkx ships this out of the box via per-permission grants with a default-deny policy.
The HR / payroll question
At two branches you probably still run payroll in a spreadsheet. At three branches that spreadsheet becomes a liability. Centralise attendance, leave, employee documents and payroll β the local tax and EOBI calculations should run per branch but roll up to one dashboard for the owner.
Scaling to a third branch β the checklist
- Document three SOPs in writing: client intake, cash collection, cancellation policy
- Appoint one manager per branch with a bounded permission grant
- Weekly 30-minute cross-branch finance review (owner + managers)
- One monthly supervision audit per discipline (not per therapist)
- Backup day: once a month, export your data and store it somewhere not in the EHR
Frequently asked questions
- Can I run multiple clinics on one BloomTalkx account?
- Yes. The data model is multi-branch from day one β you create hospitals, link therapists to each, and route finance per branch.
- How do I stop a branch manager from seeing another branch's data?
- Delegated managers are scoped to their branch via req.actingHospitalId. The default policy is deny; you grant one permission at a time.
- What about franchise models?
- The same multi-branch architecture supports franchise setups where each branch keeps its own books but owners see a consolidated roll-up.
Scale your clinic without scaling the chaos
BloomTalkx is built for 1 to 20 branches on the same account.
Book a scaling session