Here’s a scene that plays out in more ABA clinics than anyone admits. The office manager has three tabs open: the schedule, a spreadsheet of authorizations, and the billing portal. A BCBA pings her to ask whether a client still has hours left this month. She squints at the spreadsheet, says “I think so,” and hopes for the best. That “I think so” is the real cost of running a clinic on patched-together tools. An ABA practice management system exists to replace it with an actual answer.
Plainly, it’s the software your clinic runs on. Not the app where techs tap through trials (that’s data collection), and not a generic medical records system, though some products mash all three together and call the result an “all-in-one.” The practice management part is the back office. Who’s scheduled where. Which payer approved how many hours. Whether Tuesday’s session turns into a clean claim or a denial three weeks from now.
Why spell this out? Because vendors use the labels loosely, and you can end up buying a great data collection tool when your real problem is billing. Ignore the label. Ask what the thing does with an authorization, a supervision hour and a claim, and notice how long the salesperson takes to answer.
Nothing’s wrong with spreadsheets. They carry plenty of small clinics for a long time. The trouble is that ABA piles on unusual demands. Sessions last hours, not minutes. Technicians deliver most of them. A payer has to approve each hour in advance, and the code on the claim has to match the credential of the person who actually showed up. Layer on supervision rules and staff driving between living rooms and school hallways, and a basic calendar starts to wobble.
Vendors who sell ABA software say generic medical and therapy tools often lack unit tracking by CPT code and authorization setups built for ABA. They would say that, sure. So test it yourself. Can your current setup tell you, this minute, how many authorized units one child has left and who’s allowed to bill them? If getting that answer means asking three people, you know where you stand.
Other signs are less subtle. Two people book the same RBT. An authorization expires and nobody notices until the sessions are done. Billing sits waiting for notes that clinicians finish on weekends. Staff keep private spreadsheets “just in case.” One or two of these is normal growing pain. Four or five means the setup is costing real money, and probably a few good employees too.
I’d test these first, and I’d test them together, because in ABA they’re really one problem. The schedule has to respect the authorization, and everything else leans on that. A good system keeps approved hours by code, counts units as sessions happen, and warns you well before a limit or end date shows up. The better ones flag a session that would push a client over the line before it’s booked, not after it’s billed. Some platforms now add AI-assisted scheduling that spots conflicts across locations, providers and authorization limits. Lovely, as long as someone set the rules up properly. Feed it sloppy data and you’ll just get confident nonsense. Our post on ABA prior authorization covers why this part deserves so much attention.
Notes are where clinicians lose their evenings, so this is where a system either wins people over or doesn’t. The tech collects data on a phone or tablet (some products work offline and sync later), and the system turns it into a draft note. AI-assisted drafts are all over the category now. Fine, but read every line before signing. The clinician who signs is vouching for that note, and it doubles as a billing document. Our guide to ABA session notes goes through what a solid note contains.
Once a note is signed, the claim should build itself: code, units, modifiers, rendering provider, no retyping. What separates good from mediocre is the checking that happens before submission. Is the authorization active? Does the code match the staff credential? Is the note signed? Also ask what happens after a denial, and whether the system talks to a clearinghouse or expects you to bring your own. The ABA billing codes guide covers the codes those checks lean on.
RBT certifications renew every year. BCBAs have continuing education cycles of their own. A credential tracker feels boring right up until it stops you from scheduling someone whose certification lapsed last week. Dashboards matter too, but only the ones people actually use: hours delivered against hours authorized, cancellation rates, days in accounts receivable, denial reasons, caseload per BCBA. If pulling a report means an export and an afternoon in Excel, nobody will run it.
Then there’s security, and this one isn’t optional. You’re holding health data about children. Look for role-based permissions (technicians don’t need billing screens), audit logs, encrypted storage and a signed business associate agreement. Some vendors publish independent audit results like SOC 2 reports, so ask for them. And if you serve Medicaid clients at home, ask about electronic visit verification, since some states require it for in-home services.
Parent portals, mobile apps, AI dashboards, e-signature intake forms. All useful, none of them the reason to buy. Unless one happens to be your biggest daily headache, don’t pay extra for a wall of features. A smaller system your staff actually opens every morning beats a giant one half of them avoid.
Walk a single session through a decent system and the pieces make more sense. Say an RBT finishes a three-hour home session on a Wednesday afternoon. She taps through her data on a tablet, adds a couple of quick notes about how the child handled a new goal, and closes the visit. Behind the scenes the system checks the visit against the schedule, confirms the client still has units left under the right code, drafts the note from her data and drops it into a queue. The BCBA reads the draft that evening, fixes one sentence and signs. The claim builds itself. Nothing was retyped. Nobody had to email anybody.
Now picture the same session with five separate tools. Same three hours of work, but she writes the note by hand that night, someone copies the hours into a spreadsheet on Friday, and the claim gets keyed in the following week. Every handoff is a chance for a typo, a missed unit or a note that never gets signed. Small stuff. Multiply it by every session, every week, every client, and you can see why so many clinics feel buried.
Start with your own mess. Write down the five things that cost you the most time or money every month. Late claims, expired authorizations, double bookings, notes still being typed at 9 p.m. That list is your shopping list. Ask each vendor to show how their system handles every item, live, not in slides.
Then throw some real-life curveballs at them. What happens when a session runs past the authorized units? What does a BCBA see on Monday morning? How does a denial get from the payer back to someone who can fix it? What does adding a learner or a location cost, and how do I get my data out if I leave?
Pricing swings a lot. One 2026 industry roundup lists a vendor at $24 per learner per month for practice management alone, with all-in-one plans costing more, while other vendors only do custom quotes. Contracts often run 12 months. Read the term before signing anything.
If you’d like a side-by-side look, our breakdown of practice management software for ABA therapists walks through the options. And for the daily habits that make any tool work, see our guide to ABA therapy practice management.
Most failed rollouts aren’t software failures. Someone imported dirty data. Staff got a one-hour training and a pat on the back. Nobody was in charge. So pick an owner. Clean your client and authorization data before it moves. Run the old and new setups side by side for a few weeks if the budget allows. Bring BCBAs and office staff on first, technicians after the basics settle. And expect the first billing cycle to be messy, because it usually is. Watch claims closely, fix patterns fast, and keep the vendor’s support team on speed dial.
The ABA Coding Coalition says the AMA CPT Editorial Panel approved major changes to the ABA code set. Six new CPT codes are coming, some existing ones are being revised, and the Category III codes 0362T and 0373T are being retired. It all takes effect January 1, 2027, with the final wording in the 2027 CPT code book due late in 2026.
Ask every vendor how they’re handling it. Is there a published plan? Will code tables update on their own? Will the system support old and new codes during the switch? A vague answer tells you plenty.
No system fixes a clinic by itself. The right one is whichever handles your messiest problems and gets opened by your team every day. Start from the problem, test it live, and stay a little suspicious of any demo that goes too smoothly.
Think of it as the back office of an ABA clinic, built into one program: scheduling, authorization tracking, notes, billing, staff credentials and reports. Plenty of platforms also include data collection, so the clinical and admin sides share a single record.
The short list: ABA-aware scheduling, authorization tracking by code, notes connected to session data, billing with checks before submission, credential alerts, reporting and HIPAA-level security. AI notes, parent portals and electronic visit verification are bonuses that depend on your payers and your state.
A general EHR stores clinical records for any specialty. ABA software adds what ABA clinics lean on daily: unit tracking by CPT code, technician and BCBA supervision rules, session data collection and ABA billing workflows. Some ABA vendors claim general EHRs miss these, so check any tool against your own workflow rather than taking their word for it.
Many do now, and several vendors launched or expanded them in 2026. The tool drafts a note from session data and quick notes, then the clinician reviews, edits and signs. Ask how review and attestation work, because the person signing owns what the note says.
It varies with the vendor, the modules and your size. One 2026 roundup lists $24 per learner per month for practice management alone, with all-in-one plans costing more, and some vendors only quote custom prices. Contracts are often 12 months. Ask for a quote based on your real caseload, and ask what setup, training and support cost on top.
Picture a Tuesday at a mid-sized ABA clinic. A child is approved for 25 hours a week and has used 11 of them. One RBT just texted that she’s sick. And the billing person is staring at a denied claim nobody can explain. None of this is unusual. It’s simply what ABA therapy practice management looks like when the system behind the scenes is a pile of spreadsheets and good intentions.
Most of the pain comes from four spots. Scheduling. Billing. Authorizations. Staffing. They’re tangled together, which is the annoying part. A scheduling slip means a missed session, a missed session means unused hours, and unused hours are money (and therapy time) you don’t get back.
Compare ABA to a physical therapy clinic. A PT sees someone for 45 minutes, writes a note and bills a code. Done. ABA sessions can run three or four hours, often in a family’s living room or a school hallway, and most of that time is delivered by a technician who didn’t write the treatment plan. A BCBA has to oversee that tech. The payer has to approve the hours first. And the code you bill has to match who actually did the work.
One mismatch, and the claim can fall apart.
Demand isn’t making it easier. The CDC now reports that roughly 1 in 31 eight-year-olds has been identified with autism, and waitlists in plenty of areas stretch for months. More families, same small office team.
Here’s where a lot of clinics go wrong. They build the schedule around who’s free. Then at the end of the month somebody notices that a client with 25 approved hours only received 17.
Flip it. Start with what each child is approved for and work backward. If the number is 25, you’re aiming for 25, and you already know some of those hours will get cancelled, so you plan for that too.
Supervision is the thing that gets squeezed. The BACB asks for supervision of at least 5 percent of the hours an RBT spends providing ABA services. For someone working 30 hours, that’s 1.5 hours a week with a BCBA. Put it on the calendar before anything else goes in, because if you leave it for “later,” it tends to never happen.
Travel time is another sneaky one. A home-based RBT can’t finish at 2:00 in one town and start at 2:00 in the next. Everyone knows that, and it still ends up on the schedule. It also helps to keep a short list of clients who’d happily take extra hours. When a family cancels at the last minute, you have someone to call instead of an empty slot.
I like a Monday check. Open every client, compare last week’s delivered hours to the authorized hours, and call anyone who’s falling behind that same morning. It doesn’t take long. Waiting until month end takes a lot longer to fix.
Telehealth can cover some gaps, mostly parent training and certain BCBA protocol work. Industry sources say CMS has extended telehealth coverage for ABA through at least December 2026. Still, every payer has its own view, so check before you move a session online.
ABA runs on a small set of CPT codes. 97151 is the behavior identification assessment. 97153 is direct treatment by a technician following the protocol. 97155 is treatment with protocol modification, which a BCBA or similar professional does. 97156 is family guidance. MeasurePM’s ABA billing software applies the right code from the session note, so nobody has to pick from this list by hand.
When claims get denied, the reason is rarely exotic. Usually the code doesn’t fit the credential of whoever delivered the session. Or the units went past the authorization. Or the authorization ran out last Thursday. Or the note is thin. Those are process problems, not coding mysteries, and process problems can be fixed. Our guide to ABA denial management goes deeper on why claims bounce and how to prevent it.
Watch for overlap, too. Vermont Medicaid changed its ABA billing policy effective January 1, 2026, and one target was billing 97153 and 97155 for the same child in the same hour, which the state treats as billing twice for the same time. Other payers keep an eye out for it. So when a BCBA jumps into an RBT’s session, split the time and write it down properly.
Small habits make the biggest difference here. Read the note before the claim goes out, not after it comes back. Bill within a few days of the session, since old claims are harder to fix and easier to lose. And once a month, sort your denials by reason. You’ll usually find one or two causes behind most of them, and the fix is often a single training session.
Almost every payer wants prior authorization for ABA before services start. The approval spells out the hours, the codes and the dates. Step outside any of those and you’re risking a denial. In an audit, a payer can ask for money back on claims it already paid. MeasurePM’s ABA scheduling software ties the schedule to authorization tracking, so units don’t quietly run out.
Four things to track for every client: start and end dates, approved units per code, units used so far, and the date the reauthorization request is due. A spreadsheet can do it. But only if somebody updates it every single week, and that “if” is where plenty of clinics get burned.
Reauthorizations deserve a head start. Ask each payer how long reviews take, then add a cushion. I’d start at 60 days out, earlier for slow plans. Lead with progress data when you submit. Graphs and goal updates usually help a reviewer see that the hours you’re asking for match what the child needs.
The rules shift constantly, too. Ambetter announced prior authorization changes for several ABA codes, including 97152, that took effect August 1, 2026. Indiana Medicaid began phasing in lower maximum rates and ran a transition window from April through September 2026 for members age 21 and older. Nobody holds all of that in their head. A one-page cheat sheet per payer (authorization rules, unit caps, modifiers, who to call) saves a lot of guessing.
Staffing is the part of ABA practice management that feels most personal, because it is. The BACB lists 246,109 active RBTs as of January 1, 2026, and clinics still can’t keep enough of them. Turnover numbers swing depending on who you ask. One figure often cited is roughly one in three RBTs leaving the field each year, and some industry surveys report higher. Pick whichever you like. It’s expensive either way. Some estimates put the cost of replacing a single therapist between $15,000 and $25,000 once hiring, training and lost productivity are counted.
Kids feel it too. A child gets used to a specific RBT, and when that person leaves, progress can slow while a new bond forms.
So what actually helps? A real onboarding plan, for one. Two weeks of structured, closely supervised work beats a day of shadowing and a full caseload. Supervision matters too, but the kind that teaches. Logged hours satisfy a rule. Watching, modeling and feedback are what make someone want to stay. Keep caseloads sane, because burnout often starts with one client too many. And show people a path. An RBT who can see a route to BCBA, maybe with help on supervision hours or exam prep, has a reason to hang around.
Credentials need their own tracking. RBTs renew every year and complete a competency assessment as part of it, and BCBAs have continuing education cycles tied to their own certification dates. Put every expiry date in one place and set a reminder 60 days ahead. A lapsed credential can cause billing and compliance trouble that takes weeks to untangle.
Spreadsheets are fine for the first handful of clients. The cracks show when the same information lives in the schedule, the authorization tracker, the session notes and the billing file, and nobody’s sure which copy is right. Double bookings, missed expiry dates and slow billing are the usual signs.
Good practice management software for ABA therapists keeps all of that in one record. The features worth caring about are the ABA-specific ones: alerts when units run low, a check that the code matches the staff member’s credential, and reminders before a certification expires. Our post on what an ABA practice management system includes lists the rest.
One warning. Software won’t fix a weak process. If nobody owns authorizations today, a new tool will just show you the gaps faster. Decide who owns each area first.
The ABA Coding Coalition announced that the AMA CPT Editorial Panel approved major changes to the ABA code set. Six new CPT codes are coming, some existing codes are being revised, and the Category III codes 0362T and 0373T are being retired. It all takes effect January 1, 2027, and the final wording will appear in the 2027 CPT code book, due late in 2026.
Before January, ask your billing team or software vendor how they’re handling the switch. Once the final code descriptions are out, retrain whoever submits claims. And check each payer’s guidance, because payers don’t always move on the same date as the AMA.
You don’t have to rebuild everything at once. Pick what hurts most. Claims bouncing? Go through last month’s denials. Hours slipping? Try the Monday check. Techs leaving? Ask a few of them what would make their week easier, then actually do something about the answer. For more quick wins, see our list of ABA clinic efficiency tools.
Good ABA therapy practice management is mostly a handful of plain habits repeated every week. Clinics that keep them rarely end up in crisis mode.
Six new codes join the adaptive behavior services set on January 1, 2027, according to the ABA Coding Coalition. Some current codes are being revised, and the Category III codes 0362T and 0373T are going away. The full descriptions are scheduled to appear in the 2027 CPT code book, published late in 2026, so check the book and your payers’ guidance before you update billing.
Track approved units by code, compare them to units used every week, and set an alert for when a client has burned through most of their hours. Then start the reauthorization about 60 days before the end date, with current progress data attached.
RBTs can’t work independently. They need ongoing supervision from a BCBA or BCaBA, and the BACB baseline is at least 5 percent of the hours they spend providing ABA services. Some payers and states ask for more. The BACB also updated its RBT requirements in 2026, so check the current handbook and your plan contracts.
Industry sources say CMS has extended telehealth coverage for ABA through at least December 2026. Commercial plans and state Medicaid programs make their own rules, though. Confirm each payer’s policy and which codes they allow by video. Codes often used for telehealth include 97155, 97156 and 97157.
When the manual system starts costing you more than software would. Double bookings, missed authorization dates, late claims and staff keeping their own private copies of the same data are the usual signs. Look for ABA-specific features like unit tracking and credential checks.
Picture this. You are shopping for software to run your ABA clinic. A vendor walks you through a clean demo of a Behavioral Health EHR. Client records, progress notes, e-signatures, billing. Everything looks tidy. Then your clinical director asks a simple question: where do the RBTs enter session data?
The room gets quiet.
That one question is why so many ABA owners end up with the wrong tool. A behavioral health EHR and ABA practice management software sound alike, but they were built for different jobs. One is designed around a therapist’s office. The other is designed around how ABA actually runs day to day, with technicians, supervisors, authorizations, and a lot of data.
This guide explains what each type of software does, where they overlap, and how to figure out what your clinic needs. No jargon, and no pressure to buy anything. Just a clear way to think it through.
Most ABA clinics need software built around ABA workflows first. A general behavioral health EHR can hold records and notes, but it often struggles with session data, program graphs, and unit-based authorizations. If your clinic also offers other services, such as counseling or psychiatry, you may want an EHR too. The two can sit side by side.
A behavioral health EHR is an electronic health record system made for mental and behavioral health providers. Think therapists, counselors, psychiatrists, and substance use programs. It keeps the clinical record in one place and handles the paperwork around each visit.
For a solo therapist or a counseling group, that is often plenty. Visits are regular, notes are mostly text, and billing follows a simple pattern: one session, one code, one claim.
ABA works differently. One client might receive 20 or 30 hours of therapy a week, delivered by several technicians who each run different programs. That changes what the software has to do.
A general EHR can store a note about all of that. It usually cannot capture the data itself, graph it, or connect it to billing. That gap is where clinics start to feel the pain.
ABA practice management software is built around how an ABA clinic runs. It brings the clinical side (data and programs) together with the business side (schedules, authorizations, and billing). The goal is simple: session data, schedules, and claims should talk to each other instead of living in three separate tools.
A solid ABA platform usually covers these areas:
Look at that list again. Most of it is not a note. It is data that has to move from one place to another without someone retyping it.
| Area | Behavioral health EHR | ABA practice management software |
|---|---|---|
| Built for | Therapy, counseling, and psychiatry | ABA clinics and their teams |
| Session data | Written notes | Real-time data on programs and behaviors |
| Graphs | Rarely built in | A core feature |
| Scheduling | Appointments with one provider | Staff and client schedules across many technicians |
| Authorizations | Basic or manual | Tracked by code and units |
| Billing | Session-based claims | Unit-based claims tied to sessions and authorizations |
| Typical user | Clinician | RBT, BCBA, scheduler, biller, and owner |
Every product is different, so treat this table as a general pattern, not a rule.
This is the biggest gap. In ABA, the data is the treatment record. A BCBA looks at trends across weeks to decide whether a skill is moving or a behavior is dropping. If RBTs jot numbers on paper and someone types them in later, you lose time and accuracy.
ABA data collection software lets technicians enter data during the session and watch graphs update on their own. MeasurePM, for example, offers real-time analytics and customizable graphs across mobile and web.
A therapy office books one client with one provider. An ABA clinic books a learner with an RBT, adds a BCBA for supervision, and then juggles cancellations, travel, and coverage when someone calls out sick. Scheduling that understands those layers saves hours every week.
That is the idea behind ABA scheduling software: staff and client schedules in one place, so a scheduled session can flow straight into data collection and billing.
ABA is billed in units, usually 15 minutes each, under codes like 97151 for assessment, 97153 for technician-delivered therapy, 97155 for protocol modification with a BCBA, and 97156 for family guidance. Payors approve a set number of units per code. When the units run out, claims get denied.
That is why billing tools built for ABA matter. ABA billing software ties claims to completed sessions and approved units, which cuts down on errors before a claim ever goes out. MeasurePM lists automated insurance checks and precise coding as part of its billing tools.
RBTs need ongoing supervision under BACB rules, and many payors add their own requirements on top. Someone has to track it. The same goes for progress reports. If you build them from scattered notes every time a reauthorization comes up, you will lose a lot of hours. Software that already holds the data can turn it into a report in a few clicks.
Not always. It depends on what your clinic does.
If you do run two systems, ask one question before you sign: will anyone have to enter the same information twice? If yes, keep looking.
A feature list will not tell you much. Real questions will. Bring these to every demo:
One more tip. Ask the vendor to walk through your workflow, not their script. Give them a real day: a few learners, two RBTs, one BCBA, one claim. The demo gets honest fast.
MeasurePM is an all-in-one, HIPAA-compliant ABA platform. It combines data collection, scheduling, and billing, and adds a live KPI dashboard for tracking how the practice is doing. Its tools were designed with BCBAs in mind, and more than 10,000 providers use it, including about 750 BCBAs. MeasurePM also says it delivers a billing collection rate in the high 90s.
It is not the right fit for every clinic, and the best way to find out is to test it. Try it with a real session, a real schedule, and a real claim before you decide.
Sometimes, but usually not on its own. A general EHR can hold records and notes and send basic claims. It often does not collect session data, build graphs, or track authorizations by unit. A small clinic can patch those gaps with spreadsheets, but that gets messy as you add clients and staff.
An EHR centers on the clinical record for therapy-style visits. ABA practice management software centers on how ABA works: session data, programs, technician schedules, authorizations, and unit-based billing. Think of one as a record keeper and the other as the operating system for your clinic.
Yes. Clinics that offer other services often keep an EHR for the wider client record and use ABA software for daily ABA work. The key is integration, so data does not need to be entered twice. Ask every vendor which systems they connect with.
Yes, if your clinic handles protected health information, and most ABA practices do. Session data, diagnoses, and insurance details all count. Ask vendors how they store and protect data, and who can see it. MeasurePM describes itself as a HIPAA-compliant platform.
Watch for the warning signs. RBTs still use paper data sheets. Someone retypes data into another system. Authorizations run out without warning. Claims get denied over unit problems. BCBAs spend hours building progress reports. If two or three of those sound familiar, it is probably time.
A behavioral health EHR is a good tool for the job it was built for. ABA is a different job. Your clinic runs on session data, technician schedules, and unit-based billing, so your software should be built around those things first.
If you want to see how that looks in practice, you can book a free demo and walk through your own workflow.
Ask any ABA clinic owner where the week goes, and you will hear the same answers. Fixing the schedule. Chasing session data. Retyping notes. Hunting for the reason a claim was denied. None of it is clinical work, yet all of it has to get done.
The right ABA clinic efficiency tools will not remove that work overnight. But they can shrink it, sometimes by a lot. The trick is knowing which tool targets which time sink, so you do not buy software that looks great in a demo and changes nothing on a Tuesday afternoon.
This guide walks through nine tools that cut admin time in an ABA clinic. For each one, you will see what problem it solves and what to look for. Where we mention MeasurePM, we are describing what the company lists on its own website, and we will say so.
Before you pick any tool, it helps to name the problem. In most ABA clinics, admin time leaks out in a few predictable places:
Notice the pattern. Most of these come down to the same information being handled twice. Good tools remove the second handling.
| Tool | Time sink it targets |
|---|---|
| Drag-and-drop calendar | Manual schedule changes |
| Credential and authorization checks | Booking mistakes and rework |
| Mobile data collection | Retyping paper data |
| Live graphs | Hand-built charts |
| Draft session notes | End-of-day documentation |
| Automatic claim creation | Manual claim entry |
| Authorization-linked billing | Denials from authorization gaps |
| Built-in progress reports | Building reports from scattered notes |
| KPI dashboard | Finding problems too late |
A shared calendar sounds basic, but plenty of clinics still run on spreadsheets. When a technician calls out, someone has to find coverage, update the sheet, and tell everyone. A drag-and-drop calendar turns that into a few clicks, and a clear day and week view shows who is where.
If you run more than one location, look for a single view across all of them. MeasurePM’s ABA scheduling software lists drag-and-drop scheduling for staff and clients, plus multi-location support.
The most expensive scheduling mistakes are the ones you find later. A session booked with the wrong staff member, or beyond what a client is authorized for, means rework and sometimes a denied claim. Look for a tool that checks these things at the moment of booking.
According to its website, MeasurePM checks staff credentials before a session is booked and builds schedules with client authorizations in mind. It also says scheduling time drops by up to 50 percent. That is the company’s own figure, so treat it as a starting point and test it in your own clinic.
Paper data sheets are cheap, but they create a second job. Someone has to turn them into usable data. Entering data on a phone or tablet during the session removes that step.
ABA data collection software from MeasurePM lets RBTs and BCBAs enter data on any device, and the company lists real-time analytics and customizable graphs across mobile and web. When you test any tool, ask an RBT to run a real session on it. If it slows them down, they will find workarounds, and your data will suffer.
BCBAs need to see trends to decide whether a program is working. If graphs are built by hand, they get built late or not at all. Tools that update graphs as data comes in give a BCBA a current picture whenever they open a client.
That means fewer hours spent making charts and more spent making decisions. Customizable graphs matter here, because no two BCBAs look at data the same way.
Notes written from memory at the end of the day are slow and less accurate. A better setup uses the data you already collected as a starting point. MeasurePM lists AI-assisted SOAP notes as part of its platform.
If you try something like this, treat the draft as a draft. A BCBA or RBT should still read it, edit it, and sign off, because the clinical record is their responsibility.
Manual claim entry is one of the most repetitive jobs in a clinic. When claim creation is tied to completed sessions, most of the typing goes away. MeasurePM’s ABA billing software is described this way: claims generate and submit automatically once a session is complete.
Your billing team still reviews the exceptions. The difference is that they spend their time on problems instead of data entry.
ABA authorizations are approved in units, and units run out. When billing is connected to scheduling, each claim can be traced back to a session that was actually authorized. MeasurePM says its billing works this way, and that denials are tracked and managed in the same system that sends the claims.
Fewer surprises at the end of the month means fewer hours spent on appeals and rework.
Progress reports and reauthorization packets can eat a whole afternoon when the data lives in five places. When session data sits in one system, reports can be pulled straight from it. MeasurePM lists a Clinical Reporting feature for this.
Even if you choose a different platform, ask to see a real report generated from sample data. A screenshot tells you very little.
You cannot fix what you cannot see. A KPI dashboard puts numbers like utilization, revenue, and claims performance in one place, so you catch issues early instead of at month end. MeasurePM’s website describes a KPI dashboard with visibility into exactly those areas.
Decide ahead of time which two or three numbers you will check each week. A dashboard nobody opens saves no time at all.
Buying software is easy. Buying the right software takes a little more thought. Keep these points in mind:
Price matters, but it is rarely the whole story. A cheap tool that adds two hours of retyping a week is not really cheap.
Even good tools can disappoint. These are the usual reasons:
Software vendors love big numbers, and you should be careful with all of them, including ours. Here is a simple way to find your own.
Before you switch, pick three tasks, such as making schedule changes, entering session data, and creating claims. Ask the people who do them to log their time for two weeks. After the switch, repeat the exercise and compare.
It is not fancy. But it gives you a number you can trust, and it shows which tool earned its fee.
A quick example makes the point. Say your billing team spends part of every week typing claims by hand. If claim creation starts on its own after each completed session, that time does not vanish, but it moves. Instead of typing, your team reviews the few claims that were flagged. That is a better use of a skilled person’s day, and it is exactly the kind of change worth measuring.
MeasurePM is an all-in-one, HIPAA-compliant ABA platform that combines data collection, scheduling, and billing, with a live KPI dashboard and integrations. The company says more than 10,000 providers use it, including about 750 BCBAs. Every feature described in this guide comes from the company’s own website.
It will not suit every clinic, so test it with your own workflow before you decide. For a wider look at what is out there, our guide to the best ABA practice management software covers the options.
They are software tools and systems that reduce admin work in an ABA clinic. Common examples include scheduling tools, session data collection apps, billing and claims software, reporting tools, and dashboards. The goal is less retyping, fewer errors, and more time for clinical work.
Start with the one that targets your biggest time drain. If schedule changes eat your week, begin with scheduling. If data is still on paper, begin with data collection. If claims keep coming back denied, look at billing. Your staff can usually tell you where the time goes.
Often, yes. An all-in-one platform that covers scheduling, data collection, and billing removes the need to move information between separate systems. Whether it fits depends on your clinic, so test it with a real workflow before you commit. If you already rely on an EHR or payroll system, check that the new tool connects with it.
It varies with clinic size, team habits, and how well onboarding goes. Expect a learning curve at the start. The most reliable approach is to log time on a few key tasks before and after switching, so you measure the change instead of guessing.
Yes, if they handle protected health information, and most ABA tools do. Ask each vendor how data is stored, who can access it, and how access is controlled. MeasurePM describes itself as a HIPAA-compliant platform.
Saving hours in an ABA clinic rarely comes from one big change. It comes from removing double handling in a few key places. Pick your biggest time sink, fix it, measure the result, and then move on to the next one.
If you want to see how scheduling, data, and billing work together, you can book a free demo and run your own workflow through it.
A denied claim is rarely a surprise in hindsight. Someone booked one session too many. A note was missing. A code did not match the authorization. The real surprise comes later, when the payment was supposed to arrive and a denial shows up instead.
ABA denial management is the work of finding out why claims were denied, fixing and resubmitting them, and changing your process so the same denial does not come back. This guide covers the most common causes of denials in ABA, a simple way to work a denied claim, and what you can do before a claim ever goes out.
Where we mention MeasurePM, we are describing what the company says on its own website, and we will say so.
Billing for ABA is harder than billing for many other kinds of care. A few reasons stand out.
None of this means your billing team is doing something wrong. It means the work has more moving parts than a generic system expects.
MeasurePM’s own guide to billing errors names the same handful of causes that show up again and again. Here they are, in plain terms.
Sessions keep running on the usual schedule, the authorization end date passes, and nobody notices. By the time denials arrive, weeks of sessions may be affected. Appeals are possible, but the payer’s position is simple: the service was delivered outside the approved period.
Every session uses up units. If nobody tracks the running total, a practice can deliver and bill past the approved amount. Claims above the limit get denied, and because the limit is clearly written down, these denials are hard to overturn.
The service delivered, the credential of the person delivering it, and the supervision setup all affect which code applies. Use the wrong code, or the right code with the wrong modifier, and the claim can be denied. The cause is often not obvious from the claim itself, so sorting it out takes time.
A service that needs a BCBA delivered by an RBT. A staff member whose credential has lapsed. Each of these can lead to a denial, and each tends to happen where credential checks depend on someone remembering to do them.
Payers can review claims, and the notes need to show that the service happened, made clinical sense, and was delivered by a qualified person. Vague or incomplete session notes put the claim at risk.
A claim goes out, no confirmation comes back, someone sends it again, and now two versions exist. Payers can flag the duplicate, and that can cause trouble even for the legitimate original.
Every payer has a deadline for submitting claims, usually counted from the date of service. A claim that misses it can be denied with no real path to recovery.
| Cause | Best place to catch it |
|---|---|
| Expired authorization | Before the session is booked |
| Units over the approved amount | Before booking, with ongoing unit tracking |
| Wrong code or modifier | Before the claim is submitted |
| Credential mismatch | Before the session is booked |
| Missing documentation | Right after the session, and again before submission |
| Duplicate claims | Before submission, by checking claim status |
| Missed filing deadline | Right after the session, by moving it into billing quickly |
Look at that table again. Most of these can be stopped before the claim exists. That is where your effort pays off the most.
When a denial lands on your desk, use the same steps every time. A routine keeps small problems from piling up.
Be honest with yourself about appeals, too. For expired authorizations and extra units, MeasurePM’s guide says appeals are difficult and often unsuccessful. That is a good reason to put your energy into prevention.
Fixing claims one at a time keeps you busy. Reading your denials as a group tells you what to change. A simple spreadsheet is enough. Track these columns:
Once a month, sort by cause. If most of your denials come from authorization problems, you may not have a billing problem at all. You may have a scheduling problem, and that calls for a very different fix.
Think of three checkpoints: before the session, after it, and before the claim goes out.
Many denials trace back to the schedule. On its billing page, MeasurePM notes that practices tracking authorizations by hand often catch mismatches only after a claim is denied. Good ABA scheduling software should know a client’s authorization and a staff member’s credentials before a session is confirmed. According to its website, MeasurePM checks staff credentials before a session is booked and builds schedules with client authorizations in mind.
Notes are easier to get right while the session is fresh. ABA data collection software helps when session records live in the same system as your claims. MeasurePM’s billing page says session documentation from its data collection tool supports the same claim your billing team is tracking, so the records and the claim stay consistent.
A short checklist catches a lot. MeasurePM’s own revenue cycle checklist suggests a few habits worth copying:
Automation can take some of this off your plate. MeasurePM says claims generate and submit automatically once a session is complete, and that billing connects to scheduling, so each claim traces back to a session that was actually authorized. Your team can then spend its time on exceptions instead of data entry.
Not every tool handles this the same way. MeasurePM’s guide to common ABA billing errors describes what purpose-built billing software should do, and it makes a handy shopping list:
On its billing page, MeasurePM also says denials are tracked and managed in the same system that submits claims, with a KPI dashboard showing revenue, utilization, and claims performance. As with any tool, ask to see it work on a real claim.
The last one catches many clinics. A short cheat sheet for each of your main payers can save a lot of rework.
MeasurePM is an all-in-one, HIPAA-compliant ABA platform that combines data collection, scheduling, and billing. The company says more than 10,000 providers use it, including about 750 BCBAs, and it reports a billing collection rate in the high 90s. Those are the company’s own figures, so test them against your own claims. Every feature described in this guide comes from the company’s website.
It will not be the right fit for every clinic. If you are still comparing options, our guide to the best ABA practice management software covers what is out there.
It is the process of tracking denied claims, finding the cause, fixing and resubmitting or appealing them, and changing your workflow so the same problem does not repeat. Good denial management looks at patterns, not just single claims.
According to MeasurePM’s guide to billing errors, the usual causes are billing after an authorization expires, going over authorized units, using the wrong code or modifier, a credential that does not match the service, missing documentation, duplicate claims, and missed filing deadlines. Your own denial log will show which ones hit your clinic hardest.
You can try, but MeasurePM’s guide says these are difficult to appeal and often unsuccessful, because the authorization limits are clearly documented. That is why catching them before the session or the claim is the better plan.
It can help in two ways. Better checks before submission mean fewer preventable denials. And when a denial does happen, having session documentation, authorization records, and staff credentials in one system makes it faster to gather what you need. Software does not replace staff judgment, though. Someone still has to own the process.
Yes, according to MeasurePM’s billing page. Every claim is linked back to a scheduled session that was authorized, and denials are tracked and managed in the same system that submits claims.
Strong ABA denial management has two parts. You work the denials you already have, and you fix the habits upstream that create them. Most of the savings come from the second part: booking with authorization in mind, documenting right away, and reviewing claims before they leave.
If you want to see how scheduling, documentation, and billing work together on a real claim, you can book a free demo and walk through your own workflow.
If you run an ABA practice, you already know that the data is the work. Every programming decision, every supervision conversation and every progress report traces back to what was recorded during a session. So when it’s time to pick an ABA data collection app, the choice affects far more than convenience.
It affects whether your RBTs can record data without fighting their phones. Whether your BCBAs can see a trend on Tuesday instead of at the end of the month. Whether caregivers get a clear report when they ask for one.
This guide walks through how to choose, in the order I’d do it if I were sitting in your seat. No feature-list hype. Just the questions to ask, the things to test and the warning signs to watch for.
Paper data sheets and spreadsheets still work for some teams. But they have a built-in delay. Someone has to compile the numbers, graph them and flag the changes. By the time that happens, the moment to adjust a program may have passed.
MeasurePM makes a similar point on its own data collection page: data should be usable the same day it’s collected, not weeks later. Whatever tool you end up with, that’s a fair standard to hold it to.
A good app should do three things:
Everything else is secondary.
Before you open a single product page, write down how your sessions run today. It sounds obvious, but many teams skip it and end up choosing based on a demo.
Ask yourself:
Your answers become your checklist. If an app can’t match your real workflow, it doesn’t matter how impressive it looks.
Not every feature deserves equal weight. Here’s what I’d look at closely.
Different programs call for different measurement methods. Check that the app covers the ones your team relies on, for example:
If one of these is missing, your team will end up working around the app, usually with a notebook.
Graphs that update as data comes in let a clinician spot a plateau or a spike early. Ask to see how quickly a graph updates after a session entry, and whether you can view it by client, by program and by date range.
MeasurePM describes its analytics dashboards as updating as sessions happen, so trends show up immediately rather than at month-end. That’s the behavior to look for in any option you evaluate.
This is where many apps either shine or fall apart. Sessions are busy. Your RBT might be mid-prompt with a child on the floor and a tablet in one hand.
Look for:
For reference, MeasurePM’s App Store listing says the app runs on iPhone and iPad (iOS 13 or later), and it’s also listed on Google Play. Check that whichever app you’re considering supports the devices your team already owns.
No two clients are the same. Your programs, target behaviors and prompting hierarchies shouldn’t have to fit a fixed template.
Ask whether you can build and edit programs per client, upload your own curriculum if you use one, and adjust a program mid-stream without calling support. MeasurePM lists customizable programming as one of its core features, along with the ability to build treatment programs and target behaviors for each client.
Data is only half the story. Clinicians also write session notes and progress reports, and that’s where hours quietly disappear.
Look for an app that connects data to documentation. For instance, MeasurePM’s site lists AI-assisted SOAP notes and a clinical reporting feature that turns session data into progress reports, which can be reviewed internally and then shared with caregivers for e-signature. Whether features like these are useful to you depends on your workflow, so test them with a real example.
If your practice supervises RBTs or trainees, tracking hours and sessions inside the same system saves a lot of spreadsheet juggling. MeasurePM lists supervision tracking as a built-in feature. If this matters to you, ask any vendor how it works in practice.
Your BCBA, RBT, administrator and office staff don’t need to see the same screens. You also need to protect client information. Confirm that the platform is HIPAA-compliant, ask how permissions work by role, and ask for the vendor’s privacy policy in writing.
Here’s something teams often discover too late. Data collection doesn’t live alone. A completed session affects scheduling, notes, billing and reporting.
If your data app doesn’t talk to the rest of your systems, someone ends up re-entering information. That’s wasted time, and it’s where errors creep in.
MeasurePM, for example, describes a connected flow: sessions set up in its ABA scheduling software flow into data collection, and completed sessions feed into its ABA billing software for claims. You don’t have to buy everything from one vendor. But if you do use separate tools, ask how they connect, and what happens when they don’t.
A demo shows you the best version of a product. A trial with your own team shows you the real one. Here’s the process I recommend.
If you’re interested in MeasurePM, you can book a demo to see the data collection workflow with your own scenarios in mind.
App store listings are a useful reality check. They show how people actually experience an app, not how it’s marketed.
MeasurePM’s mobile app is listed on Google Play and the Apple App Store. Whichever app you’re evaluating, do the same thing: read the most recent reviews, not just the average score. Look for patterns. Are the complaints about login problems, editing notes, loading speed or missing data? Are the comments recent or years old? Does the developer respond, and do the release notes show those issues being fixed?
Then take what you find and put it to the vendor directly. A good vendor will answer without getting defensive. Ask how they handle bug reports, how often they release updates and what the support process looks like.
Reviews from a handful of users won’t tell you everything, and every app has unhappy users. But a recurring problem that matches something in your own workflow, like a data-entry glitch, deserves a straight answer before you sign anything.
Some warning signs show up again and again when practices regret a software choice:
Price matters, but it’s rarely the whole picture. A cheaper app that costs your team an extra hour a week in workarounds isn’t cheaper.
When you compare costs, ask:
MeasurePM has a pricing plan page on its site. Get the specifics in writing from any vendor before you decide.
If you’re stuck between two options, score each one on a basic scale from one to five across these areas:
Total the scores, then compare them against your gut feeling after the trial. If they disagree, trust the trial. It reflects how your team behaves, not how the brochure reads.
An ABA data collection app is software that lets therapists and clinicians record session data, such as behavior counts, durations and skill acquisition trials, on a phone, tablet or computer. Most also graph the data automatically so clinicians can review progress and adjust programs.
Start with support for the data types you use, real-time graphing, mobile access, customizable programs and reporting. After that, consider supervision tracking, session notes, role-based access and HIPAA compliance. Connections to scheduling and billing are also worth checking.
Most practices benefit from both. A mobile app is handy during sessions, while a web dashboard is better for reviewing graphs, building programs and writing reports. Ask whether the two stay in sync, and how data entered on one shows up on the other.
Ask whether the platform is HIPAA-compliant, how permissions are set by role and where the vendor stores data. Request the privacy policy and read it. For anything unclear, ask the vendor in writing and keep the response.
It depends on your practice. An all-in-one platform can reduce double entry between data collection, scheduling and billing. A standalone app can be a good fit if you’re happy with your other systems and want a focused tool. Whichever you pick, test how data moves between your tools.
The right ABA data collection app is the one your team will actually use, session after session. Start with your workflow, shortlist a few options, test each one with a real client scenario and read recent reviews with an open mind.
Choose the tool that makes accurate data easy to collect and easy to use. The rest, from reports to billing, builds on that foundation.
Picture the end of a session. The RBT is packing up, the learner is already heading out, and there’s a clipboard full of tally marks and half-filled boxes. That clipboard is the only record of the last two hours. A few days later a BCBA reads it and decides whether the program stays, changes, or goes. If the numbers are fuzzy, so is the decision.
That’s ABA data collection in a nutshell. You write down behavior and skill progress the same way every time, so a Board Certified Behavior Analyst (BCBA) can tell whether an intervention is working. Below are the main methods with a quick example of each, a way to choose between them, the habits that keep data trustworthy, and what shifts when a clinic leaves paper behind.
Put simply, you pick one behavior, measure it the same way every session, and keep a record you can graph. Sometimes you want more of the behavior, like requesting or following directions. Sometimes you want less, like elopement or aggression.
The BCBA uses that record to keep a program, change it, or start fading it. Parents get something real to look at in a progress meeting instead of “he had a good week.” Payors tend to ask for it at authorization time.
Before you choose a method, fix the definition. Say two Registered Behavior Technicians (RBTs) sit in the same session and both are told to count aggression. One counts a shove. The other counts a shove and a glare. Same learner, different numbers.
A definition like “any time the learner’s hand or foot makes contact with another person’s body” ends that argument before it starts. When your team’s data won’t line up, look here first, not at the RBTs.
There are a lot of methods, but they sort into two camps. Continuous measurement catches every instance of the behavior while you’re watching. Discontinuous measurement samples part of the session, which is the realistic choice when one person can’t stare at one learner for two hours.
The simplest one: count it. A learner asks for help 7 times in a 60 minute session, so frequency is 7. It works best when the behavior has a clean start and stop, like requests, hitting, or words said.
Sessions rarely run the same length, though. Divide the count by the time and you get a rate, 7 per hour here, which lets a short Tuesday sit next to a long Monday without misleading you.
A tantrum lasts 4 minutes on Monday and 11 on Tuesday. Count them and you get “one tantrum” both days, which hides the only thing that changed. Time it instead. Duration is the pick for tantrums, time on task, or staying calm through a transition.
Latency is the pause between your instruction and the learner starting. You say it’s time to clean up, and 40 seconds later they move. Forty seconds is your number. It’s handy for compliance goals, and if the pause shrinks over a few weeks, the skill is getting stronger.
Discrete trial teaching scores every trial as correct, incorrect, or prompted. Ten trials of touching the red card, eight right with no prompt, so 80 percent independent. Write the prompt level down too. A correct answer after a full physical prompt isn’t the same as one the learner got alone, and blending them makes progress look better than it is, or hides that there isn’t any.
Break the skill into steps (hand washing has 8) and mark each one independent or prompted. Steps 1 to 5 alone, help with 6 through 8? Now you know exactly where tomorrow’s teaching goes.
ABC stands for antecedent, behavior, consequence: what happened right before, what the learner did, what happened right after. It’s usually a short written note. The RBT asks the learner to put the tablet away, the learner drops to the floor and screams, an adult gives two more minutes of tablet time. One entry doesn’t prove much. Five or six start to show why the behavior keeps working for the learner.
Some behaviors move too fast to count one by one. So chop the session into short intervals, say 10 seconds, and score each one. There are three flavors.
Sometimes the behavior leaves evidence behind. Worksheet problems finished, toys back in the bin. Measure the evidence instead of the behavior. It’s useful when you can’t be in the room.
Here’s how a two hour session with one learner might actually go. The RBT runs color matching as discrete trials, scoring each trial and its prompt level. Midway they move to hand washing and mark steps off a task analysis. All the while, a tally of the learner’s requests runs in the background. Then a tantrum hits: timer on, and an ABC note once things calm down.
At the end, the BCBA has four pictures of the same learner. Accuracy on a taught skill. Independence on a routine. How much they communicate. What the challenging behavior looked like. One method couldn’t have given all four.
Three questions help. Does the behavior start and stop cleanly, or does it just drift on? Do you care how often, how long, or why? And the one people skip: what can the RBT really manage while also running the session?
A method that looks great on paper but is too heavy to run live ends up skipped, or filled in from memory at the end of the day. I’d rather see a simpler method used correctly than a clever one used badly.
| Method | What it measures | Good fit for |
|---|---|---|
| Frequency and rate | How often a behavior occurs | Requests, hitting, words said |
| Duration | How long a behavior lasts | Tantrums, time on task |
| Latency | Time from cue to response | Following instructions, transitions |
| Trial-by-trial | Correct, incorrect, or prompted responses | Discrete trial skill programs |
| Task analysis | Steps completed independently | Hand washing, dressing |
| ABC | What happens around a behavior | Assessment, finding function |
| Partial interval | Whether behavior occurred in the interval | High rate behavior |
| Whole interval | Whether behavior filled the interval | Behavior you want to last longer |
| Momentary time sampling | Whether behavior is happening at the check | Busy sessions, group settings |
| Permanent product | The result left behind | Completed work, tidy-up tasks |
Paper isn’t the enemy. It’s nearly free, everyone knows how to use it, and it doesn’t need wifi. The pain shows up later. Someone has to type the numbers in. Graphs get drawn by hand, or don’t get drawn. Sheets disappear. And client information on loose paper is a privacy problem for any practice handling protected health information.
Software moves data entry into the session itself. If you’re shopping, here’s what to look for:
MeasurePM’s ABA data collection software was designed by BCBAs. RBTs and BCBAs can enter session data on any device, with real-time analytics and customizable graphs on mobile and web. The Clinical Reporting feature turns session data into progress reports, and AI-assisted SOAP notes sit alongside data collection and treatment planning to cut down end-of-day paperwork. Sessions set up in ABA scheduling software flow into data collection, and completed sessions feed ABA billing software for claims. More than 10,000 providers, including about 750 BCBAs, use the platform.
If you’re comparing platforms more broadly, our guide to the best ABA practice management software goes wider. Whichever one you pick, run it through a real session before you commit.
Frequency and rate, duration, latency, trial-by-trial data, task analysis data, ABC data, interval recording (partial, whole, and momentary time sampling), and permanent product recording. Each answers a different question, so plenty of learners have more than one running at once.
Every session, for every behavior or skill in the plan. Recording as the session happens keeps it accurate. How often the BCBA reviews the graphs is a clinical call, but it should follow a regular schedule instead of waiting for reauthorization.
Continuous measurement captures every occurrence of a behavior during the observation, which is what frequency, duration, and latency do. Discontinuous measurement samples the session, which is what the interval methods do. Continuous gives the fuller picture. Discontinuous is easier when staff can’t watch one behavior the whole time.
RBTs usually take the data in session because they’re the ones working with the learner. The BCBA decides what to measure, designs the data system, trains the team, and analyzes the results to adjust the program.
Yes, if your practice handles protected health information, and session data tied to a client counts. Ask any vendor how they secure data and who can access it. MeasurePM is a HIPAA-compliant platform.
If we had to boil it down: define the behavior clearly, match the method to the question, record during the session, and actually look at the graphs. That’s most of it.
If paper is slowing your team down, ask for a live walkthrough of how MeasurePM handles it. You can book a demo or read the ABA data collection software page first.
Demos are easy to love. Everything loads fast, the sample client has perfect data, and nobody’s authorization is about to expire. Real clinics don’t look like that. A BCBA calls out at 7 a.m., a payer denies a claim for a reason nobody can find, and your biller is rebuilding a report in Excel for the third time this month.
So when you shop for ABA practice management software, judge it on the bad days. The checklist below is built for that, ten checks in roughly the order I’d run them.
Test ten things: data collection, scheduling, billing, authorization tracking, reporting, security, ease of use, integrations, onboarding and support, and pricing. Favor platforms that connect these in one system, and confirm every claim in a demo using your own real scenarios, not the vendor’s script.
Three things, at minimum: capture clinical data, schedule staff and clients, and bill insurance for what was delivered. Most clinics also want reporting, a caregiver portal, and authorization tracking.
Why bundle them? Because a session changes shape as it moves through your clinic. It starts as a calendar slot, becomes data, then becomes a claim. When each stage lives in a different tool, somebody on your team is the human glue between them, and that person’s time isn’t free.
The ten checks below all ask one question in different ways: does each stage hand off cleanly to the next?
If it slows the therapist down, they’ll jot things on paper and enter them later. Then your data is only as good as their memory.
Ask for a phone or tablet demo of a live session. Watch how programs and targets are set up per client, how measurement types work, and whether graphs update as data comes in. MeasurePM’s ABA data collection software is a handy reference point. Its features page describes an iOS, Android, and Kindle app “optimized for offline use,” along with customizable programming and real-time graphs. Offline mode is worth testing with any vendor, since Wi-Fi in a client’s home is never guaranteed. And whoever you evaluate, have an RBT run the mock session, not a salesperson. Friction shows up in about two minutes.
Session notes deserve a question too. Templates or AI-assisted drafts can save time, so ask who reviews and signs them. MeasurePM lists template-based SOAP notes and AI SOAP Notes, plus supervision-hour tracking and caregiver e-signature on progress reports. Whether you need those depends on your clinic, but this is the level of ABA-specific detail to look for.
A calendar that only knows who’s free is a calendar that will schedule the wrong person for the wrong client.
Ask the vendor to book a session for a staff member who lacks the required credential. What happens? Then ask what the system does when a client has two approved units left. MeasurePM’s ABA scheduling software is described as authorization-aware. Its site also lists rules that prevent non-credentialed staff from being booked, drag-and-drop calendars color-coded by therapist, client, or location, and email and SMS reminders. Any competitor should be able to show you the same behavior live.
If you run several sites, check that you can see all of them in one view.
This one is simple. A claim should be built from the completed session, not retyped by a person who is also answering the phone.
When it works, every claim traces back to a documented, authorized session, which makes payer disputes much less painful. MeasurePM’s ABA billing software is built on that idea. In a demo, ask the vendor to follow one session from the calendar to a submitted claim without leaving the system. If they jump between screens that look like separate products, take note.
Payer coverage matters here too. MeasurePM’s features page says claims go to 100+ payers directly, with pre-filled codes, and names Medicaid, Aetna, and Blue Cross. Its billing page describes claim status moving through the clearinghouse to “Sent to Finance.” Whatever platform you look at, check that your own payers are on the list.
You should be able to open a client and see units approved, units used, units left, and the end date. No spreadsheet. No counting.
Ask what warnings fire before hours run out and whether sessions outside an approval get flagged. Eligibility verification is worth a separate question, since some platforms include it and some don’t. MeasurePM’s features page, for example, lists authorization tracking, eligibility verification, and copay management together under revenue cycle management.
Denials will happen. Fine. The useful question is whether you can see them, sort them, and work them in the same place you submit claims.
Ask the vendor to pull up a denied claim and show how your team would follow it through. Then check reporting more broadly: utilization, staff productivity, revenue. Which reports are built in, and which ones need a support ticket?
For a sense of what to expect, MeasurePM’s site describes real-time dashboards for payments, denials, and balances, report export for accounting, and compliance reports for insurance audits that generate “with a single click.” Its billing page adds that denials are tracked on the same dashboard as scheduling and revenue.
Anything holding client health information has to meet HIPAA requirements. Nearly every vendor says they do. Your job is to verify.
Ask how data is encrypted, how user permissions work, and whether they’ll sign a business associate agreement. Ask about backups and uptime. For reference, MeasurePM’s features page states end-to-end encryption and secure cloud storage and calls the platform HIPAA-compliant. It doesn’t mention a business associate agreement or independent audits, so those remain questions to ask. [VERIFY: confirm BAA availability and any independent security audits with the vendor before publishing claims beyond what the site states.]
Try role-based access in the demo too. Your front-desk scheduler and your clinical director shouldn’t see identical screens.
Software that staff avoid becomes a pile of workarounds. Hand the mouse to your team and have each person run their five most common tasks. Note where anyone gets stuck.
Training hours are a real cost, so a cleaner interface pays for itself. Also check the caregiver side. A portal where parents see upcoming sessions and progress can cut down on front-desk calls, so find out what families can and can’t see. MeasurePM’s site describes caregiver access to progress updates, session notes, goal tracking, and billing information.
“Integrates with many systems” tells you nothing. Ask which ones, by name: payroll, accounting, telehealth, EHR, whatever you run. MeasurePM’s homepage mentions connections with EHR, payroll, and telehealth tools, and the features page lists report export for accounting. Whichever vendor you’re looking at, get the specific product names confirmed.
Then ask the awkward question. If you leave in three years, what do you take with you, and in what format? Vendors rarely bring this up. How they answer says a lot.
Switching is disruptive, so find out who moves your client, authorization, and staff data, how long that usually takes, and what you need to prepare. MeasurePM’s site describes personalized onboarding from an expert team and a helpdesk staffed by former RBTs, reachable by phone, email, and chat. Its features page also says three in-house BCBAs work with the mobile development team. The site doesn’t describe data migration or give set timelines. [VERIFY: confirm onboarding timelines, migration support, and support hours with the vendor in writing.]
For support, ask about channels and hours, but also about who’s on the other end. Someone who knows what an authorization unit is will fix your problem faster than someone reading a script. And ask for a reference from a clinic about your size.
Many platforms price by module, so your total depends on what you bundle. MeasurePM’s pricing page lists no dollar amounts. It describes flexible plans and bundling across data collection, scheduling, and billing, with a personalized quote, and says setup support is available at a discounted rate. That’s a common model, and it’s fine, provided you get the full picture in writing.
Ask what’s included, what costs extra, how setup is priced, and what leaving looks like. And remember that a cheap tool that needs extra staff hours to reconcile claims isn’t cheap.
For most ABA clinics, all-in-one is the better starting point, since scheduling, notes, and billing lean on each other constantly. Separate tools can work if you already have strong ones you want to keep, but someone has to keep them in sync.
| All-in-one platform | Separate best-of-breed tools | Generic medical software | |
|---|---|---|---|
| ABA authorization handling | Built into scheduling and billing | Varies by tool | Usually limited |
| Data entry | Once, then reused | Often repeated | Often manual |
| Staff training | One system | Several systems | One system, not ABA-specific |
| Swapping out one piece | Harder | Easier | Varies |
| Best fit | One record from session to payment | Clinics keeping tools they like | Non-ABA practices |
Neither choice is wrong everywhere. The question is whether your team spends its week treating clients or reconciling screens.
Bring five scenarios and make each vendor walk through them live:
Polished demos hide problems. Messy scenarios reveal them.
Vague answers about authorizations are the big one, along with a vendor who can’t show a denied claim being worked. A few others:
None of these disqualifies a vendor on its own. Each deserves a direct question and a written reply.
Choosing ABA practice management software mostly comes down to how well one system carries a session from calendar to clinical record to claim. Work through the ten checks, put every vendor through the same scenarios, and listen to the people who’ll use it daily.
If MeasurePM is on your shortlist, book a demo and bring your own cases. Whatever you pick, get the security, onboarding, and pricing answers in writing before you sign.
It’s a platform that helps ABA providers run their clinic, usually combining clinical data collection, staff and client scheduling, and insurance billing. Many also include reporting and caregiver access. The goal is to keep sessions, authorizations, and claims connected so staff avoid re-entering information in several tools.
Start with data collection that works during sessions, scheduling that respects authorizations and staff credentials, and billing built from completed sessions. Denial tracking, reporting, and security matter too. The right mix depends on your size, payers, and number of locations, so test against your own workflow.
Most clinics do better with an all-in-one platform because scheduling, documentation, and billing depend on one another. Separate tools can work when you already rely on strong systems you want to keep, but someone must keep them synchronized. Weigh that ongoing reconciliation work against the added flexibility.
Ask the vendor directly. Request their security documentation, confirm they’ll sign a business associate agreement, and ask how data is encrypted and how user access is controlled. A compliance claim on a website is a starting point, not proof, so get the details in writing.
It depends on your data volume, how clean your authorization records are, and how many locations you run. Ask each vendor for a realistic timeline and a list of what you need to prepare. Auditing active authorizations before migration usually smooths the process and stops old errors from carrying over.
Here’s how it usually goes. A clinic is humming along, then an authorization runs out in the middle of the month and nobody catches it until the payer does. Or a claim bounces because the schedule says Tuesday and the session note says Wednesday. Or a BCBA types the same session data twice, and billing keys it in a third time. Somebody finally snaps and says we need better software.
So begins the ABA software comparison. You open a few tabs and find ranked lists, almost all written by vendors, almost all with the author’s own product somewhere near the top. Fair enough, that’s marketing. But it doesn’t help much when you’re picking something your whole team will use every day. This guide is meant to. Eight platforms, what to check before you commit, and a way to decide that won’t eat half a year.
Open any vendor site and you’ll see the same words: scheduling, billing, data collection. Useless for choosing. What matters is how those pieces hand off to each other, plus a handful of things that never make the homepage.
Begin with the seam between scheduling and billing, because that’s where most of the pain lives. If someone has to re-enter a finished session before it turns into a claim, you’re basically paying people to create denials. Better systems pass the provider, service code, units and authorization along on their own. And good ABA scheduling software checks the authorization before the session gets booked. Finding out it expired from a rejection letter three weeks later? That’s the costly way.
Data collection comes next, and honestly this is where your staff’s opinion should count most. RBTs are in living rooms and classrooms, half the time with bad signal. Does the app work offline and sync later? Does what they enter flow into the note and the claim, or does it sit in its own little silo? If your team hates ABA data collection software, they’ll find workarounds, and that’s usually how compliance gaps start.
Billing is its own question, because ABA billing software means different things to different vendors. It might be a claims tool or a clearinghouse connection, or it might be an outsourced team that works your denials for a cut. Those aren’t the same purchase, and they don’t cost the same. Find out which one you’re being sold, and who chases the rejections.
Credentialing and authorization tracking rarely show up in demos, because they’re boring. They’re also where clinics get hurt. A license lapses. A re-authorization date slips by a week. Suddenly the “system” is a spreadsheet nobody really owns. Some platforms track all this natively; others leave it to you. Ask to see it working.
Support and security come last, but don’t skimp on them. At some point you’ll need a human on the phone, and it’ll be the Monday payroll is due. Any vendor handling client data should sign a BAA without fuss, and a SOC 2 report is a good sign if they have one.
Quick disclosure: we make MeasurePM, so take our entry with a grain of salt, same as you would anyone’s. Everything here comes from public vendor pages and published listings, and prices are as of October 2026. Where a vendor doesn’t publish a number, the table says so. We didn’t want to guess.
| Platform | Best for | Key strengths | Pricing model | Keep in mind |
| MeasurePM | Small to mid-size clinics wanting one operations hub | Scheduling, billing, data collection, owner dashboards | Not publicly available (quote) | Ask about credential tracking in the demo |
| Motivity | Clinics, schools, and enterprises that put clinical data first | Data collection with 1,000+ templates, scheduling, credentialing, RCM services | Published: from $24 per learner/month; $48 for the full suite | Flexible, so expect some setup time |
| Theralytics | Growing clinics that want one login | Scheduling, billing, data collection, payroll, SOC 2 Type 2 | Published: $20 per client/month for practice management, $30 combined; 10-client minimum plus base fee | Built for ABA-only practices; read the minimums |
| CentralReach | Large, multi-location organizations | Scheduling, billing, payroll, analytics, staff training | Quote only | Can feel heavy for small teams |
| Rethink | Providers who want ABA plus training and a program library | Staff training, pre-built programs, school and child therapy reach | Quote only | Broader than ABA, so test ABA-specific workflows |
| Passage Health | Clinics wanting a lightweight all-in-one | Clean interface, quick onboarding | Quote only | Compliance and credentialing detail is thin publicly |
| AlohaABA | Small to mid-size clinics that value simplicity | Scheduling, billing, payroll, compliance tracking | Quote only | Welina, its data collection tool, launched in beta; check its status |
| Raven Health | New and growing providers | Mobile-first data collection, session notes, billing services | Data collection from $29 per client/month plus $300 implementation | Enterprise compliance features aren’t detailed publicly |
MeasurePM keeps scheduling, billing, and data collection in one place, and it leans toward owners who want to see where hours and revenue are actually going. Think small to mid-size clinic, not a company with a dedicated IT team. Pricing is quote-based, so you’ll need a demo to see a number. When you get one, push on credential and license tracking, and have them take a single claim from schedule all the way to payment.
Motivity started on the clinical side and worked outward. Session data feeds scheduling, billing, and credentialing, and clinics, schools, and bigger organizations all use it. It also publishes prices, which almost nobody else here does: from $24 per learner a month for data collection or practice management, $48 for everything. The flip side is flexibility. A tool that bends to how you work first needs you to know how you work, so set aside time for setup.
Theralytics advertises $20 per client per month for practice management or data collection, and $30 if you want both. Then come the strings: a 10-client minimum and a monthly base fee that its own page puts around $200 to $300, depending on the package. If you’ve got six clients, that stings. With sixty, it barely registers. You get scheduling, billing, data collection, documentation, and payroll under one login, an optional full-service billing arrangement at 4.5% of receivables, and a SOC 2 Type 2 report.
CentralReach is the heavyweight. Scheduling, billing, payroll, clinical data, training, analytics across sites: it has all of it, and it expects somebody on your team to configure and maintain the whole thing. Pricing comes after a consultation. A ten-person clinic will probably find it too much. A multi-location network with an operations team will probably put it on the shortlist.
Rethink covers ABA, schools, and wider child therapy, and the draw is its staff training library and ready-made programs. Hiring a wave of new RBTs? That content can save you real hours. The trade is focus: a platform this broad may give ABA-specific workflows less love than an ABA-only product would, so test your own scheduling and billing cases before you sign. Pricing is quote-only.
Passage Health sells itself as an all-in-one clinical and practice management platform with a clean interface and quick onboarding. If you’re tired of clunky software, that’s attractive. Pricing isn’t published, and there’s not much public detail on compliance or credentialing. That’s where to start asking.
AlohaABA handles scheduling, billing, payroll, and compliance tracking, and small teams tend to pick it up fast. Data collection is the question mark. Its tool, Welina, launched as a beta, so find out where it stands now and whether you’d still need something separate. Pricing is by quote.
Raven Health is mobile-first. Think quick in-session data collection, notes, graphs, plus billing services that include RCM. The data collection essentials tier is listed at $29 per client per month with a $300 implementation fee; anything beyond that needs a quote. New providers tend to like how easy it is. Bigger clinics should push for details on credentialing and compliance, because none of it is spelled out publicly.
Keep it cheap and simple. Check the minimums before a low per-client rate charms you, because a 10-client minimum or a monthly base fee changes the math fast when you’ve got four clients. ABA practice management software built for small teams usually beats anything that needs heavy configuration.
Somewhere between 20 and 60 clients, the scheduling-to-billing handoff starts to pay for itself. Each new hire adds more re-entry and more denials. So integration, authorization checks, and billing support should sit at the top of your list. Then dig into implementation fees and find out who moves your data.
Now you’re juggling reporting across sites, role-based permissions, payroll, maybe an API. Enterprise platforms earn their price here. Still ask about the rollout timeline. Configuration-heavy projects drag, and someone on your side has to own it.
What counts as the best ABA software depends on your size, your payers, and how much setup you can stand. A tool that fits a ten-person clinic can frustrate a ten-site network. The reverse is true as well.
Buying off the demo is the big one. Demos show the happy path, every time. Make the rep run your ugliest case live: a session that crosses an authorization limit, a provider covering for a colleague mid-week, a claim that needs a correction.
Price is the next trap. ABA software pricing might be per client, per user, flat, or a cut of receivables, and then base fees, implementation fees, and add-on modules pile on top. A $20 per-client rate sounds great until the minimum and the base fee show up. Run the monthly total at your size today, and again at double.
Nobody thinks about migration until it stalls everything. Your historical data, authorizations, and client records have to go somewhere. Who moves them? How long does it take? What happens to your data if you leave?
Then there’s the people part. Your schedulers and RBTs will be in this thing all day. Let them try it first. They’ll spot the annoying bits in an afternoon.
Last one: don’t treat billing as another department’s problem. Split the clinical, scheduling, and billing tools apart and someone ends up reconciling them by hand. That person isn’t cheap.
A good ABA software comparison ends with two or three finalists, not one winner. Choose the one your schedulers, RBTs, and billing people will use without inventing workarounds, at a price that still makes sense once you’ve doubled in size.
If MeasurePM is on your list, book a demo and bring your messiest scheduling-to-billing case. It’s the fastest way to find out whether it fits.
From what vendors publish, roughly $20 to $48 per client per month as of October 2026. A few list nothing at all. Base fees, minimums, implementation charges, and add-ons can move the real monthly bill a lot, so get a written quote for your current size before you compare anything.
Practice management is the business side: scheduling, authorizations, billing, payroll, reports. Data collection is the clinical side: logging session data, graphing progress, writing notes. Some platforms do both, some do one better than the other. What matters is how cleanly data moves from one to the other.
Mostly, yes. If a booked session becomes a claim on its own, you skip the re-entry and the mismatches behind a lot of denials. And a system that checks authorizations while you’re scheduling catches problems that separate tools only surface after a payer rejects the claim.
Expect several weeks, at least. It depends on how much history has to move, how many people need training, and who handles the migration. Get a written timeline from every vendor, plus a straight answer on who does the data transfer, you or them.
At minimum: a signed BAA, encryption, two-factor authentication, and audit logs. Those are the basics. A SOC 2 report is a bonus where one exists. Also ask where your data is hosted, and what happens to your records if you ever leave the platform.
Put three cards in front of a learner and say “touch car.” He taps the card on the left. Next trial, “touch shoe,” and he taps the left card again. Then “touch cup.” Left again. About a third of those answers will be right by pure luck, and if all you track is percent correct, the data can look like progress.
That’s the problem stimulus discrimination training in ABA is meant to solve. You want a learner who responds to the right cue and ignores the wrong ones, and you want a data sheet that can tell real learning from a lucky habit. Below you’ll find the core concepts, clinical examples, teaching steps, and a practical way to track data so you can trust what it’s telling you.
Quick summary
- Stimulus discrimination means a response is reinforced in the presence of one stimulus (the SD) and not in the presence of another (the S-delta).
- Most early learner programs, like receptive identification, use conditional discrimination.
- Percent correct alone can mislead you. Track prompt level, field size, and error patterns too.
- Set the mastery criterion before you start, and know what chance level looks like for your field size.
Stimulus discrimination training teaches a learner to respond differently depending on what’s in front of them. A response gets reinforced when a certain stimulus is present and doesn’t when it isn’t. After enough repetitions, that stimulus starts to control the behavior.
Two terms do most of the work here. The discriminative stimulus (SD) signals that a response will be reinforced. The stimulus delta (S-delta) signals that it won’t. A phone ringing is an SD for answering it. A silent phone is an S-delta.
| Situation | SD | Response | S-delta | What happens in S-delta |
|---|---|---|---|---|
| Receptive identification | Instruction “touch red,” red card in the field | Touches red card | Blue card in the field | No reinforcement, trial re-presented |
| Responding to name | Adult says the learner’s name | Looks toward the adult | Adult says a different name | Looking isn’t reinforced |
| Requesting | Adult is holding the snack | Says “chips, please” | Adult has nothing in hand | Request isn’t reinforced in training |
| Crossing the street | Walk signal | Crosses | Don’t-walk signal | Waits |
One quick note before moving on. Discrimination and generalization pull in opposite directions. Generalization means responding the same way across similar stimuli, like recognizing a dog whether it’s a poodle or a lab. Discrimination means responding differently across stimuli that matter, like telling a dog from a cat. Good programming needs both, which is why generalization shows up later in the teaching steps.
A simple discrimination has one SD. You respond when it’s present and not when it’s absent. Answering the phone when it rings is the classic case.
A conditional discrimination is trickier, because the right response depends on a combination of stimuli. In receptive identification, the red card is correct only when the instruction is “red.” Say “blue” and the same red card is now wrong. The learner has to track the instruction and the array at once.
That’s why receptive ID looks easy on a program sheet and turns out to be hard in a session. Matching, receptive labels, and most “find the one that…” targets are all conditional discriminations.
These are the targets you’ll see most often in clinic programs.
Receptive identification is the obvious one. The instruction is “touch car,” the field holds a car and two other items, and only the car gets reinforced.
Identical matching works the same way with a sample. The learner gets a cup card and places it with the matching cup, ignoring the shoe.
Responding to name falls here too. The name called is the SD, and other names or sounds are S-deltas. For many young learners this is the first discrimination worth teaching.
Requesting by audience is a quieter example. A learner who asks for the iPad should ask the adult who’s holding it, not a person across the room with empty hands. The adult holding the item is the SD.
Safety skills count as well. Reading a walk signal versus a don’t-walk signal, or stopping at a stop sign, are discriminations with real consequences.
Social targets use the same logic. Greeting someone who just arrived is reinforced, while greeting the wall isn’t, which sounds silly until you meet a learner who greets everyone at the same volume all day.
The procedure changes by program, but the shape is pretty consistent.
Mixing in a few mastered targets between new ones helps too. It keeps reinforcement flowing and gives the learner an easy win after a hard trial.
Say Leo is four. In baseline, his RBT runs “touch car,” “touch shoe,” and “touch cup” in a field of three, ten trials. Leo gets 3 of 10 right, and 8 of his 10 selections are the card on the left. That’s a position habit, not knowledge.
The plan: drop to a field of two (car and cup), rotate positions every trial, use a gestural prompt at first, and fade it as soon as he responds without it. After a few sessions he’s at 9 of 10 independent in the field of two. Then the field goes to three, and then new pictures and real objects get added.
The written goal might read: Leo will touch the named item from a field of three, with positions rotated, at 90% independent across three consecutive sessions, with two staff members and in two settings.
Notice that a position pattern sat in the baseline data the whole time. Only a data sheet that records which card was chosen would show it.
The bare minimum is correct or incorrect on each trial. You’ll want more than that, because a single percent hides a lot.
| What to record | What it tells you |
|---|---|
| Independent correct (percent) | Overall progress, without prompts |
| Prompt level on each trial | Whether the learner is truly independent or leaning on the prompt |
| Which item was selected on errors | Position bias, or a favorite item the learner always picks |
| Field size and distractors | How hard the trial really was |
| Staff member and setting | Early signs of generalization (or lack of it) |
| Sessions to criterion | Pace, and when it’s time to change the teaching |
With a field of two, guessing gets you about 50%. With a field of three, about 33%. If a learner is sitting at 40% in a field of three, that’s barely above guessing, and calling it “emerging” overstates it. Write chance level next to the goal so everyone reading the graph knows what the floor is.
Pick the criterion before you start teaching, not after you see the data. Something like 80% to 90% independent across two or three consecutive sessions is common, but your clinic and funder rules decide. Whatever you pick, add the number of staff and settings, so mastery means the skill works beyond one therapist in one room.
If data hold flat for several sessions, change something. Maybe the distractors are too similar to the target, maybe the prompt never faded, or maybe the reinforcer lost its pull. And if errors cluster on one position or one item, that’s a clue about the cause. Trend lines make this easier to see than a column of numbers.
Position bias is the quietest one. If target placement isn’t rotated and the data sheet doesn’t capture where the learner pointed, the pattern stays invisible.
Teams also expand the field too fast. Moving from two items to five because the learner hit criterion once usually just produces a new pile of errors.
Teaching with one example is another trap. A learner who only sees one red card may be responding to that card’s bent corner rather than to “red.” Using several examples, in different materials, helps the skill transfer.
Prompt dependence sneaks in when a prompt that should fade stays in place. The learner gets correct answers, the graph climbs, and nobody notices the answers disappear when the prompt does.
Changing the instruction wording from trial to trial can muddy things early on. Keep it consistent until the discrimination is stable, then vary it.
And finally, treating prompted and independent responses as the same data point. They aren’t. A 90% that includes heavy prompting isn’t a 90%.
Most of what makes discrimination data useful (prompt level, field size, error patterns, trend) is also what makes it tedious on paper. That’s usually where good programs slip: the information is collected, but nobody can see it clearly in time to adjust.
MeasurePM’s clinical data collection is built for this kind of workflow, with real-time analytics and mobile access, so your team can record trials during the session and see the graph update right away. Its customizable programming lets you set flexible measurement types for skill acquisition, success criteria, trend detection, and automatic progression of targets and prompts. That fits discrimination programs well, since the field size and prompt level change as the learner moves along.
The same records feed documentation. Progress reports that tie each goal to session data make authorization requests easier to write, and connected ABA billing software keeps claims lined up with the services you delivered.
If you’d like more clinical and operational reading, the MeasurePM resource center has other ABA guides.
It’s a teaching procedure where a response is reinforced when one stimulus is present and not reinforced when another is. Over time the learner responds to the right cue and ignores the wrong ones. Common targets include receptive identification, matching, responding to name, and reading safety signals.
An SD signals that a response will be reinforced. An S-delta signals that it won’t. In “touch red,” the red card is the SD and the blue card is the S-delta. The learner learns to respond to the first and hold off on the second.
Discrimination means responding differently to different stimuli. Generalization means responding the same way across similar stimuli. A learner who calls both a poodle and a lab a “dog” is generalizing. One who doesn’t call a cat a “dog” is discriminating. Good programs teach both.
When independent correct responding meets the mastery criterion you set at the start, usually across several consecutive sessions, with more than one staff member and setting. Also check that errors aren’t clustering on one position or item, and that results sit well above chance for the field size.
It’s when the correct response depends on a combination of stimuli. In receptive identification, touching the red card is right only if the instruction was “red.” The same card is wrong when the instruction is “blue.” Matching and most receptive language targets work this way.
Good discrimination training comes down to a few habits: clear targets, prompts that fade, positions that rotate, and data that records more than right or wrong. Decide the criterion up front, keep an eye on chance level, and read the error patterns as closely as the percent correct.
If you’d like to see how that data looks in a single system, you can book a MeasurePM demo.