An ABA scheduler daily checklist is a repeatable control routine for the locked visit cohort, new requests, client and staff changes, supervision, communication supports, payer holds, rooms, travel routes, conflicts, notices, and reconciliation. It assigns each review a time, source, owner, decision boundary, and evidence. Urgent safety, clinical, access, privacy, and workforce matters route to their qualified owners.

Open with the current cohort

Lock the day's visits and record late additions separately. Confirm client, service, time, duration, assigned staff, supervisor, location, modality, room or route, access support, payer state, and release status. Preserve held and canceled visits.

Use a defined snapshot time and give the file or report a version identifier. A useful daily row includes the visit ID, planned start and end, client and guardian contact route, service and place of service, staff role and credential state, supervising clinician, authorization reference, requested communication support, travel or room resource, latest confirmation, and current owner. Limit the scheduler's view to the information needed for the work. Sensitive clinical detail belongs in the appropriate clinical record, with a link or status flag when the scheduling decision depends on it.

Choose a small set of operational states that have written definitions. For example:

  • Ready: every required release field is supported by current evidence.
  • Held: the visit remains planned, yet a required item is open and service cannot be released under the practice rule.
  • Canceled: an authorized person made a final cancellation decision and the reason and notice are recorded.
  • Changed: an approved replacement value is recorded while the original remains visible.
  • Unresolved: the team lacks enough evidence to select a final state before the next escalation time.

Color can help a dashboard scan, but the stored state, reason, time, and source are the record. A red cell with no owner is not a control.

Set a daily review rhythm

Run the checklist at named times that fit the practice, such as opening, before the first travel block, midday, and closeout. The opening review catches overnight messages and callouts. A pre-service check confirms same-day changes that affect safe release. Midday focuses on late-day capacity and unresolved holds. Closeout reconciles actual outcomes and hands off open work.

Each checkpoint should identify the reviewer, snapshot time, visits examined, exceptions found, actions taken, and next review time. A missed checkpoint becomes its own exception. If the scheduler is absent, the backup should know which report to open, which states they may change, and whom to contact for reserved decisions.

Review new and changed work

Triage availability changes, callouts, reschedule requests, payer updates, site issues, and access needs. Record received time, affected visits, source, current state, owner, due time, and escalation. Avoid resolving reserved decisions in the scheduling queue.

For every change, retain the original value and append the proposed value, requester, request time, effective time, reason category, source location, approver when required, notice status, and linked visits. A family request, staff report, payer portal message, and clinician instruction carry different authority. The scheduler can authenticate the source and route the request without interpreting a clinical instruction or making a benefits determination.

Use a two-step release for consequential changes. One person enters or proposes the change. The designated owner verifies any required clinical, workforce, access, payer, or safety condition and records the disposition. Routine corrections may use a simpler rule, but that rule should name the fields and circumstances that qualify. Bulk changes deserve a preview showing every affected visit before release.

Keep authority visible

The BACB Ethics Code supports attributable clinical decisions for covered professionals. HealthCare.gov cautions that preauthorization does not promise cost coverage. Scheduling coordinates the evidence and applies approved release rules.

Write the authority map beside the checklist. A qualified clinician owns clinical appropriateness, treatment configuration, risk precautions, and supervision decisions within scope. Credentialing or compliance staff confirm qualification evidence. The payer or delegated reviewer determines benefit and authorization status under the applicable plan. Payroll or human-resources staff interpret paid-time questions under current law and policy. Privacy or security owners handle questionable disclosures or misdirected messages. Operations owns the queue, evidence completeness, defined release rules, and timely escalation.

When two sources conflict, hold the affected field and show both sources. Record who will decide, what additional evidence is required, and the last safe decision time. A newer message does not automatically outrank an authoritative record.

Check communication and access

DOJ effective-communication guidance informs usable communication for covered entities. Confirm interpreters, AAC-related supports, alternate formats, preferred channels, delivery states, and backups. Route a missing support as an access action, not client unavailability.

Record what was requested, who requested it, the approved or selected support, vendor or staff assignment when applicable, confirmation time, and backup. Do not use an ordinary reminder as proof that a person received an accessible notice. When an AAC device, interpreter, communication partner, sensory support, or accessible transport arrangement is required for the planned setting, show that requirement as a release field.

Keep message content minimal. Use verified contact routes and approved systems, check the recipient before sending, and record delivery outcome without copying unnecessary protected information into a scheduling note. A misdirected message, suspected account compromise, or unauthorized access follows the privacy or security incident path. It should not be buried under a generic communication-failed label.

Work exceptions to a decision

An exception queue should display affected visit, consequence, age, current state, last action, next action, owner, due time, and escalation level. Set escalation times from the visit's start and the consequence of delay. A missing room for a visit starting in 30 minutes needs a different route from a routine preference update for next month.

Define safe stop conditions. Examples include missing qualified staff, an unresolved clinical instruction, unavailable required access support, unsafe site conditions, a payer hold under the practice's financial policy, or a conflict that could expose private information. The designated owner decides the disposition within their authority. If no decision arrives by the cutoff, the published fallback applies and the family receives a usable notice through the appropriate route.

A fictional morning check

Canyon Grove ABA locks 34 visits. Twenty-nine are ready at the first review. Two await staff, one awaits access support, one has a payer hold, and one needs clinical review. Readiness is 29 of 34, or 85.3%. Each held visit has an owner and next check.

At the second review, one staff assignment and the access support are confirmed, bringing readiness to 31 of the original 34, or 91.2%. The payer hold remains a payer-state issue, and the clinical question remains with the qualified clinician. The final unstaffed visit is offered an approved alternative. The team reports both snapshots and keeps the denominator at 34. It does not recalculate the rate after removing held visits. At closeout, each of the original 34 has an actual outcome linked to its morning state.

Close the day

Reconcile actual visit state, staff time, service time, notices, documentation, authorization use, charges, incidents, and open corrections. Carry forward only items with a named owner, age, next action, and due time. Review repeated misses by workflow version.

Treat service delivery, documentation completion, charge release, claim submission, adjudication, and payment as separate events. A completed visit may still require a note correction. A valid authorization may still yield a denied claim. Closeout should preserve these distinctions and link downstream work without changing the visit's actual service state.

Owner review questions

Before adopting the checklist, ask:

  • Which snapshot defines the daily denominator, and how are late additions displayed?
  • Which fields must be supported before a visit can move to ready?
  • Who can propose, approve, release, cancel, and correct each type of change?
  • What forces a clinical, access, privacy, workforce, payer, or safety escalation?
  • Which system is authoritative for staff qualifications, clinical direction, payer evidence, and contact preference?
  • Can an auditor reconstruct the original plan, change, decision, notice, and outcome?
  • Does the backup scheduler have the access and training needed to run the control?
  • Which daily exceptions will receive a weekly pattern review?

Start with a shadow run on one full day. Lock the cohort, run the checkpoints, and compare the checklist with actual outcomes without changing the live release process. Resolve unclear definitions and authority gaps before the checklist becomes a production control.

Limits of the checklist

This checklist is an editorial operating design. It does not determine clinical appropriateness, establish benefits or payment, interpret wage-and-hour law, authorize disclosure, verify licensure, or replace emergency procedures. Applicability depends on the practice's services, locations, contracts, systems, workforce rules, privacy obligations, and state law. Qualified owners must approve the release gates, record access, retention, escalation, and exception rules before use. A daily control can show that required evidence is present; it cannot prove that every underlying professional judgment or external source is correct.

Related resources

Sources