An ABA weekly schedule review follows a locked week of visits from readiness through delivery and reconciliation. It examines client choice, staffing, supervision, communication access, payer holds, rooms, travel, documentation, paid time, cancellations, service loss, exceptions, and open corrections. The review pairs rates with raw counts and preserves every held or unresolved visit so owners can improve the system without hiding incomplete work.

Lock the weekly cohort

Define the week, time zone, included services, and snapshot. Keep all released, held, canceled, added, and unresolved visits. Store original schedule version, later changes, client, service, provider, supervisor, setting, modality, access, and payer fields.

Write the inclusion rule before opening the dashboard. Decide whether the cohort is based on visits planned at a weekly cutoff, every visit ever scheduled for that service week, or another clearly defined population. Preserve late additions as a separate count. Keep the same cohort when comparing readiness, delivery, loss, and reconciliation so a team cannot improve a rate by deleting canceled or unstaffed work.

At minimum, retain visit ID, original and final values, service, scheduled duration, client, staff role, supervisor, setting, modality, travel or room resource, access support, payer evidence reference, all change events, actual disposition, service minutes, staff-time reference, note state, charge state, incident reference, and open correction. Store source, author, and time for changes. Limit the weekly reviewer's access to what the role needs and link to restricted records instead of copying sensitive detail into an owner worksheet.

Make the review reproducible

Save the query or report version, extract time, time zone, filters, cohort count, excluded records, and reviewer. Use written definitions for ready, delivered, client-canceled, practice-canceled, unstaffed, held, inaccessible, unresolved, recovered, and closed. If a definition changes, label the first affected week and avoid presenting the new series as directly comparable without an explanation.

Sample several visit rows back to their source systems. Include successful visits and exceptions. Confirm that the schedule, clinical record, time record, notice, payer state, and downstream status refer to the same visit while retaining their distinct meanings. A dashboard total is useful only when an authorized reviewer can reconstruct its components.

Review readiness and delivery separately

Calculate ready visits divided by the locked cohort at the chosen cutoff, then delivered visits divided by the same original cohort. Report changed, canceled, held, unstaffed, inaccessible, and unresolved visits by counts and hours. Link makeups without erasing loss.

Pair every percentage with its numerator, denominator, cutoff, and unit. Visit yield and hour yield can move differently because visits have different lengths. Report planned hours, delivered hours, and unrecovered lost hours alongside visit counts. A makeup belongs in a recovery measure linked to the original loss; it does not turn the original visit into delivered-as-planned.

Use separate measures for separate questions. Examples include:

  • cutoff readiness: ready visits divided by the locked visit cohort;
  • delivered yield: visits delivered divided by that same cohort;
  • planned-hour delivery: delivered service hours divided by hours planned at cutoff;
  • access failure: visits not delivered because a required support failed divided by the locked cohort;
  • closeout completeness: visits with final operational disposition divided by the cohort;
  • correction aging: open corrections grouped by age and consequence.

Stratify only where the groups are large enough to interpret responsibly and the use is appropriate. Site, time block, workflow version, service, travel pattern, and access-support type may reveal system conditions. Avoid staff ranking from small, mixed, or clinically different cohorts.

Keep professional and payer authority separate

The BACB Ethics Code supports attributable clinical decisions for covered professionals. HealthCare.gov cautions that preauthorization does not promise cost coverage.

A weekly review can show that clinical evidence or payer evidence was missing at a release checkpoint. It should not reinterpret the clinical decision or declare a service payable. Qualified clinicians own treatment, supervision, risk, and documentation decisions within scope. Credentialing owners confirm qualifications. Payers decide authorization and claim outcomes under their processes. Operations owns scheduling workflow and resources. Privacy and security roles govern access, disclosure, and incidents. Legal and workforce specialists interpret employee-time obligations.

When one operational defect touches several lanes, create linked actions with separate owners. For example, a visit may have a late staff change, missing supervision confirmation, extra travel time, and a corrected claim field. One summary label would conceal distinct decisions and deadlines.

