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.
Picture this. A mom tells you her four-year-old “talks all the time.” You sit with him for twenty minutes and he says almost nothing you didn’t prompt. Is she wrong? Not really. Are you? No. That gap is the reason skills assessment in ABA exists in the first place. It shows you what a learner can do, where they can do it, and with whom, and it does that before anybody writes a goal.
This guide walks through what the assessment measures, how to choose between the common tools, how to turn scores into goals, and where things tend to go sideways.
Quick summary
Officially, it maps current abilities across communication, social skills, daily living, academics, and motor skills. Day to day, it answers three blunt questions. Where is this kid right now? What do we teach first? And how will we know it’s working?
It’s not an FBA. An FBA asks why a particular challenging behavior happens, and a skills assessment asks what’s missing from the repertoire. They overlap, though, more than you’d think. A child who can’t ask for a break might be escaping through problem behavior. That’s an FBA question, but the fix is a skill.
The baseline matters more than people admit. Without one, a six-month progress report runs on memory and good intentions. With one, you can point at a number and say, here’s where we started.
Intake, obviously. The initial assessment shapes the treatment plan and usually the first authorization request.
Reassessment is the one that sneaks up on teams. A lot of funders want updated data roughly every six months, but it varies by payer, so check the rules for each one you bill. Put the date in the calendar at intake and give it an owner. A shared ABA scheduling system makes this easier, since the reminder sits right beside the sessions it affects.
Then there are the quieter triggers. If a learner plateaus, reassess before you start blaming the learner. Maybe they’ve picked up skills nobody is tracking. Maybe the program drifted. And when a child changes settings (home to center, new school, leaving early intervention), the old baseline just doesn’t describe their day anymore.
Most clinics end up with two tools. One guides teaching, one satisfies funders and compares the learner with same-age peers.
| Tool | Best for | What it measures | Limitation to keep in mind |
|---|---|---|---|
| VB-MAPP | Early learners and learners with language delays | 170 verbal behavior milestones, plus barriers and transition assessments | Built around early development, so it fits older, more advanced learners less well |
| ABLLS-R | Learners who need a detailed, skill-by-skill breakdown | 544 skills across 25 areas, including language, self-help, academics, and motor | Thorough scoring takes real time |
| AFLS | Adolescents and adults, or anyone working toward independence | Functional living skills across home, community, school, and vocational settings | Not designed to build early language |
| PEAK | Learners ready for flexible, generalized responding | Relational and generalization skills drawn from relational frame theory | Works best when the team already knows the framework |
| Vineland-3 | Funder documentation and eligibility | Standardized adaptive behavior scores for communication, daily living, socialization, and motor | Doesn’t produce a teaching program on its own |
People tend to file the Vineland-3 under “paperwork.” Fair, but it’s also the only one here that tells you how a learner compares with peers their age, and some families really want that number.
A rough way to pick:
For wider guidance on assessment and treatment planning, the Council of Autism Service Providers publishes practice guidelines that are handy to have bookmarked.
Talk to caregivers first. Before the test kit comes out. Twenty minutes with a parent tells you what happens at home, what’s been tried, and what the family actually wants. It also surfaces skills that never appear in a clinic room.
Don’t judge a learner from one room, either. Kids behave differently at home, at school, and in the clinic. If a skill only shows up in one place, that’s one you’ll need to program for generalization later.
For items you can’t answer by watching, use direct testing: present the task, record the response, note the prompt level. Keep it short, though. Several brief sessions with breaks usually beat one long one, especially for young learners or kids who are new to ABA. A tired child isn’t showing you their real repertoire.
Take notes while it’s happening. By the end of the day, you’ve already forgotten the small details, and small details are often the useful ones.
On roles: the BCBA designs and interprets the assessment, in line with the BACB Ethics Code. RBTs can collect data under supervision. Teachers and caregivers fill in what you can’t see.
Scores don’t write goals. You do, and half the work is deciding what you won’t teach yet.
Start with patterns. Strong receptive language next to weak expressive language points one direction, while low scores across the board point another. Then ask what changes daily life. Asking for help beats naming colors, pretty much every time.
Break big skills down. “Dressing independently” becomes a task analysis: arms through sleeves, shirt over the head, and onward. Each goal needs a mastery criterion that anyone can score. “Improve vocabulary” isn’t scoreable. “Label 20 items at 90% across three consecutive sessions” is. And write generalization into the goal itself by naming people, settings, and materials.
Say Maya is five. Her VB-MAPP shows strong labeling and imitation, but requesting is thin. She asks for a few favorite items and reaches or whines for everything else. Her caregiver mentions meltdowns when a zipper sticks or a snack container won’t open.
So where do you start? Not with more labeling. With requesting help.
A new RBT could pick that up on Monday and run it without calling you. That’s the bar.
Leaning on a single tool tops the list. Every instrument has blind spots. If the learner or the funder needs it, pair a curriculum-based tool with a standardized one.
Skipping caregiver input is next. Clinic performance is a slice of the picture, and without the interview you lose skills and priorities both.
Vague goals are sneakier. Quick test: if two clinicians would score the same goal differently, it isn’t measurable yet.
Generalization gets forgotten constantly. A skill that works with one therapist in one room hasn’t really been learned. It’s been rehearsed.
And then the operational stuff. Reassessments run late because nobody owned the date. Scores end up spread across paper forms, spreadsheets, and email threads, someone retypes them, and eventually a number goes missing.
If you want more reading on any of this, the MeasurePM resource center has other ABA guides.
An assessment sitting in a PDF on somebody’s drive loses value quickly. The goals from intake should show up in the RBT’s session view, and the data from those sessions should roll back into your progress report. When that’s manual, BCBAs end up retyping numbers at night.
MeasurePM is an all-in-one, HIPAA-compliant ABA platform with clinical data collection at the center, plus real-time analytics and customizable graphs on mobile and web. Session data feeds the graphs you take into the next reassessment, so you’re not rebuilding the story from scratch.
The funding side uses the same records. Reports that tie each goal to session data make authorization requests easier to write, and connected ABA billing software keeps claims matched to the services you delivered.
Once before treatment starts, then on whatever schedule your funder sets, which is often about every six months. Do one sooner if progress stalls, the learner regresses, or life changes in a big way, like a new school or a move from home-based to center-based services. Check timing with each payer.
The VB-MAPP centers on verbal behavior milestones, so it’s a common fit for early learners and language delays. The ABLLS-R breaks skills into finer pieces across language, self-help, academics, and motor areas, which suits older or more varied learners. Teams usually decide based on age and how much programming detail they need.
A BCBA runs the show: picks the tools, interprets the results, and writes the recommendations. RBTs can help collect data or administer specific items under supervision. Caregivers and teachers add their view through interviews and rating forms, and that’s often where you learn how skills look outside the clinic.
Some are. The Vineland-3 is standardized and compares a learner with same-age peers. The VB-MAPP, ABLLS-R, and AFLS are criterion-referenced, which means they measure mastery of specific skills rather than ranking the learner against a norm group. Plenty of clinics use one of each type.
A skills assessment tells you what a learner can’t do yet. An FBA tells you why a particular behavior keeps happening. Different questions, and many learners need both. The answers feed each other, especially when a missing skill, like asking for help, is what drives the behavior.
A good skills assessment in ABA ends with goals a new RBT can run, data that shows whether they’re working, and a baseline you can stand behind at reassessment. Pick tools that fit the learner. Write goals you can score. Keep the data in one place.
If you’d like to see that in a single system, you can book a MeasurePM demo.
Differential reinforcement in ABA is one of the first tools a BCBA reaches for when a behavior needs to go down and a better one needs to come up. The idea is simple: reinforce some responses, withhold reinforcement for others, and let the contrast teach. The details are where plans tend to fall apart. This guide covers the five main types with examples you can picture in a real session, how to choose between them, and what data to collect.
Differential reinforcement means reinforcing a response under certain conditions while withholding reinforcement under others. In behavior reduction, the problem behavior stops paying off and something else starts paying off instead. It’s a less intrusive option than punishment-based procedures, and it’s easier to explain to families and school teams, since they can see what the learner is being taught to do.
Most DR procedures pair a reinforcement contingency with extinction for the problem behavior. Skip the second part and the plan quietly stops working. Whichever type you pick, the reinforcer should also match what the FBA says the behavior is getting the learner.
In DRA, you reinforce an appropriate alternative behavior and withhold reinforcement for the problem behavior. The alternative doesn’t have to resemble the problem behavior at all. It just has to be something you’d rather see. When it serves the same function, as in functional communication training, DRA teaches the learner a better way to get what they want.
It works best when you know the function and can teach a replacement skill. It’s a weaker choice when the learner can’t yet perform the alternative, or when the problem behavior is dangerous and you can’t safely withhold reinforcement.
Example: A 4-year-old in a clinic program grabs toys from peers. His RBT teaches him to hand over a “my turn” card. Each time he does, he gets the toy within a few seconds, with the peer prompted to share. Grabbing is blocked and earns nothing. The first week is mostly prompted. By week three the prompts are fading and the card comes out on its own.
DRI reinforces a behavior that can’t happen at the same time as the problem behavior. If the learner is doing one, they physically can’t be doing the other. That removes the gray area about whether the alternative is occurring.
It works when the problem behavior has an obvious physical opposite, like being seated versus out of seat, or hands in lap versus hitting. It’s a poor fit when no truly incompatible behavior exists, which is more often than people expect.
Example: An 8-year-old in a general education classroom leaves her seat repeatedly during independent work. She earns a token at the end of each 5-minute block spent fully seated, and four tokens buy a few minutes with a favorite book. When she leaves her seat, the teacher gives no attention and quietly redirects her.
DRO delivers reinforcement when the problem behavior hasn’t occurred for a set period. It doesn’t care what the learner does instead, only that the target behavior stays away. In whole-interval DRO, the behavior must be absent for the entire interval. In momentary DRO, it only has to be absent when the interval ends.
DRO fits when behavior needs to come down quickly and there’s no obvious alternative, or as a bridge while you teach a replacement skill. Its weakness is that it teaches nothing. A learner can earn reinforcement while doing some other problem behavior, so keep an eye out for that.
Example: A 5-year-old screams at the dinner table at home. Baseline shows it happening roughly every four minutes. The BCBA sets the starting interval at two minutes, shorter than the typical gap, so success is possible right away. Each screaming-free interval earns a sticker and praise from a parent. If he screams, the timer resets. Over several weeks the interval stretches to three minutes, then five.
DRL reinforces a behavior when it occurs at or below a set rate. Unlike the others here, the goal is reduction, not elimination. Variations include full-session DRL (stay under a limit for the session), interval DRL, and spaced-responding DRL (a minimum time must pass between responses).
Use it for behaviors that are fine in moderation and a problem in excess, like calling out answers or asking for help over and over. Don’t use it for anything dangerous or anything that shouldn’t happen at all. Set the first limit near baseline, because a limit far below it sets the learner up to miss reinforcement again and again.
Example: A 9-year-old in a clinic-based school program asks “Is this right?” about 20 times in a 30-minute work block, and it’s breaking up his work. The team sets the first limit at 15. Staying at 15 or under earns a point, and points trade for a short game at the end of the session. Every few sessions the limit drops.
DRH is the odd one out. It reinforces a behavior when it occurs at or above a criterion rate, so it’s used to increase a behavior, not decrease one. The behavior needs to already be in the learner’s repertoire. If it isn’t, you’re looking at prompting or shaping first.
Use it when you want more of a good thing, like peer initiations, on-task responses, or answering questions.
Example: A 6-year-old in a social skills group greets or invites a peer to play once, maybe twice, per session. The criterion is three initiations in a 20-minute group. When she reaches it, she picks the closing activity. After several sessions at criterion, the team raises it to four.
| Type | Reinforcement delivered when | Best used for | Example |
|---|---|---|---|
| DRA | An appropriate alternative behavior occurs | Teaching a replacement skill | Handing over a “my turn” card instead of grabbing |
| DRI | A behavior that can’t occur with the problem behavior occurs | Problem behaviors with a clear physical opposite | Staying seated instead of leaving the seat |
| DRO | The problem behavior is absent for a set interval | Fast reduction when no alternative is obvious | No screaming for 2 minutes |
| DRL | The behavior occurs at or below a set rate | Behaviors that are fine in moderation | 15 or fewer help requests in 30 minutes |
| DRH | The behavior occurs at or above a set rate | Increasing a behavior already in the repertoire | 3 or more peer initiations in 20 minutes |
Start with the function from the FBA, then work through these questions in order:
In practice, DRA is the default for good reason, since it builds a skill. DRO often works best as a short-term bridge. Plans that combine procedures are common, such as DRA with a brief DRO to bring the rate down while the new skill takes hold.
Reinforcing the problem behavior by accident. This usually happens at the worst moment. A parent holds the line through nine screams and gives in on the tenth. That teaches the learner to scream ten times.
Starting with intervals or limits that are too hard. If a DRO interval is longer than the learner’s typical gap between behaviors, they’ll rarely earn anything. Early success matters.
Thinning too fast. Stretching an interval or tightening a limit after one good session is tempting. Wait for stable data first.
Delaying reinforcement. The longer the gap between the target response and the reinforcer, the weaker the contingency.
Skipping the preference assessment. A reinforcer that worked last month may be stale now. Check again.
Letting integrity slip. The plan only works as well as the least consistent person running it. Caregivers and school staff often need a short, written version and a quick check-in after the first week.
Reinforcing something worse in a DRO. Because DRO rewards “anything but,” watch what the learner does right before the interval ends.
Good DR data answers two questions: is the target behavior changing, and is the plan being run as written? Record these:
Graph it with clear phase-change lines, and review it on a regular schedule. The graph is what tells you when to thin the schedule, change the criterion, or rethink the function.
Paper data sheets work for a small caseload. They get hard to manage when several RBTs run the same plan across sessions, and a supervisor ends up reconciling sheets before a team meeting. With ABA data collection software, RBTs can enter data during the session on mobile or web, and BCBAs can see real-time analytics and customizable graphs between supervision visits instead of after the fact. MeasurePM’s clinical reporting and graphing tools turn that data into progress reports without rebuilding charts by hand.
DRA reinforces a specific alternative behavior, so the learner is being taught what to do. DRO reinforces the absence of the problem behavior for a set interval, regardless of what the learner does instead. DRA builds a skill. DRO mainly lowers the behavior, which is why it’s often used briefly or alongside DRA.
Neither is better across the board. DRI works when a clear behavior can’t happen alongside the problem behavior, like staying seated instead of leaving the seat. DRA is more flexible, since the alternative can be any appropriate behavior. Many problem behaviors have no truly incompatible response, so DRA gets used more often.
Use DRL for behaviors that are acceptable in moderation but become a problem at high rates, like calling out answers or asking for help repeatedly. Set the first limit close to the baseline rate, then lower it gradually. Avoid DRL for dangerous behavior or anything that shouldn’t happen at all. DRA or DRO fits those better.
For DRA, DRI, and DRO, extinction (withholding reinforcement for the problem behavior) is usually part of the plan, because otherwise the problem behavior keeps paying off. It isn’t always possible, though. If the behavior is dangerous, the team needs a safety plan first. DRL and DRH work differently, since they adjust reinforcement around rate.
Differential reinforcement works when the plan is specific, the reinforcer matters to the learner, and everyone runs it the same way. Data is what shows whether that’s happening. If your team still reconciles paper sheets before supervision meetings, it may be worth seeing what session data tracking looks like in MeasurePM. You’ll find more guides in the MeasurePM resource center.
Ask three clinicians how they track a behavior and you’ll probably get three different answers. One keeps tally marks on a clipboard. Another runs a stopwatch. A third glances at the learner every ten seconds and ticks a box.
All three are collecting data. Only one of them is collecting everything.
That’s the heart of continuous measurement ABA work: you record every occurrence of a behavior during an observation period, so nothing slips through the gaps between checks. It sounds simple, and in principle it is. In practice, doing it consistently across staff, sessions, and settings takes some thought.
Quick answer: Continuous measurement in ABA is a data collection approach where an observer records every instance of a target behavior for the entire observation period. The main types are frequency, rate, duration, latency, and inter-response time (IRT). Because nothing is sampled or estimated, it gives a complete record of how a behavior occurs.
It’s a way of recording behavior where the observer captures every occurrence, or the full length of each one, during a set window. It matters because treatment decisions follow the data, and gaps in the data can quietly push those decisions in the wrong direction.
Picture a learner who hits peers during play. If you check every thirty seconds, you might catch the behavior in two intervals. The real count could be higher. It could be lower. You wouldn’t know. Record every instance instead, and the team sees the actual number and can tell whether the plan is working or just looking like it is.
That’s also why discontinuous methods are often judged by how closely they match continuous data. Continuous recording is the reference point.
The observer watches for the full observation period and records each occurrence, or its length, as it happens. Afterward, the data is summarized as a count, rate, or time and graphed so the team can see change over time.
Here’s how a typical session flows:
None of this is hard on paper. The hard part is doing it the same way, every session, with every staff member.
The main types are frequency (and rate), duration, latency, and inter-response time. Each one captures a different dimension of behavior, so the right choice depends on the question you’re trying to answer.
Frequency is a straight count: how many times did it happen? Rate puts that count against time, which keeps sessions of different lengths comparable.
Here’s why that matters. Say a learner hits peers 6 times in a 20-minute session on Monday and 9 times in a 45-minute session on Tuesday. Nine sounds worse than six. But Monday’s rate is 0.3 per minute (6 ÷ 20) and Tuesday’s is 0.2 per minute (9 ÷ 45). The behavior actually went down.
Frequency and rate work best when a behavior has a clear start and stop, like requests, hitting, or elopement attempts. These numbers are made up for illustration, but the math is the same on any real data sheet.
Duration tells you how long a behavior lasts, either per episode or as a total across the session. It answers a question that frequency can’t.
Two tantrums in a session could be two one-minute episodes or two twenty-minute ones. Same count, very different picture. If a learner has three episodes lasting 2, 5, and 8 minutes, total duration is 15 minutes and the average episode is 5 minutes. Which number matters more depends on what your team is trying to change.
Latency is the time between a cue, like an instruction, and the start of the response. It shows up a lot in compliance and skill-acquisition work. If the gap between a direction and the learner’s first move gets shorter over a few weeks, that’s progress, even if the behavior itself looks the same.
IRT is the gap between the end of one response and the start of the next. It’s handy when spacing is the real concern, like the pace of bites during a meal or repetitive behaviors that bunch together. A longer IRT usually means responses are getting less frequent, sometimes before the overall count shifts much.
Use it when a behavior is discrete, easy to count or time, and important enough that missing instances could change a clinical decision. Safety-related behaviors and skill-acquisition targets are the usual fits.
If one of these is missing, that doesn’t automatically rule the method out. It just means you need a plan for keeping it sustainable.
Start with the question your team needs answered, then match the measure to it. The behavior itself usually points the way if you ask a few simple questions.
Sometimes one behavior needs two measures. A learner who screams might need frequency (how many episodes) and duration (how long each one runs). Pick the measure that helps the team decide something, not the one that’s easiest to write down.
Continuous measurement records every occurrence during the observation period. Discontinuous measurement records whether behavior happened in selected intervals or at specific moments, which gives you an estimate. Continuous is more complete. Discontinuous is easier to run when staff attention is limited.
| Continuous | Discontinuous | |
| What it records | Every occurrence | Occurrence within intervals or at moments |
| Examples | Frequency, duration, latency, IRT | Partial interval, whole interval, momentary time sampling |
| Output | Counts and times | Estimates, often a percentage of intervals |
| Observer demand | High | Lower |
| Best for | Discrete or high-stakes behaviors | Busy settings, very rapid behaviors |
Partial interval recording tends to overestimate how much behavior occurred. Whole interval tends to underestimate it. Momentary time sampling can go either way. Plenty of teams use both families of methods and match the choice to the behavior and the setting.
The main drawbacks are workload and practicality. Recording every instance takes sustained attention. That’s tiring over a long session, and it’s tough to keep up while you’re also running a program or supervising a group.
None of this makes continuous measurement a bad choice. These are just reasons to be honest about what your team can realistically sustain.
Accuracy comes down to three habits: clear operational definitions, trained observers, and regular interobserver agreement (IOA) checks. Technology helps by taking over the manual tallying and math.
Electronic data collection replaces tally sheets and stopwatches, and it takes the manual math off your plate. With MeasurePM’s ABA data collection software, RBTs and BCBAs can enter session data on any device, mobile or web, and use customizable graphs and reports to monitor progress.
Teams can tailor data collection to their organization’s standard of practice, with flexible measurement types for behavior tracking, plus trend detection and supervision tracking. Data is stored with encryption in a HIPAA-compliant setup. Scheduling and billing sit in the same platform, and the features page lists what’s included.
If a behavior drops to low levels, ask whether a lighter method would now do the job. Continuous measurement should serve the plan, not the other way around.
The most common mistakes are vague behavior definitions, comparing raw counts across sessions of different lengths, and skipping IOA checks. All three are easy to fix once you know to look for them.
When data looks messy, one of these is usually the cause before the method is.
Yes, if you’re selective about it. You don’t need continuous recording for every behavior in every session. Many teams save it for the highest-priority behaviors and use discontinuous methods for the rest.
That’s a legitimate clinical choice, as long as it’s written down and the reasoning is clear. The goal is data that’s accurate enough to guide decisions and realistic enough that staff will collect it consistently, day after day.
Continuous measurement ABA methods give clinicians the fullest view of a behavior, provided the behavior suits the method and the team can sustain it. Start with a clear definition, choose the measure that matches your question, and check agreement on a schedule. When the method stops being realistic, adjust it instead of forcing it.
MeasurePM was founded in 2020 by ABA professionals, and its team includes BCBAs, so these are everyday problems for us. If you’re reviewing your data systems, you can book a demo to see how session data is handled. For more practical ABA topics, browse the resource center.
Continuous measurement in ABA means recording every occurrence of a target behavior throughout an observation period, rather than sampling part of it. Common measures include frequency, rate, duration, latency, and inter-response time. Because every instance is captured, clinicians get a complete record they can graph and use to guide treatment decisions.
Examples include counting how many times a learner requests a break (frequency), timing how long a tantrum lasts (duration), measuring the seconds between an instruction and the start of compliance (latency), and timing the gap between two bites of food (inter-response time). Each captures a different dimension of behavior.
Generally yes, because it captures every instance instead of estimating. Interval and time-sampling methods can overestimate or underestimate behavior depending on the method and interval length. Accuracy still depends on observer attention and clear definitions, so a well-run discontinuous method can outperform a poorly run continuous one.
No. Very rapid behaviors, such as constant rocking, are hard to count reliably, and some settings do not allow constant observation. In those cases, partial interval, whole interval, or momentary time sampling can be more practical. A BCBA usually chooses the method based on the behavior, the setting, and the staff available.
No. Continuous measurement can be done with tally sheets, stopwatches, and paper graphs. Software makes it easier by recording counts and times in real time, calculating rate automatically, and building graphs. That reduces manual errors and saves time, especially across many clients and sessions.
A new RBT can’t apply for certification until someone signs off on their RBT Competency Assessment. Usually that’s a BCBA who already has a full caseload, a stack of notes to review and a supervision calendar that never quite works out.
That’s why it helps to know exactly what the assessment requires before you block out the time. This guide is written for the person doing the assessing, not the candidate, and it follows the BACB RBT Handbook updated in June 2026.
Quick answer: To conduct an RBT Competency Assessment, confirm the candidate has finished the 40-hour training, use the current BACB packet, observe each task using the demonstration methods the packet allows, record the outcome for every task, and sign off. The assessment must fall within 90 days before the candidate applies.
It’s the BACB’s skills check for new RBTs. The candidate performs the tasks listed in the BACB packet for a qualified assessor, the assessor signs off, and the signed packet is uploaded with the application.
It isn’t the only hurdle. There’s also the 40-hour training, a background check, an abuse registry check and the exam. But it’s the one step where somebody at your clinic watches the candidate work and makes the call, and that deserves some care. Whoever ends up supervising this RBT will answer for the work they do with clients.
A qualified BACB-certified professional who isn’t related to, subordinate to, or employed by the candidate.
Check that before anything else gets scheduled. In a small clinic it’s surprisingly easy to land on an assessor who is the candidate’s relative, or who reports to them. Catch it early and it’s a quick swap. Catch it after the packet is signed and you may be doing the whole thing again.
Most clinics just use the supervising BCBA. If more than one person assesses, talk through what “competent” looks like for each task before the first session. Two assessors can read the same line differently, and candidates will feel the difference.
It has to come after the 40-hour training ends, and within the 90 days before the application goes in. Too early and it doesn’t count.
Say a candidate finishes training in January and plans to apply in late spring. Assess them in February and you’ve probably used up the assessment before the application is even started. Wait, and book it once the application date is close.
A few other numbers sit nearby. The training itself has to stretch over at least 5 days and no more than 180. The application needs three documents (the attestation form, the training certificate and the completed assessment), and once it’s started it stays active for 90 days. The easiest approach is to pick the application date, count back, and schedule from there.
The BACB publishes the packet, so candidates can see the task list. Let them. Nobody should meet the assessment cold.
Better still, have them practice during supervised sessions beforehand: run a session, take data, write a note, deal with a scenario that goes sideways. Ten-minute rehearsals with feedback fit into a clinic day. Hour-long review sessions usually don’t.
On assessment day itself, stop coaching. You’re there to watch.
Start with the current packet, observe each task, score it, note how it was demonstrated, and sign only when everything is done.
Don’t sign. It’s tempting to wave through someone who’s nearly there, but your signature says they demonstrated every task.
Write down which one fell short and what you saw. “Needs more practice” helps nobody. “Stopped the timer before the behavior ended” does. Set up supervised practice on that skill, then go back to it.
And keep an eye on the calendar, since the assessment still has to land within the 90 days before the application.
Most of the errors here are clerical. Assessing at the wrong time. Pulling up an old packet. Missing the relationship problem until the signatures are on. Writing “did well” in the notes instead of recording the task, the method and the outcome.
Two are less obvious. First, the assessment doesn’t replace supervision. RBTs still need supervision for at least 5% of their service hours each month, with two face-to-face contacts and at least one direct observation.
Second, don’t hand out answer keys or scripts. The RBT Ethics Code (2.0) bars RBTs from cheating or helping others cheat on competency assessments, and a candidate who already has the answers isn’t really being assessed on anything.
The initial assessment is for new applicants. A recertification assessment applies to current RBTs recertifying through the end of 2026, and it’s overseen by a qualified BACB-certified RBT supervisor. After that, renewal moves to a two-year cycle, though the assessment still applies to RBTs returning from voluntary inactive status.
| Initial | Recertification (through 2026) | Reentry (from Jan 1, 2027) | |
| Who | New RBT applicants | Current RBTs recertifying in 2026 | RBTs returning from voluntary inactive status |
| Timing | After 40-hour training, no more than 90 days before applying | No more than 45 days before the expiration date | No more than 45 days before requesting reactivation |
| Afterward | Upload with application, then take the exam | Two-year cycle begins, with 12 PDUs required | Certification resumes once a supervisor is on record |
RBTs who recertify on or after January 1, 2026 complete one last assessment, then earn 12 hours of professional development per two-year cycle. From January 1, 2027, the form returning RBTs use is renamed the RBT Reentry Competency Assessment. The content stays the same.
The signed packet is the easy part. Getting to it takes training dates, observation time, the 90-day countdown and supervision logs, and when those live in separate spreadsheets, something slips.
Some clinics use ABA scheduling software to block observation time and ABA data collection software to keep session records in one place. Whatever you use, make sure each candidate’s file shows the training completion date, the assessment date and packet version, the assessor’s name (with the relationship check done), the planned application date, and where the signed copy lives.
Supervisors and RBTs must also keep supervision documentation for at least seven years, even after the supervisory relationship ends. A filing habit now saves a scramble if the BACB ever asks.
The BACB only accepts RBT applications from residents of certain countries, and its June 2026 handbook lists the US and Canada among them. In Canada, Ontario residents can no longer apply for RBT certification, and BACB exam sites exclude Quebec and Ontario.
If your clinic operates elsewhere, Brazil included, check the BACB’s current list of eligible countries before you bring candidates through the process.
A qualified BACB-certified professional can serve, provided they are not related to, subordinate to, or employed by the candidate. In most clinics, that is the supervising BCBA. If your only available assessor has a tie to the candidate, ask another certified colleague to assess instead.
The assessment must be completed no more than 90 days before the candidate submits their RBT certification application. If that window passes before they apply, the assessment would no longer meet the requirement. Schedule it close to the application date, once the training certificate and attestation form are ready.
Through 2026, RBTs recertify annually with a recertification assessment. Those who recertify in 2026 complete that last assessment, then move to a two-year cycle with 12 hours of professional development. RBTs returning from voluntary inactive status still complete the assessment, called the Reentry assessment from 2027.
No. The BACB requires the assessment to come after the 40-hour training is complete. Have the candidate’s training certificate in hand first, then schedule the assessment so it lands within 90 days of their planned application date.
Keep a copy of the signed packet, the training certificate and the application documents, since the BACB does not return submitted documents. Supervisors and RBTs must also retain supervision documentation for at least seven years. Store everything in one organized place so an audit request never turns into a search.
A good RBT Competency Assessment is mostly timing and paperwork. Book it inside the 90-day window, pick an assessor with no conflicts, and keep a copy of everything you sign. The skills part you already know how to do.
If you want a simpler way to organize supervision schedules and session data across your clinic, you can book a MeasurePM demo and see how it fits your workflow.
The best ABA billing software depends on your practice size and how much billing you want to handle in-house. MeasurePM suits practices that want authorization-linked billing inside one platform. CentralReach is used by larger and multi-disciplinary providers. Theralytics offers software plus managed billing. AlohaABA suits small practices that want published pricing.
Key takeaways
| Software | Best for | Pricing (as published) | Billing model |
|---|---|---|---|
| MeasurePM | Authorization-linked billing in an all-in-one platform | Pricing plans with bundle discounts | Software platform |
| CentralReach | Larger and multi-disciplinary providers | Contact vendor for pricing | Software plus managed billing service (BillMax) |
| Theralytics | Software plus optional outsourced billing | $20 per client/month; managed billing 4.5% of receivables | Both |
| AlohaABA | Small to mid-size practices | $29.99 per staff/month | Software platform |
| Ensora ABA Suite | Growing practices wanting one suite | Quote based | Software plus optional team |
| Motivity | Clinically driven ABA practices | Confirm with vendor | Software platform |
Pricing reflects vendor-published information at the time of writing and may change. Confirm current rates directly with each vendor.
ABA billing software is a tool that turns completed therapy sessions into insurance claims, tracks each claim through the payer, and manages denials. Unlike generic medical billing tools, it understands ABA-specific rules such as session-level authorizations, CPT codes and payer requirements.
Good ABA billing software usually covers four jobs:
Direct answer: MeasurePM is an all-in-one, HIPAA-compliant ABA platform where billing connects directly to scheduling and clinical data collection, so every claim traces back to an authorized session.
Key features
Pros
Cons
Pricing: See the MeasurePM pricing page. Bundle discounts apply when you combine modules.
Direct answer: CentralReach is a large ABA and multi-disciplinary platform with AI-powered practice management tools, used by larger and multi-disciplinary organizations.
CentralReach offers a managed billing service called BillMax. The company reports high collection rates for customers, though these are vendor-stated figures. On Capterra it holds a 4.3 rating from about 155 reviews.
Pros: Broad feature set across ABA, speech and occupational therapy. Cons: Pricing is not published, so you need a quote to compare costs.
Direct answer: Theralytics offers billing software and an optional managed billing service, so practices can start in-house and outsource later.
It publishes software pricing at $20 per client per month and lists managed billing at 4.5% of receivables. It supports two clearinghouses and holds a 4.8 rating on Capterra from 108 reviews.
Pros: Flexible model and public pricing. Cons: Minimum client count and base fees can raise the effective price for very small practices.
Direct answer: AlohaABA is a practice management tool with billing built in, priced at $29.99 per staff member per month.
It offers session-to-claim workflows, authorization tracking and a free trial. It holds a 4.9 rating on Capterra from 59 reviews.
Pros: Published, predictable pricing. Cons: Data collection is priced as a separate add-on, so check the total cost.
Direct answer: Ensora ABA Suite combines billing, scheduling, payroll and telehealth, with an optional managed billing team.
It generates CMS-1500 forms and supports ABA-specific coding workflows.
Pros: Billing, scheduling, payroll and telehealth in one suite. Cons: Pricing is quote based; third-party listings cite a starting point around $500 per month, so confirm the total cost including any add-ons.
Direct answer: Motivity describes itself as a clinically-first platform where session data connects to scheduling, billing and credentialing.
It says it serves both emerging practices and large organizations.
Pros: Clinical focus and flexible program building, as described by the vendor. Cons: Confirm pricing and billing depth during a demo.
Billing software gives your team the tools to submit and track claims. A managed billing service supplies people who run billing for you, usually for a percentage of collections.
Choose software if you have, or plan to hire, a biller, and you want control and lower cost. Choose a managed service if you do not want to hire and manage billing staff, or if denials are piling up. Many practices start with software and add outsourcing later. The right choice depends on staff, claim volume and cash flow.
Authorization tracking linked to scheduling. Practices that track authorizations manually often discover mismatches only after a claim is denied. When billing connects to scheduling, sessions can be checked against approved units first.
Claim scrubbing and denial management. Look for error checks before submission and one place to track and work denials.
Clearinghouse and payer coverage. Confirm your state Medicaid plan and commercial payers are supported.
Real-time reporting. A KPI dashboard shows revenue, utilization and claim status so problems surface early.
Security. HIPAA compliance and a signed Business Associate Agreement are essential.
Pricing transparency. You should be able to budget before committing to a contract.
We reviewed publicly available information, including vendor websites, pricing pages, industry comparison articles and published ratings on review sites such as Capterra. We weighted billing automation, denial handling, connection to scheduling and documentation, pricing clarity and security. Vendor performance claims are labeled as vendor-reported. Details change, so verify current information before you buy.
Solo or small practice: Look for simple setup and clear pricing. AlohaABA, Theralytics or MeasurePM are worth a demo.
Growing multi-clinic practice: Prioritize authorization-linked billing and reporting. MeasurePM, Ensora and Motivity fit here.
Larger or multi-disciplinary organizations: CentralReach is worth a demo, especially if you also offer speech or occupational therapy.
Want billing outsourced: Consider a managed service such as Theralytics or CentralReach BillMax.
Among vendors that publish pricing, ABA billing software starts at around $20 per client per month (Theralytics) or $29.99 per staff member per month (AlohaABA). Several other platforms, including CentralReach, require a quote. Managed billing services usually charge a percentage of collected revenue, for example Theralytics lists 4.5% of receivables.
ABA billing software is a tool your team uses to submit claims and track payments. A billing service is a team that performs those tasks for you. Software costs less but requires staff time, while services cost a share of collections but reduce workload.
Yes. Software that checks claims for errors before submission and links billing to authorized sessions can prevent common denials. It cannot fix missing authorizations or poor session notes, so clean documentation is still essential.
Many ABA billing platforms support Medicaid and commercial insurance, and many track authorizations. Medicaid rules vary by state, so confirm that your specific state plan and payers are supported before you sign.
The timeline depends on your vendor and practice size. Open claims usually need to clear in the old system while new claims start in the new one, so ask each vendor for a written transition plan and data export options before you sign.
There is no single best ABA billing software for every clinic. If you want billing that connects directly to scheduling and clinical data, MeasurePM is built for that workflow. If you are a large enterprise, or want billing fully outsourced, other options may fit better. Shortlist two or three, book demos, and test your real payers.
Ready to see it in action? Book a free MeasurePM billing demo and test your own payers.