ABA peak hour coverage is a time-band plan for periods when mature demand and released visits approach usable staffing, supervision, room, travel, and communication-support capacity. It locks the peak cohort, assigns qualified resources, protects documentation and contingency time, and defines stop conditions for new releases. The plan separates possible demand, booked work, current readiness, and actual delivery.

Define the peak band

Use actual request and delivery data to set day, start and end times, sites, territories, services, and review period. Preserve requests outside the band. Recalculate when school calendars, work schedules, service lines, transportation, or seasonal demand changes.

Build from released visits

List client, service, staff role, supervisor, room or route, payer configuration, access support, duration, transition, and downstream commitments. Add mature unscheduled demand as a separate layer so it informs planning without inflating booked capacity.

Protect supervision and nonservice work

The June 2026 RBT Handbook supplies current RBT supervision requirements. DOL Fact Sheet 22 provides federal hours-worked orientation. Include notes, travel, meetings, breaks, training, and reserve.

Set release and stop rules

Define minimum qualified coverage, supervision, rooms, travel margin, access supports, callout reserve, clinical escalation, and maximum unresolved conflicts. Pause new releases when a hard gate fails or the contingency reserve drops below its approved threshold.

A fictional afternoon band

Redwood Path ABA has 44 possible 3 p.m. to 6 p.m. visits. Thirty-six are fully released, four remain unstaffed, two await access supports, and two are clinically held. Peak readiness is 36 of 44, or 81.8%. Only the 36 cleared visits enter the published schedule.

Review actual peak performance

Track demand, released and delivered visits, unstaffed work, room conflicts, travel delays, missed supervision, access failures, service loss, overtime, documentation delay, and reserve use. Segment by service, site, role, payer, and time band.

Lock the peak demand cohort

Define which requests and visits qualify for the peak band, the as-of date, service, site, territory, and maturity rule. Keep active released visits, held visits, schedule-ready demand, and earlier-stage demand in separate layers. Preserve raw counts and requested service hours.

Avoid calling every referral peak demand. The plan should show committed work and credible near-term demand without turning uncertain interest into a staffing requirement.

Build a configuration matrix

For every peak visit, list service, duration, qualified role, supervisor, room or route, setting, modality, payer configuration, access support, travel or turnover, and downstream constraint. Match unique staff and resources to exact requirements.

Report uncovered requirements by type. Ten missing visits may reflect one unavailable supervisor, two inaccessible rooms, or a broader staffing shortage, and each requires a different response.

Use explicit readiness states

Track proposed, gate review, schedule-ready, assigned, released, confirmed, held, delivered, canceled, and reconciled. Keep clinical, payer, staff, supervision, access, and client-choice decisions in separate fields. One green schedule status should not substitute for their evidence.

Give held work an owner, reason, next action, and review time. Do not let incomplete visits disappear from readiness rates.

Preplan callout and overload responses

Define the qualified backup pool, reassignment rules, communication route, clinical review, room or travel effect, and stop condition. Rank response options by safety, continuity, access, and client choice rather than by revenue alone. Preserve each changed assignment and actual service.

If the reserve is exhausted, pause new releases and route affected visits through the approved hold, reschedule, referral, or continuity process.

Protect staff workload

Account for preparation, notes, supervision, travel, breaks, meetings, training, and recovery after demanding work. Measure repeated late documentation, missed breaks, overtime, unscheduled supervision, and cross-site transitions during peak bands. Invite staff corrections through a protected process.

A fully booked peak schedule can be operationally unsafe or unsustainable even when every visit appears assigned. Review capacity before performance deteriorates or turnover rises.

Keep access and family choice in the plan

Confirm usable communication, interpreter or AAC support, accessible rooms, transportation assumptions, and compatible family windows before release. Record offered options and the person's response. Do not label an inaccessible or impractical time as accepted demand.

Analyze which support gaps recur in the peak band. Build standing capacity or alternate routes where evidence shows the need rather than treating each event as an exception.

Measure peak outcomes

Report mature demand, schedule-ready work, released visits, delivered visits, service hours, holds, cancellations, reserve use, callouts, reassignment, overtime, access failures, late records, and client corrections. Use the original cohort and a defined maturity date.

Review whether new staffing, changed hours, room use, or route design improved sustainable delivery. Separate scheduling outcomes from clinical response, claims, and payment.

Review peak decisions after the band closes

Sample overrides, late releases, reserve use, and held visits against the approved rule. Confirm that revenue pressure did not bypass supervision, access, workload, or clinical gates, and assign correction owners where evidence is missing.

Preapprove overload and no-fit routes

For each peak band, define what happens when a callout, late school release, transport issue, supervisor conflict, site constraint, or unexpected demand consumes the reserve. Name the decision owner, update time, coverage search sequence, clinical and payer gates, family communication, and safe stop condition. The plan should support a qualified assignment or a controlled no-fit outcome without weakening requirements as the clock advances.

Model correlated events. One school closure or storm may affect several clients, employees, and routes at once, making a buffer based on isolated absences inadequate. Identify the threshold that activates broader continuity or incident management. Keep held and canceled visits in the original peak cohort so apparent utilization does not improve when the hardest demand disappears.

Measure whether the peak model is sustainable

Track unique clients, requested and released visits, delivered service, callouts, substitutions, travel, supervision, late notes, overtime, split gaps, safety events, communication failures, continuity, and staff and family feedback. Compare by territory and configuration. A high fill rate can still be unstable when it depends on repeated urgent outreach or work outside the planned day.

Owner peak-coverage questions

  • Is the demand cohort mature, time-banded, configuration-specific, and deduplicated?
  • Does assignment-ready capacity protect travel, supervision, documentation, and contingency?
  • Are overload thresholds, backup roles, communication times, and stop rules explicit?
  • Can families receive only verified options through usable routes?
  • Does the plan retain service loss, failed gates, and manual exceptions?
  • Do recurring peak gaps produce recruiting, territory, hours, intake, or service-design decisions?

A correlated peak failure example

A school closure moves five clients into the same earlier afternoon band while two staff members are absent. The ordinary reserve can cover one visit, not the combined shift. The plan activates its broader continuity route, holds unverified configurations, and gives families timed updates and supported choices. It does not fill the board by compressing travel or using staff whose supervision or payer gates are incomplete.

The final cohort records two delivered visits, one accepted alternative, one cancellation, and one unresolved need. Leadership reviews the event as correlated demand, not five unrelated scheduling misses. The result changes the next school-calendar scenario and the threshold for protecting extra capacity during known disruption periods.

Related resources

Sources