ABA recurring schedule revalidation checks a defined block of future visits before they copy forward. It confirms current client choice, clinical plan, payer dates, assigned staff, qualifications, supervision, location, modality, travel, communication access, closures, and actual delivery patterns. Each recurring series keeps a source version, review date, owner, failed gates, and next review trigger.
Set the revalidation window
Choose how many future weeks or visits enter the review and when the snapshot locks. Include recurring-series ID, client, service, day, time, duration, setting, modality, provider, supervisor, payer period, access supports, source version, and last actual service date.
Use a gate record for each series
For every recurring series, store:
| Gate | Current evidence |
|---|---|
| Client or family | Current acceptance, availability, usable contact |
| Clinical | Service and configuration decision, effective period |
| Staff | Role, competence, availability, workload |
| Supervision | Qualified relationship and capacity |
| Payer or financial | Product, route, provider, location, dates and quantity |
| Access and setting | Communication support, room or route, safety state |
| Delivery pattern | Recent completions, changes, cancellations, open issues |
Give each gate a source, checked date, owner, and next trigger.
Check current client and clinical state
Confirm the person or family still accepts the pattern and can use the communication route. A qualified clinician reviews whether service, schedule, setting, and assigned team remain clinically appropriate. The BACB Ethics Code addresses involvement, competence, risk, documentation, and evaluation for covered professionals.
Review evidence that expires at different times
Authorization, clinical plan, staff role, supervision, room status, interpreter confirmation, and family availability can have different effective periods. A series clears only through the earliest controlling expiration or planned review. Record that next stop date.
When one gate remains pending, copy neither the full series nor an unsupported portion of it. Create a shorter approved period only when the current evidence supports it and the responsible roles authorize that state.
Recheck payer and access evidence
Verify authorization dates and exact provider, service, setting, modality, frequency, and units when applicable. HealthCare.gov warns that preauthorization does not promise cost coverage. DOJ effective-communication guidance informs communication-support planning for covered entities.
Preserve changes as new versions
When the review changes day, time, duration, staff, supervisor, location, modality, access support, or payer configuration, end the earlier version and create a proposed new one. Reopen the affected gates and communicate only after the new configuration clears.
Keep already delivered visits attached to the earlier version. This supports later questions about staff time, documentation, authorization use, and claims without rewriting the schedule that governed the service.
Compare the template with reality
Review delivered visits, cancellations, early ends, staff changes, travel variance, access failures, late records, school or work changes, and closure dates. A recurring template that rarely matches actual delivery needs redesign instead of another automatic copy.
Use a stability test before copying
Choose a recent observation window and compare scheduled with actual start, duration, location, modality, staff, cancellations, and client corrections. Define what variance triggers redesign. A single emergency exception can coexist with a stable pattern, while repeated weekly changes signal that the template is inaccurate.
Ask the person or family whether the pattern still fits ordinary life and communication needs. Treat that input as evidence rather than inferring fit from attendance alone.
Trigger review when a dependency changes between cycles
A fixed cadence is the backstop, not the only revalidation event. Open an exception review after a client or family preference change, plan update, school-calendar shift, authorization change, provider or location status change, staff availability change, supervisor reassignment, leave, transport change, access need, repeated cancellation, safety event, site closure, or system correction. The event record should identify which future visits are affected and which facts remain valid.
Avoid restarting every gate indiscriminately. A new caregiver contact may require communication and representative-record work without changing clinical fit. A new service location can affect travel, facility, payer, staff, and safety evidence at once. Map dependencies so the scheduler knows what must be rechecked, who owns it, and whether the series stays released, becomes partially held, or needs a new version. Preserve the earlier approval and the event that changed it.
Reconfirm the lived schedule, not only the template
Ask the client or authorized representative whether the recurring days, times, setting, communication route, transport assumptions, and handoffs still work. Ask staff whether the full paid day, travel, documentation, supervision, and opening or closing duties match the released pattern. Use accessible methods and minimize sensitive detail in the schedule record. A silent calendar is not evidence that the pattern remains acceptable or workable.
Compare the prior six weeks with the template: actual starts and ends, cancellations, late arrivals, staff substitutions, supervision, authorization use, travel, communication failures, and unresolved corrections. Repeated deviations may show that the nominal series should be redesigned rather than copied forward. Qualified clinicians decide clinical changes, while payer and workforce specialists decide within their own scopes. Revalidation closes only when the next version and every held exception have an owner and disposition.
A fictional six-week review
Seaside Learning reviews 46 recurring series before creating six more weeks. Thirty-eight clear every current gate. Four await family confirmation, two await payer evidence, one lacks supervision, and one needs an access-support change. Revalidation readiness is 38 of 46, or 82.6%.
Keep the eight holds in the original review
The four family-response rows, two payer rows, supervision row, and access row retain separate owners and ages. Do not create future visits for them and later call the schedule tentative. A family-response delay should be measured separately from practice preparation and communication timing.
For the 38 cleared series, count the actual future visits created and verify a sample. One series can create many visits, so series readiness and visit accuracy use different denominators.
Release and monitor
Copy only cleared series, preserve held rows, and version the new block. Track series reviewed, ready, held by reason, copied, changed within two weeks, canceled, inaccessible, and reconciled. Trigger an early review after a material clinical, payer, staff, location, access, or delivery change.
Audit the first two weeks
Compare copied visits with the approved series and actual delivery. Confirm staff, supervision, setting, access support, notices, authorization quantity, documentation, and charge state. Reopen the series when a systematic error appears rather than correcting each visit silently.
Use findings to change the revalidation horizon, source ownership, family outreach, and copy controls. Retain results by schedule version so improvement can be measured accurately across later cycles.
Owner revalidation questions
- Is the review attached to the exact series, version, client, staff pattern, location, and effective period?
- Were client preferences, clinical fit, staff commitment, supervision, payer state, access, travel, and facilities rechecked from current evidence?
- Do event triggers open targeted review between fixed cycles?
- Were actual visits compared with the nominal template over a defined period?
- Are held visits, expiring evidence, and unresolved corrections kept in the original cohort?
- Did the person or authorized representative receive and confirm the released pattern through a usable route?
A copied-forward series should be treated as a new release decision supported by current facts. Prior success can inform the review but cannot replace it.
Related resources
- ABA Schedule Version Rollback Workflow
- ABA Float Staff Assignment Workflow
- ABA Unstaffed Visit Escalation Queue
- ABA Staffing Capacity Buffer Policy
