Este artículo está en inglés. Use el selector EN | ES para navegar el resto del sitio en español.
Scheduling6 Scheduling Checks That Stop Unbillable ABA Sessions
Double-booking, unqualified renderers, weekly caps, availability, leave, and missing authorization lines — the six checks TargetFlo runs so sessions on the calendar can actually be billed.
Most unbillable ABA sessions were doomed when they were scheduled: the wrong credential on a 97155, a week booked past the authorization's cap, a session with no authorization line at all. TargetFlo checks the calendar at the moment of scheduling — warnings let coordinators plan, blocks stop sessions that could never be billed.
| Situation | What TargetFlo does |
|---|---|
| Client double-booked | Blocks it |
| Renderer not qualified for the code | Blocks it (Admin override with a reason) |
| Week over the authorization's weekly cap | Warns: Overbooked |
| Session outside the person's availability | Warns |
| Team member on approved leave | Warns and suggests who can cover |
| Completing a billable session with no authorization line | Blocks it (Admin override with a reason) |
Why warnings and blocks are different
Coordinators need room to plan a messy week, so capacity problems are warnings. Problems that make a claim impossible — a client in two places, an unqualified renderer, no authorization — are blocks.
Every override leaves a trail
Overrides are recorded in the event's history and in the audit log, with the reason.
Read more on Scheduling & Authorizations and Why scheduling must connect to authorizations.
- ABA scheduling software
- ABA authorization tracking
- ABA authorization utilization
- unbillable ABA sessions
Véalo en TargetFlo
Saquemos la admisión del fax
Reserve una demo de 30 minutos: mapeamos su flujo de referidos al pipeline de 9 etapas, conectamos su fax y mostramos elegibilidad en admisión.
Reservar demoFAQ
