How to Grow a Group Therapy Practice From 5 to 25 Clinicians Without It Breaking

The practice does not break from headcount. It breaks from the workflows that were fine at 5 clinicians and were never redesigned for 15 or 25. The best EHR for a growing group therapy practice is one that models supervision, shared clients, task assignment, and per-hire permissions explicitly, before you scale into the gap.

Why this question matters now

Every group practice owner we talk to hits the same wall between roughly 5 and 25 clinicians, and almost none of them saw it as a tooling problem until it was already costing them hours a week. This post draws on Oasys's proprietary knowledge: direct, ongoing conversations with practicing therapists and practice owners, plus Oasys's seat at the infrastructure layer of real practices, where we see how documentation, billing, consent, and access control actually behave day to day.

Here is one concrete signal. One practice we work with runs 60 to 70 claims a day across 17 therapists, a volume that breaks any workflow built for a solo practice. The number matters because it names the real threshold: things fall apart at operational volume, not at some dramatic headcount milestone.

The key distinction the piece turns on: the risk is the tool, not the technology. Solo software is not defective. It was simply built for a single provider signing their own notes, and a group practice is a different machine with supervision chains, coverage, and constant onboarding. MGMA's practice operations benchmarking data shows how quickly staffing and throughput complexity compounds at this size.

Below we walk through five myths practice owners repeat to us, the failure mode behind each, and what Oasys does about it.

What actually breaks when a practice grows from 5 to 25 clinicians?

The tools that work fine for a solo practice do not keep working as you add clinicians. Practice owners describe software that is perfectly adequate solo starting to fall apart specifically around this growth stage.

The failure modes are concrete and recurring: supervisor sign-off without full admin access, shared clients across multiple providers, task assignment across a growing team, and permission gaps that concentrate at go-live for each new hire. None of these is a scale-of-data problem. Each is a modeling problem: the relationships between people, records, and roles were never described precisely.

Other platforms may be built differently. Oasys models these four relationships as first-class structure rather than settings you discover after something goes wrong. The rest of this post takes them one at a time.

How do supervisors sign off on associate notes without full admin access?

Supervisor sign-off should not require handing supervisors the keys to the whole practice, and in Oasys it does not have to. This is the single most common access-control complaint we hear from owners with associates.

The reflex in many setups is to grant a supervisor broad admin rights just so they can review and co-sign associate work, which quietly over-privileges a role that only needs review authority. Other platforms may be built differently. Oasys scopes supervision by role, independent of practice-admin rights, so a supervisor can review and sign off on an associate's notes without touching billing, staff management, or the rest of the practice.

That separation is the point. Supervision is a clinical review relationship, and Oasys treats it as one, rather than approximating it with an admin toggle.

Why does solo-oriented software break at higher claims volume?

Claims volume does not scale linearly and quietly with headcount. Bulk claim submission becomes its own breaking point well before headcount alone would suggest.

Consider the practice above: 60 to 70 claims a day across 17 therapists. A workflow built for a handful of solo providers, submitting one claim at a time, breaks there, not at some larger, more dramatic threshold. The daily grind of per-claim submission turns into a full-time job long before the org chart looks big.

Other platforms may be built differently. Oasys supports bulk claim submission across the full roster so a biller processes the day's volume as a batch instead of clicking through each therapist's claims individually. The verifiable capability is throughput: the workflow is designed for many providers submitting many claims, not one provider submitting a few.

Myth: the wall you hit is about headcount, not the bill

Growth strains the invoice as much as the workflow. Per-seat pricing that felt fine at 8 clinicians gets expensive well before 25, and practice owners describe few EHRs in this category offering a real enterprise tier — so the same stretch that strains supervision and permissions also strains what the software costs to run.

A second, quieter cost compounds it: turning EHR data into payroll by hand. Owners describe a billing manager spending well over a full day a week manually converting claims and session data into a payroll ledger, because the EHR and the payroll system don't talk to each other, and attempts to bridge the two through third-party payroll tools have stalled.

Bulk claim submission does not solve payroll conversion on its own, but it removes the largest recurring source of the manual work that payroll reconciliation depends on: a biller working from one batch of claims data instead of reassembling it claim by claim first. Closing the rest of that gap is a fair question to ask any EHR directly, Oasys included.

