Skip to main content

ABA Buyer Intent Guide

How do you recover cancelled ABA hours?

A cancellation is not one problem, it is two, and both of them tend to get run the same way: a coordinator with a phone and a list of names. That holds until the day it does not. What follows is the sequence itself, written so it works on a whiteboard, with a note at each step about where a tool takes the manual part off a person.

Quick answer

Run one sequence every time. Catch the cancellation while the hour can still be used, decide whether it is a family cancellation or a staff callout, put the makeup offer or the open hour in front of the people who can act on it, keep the family approval step, and count the hour only at delivery.

What is the sequence when a session cancels?

Five steps, in order, and the order is the part that matters.

Catch the cancellation while there is still day left to do something with it. Decide which of the two situations you are in, because they run differently. Put the makeup offer in front of the family, or the open hour in front of the technicians who could claim it. Keep the family’s approval in front of anything that touches their calendar. Count the hour only when the session is delivered.

That is all of it. It runs on a whiteboard, a phone, and one person willing to make calls, and the free playbook covers the same ground with no software attached. If you want the short version of the argument rather than the steps, it is on the ABA cancellation recovery page.

What software removes is the calling. Every step above still happens, it just stops depending on whether a coordinator had the time and the phone numbers on the one afternoon it mattered.

How early does a cancellation have to be caught?

Early enough that the hour still has somewhere to go.

A cancellation that surfaces the night before is a problem with options. The same cancellation discovered when the technician is already in the driveway is a loss with paperwork attached.

So the first step is not recovery, it is detection: a confirmation the day before, an easy way for a caregiver to tell you without making a call they will never make, and somebody whose actual job it is to see it come in.

This is the step that often gets done halfway. The reminder goes out. Nobody is watching for the reply.

Is this a family cancellation or a staff callout?

Two different problems, two different runs, and sorting them is step two for a reason.

A family cancellation means the child is not available. There is no slot to fill and nobody is placed into it. What you are building is a makeup offer for that family, at a time they can realistically keep, and they either approve it or they do not.

A staff callout runs the other direction. The child is available and the plan still calls for the hour, so the hour is the thing being protected. It posts as an open hour that a qualified technician may choose to claim.

Making that call on the whiteboard before anyone picks up a phone is what keeps the next three steps from running in the wrong direction. Calls get wasted when a family cancellation is run as though it were a staffing hole.

How does an open hour reach the people who could take it?

Not by group text.

A blast to everyone hands the decision to whoever happens to look at their phone first, and it puts a coordinator in the middle of every reply. Then the coordinator is the one reconciling who answered first, on top of everything else that afternoon.

Put the open hour where the people who could take it will see it, and let them claim it by choice. Nothing is auto-assigned and nobody is placed into a shift. On a whiteboard that is a board in the staff room and a rule everyone knows: first name written takes it.

In Infinite Suite OS the claim works the same way, and the booking is checked against the authorization cap and the daily unit limits before it holds. That check is about approved time, not about people. There is no credential screening on this path and it would be dishonest to imply one: credential checking belongs to a separate billing claims gate, and the two should never be described as if they were one.

When does the hour count as recovered?

At delivery, inside the same authorization period. Not at the booking.

A claimed open hour is a promise. An approved makeup is a promise. Promises cancel too, sometimes for the reason the first session cancelled.

Before delivery there is one gate that does not move: the family’s yes. No recovered hour reaches a family calendar without their approval, and in Infinite Suite OS that is enforced by the engine rather than left to whoever happens to be running the schedule that day.

Then the session is delivered, or it is not. If it is, you have a recovered hour and a number you can defend in a room full of people asking. If it is not, you are back at step one with less of the period left. What share of hours your clinic gets back is your own number: this site publishes a labeled simulation and a calculator you fill in with your own figures, and neither one is a prediction about you.

What happens when nobody has an open hour?

Nothing happens, and that is worth saying out loud rather than burying.

If every technician is booked and no one has a free hour, there is no recovery path to run. No step in this sequence invents a person. That is the ceiling on all of it, and no sequence and no software gets around it.

What the sequence does is make sure the openings that already exist find the hour that needs them, before the day ends and the hour is gone for good. That is a smaller claim than the word recovery usually invites. It is also the one that survives a real Tuesday.

Frequently asked questions

What is the first step in recovering a cancelled ABA hour?

Catching the cancellation while the hour can still be used. A cancellation found the night before has options, and the same cancellation found at the door is already a loss. Detection is a scheduling habit, not a recovery feature.

Is a family cancellation handled differently from a staff callout?

Yes, and treating them the same sends a coordinator down the wrong path before the first call is dialed. A family cancellation produces a makeup offer that the family approves, with no slot to fill and nobody placed into it. A staff callout posts an open hour that a qualified technician may choose to claim.

Who approves a makeup session?

The family. No recovered hour reaches a family calendar without their yes, and in Infinite Suite OS that consent step is enforced by the engine rather than left to a policy someone remembers. A makeup nobody agreed to is not a recovery, it is a scheduling conflict waiting to happen.

Is a technician ever assigned to an open hour?

No. An open hour is posted, and qualified technicians may choose to claim it. Nothing is auto-assigned and nobody is placed into a shift. Claiming by choice is the design, not a setting somebody can turn off.

Are credentials checked when someone claims an open hour?

No, and it matters that nobody pretends otherwise. On the recovery path the booking is checked against the authorization cap and the daily unit limits, which is about approved time rather than about people. Credential checking lives in a separate billing claims gate, and the two are not the same check.

When does a rescheduled session count as recovered?

Only when it is delivered, inside the same authorization period. A booking is a promise and promises cancel, so counting the booking inflates every number underneath it. The delivered session is the recovery.

Can a clinic run this without software?

Yes. The whole sequence works on a whiteboard, and the free playbook lays it out that way. Software mainly removes the phone calls nobody has time to make, and it cannot do anything at all when no one has a free hour.

Payer-neutral, and not billing or legal advice. Infinite Pieces never sets or recommends a child’s hours; the BCBA owns the plan. Any recovery figures published elsewhere on this site are labeled simulation, and a clinic’s own operating calendar changes them. Working demo using fictional data. No PHI, customers, or production deployment are implied.