Category guide
ABA practice management software
An ABA practice management system is the clinical and financial spine of a clinic: data collection, programme authoring, scheduling, notes, claims. CentralReach, Rethink, Motivity, Theralytics and Lumary all sit in this category, they all sign business associate agreements, and for the work they cover they are not optional.
This page is what the modules actually are, how to evaluate them without being shown a demo instead, and the one job every system in the category leaves to somebody else. We build a tool for that job, so read the last section knowing that.
What is actually in one.
Vendors package these differently and price them separately more often than the marketing suggests. Establish which of the eight you are buying.
Clinical data collection
Trial-by-trial and duration data captured in session, usually on a tablet, against targets defined in the treatment plan. Graphs and phase-change lines for the supervising analyst. This is the module a technician spends the most time in and the one worth testing hardest in a trial.
Programme and treatment plan authoring
Where targets, mastery criteria and behaviour plans are written and revised, and where the library of programmes lives so a new client does not start from a blank page.
Scheduling
Matching technicians to clients across a week, with authorisation limits, credential requirements and drive time. This is the module that decides whether the clinic runs, and it is where a bad system costs a scheduler ten hours a week.
Session notes and documentation
Structured note capture tied to the appointment and the data, so the note the funder eventually reads reconciles with the units billed. Usually with signature capture and same-day entry enforcement.
Billing and revenue cycle
Claim generation from delivered sessions, authorisation tracking, clearinghouse submission, denials and remittance. For most organisations this is the module that justifies the price of the whole system.
Credentialing, HR and payroll feeds
Certification expiry, supervision hour tracking, and the export that gets technicians paid for what they actually delivered rather than what was scheduled.
Reporting
Utilisation against authorisation, cancellation rates, billable hours per technician, clinical progress across a caseload. What a director looks at on Monday.
Caregiver portal
A place a parent can log in to see documents, sign things, and sometimes review progress. Present in most systems, and the module with the lowest actual usage in almost every clinic that has one.
How to evaluate one without being sold to.
Every system in this category demos well. These are the six exercises that distinguish them, and they are all things a vendor can do live if the answer is good.
Time the data collection flow with a stopwatch, on a technician.
Not on a director in a demo. The difference between four taps and nine, multiplied by a hundred trials a session and thirty staff, is the whole difference between a system that gets used as designed and one where data gets written on paper and entered at 5pm. Ask to run a real session on it during a trial.
Ask what happens with no signal.
Sessions happen in homes, in cars, in schools with hostile wifi. A system that loses a session’s data on a dropped connection will be worked around within a week, and the workaround is paper.
Make them reschedule a week in front of you.
Take a real scenario: a technician calls in sick on Tuesday, four clients across two sites, two of them with authorisation limits about to be breached. How many screens does that take? This is the task the system is actually used for most, and it is the one demos are structured to avoid.
Get the BAA before the trial, not after it.
A trial with real clients in it is a disclosure of PHI. The serious vendors in this category state plainly that they act as business associates and will produce the agreement without a fuss; treat any hesitation as information.
Establish who owns the data and how it leaves.
Ask for the export format, and ask specifically whether raw trial-level data comes out or only summary reports. A migration where you can take graphs but not the underlying data is not a migration.
Cost it per location and per user, at next year’s headcount.
Per-seat pricing in a category with high technician turnover behaves differently from how it looks in a quote. Ask what happens to the price when you add a site, and whether the implementation fee recurs.
A note on “ABA schedules”.
This phrase means two unrelated things and both are searched. One is staff and client scheduling, which is a module of the systems above rather than a product most clinics buy separately — a schedule disconnected from authorisations and billing creates as much work as it saves. The other is schedules of reinforcement: the rule determining which instances of a behaviour produce reinforcement, fixed or variable, ratio or interval. That one is clinical, and it is defined in the ABA glossary.
The job the whole category leaves out.
Not a defect. Nobody built a practice management system to solve this, and it is a different product with a different primary user.
A portal is pull. A parent needs push.
Every system in this category has somewhere a parent could log in. Almost nobody logs in. A parent does not want a destination to visit; they want to know at 2pm that the transition after lunch went badly, because the alternative is finding out at pick-up or not at all. Those are different products, not different amounts of the same product.
The person with the information is the least senior person in the building.
Practice management systems are architected around the analyst and the biller. The technician is a data-entry endpoint. But the technician is the only person who knows how the afternoon went, and any parent-communication design that routes through a BCBA writing a summary later will produce a summary later.
The clinical record and the parent update have different readers.
A session note is written for a supervisor, a colleague and an auditor, in the technical vocabulary, because those readers need it. It is not what you hand a family. Deriving the second from the first is the right architecture; expecting the first to serve as the second is why parent communication quietly stops happening.
So the channel reappears on personal phones.
Not through negligence. A parent asks a technician a question at pick-up, the technician gives out their number because the alternative is being unhelpful to a worried family, and eighteen months later a third of the caseload is being managed through threads no supervisor has ever seen. The system did not fail; it never covered this.
The diagnostic question, if you want to know whether this applies to you: how many families are currently reaching a member of your staff on that person’s own phone number? The answer is almost always higher than leadership estimates, and the number is what makes the case internally.
Where Cliqit sits, stated plainly.
Cliqit is not a practice management system, an EMR or a billing product. It does not collect trial data, schedule anybody or produce a claim. If you are shortlisting systems to run your clinic on, we are not on the list and should not be.
It runs alongside whichever one you choose, and it does the parent- and team-facing half: staff tap an update, the family gets it immediately, the next technician sees the same log, and the end-of-day summary writes itself from what was already recorded. How that works next to an existing system is set out in parent communication alongside your practice management system.
Questions clinics ask about this.
What is ABA practice management software?
A single system covering the operational and clinical administration of an ABA clinic: capturing session data against treatment targets, authoring programmes and behaviour plans, scheduling technicians against authorisations, producing session notes, generating claims and tracking the revenue cycle, and reporting on utilisation and progress. CentralReach, Rethink, Motivity, Theralytics, Lumary and CodeMetro are among the systems in the category.
What is the best ABA practice management software?
There is no honest single answer, and anybody offering one is selling something. The choice turns mainly on size and on which module hurts most: a two-site clinic with clean billing and a scheduling nightmare should choose differently from a twelve-site organisation with a denials problem. The evaluation that predicts satisfaction is timing the data collection flow with an actual technician and rescheduling a real week in the demo.
Do these systems sign a BAA?
The established vendors in the category do, and say so publicly. CentralReach describes complying with collective responsibilities under HIPAA; Motivity incorporates a HIPAA business associate agreement into its terms of service; Theralytics states it operates as a HIPAA business associate and executes BAAs as required. This is the meaningful difference between this category and the school communication apps clinics sometimes end up using instead.
Is Cliqit an ABA practice management system?
No, and it is not trying to become one. Cliqit does not collect trial data, does not schedule, does not bill and does not write your session notes. It does one job — getting what happened during the day to the parent, and to the next technician — and it runs alongside whichever system you already use. If you are looking to replace CentralReach, we are the wrong product.
What does ABA software cost?
Practice management systems in this category are typically priced per user per month with an implementation fee, and the total for a multi-site organisation runs into thousands a month. That is not a criticism — revenue cycle management is worth real money. It does mean the marginal cost of adding a specialist tool for one job should be judged on its own terms; Cliqit is $299 per location per month with unlimited staff, parents and children.
What about ABA scheduling software specifically?
Scheduling is a module of every system in the category rather than a product most clinics buy separately, because a schedule that is not connected to authorisations and to billing creates as much work as it saves. If you are searching for "ABA schedules" and you meant fixed and variable ratio and interval schedules of reinforcement, that is the clinical term and it is defined in the ABA glossary.
Can we run parent communication out of our practice management system?
You can send documents and messages through the caregiver portal, and for signatures and treatment plans that is exactly where it belongs. What does not work is daily communication, for a structural reason rather than a quality one: a portal requires the parent to come and look, and a system built around the analyst and the biller is not a tool a technician opens in the ten seconds between transitions.
Do we need a separate tool for multiple locations?
Not a separate practice management system — running two is worse than running one imperfect one. What does tend to fragment across sites is exactly the layer the system does not cover: each location independently picks its own way of talking to parents, for the same good reason, and a growing organisation ends up with four different answers to the same question.
Related
Sources
Every claim about another product on this page is a quote from that product’s own documentation, linked below with the date we last read it there. Vendors revise these pages. If you find one of these out of date, tell us and we will correct it.
- [1] CentralReach — Security · checked August 26, 2026
- [2] Motivity — HIPAA Business Associate Agreement · checked August 26, 2026
- [3] Theralytics — Security · checked August 26, 2026
Keep the system you have.
Fifteen minutes on the one gap it leaves. If your practice management system already covers daily parent communication for your caseload, we will tell you to skip us.