The word recovery is easy to misuse
A clinic can say it found a makeup opportunity.
That does not mean the family accepted it.
A family can accept a proposed window.
That does not mean an appropriate staff member claimed it.
A staff member can claim it.
That does not mean the BCBA approved unfamiliar coverage, the authorization period fit, or the session was scheduled.
A session can be scheduled.
That still does not mean it happened.
If all of those stages are collapsed into one number, leadership cannot tell whether the process works.
Stage 1: the hour becomes at risk
The funnel begins when scheduled care is disrupted.
The event may be a caregiver cancellation, an RBT callout, a schedule conflict, a location problem, or another operational change. The original event matters because the available recovery paths may differ.
The system should record:
- What was scheduled.
- Who initiated the change.
- When the organization learned about it.
- How much notice was available.
- Whether the family or staff member offered alternative availability.
- Whether the session remains inside the authorization period.
This is not a judgment about blame.
It is the starting condition for understanding what happened next.
Stage 2: a realistic opportunity is identified
A possible recovery opportunity exists only when several facts line up well enough to consider it.
A family may provide makeup windows. A regular RBT may have another opening later in the week. A cancellation elsewhere may free an appropriate staff member. A familiar backup may become available. A clinically approved alternative service may be considered by the treatment team if it is actually appropriate and authorized.
The important word is realistic.
Generating every mathematical overlap between two calendars can create noise. A useful opportunity should account for the known constraints before anyone spends time on it.
That may include:
- Family availability.
- Staff availability and declared capacity.
- Drive time and geography.
- Staff familiarity or coverage eligibility.
- Authorization dates and service requirements.
- Clinical review rules.
- The purpose and likely value of the proposed session.
Even then, it is only an identified opportunity.
Stage 3: the people involved accept
A system should not turn a possibility into an assignment without the people.
The family can accept, decline, or request a different option.
The staff member can claim or decline a voluntary opportunity.
The regular team may prefer to schedule a later makeup themselves.
These responses should be simple enough that the workflow reduces work rather than creating another series of phone calls.
The system also needs to record silence honestly. No response is not acceptance. An expired offer is not a completed recovery.
Stage 4: required clinical review occurs
Some opportunities may be safe to schedule under pre-established rules. Others may require direct review.
Examples include unfamiliar staff, higher-intensity support needs, significant communication or safety considerations, changes in setting, or a temporary coverage plan that limits which programs should be run.
The clinical reviewer should be able to approve, decline, or request changes with a structured reason.
The software should not convert those reasons into automated clinical decisions for future learners. It can make the rules and history visible to qualified people.
Stage 5: the session is scheduled
Scheduling is a real milestone, but it is not the final result.
At this point, the system should confirm that the date, time, people, setting, and authorization period align. Notifications should reach the family and staff. The covering RBT should receive only the approved context needed for the session.
The event should also appear in whatever export or integration process the organization uses to keep its existing EMR and operations aligned.
Infinite Suite OS is designed to sit beside the EMR, not become the billing or claims system.
Stage 6: the session is completed
Completion is where a recovery can finally be counted as completed care.
Even then, the organization may want to distinguish:
- The full planned duration was completed.
- A shorter session was completed.
- The session started but ended early.
- The session was cancelled again.
- Documentation or required follow-through remains incomplete.
That detail prevents a scheduled block from being mistaken for an outcome.
Reason codes are as important as conversion rates
A funnel tells leadership where opportunities stop.
Reason codes help explain why.
Useful categories may include:
- Family declined unfamiliar coverage.
- Family had no workable makeup time.
- Regular RBT preferred to recover the hour later.
- No staff with appropriate familiarity was available.
- Travel made the opportunity unrealistic.
- Clinical review declined the match.
- Authorization timing did not fit.
- Staff capacity or overtime concern.
- The learner was better served by waiting.
- The makeup was scheduled and later cancelled.
Those reasons should not become a weapon against families, RBTs, schedulers, or BCBAs. They are signals about the operating environment.
The dashboard should show the whole funnel
An executive or regional view should answer more than “How many hours did we recover?”
It should help leaders ask:
- How many hours became at risk?
- How quickly did the organization identify a realistic path?
- Where are families waiting for a response?
- Where are staff opportunities expiring?
- How often does clinical review approve or decline alternate coverage?
- Which barriers happen most often by site, region, service model, or notice period?
- How many scheduled makeups become completed sessions?
- Are the same people being asked to carry the recovery process repeatedly?
These are operational questions. They do not replace clinical interpretation, payer review, or audited financial reporting.
What the Infinite Suite OS demo measures
Infinite Suite OS is currently a working demo using fictional data. There are no customers or production clinic results.
The demo is built around the idea that recovery should move through visible stages rather than appear as one optimistic number. Leadership can see an hour at risk, the proposed path, the human responses, the review state, the schedule state, and whether care was completed.
The production version still has to be built with tenant isolation, real authentication, live data, integrations, audit records, and organization-specific rules.
But the measurement principle is already clear.
Identified is not recovered.
Accepted is not recovered.
Scheduled is not recovered.
Completed care is recovered care.