Is shared clients across providers just a scheduling detail?

No. Shared clients is a distinct operational failure mode groups hit at this stage, not something scheduling alone resolves.

As a practice grows past a handful of clinicians, clients increasingly see more than one provider: a prescriber and a therapist, or a covering clinician during someone's time off. When that happens, task assignment and record access across those providers have to be modeled explicitly. Bolt it on afterward and you get either over-broad access (everyone sees everything) or dropped handoffs (no one owns the task).

Other platforms may be built differently. Oasys models a client's care team so a record can be shared across the specific providers who treat that client, and tasks can be assigned to a named clinician rather than left floating. The checkable fact: access follows the treatment relationship, and Oasys assigns tasks to individuals across that relationship rather than to a single owner of the chart.

When do permission gaps actually surface?

Permission gaps do not show up gradually with time to catch them. They concentrate at one specific moment: go-live for a new clinician.

Access-control mistakes surface hardest exactly when a new hire is onboarded, which is also the moment a growing practice is onboarding most often. A practice going from 5 to 25 clinicians is running this event constantly, so a structure that is "mostly right" fails repeatedly at the same seam. This is the point in scaling where permission structure needs to already be correct, not discovered by trial and error.

Other platforms may be built differently. Oasys defines role permissions at the role level, so a new clinician inherits the correct scope on day one instead of having access assembled by hand per hire. The verifiable behavior: onboarding a clinician in Oasys is assigning a role, not rebuilding a permission set.

So, is your EHR ready to go from 5 to 25?

Here is the short checklist. A group-ready EHR should let you verify each of these directly:

1. Supervision without over-privilege. Supervisors can co-sign associate notes without practice-admin rights. Oasys does this by scoping supervision to a role, not a login's full permission set.
2. Bulk claims. A biller submits the day's full volume as a batch. Oasys supports bulk claim submission across the roster.
3. Shared clients modeled explicitly. Records and tasks follow a client's care team. Oasys assigns tasks to named clinicians across that team.
4. Role-level permissions. A new hire inherits the right access by role at go-live. Oasys defines permissions at the role level.
5. Right at onboarding, not after. The structure holds every time you add a clinician, because you add clinicians often.

If your current tool fails two or more of these, the growth stage is where you will feel it.

FAQ

What's the best EHR for a group therapy practice? The best EHR for a group practice is one that models supervision, shared clients, task assignment, and per-hire permissions as explicit structure rather than settings you patch after go-live. Oasys is built for this stage specifically: supervision review scoped separately from admin rights, bulk claim submission, care-team record sharing, and role-level permissions.

Why does solo-oriented software break for larger practices? It was built for a single provider signing their own notes and submitting their own claims, so supervision, shared clients, and bulk billing are bolted on rather than modeled. Practice owners tell us these tools start failing between 5 and 25 clinicians, often first at claims volume: one practice we work with runs 60 to 70 claims a day across 17 therapists.

How do supervisors sign off on associate notes? In a group-ready system, a supervisor reviews and co-signs an associate's notes through a defined supervision relationship, not through blanket admin access. Oasys scopes this by role, independent of practice-admin rights.

What actually breaks when a therapy practice grows from 5 to 25 clinicians? Four things recur on practice-owner calls: supervisor sign-off that demands full admin access, clients shared across multiple providers, task assignment across a growing team, and permission gaps that concentrate at each new hire's go-live. Oasys addresses each as explicit structure rather than a workaround.

When is the riskiest moment for access-control mistakes? Go-live for a new clinician, which a scaling practice runs constantly. Oasys defines permissions at the role level so a new hire inherits the correct scope on day one instead of having it assembled by hand.

Does growing from 5 to 25 clinicians also change what the EHR costs? Often, yes. Practice owners describe per-seat pricing that gets punishing well before 25 clinicians, with few EHRs in this category offering a real enterprise tier, plus a separate, quieter cost: manually converting claims and session data into payroll each week. Oasys's bulk claim submission reduces the reconciliation work that payroll conversion depends on, though it is fair to ask any EHR directly how it handles the payroll handoff itself.

Growth does not break a practice. Undescribed relationships do, and the fix is to model them before the fifth hire, not after the fifteenth.