An ABA weekly capacity forecast estimates usable service capacity for a future week by service, role, setting, time band, geography, supervision, communication access, travel, documentation, training, absence, and contingency. It starts with paid labor and resource availability, then subtracts or constrains nonservice work and hard gates. The result is a configuration-specific range rather than a single total of nominal employee hours.

Choose a capacity unit

Forecast qualified service hours, visits, cases, rooms, routes, or another unit that matches the decision. Segment by role, service, site, modality, day, and time band. Avoid converting unlike configurations into one interchangeable number.

Build from actual availability

Start with scheduled paid hours. Reserve supervision, documentation, training, meetings, travel, transitions, breaks, leave, and known restrictions. DOL Fact Sheet 22 supplies general federal hours-worked orientation.

Apply supervision and access constraints

The June 2026 RBT Handbook provides current certification-supervision requirements. Certification minimums remain distinct from sufficient clinical oversight. Check communication supports, setting, technology, and travel before calling an hour usable.

Use scenarios

Build base, constrained, and disruption cases. Vary absences, callouts, travel, documentation load, room closure, supervision, and access-support availability. State each assumption and preserve a contingency reserve instead of filling every theoretical slot.

A fictional forecast

Juniper Bay ABA has 520 paid staff-hours next week. It allocates 350 service, 55 documentation, 32 travel, 28 supervision, 20 training and meetings, 15 leave, and 20 contingency. The categories total 520 hours. Only the 350 service hours enter the service-capacity layer, then case-specific gates apply.

Compare forecast with actuals

Track usable capacity forecast, released hours, delivered hours, overtime, unused reserve, callouts, service loss, late records, missed supervision, and access gaps. Rebuild assumptions after material variance. Forecast accuracy and safe capacity are separate questions.

Create a weekly resource ledger

List every unique worker, supervisor, room, route, technology dependency, and access resource once. For workers, record paid availability, role, qualifications, approved service and setting configurations, time band, location, planned leave, and current restrictions. For rooms and supports, record the same usable windows and constraints.

Use stable identifiers so the same person or room cannot be counted twice across teams, sites, or tentative schedules.

Separate subtractions from hard constraints

Documentation, meetings, training, breaks, and travel consume paid time and can be subtracted from availability. Supervision, qualifications, location, modality, payer configuration, access support, and room compatibility often constrain which service can use the remaining time. Model both types.

Ten unassigned hours from incompatible workers do not become ten usable service hours by addition. Report stranded capacity and the constraint that prevents a match.

Convert hours into usable appointment shapes

An hour total does not show whether capacity can support the required duration, frequency, transition, and time band. Build standard appointment shapes by service and setting, including travel or room turnover. Apply them to actual open windows.

Report both qualified hours and feasible visit blocks. Fragmented availability may hold several hours but no complete visit. Preserve smaller openings for services that can appropriately use them.

Protect unique-worker and supervision limits

Aggregate capacity by unique worker and calendar. Then apply supervisor availability and the practice's clinical workload limit. Certification minimums are a floor for covered requirements, while safe and effective supervision depends on the actual people, services, risks, settings, and supervisor workload.

Do not assign the same supervisor minute to overlapping obligations. Keep scheduled supervision, case review, observation, feedback, and urgent support visible.

Govern the contingency reserve

State the reserve purpose, unit, owner, minimum threshold, and approved uses. Separate staff callout reserve, clinical escalation time, room or technology backup, and travel disruption capacity where they are not interchangeable. Log every use and the remaining amount.

If routine demand repeatedly consumes the reserve, the base forecast is understated. Rebuild normal capacity instead of resetting the reserve each week without explaining the variance.

Run configuration-specific scenarios

Build at least a base case and one constrained case using named assumptions. Model a supervisor absence, high-callout day, room closure, interpreter unavailability, severe travel delay, or higher documentation load. Recalculate by service, site, time band, and role.

Show which visits would remain releasable and which would be held. Scenario results support decisions; they do not authorize changes to client care or staff assignments.

Reconcile forecast, release, and delivery

At week end, compare forecast usable hours with published schedule hours, actual service, paid nonservice work, overtime, callouts, reserve use, unused compatible capacity, and stranded capacity. Explain variance using controlled reasons and source records.

Keep schedule release, delivered service, claim state, and payment separate. A capacity forecast should improve resource decisions without becoming a billing estimate.

Publish the forecast with limits

Show the version, as-of time, scenario, confidence, accountable owner, and next refresh beside every capacity result. Restrict leaders from copying an old total into hiring, sales, or scheduling decisions after its assumptions expire.

Stress-test the actual weekly roster

Build one base week and at least three variations: a common callout, a supervisor conflict, and a high-travel or high-cancellation pattern. Use named or role-specific committed windows, locations, qualifications, supervision relationships, access skills, and payer configurations. Recalculate service, travel, documentation, meetings, training, breaks, contingency, and closing work. A percentage reduction applied to total hours cannot reveal which appointment shapes disappear.

Track the bottleneck in each scenario. The practice may have technician hours but lack one supervisor window, one communication competency, one site, or one evening travel route. Keep constrained capacity out of the released number and assign the repair. If a scenario depends on overtime, moved documentation, reduced supervision, or uncommitted availability, label it as a decision requiring the appropriate qualified review.

Prevent averages from creating impossible schedules

Publish capacity by day, time band, territory, role, service, and usable appointment shape. Ten one-hour fragments are not one ten-hour block, and hours held by different people cannot always combine. Compare the forecast with specific demand cells before opening starts or recurring visits. When unmatched fragments repeat, route them to territory, schedule design, recruiting, or intake decisions rather than presenting them as unused service opportunity.

Owner weekly-capacity questions

  • Does the ledger start with committed paid time and reserve every required duty?
  • Are hard constraints distinct from estimated subtractions and contingency?
  • Can every released appointment shape map to a qualified person, supervisor, place, payer state, and time?
  • Were common and correlated disruptions tested on the actual roster?
  • Are forecast, offered, released, delivered, canceled, and paid hours reconciled separately?
  • Does repeated variance change the next forecast and an owned capacity decision?

A roster-level capacity example

The weekly ledger contains 160 committed paid hours. After documentation, travel, supervision, meetings, training, breaks, and contingency, 104 potential service hours remain. Configuration testing shows that only 88 fit actual demand because 16 hours are fragmented across the wrong territories or time bands. A supervisor callout scenario reduces release-ready service to 76 hours, even though technician availability is unchanged.

Leadership publishes 88 as the base usable capacity and 76 as the downside case, with the assumptions and affected appointment shapes. The 16 unmatched hours remain visible for territory and schedule redesign. They are not offered as if any open employee hour can cover any waiting client.

Related resources

Sources