The schedule tells you no before the client does.

A double booking is refused, not reported

ABAVault™ checks both sides of every session as it is saved. A technician cannot be placed on two sessions that overlap, and a client cannot be booked twice, and neither check cares whether the two sessions sit at different locations.

• Staff overlap and client overlap are separate checks, because they are separate mistakes
• Overlaps inside one save are caught too, so a bulk paste cannot slip a pair through
• A hire who has not been cleared to start cannot be put on a session at all

It knows who is available, and who the family asked for

Staff keep an availability window per day and clients keep their own, so the grid stops offering a slot nobody can work. Families and BCBAs can name preferred staff, and the suggestion engine scores open slots against those preferences rather than filling the first gap it finds.

• Auto-scheduling suggests and drafts; a person still approves
• The scoring uses those preferences, so naming one changes which slot comes up first
• Telehealth sessions carry their own meeting link

The credential that lapses on Thursday

The schedule can tell you which staff have a credential lapsing inside the window you are about to fill. A lapsed RBT certification does not announce itself on a Tuesday afternoon; it announces itself when a payer refuses the claim two months later.

Credential tracking lives in HR →

Changes that do not start a phone tree

Callouts, cancellations and schedule exceptions are handled in the schedule itself, and ABAVault tells the people affected. A cancelled session keeps its reason, so the pattern is still there to read at the end of the month.

All features →