Include access and workforce load

DOJ effective-communication guidance informs access for covered entities. DOL Fact Sheet 22 supplies federal hours-worked orientation. Review travel, waiting, notes, meetings, training, supervision, overtime, and missed breaks alongside visits.

Treat an unavailable interpreter, failed accessible notice, missing AAC support, inaccessible room, or unusable technology as an operational access exception with a named owner. Do not classify the visit as ordinary client cancellation unless that is what the evidence supports. Review whether the same support, vendor, site, communication route, or handoff recurs.

Compare staffing demand with actual work patterns. Show planned direct service, actual direct service, travel, waiting, documentation, meetings, training, supervision, and corrections separately. The review can surface late schedule changes that create additional work. The appropriate payroll or legal owner determines compensability under the facts and applicable law.

Review exceptions and escalation performance

For each exception category, examine count, affected visits and hours, age, consequence, detection point, source, owner, escalation time, final disposition, and repeat pattern. Separate events detected before the readiness cutoff from those arising later. This distinction shows whether the control failed to find existing gaps or a new event occurred after review.

Track whether required family notices were sent through the preferred usable route, whether delivery failed, and whether a backup was attempted. Keep message content minimal and use approved systems. Link privacy, security, safety, or clinical incidents to their restricted workflows without duplicating protected narratives in the weekly report.

A fictional week

Pine Coast ABA locks 120 visits. One hundred ten are ready by the cutoff, 104 are delivered, six client-cancel, four practice-cancel, three remain unstaffed, two are held, and one is inaccessible. Delivered yield is 104 of 120, or 86.7%.

Those listed exception counts total 16 while 104 visits were delivered, accounting for the full cohort of 120. The practice also reports 267 of 300 planned hours delivered, or 89.0%. The difference between visit yield and hour yield reflects the lengths of the visits that did not occur. It is not an arithmetic error.

Five makeup visits occur the following week. They are reported as 5 recoveries linked to the 16 lost visits. The original week's delivered yield remains 104 of 120. The review shows which losses remained unrecovered, the time to offer, whether the family accepted, and whether the later service met current clinical, staffing, access, and payer requirements.

Assign corrective work

Record issue, affected cohort, consequence, source, owner, action, due date, and retest. Track readiness, delivery, service loss, access gaps, late notes, paid-time corrections, payer rejects, incidents, and unresolved work by workflow version.

Choose actions that address the supported condition. A recurring route problem may justify new travel buffers. Late access confirmations may require an earlier vendor checkpoint. A high unresolved count may require clearer state definitions or backup ownership. For every change, set a baseline, expected signal, test period, responsible owner, review date, and rollback or adjustment rule. Monitor for unintended effects on client choice, staff workload, privacy, continuity, and access.

Owner questions for the weekly meeting

  • Is the cohort locked, and are late additions visible separately?
  • Do visit and hour measures show their raw denominators and cutoffs?
  • Which exceptions were present before readiness review, and which arose later?
  • Are client choice, assent-related concerns, communication support, and access failures represented accurately?
  • Are clinical, payer, workforce, privacy, and operational states kept separate?
  • Can a reviewer trace a sample from original schedule through changes and actual outcome?
  • Which open corrections lack an accepted owner or due time?
  • What one corrective action has the strongest evidence, and how will the team retest it?

Limits of a weekly review

This review is an editorial quality-control design. It does not establish clinical quality, medical necessity, payer coverage, claim payment, legal compliance, or correct wage treatment. Rates can be misleading when definitions, service mix, cohort size, or data completeness differ. Weekly aggregates can also conceal an individual safety, access, or continuity concern that needs immediate action. Owners should have qualified clinical, payer, workforce, privacy, security, accessibility, and legal reviewers approve the definitions, access controls, response routes, and retention rules that apply.

Related resources

Sources