An ABA reschedule request workflow preserves the original visit, records the requested change, and tests proposed alternatives for client choice, clinical fit, qualified staff, supervision, setting, travel, communication access, authorization, and notice. A request can remain received, under review, options offered, accepted, released, declined, or closed. The replacement visit receives its own identity and release evidence.
Capture the request
Record original visit ID, requester, request time, reason they choose to share, acceptable dates and windows, setting or modality constraints, transportation, access needs, desired response date, contact route, and any visits affected by the change.
Use a request record with clear states
A build-ready record includes received, clarification due, options under review, clinical decision due, options offered, family response due, release-ready, released, declined, no viable configuration, or closed. Give each state an owner, entry time, next action, and due time.
| Field group | Required facts |
|---|---|
| Original visit | Service, date, time, staff, setting, status |
| Request | Requester, received time, desired windows, constraints |
| Options | Exact configurations, evidence, expiration |
| Decisions | Clinical, family, payer, staffing and access states |
| Outcome | Replacement ID, original disposition, actual delivery |
Link sensitive reasons rather than copying them into a broad scheduling queue.
Preserve the original visit
Keep its planned state and history. A proposed replacement links back to it with a reason and version. Cancel, hold, or close the original only under the authorized workflow after the replacement decision or explicit client choice.
Offer only real configurations
Before presenting a time, verify staff, supervision, room or travel, service, setting, modality, payer dates, access support, and qualified clinical review. State which evidence is confirmed and how long the option remains available. Avoid offering the same scarce slot to several people without a documented sequence.
When no option clears, give the family the current state, next review, and available continuity or referral route. Do not characterize lack of practice capacity as the family's refusal to schedule.
Test each option
Verify clinical appropriateness, client agreement, staff qualifications, supervision, location, modality, travel, access support, payer period, authorization quantity, and downstream conflicts. HealthCare.gov cautions that preauthorization does not promise cost coverage.
Keep decisions with their owners
A qualified clinician decides case-specific clinical appropriateness. The payer owns its authorization or coverage action. Operations confirms resources. The client or authorized decision maker chooses among available options through the applicable process. Access and workforce owners act within their domains.
Store these as separate dated decisions. A generic approved field makes it impossible to tell whether the family selected a time, the clinician approved a change, or the payer updated an authorization.
Communicate through a usable route
DOJ effective-communication guidance informs aid and service selection for covered entities. Offer clear dates, times, locations, modality, response window, and consequences of no response. Record sent, delivered, acknowledged, accepted, or declined separately.
Manage option expiration fairly
Tell the family when an option expires and how to request another. Measure the practice's time to prepare and deliver the option separately from the family's response time. Failed delivery or inaccessible communication should pause the response clock under the approved policy.
When an option expires, preserve the offered configuration and response evidence. Return the request to the defined queue state rather than closing it as declined unless that is what the person communicated.
Let people compare complete options without pressure
Present each option with the date, start and end, setting, modality, staff role when appropriate, location, transport assumption, expected duration, response deadline, and any fact still awaiting verification. Identify what happens to the original visit and whether another option remains under search. Do not frame an inconvenient or clinically unreviewed configuration as the only way to preserve care.
Record accepted, declined, alternative requested, expired, withdrawn, and unreachable separately. A decline should not reduce a person's priority or become evidence of noncompliance. If capacity changes before the response deadline, tell the person promptly and preserve why the option was withdrawn. When two people could use one slot, apply the approved allocation policy and document the result instead of letting message speed become the hidden priority rule.
A fictional request queue
Green Valley ABA receives 16 requests. Ten result in a fully released replacement, three remain with options offered, two are declined by the family, and one has no viable current configuration. Release yield is 10 of 16, or 62.5%; disposition completeness is 12 of 16, or 75%.
Correct the disposition denominator
The ten released and two family-declined requests have final dispositions, producing 12 of 16. The three options offered and one no-current-configuration record remain operationally open unless the policy defines that last state as a final closure. Report their age and next action.
After the service window, measure whether released replacements were delivered. Reschedule release, visit delivery, authorization use, claim state, and payment answer different questions and require separate cohorts.
Reconcile the schedule
Update original and linked visit states, staff assignments, supervision, room or route, notices, authorization usage, documentation, timekeeping, charges, and claims. Track request age, options, release time, service loss, access gaps, reversals, and unresolved downstream differences.
Review recurring reschedule causes
Segment requests by time band, school or work transition, transportation, staffing, site, travel, access, payer timing, and schedule error. Record only the reason a person chooses to share and avoid assigning motives. Repeated patterns can reveal a mismatch between advertised and usable capacity.
Use the evidence to adjust hours, territories, staffing reserves, reminder channels, and family outreach. Preserve qualified clinical decisions and accommodation routes separately.
Measure both request handling and final service
Report response time, viable options, family selection, released replacements, completed visits, and unrecovered service hours. A fast response with unusable options is different from a released visit that later fails, so each stage needs its own cohort.
Owner reschedule questions
- Is the request linked to the original appointment and preserved as its own controlled record?
- Are acceptable windows, access needs, transport, location, modality, and communication route current?
- Did each option clear clinical, payer, staff, supervision, site, and timing gates before release?
- Can the person understand the complete option, deadline, and consequences of each response?
- Are expired and declined offers retained without closing the underlying need improperly?
- Does final reconciliation update schedules, notices, authorizations, staff work, and linked recovery records?
Measure both handling speed and whether service ultimately occurs in a workable configuration. Fast closure can conceal an unresolved client need.
A two-option reschedule example
A family asks to move a Wednesday visit because of a temporary school activity. The practice can offer Friday at the usual center with the current team or Tuesday at a different site with a configuration still awaiting review. Operations releases only the Friday option and describes Tuesday as under review, with a time for the next update. The original Wednesday visit remains linked and unchanged until the family decides.
The family asks for Tuesday because Friday conflicts with work. After the required clinical, payer, site, supervision, and staff gates clear, operations sends the complete Tuesday option with a fresh response window. Acceptance creates a new schedule version and the original visit receives its linked disposition. The example preserves family choice without presenting a possible slot as ready or erasing the path that produced the final arrangement.
Related resources
- ABA Makeup Session Offer Workflow
- ABA Cancellation Reason Coding Guide
- ABA Waitlist Priority Review
- ABA No-Show Response and Outreach Workflow
