Owner
Roster, coverage, throughput, revenue follow-up, and compliance dates are visible from one practice view.
For group & enterprise practices
One system for the whole practice, with each role seeing its own work.
Owners, supervisors, billers, and clinicians work from the same record. Everyone sees what their job needs and nothing it does not.
Team operations · role-aware access · supervision · revenue follow-through
Practice operationsWhole team
One practiceshared thread
Whole rosteroperational view
Role scopedclinical access
OwnerRoster, coverage, throughput, compliance datesPractice view
SupervisorAssigned reviews, co-signs, supervision evidenceReview queue
BillingClaims, remittances, denials, authorization follow-upRevenue queue
ClinicianCaseload, documentation, client follow-throughOwn work
Group and enterprise operations are part of the product hierarchy.PeopleRoster, roles, supervisionWorkCoverage, queues, ownershipPracticeRevenue and compliance oversight
The practice command center
What the owner opens on a Monday.
A group practice does not fail on documentation speed. It fails on the things nobody owns: supervision hours nobody is counting, co-signatures nobody is chasing, licensure deadlines nobody is watching, and revenue nobody is following. These are the surfaces that hold them.
Attention required4 clinicians · 2 states
Roster
- Clinician AClinical Supervisor · MNUp to date
- Clinician BAssociate · MNSupervision overdue
- Clinician CAssociate · WIOn track
- Clinician DClinician · MNUp to date
Caseload and productivity
- Clients
- 38
- Sessions
- 104
- Cancel rate
- 6%
- Missing notes
- 3
- Awaiting co-sign
- 2
- Upcoming
- 27
Supervision
- Recorded hours
- 112
- Logged sessions
- 46
- Awaiting co-sign
- 2
- Window status
- Open
Licensure and CE
- Total hours
- 612
- State requirements
- MN · WI
- Verified
- 4 of 5
- Attention required
- The owner view opens on what is outstanding rather than on a dashboard of totals: missing notes, overdue supervision, unworked claims. It says all clear when there is nothing.
- Caseload and productivity
- Clients, sessions, cancellation rate, missing notes, co-signatures owed, upcoming appointments and revenue, per clinician and across the roster.
- Supervision and co-signature
- Recorded hours, logged supervision sessions, what is awaiting a co-signature and whether the supervision window is open.
- Licensure, hours and CE
- Hours logged against the requirement for each state and credential, with the client and setting recorded and verification tracked toward the application.
- Roster, roles and access
- Organization, clinical supervisor, associate and staff roles, who is assigned to whom, and clinicians who have been offboarded.
- Multi-state and payer mix
- Where the roster is licensed to practise, and where the money is coming from across payment sources.
Every capability above ships today and is included in the practice plan rather than sold as a separate module. Group and enterprise pricing is scoped to the roster, supervision model, migration and security needs, so it is agreed with the practice rather than published here.
The same practice, seen from the right vantage point.
The platform keeps one operational thread while preserving the role boundaries a group practice depends on.
Supervisor
Co-sign queues, supervisee work, and supervision evidence are available without a practice-wide clinical view.
Biller & staff
Claims, remittances, denials, authorizations, and follow-up stay visible without opening clinical access unnecessarily.
Clinician
Session preparation, documentation, client activity, and assigned follow-through stay focused on their own work.
Team operations scale by responsibility, not by another disconnected tool.
Adding a clinician should not mean rebuilding the same workflow in another system. Shared records give each role the context it needs and keep access scoped to the work it owns.
| Practice work | Primary vantage | How the shared system holds it |
|---|---|---|
| Clinical caseload | Clinician | Preparation, documentation, and assigned follow-through stay with own work. |
| Supervision | Supervisor | Assignments, co-sign requirements, review queues, and evidenced hours stay connected. |
| Revenue follow-up | Billing & owner | Claims, remittances, denials, and authorization work remain visible across the roster. |
| Coverage | Practice operations | Handoffs, tasks, reminders, and the next responsible person stay attached. |
| Access | Assigned role | Each person works from shared records with access limited by their role. |
| Practice oversight | Owner | Roster, throughput, compliance dates, and operational health share one practice view. |
Built to scale the practice, not the overhead.
Adding a clinician should not mean rebuilding the same workflow in another tool. Shared systems give each role the context it needs and keep access scoped to the work it owns.
Role-aware team operations
Owners, supervisors, clinicians, billers, and practice staff work from shared records with access limited by their assigned role.
Supervision and co-sign workflow
Supervision assignments, review queues, co-sign requirements, and evidenced hours stay connected instead of living in separate trackers.
Practice-wide revenue workflow
Claims, remittances, denials, prior authorization work, and follow-up are visible across the roster without opening clinical access unnecessarily.
Coverage and follow-through
Handoffs, tasks, reminders, and operational coordination stay attached to the client and the people responsible for the next step.
Operational clarity
Shared context. Scoped access.
The owner sees operational health
Roster, coverage, revenue follow-up, throughput, and compliance dates.
The supervisor sees assigned review work
Supervisee work, co-sign queues, and supervision evidence.
The biller sees revenue workflow
Insurance follow-up without unnecessary clinical access.
The clinician sees their own caseload
Clinical work and assigned follow-through stay focused.
Plan the right setup for your group.
Group and enterprise arrangements depend on roster size, roles, supervision structure, and migration needs. The demo is where those requirements are mapped.