An ABA schedule demand heatmap shows where mature service requests concentrate by service, setting, geography, day, time band, access need, payer or financial route, and readiness state. It uses a defined cohort and separates inquiries, clinically eligible requests, accepted offers, and schedule-ready cases. Owners can compare demand with qualified capacity without presenting a waitlist total as promised starts or approved care.
Define the demand cohort
Choose a received-date window and an exposure cutoff. Include one row per request with requested service, setting, geography, time bands, start horizon, access needs, payer route, current clinical and operational state, and last verification date. Preserve withdrawn, referred, waiting, and unresolved requests.
Create a demand record before drawing the heatmap
Use stable categories and retain the source of every field:
| Field group | Values to capture |
|---|---|
| Request | Received date, service, setting, modality, start horizon |
| Availability | Days, time bands, geography, travel limits |
| Access | Language, communication, mobility, sensory, transport |
| Readiness | Administrative, clinical, payer, family, staffing states |
| Outcome | Waiting, offer, accepted, started, referred, withdrawn |
Collect only what the current planning decision needs. Keep clinical and other sensitive detail in its controlled record.
Use maturity layers
Report inquiries received, administratively eligible requests, completed clinical decisions, accepted offers, and schedule-ready cases separately. HealthCare.gov cautions that preauthorization does not promise cost coverage. Payer status remains one layer rather than proof of readiness.
Choose geography and time bands carefully
Use territories that match how the practice actually schedules, such as center catchments, drive-time zones, telehealth jurisdictions, and staff starting areas. Record the version. ZIP codes and straight-line distance can conceal bridges, traffic, rural travel, and boundaries that change authority or payer configuration.
Choose time bands narrow enough to guide capacity but broad enough to protect privacy and remain stable. Preserve a person's exact availability in the operational record while displaying aggregated cells to owners.
Make access visible
Map interpreter, communication, mobility, sensory, transportation, and scheduling supports as implementation requirements. DOJ effective-communication guidance informs how covered entities select suitable aids and services. Access needs should shape capacity planning instead of lowering a person's demand status.
Prevent double counting across cells
A request can fit several time bands, locations, or modalities. Count unique requests for total demand and clearly label cell counts as possible placements. Do not sum overlapping cells as if each represented a different person. Store the acceptable combinations so matching tools can use them without inflating demand.
When a person changes availability, preserve the earlier version and effective date. A request that has started service leaves the waiting cohort under the predeclared rule rather than disappearing retroactively from older reports.
Compare demand with usable capacity
Overlay qualified staff, supervision, rooms, travel zones, modality, access supports, and released payer configurations. Use the same time bands and geography definitions on both sides. A nominal staff hour outside the required configuration supplies no usable capacity for that cell.
Calculate the gap by configuration
For each cell, show mature requested visits or hours, schedule-ready demand, currently released capacity, offers in progress, and the resulting gap. Use the smallest constrained resource, such as supervisor time, interpreter availability, accessible room, or payer-recognized staff.
Keep forecast hires and rooms outside current capacity until their release gates clear. Display them as planned capacity with assumptions and expected dates. This lets owners see opportunity without promising starts that the practice cannot deliver.
Show uncertainty instead of painting every cell as exact
Demand records often contain dates, preferences, and service details of different quality. Give each cell an evidence label such as confirmed and current, current but flexible, incomplete, stale, or inquiry only. Show the confirmed count separately from the possible range. A cell with eight current schedule-ready requests is operationally different from one with three confirmed requests and five unverified inquiries, even when both display eight on a single-color chart.
Record why an item is uncertain and the next action. A missing current preference needs outreach, while an unresolved clinical configuration belongs with the qualified reviewer and a payer question needs written verification. Do not let the heatmap silently treat an unavailable family, expired authorization, or incomplete intake as zero demand. Preserve the record in its maturity layer and age it from the event that made action possible.
Turn high-gap cells into bounded experiments
For each material gap, identify the decision the heatmap supports: targeted recruiting, territory redesign, a temporary operating-hours test, transportation work, supervisor allocation, space planning, or an intake boundary. Define the affected cell, baseline, intervention, owner, start and end dates, cost, continuity safeguards, and measures. Keep clinical recommendations, payer decisions, employment terms, and client choices with their responsible roles.
Suppose the Tuesday and Thursday 3:30-to-6:30 p.m. north-territory cell contains 12 mature requests and six assignment-ready hours. The owner might test a part-time recruiting campaign and one route redesign for six weeks. Track applicants who reach commitment, usable service hours, travel, supervision, accepted offers, delivered visits, and effects on nearby cells. If the gap persists, the next decision uses the observed result rather than treating the original heatmap as a permanent forecast.
A fictional heatmap
Meadow Point ABA locks 50 mature requests. Twenty-two request weekday after-school hours, 14 mornings, nine weekends, and five mixed windows. Only 13 after-school requests are schedule-ready. The heatmap therefore reports 22 requested and 13 ready, while all nine pending after-school requests keep a state, owner, and age.
Read the fictional cell in context
The 22 after-school requests show demand for that band, while 13 show the subset ready under the defined gates. The nine pending records may need different actions, so report clinical review, payer evidence, family response, staffing, or access support separately. Do not call the 13 a conversion rate unless the cohort and event support that use.
Compare the 13 ready requests with released after-school capacity using the same service, setting, geography, and period. A company-wide capacity total would not answer whether those specific requests can start.
Review changes over time
Track cohort size, state transitions, ready demand, usable capacity, days waiting, offers, starts, declines, access gaps, and service-line losses. Compare versions by the same definitions. A shift in referrals, payer rules, school calendars, staffing, or family preferences should trigger a fresh map.
Use the heatmap for explicit decisions
At each review, choose which capacity to recruit, develop, move, or stop advertising. Record the evidence, owner, budget or operational dependency, and next review. Keep client-level offers under the approved sequencing and clinical processes.
Measure whether the action changed real start times, service reliability, and access rather than only filling the visual gap. Retain historical heatmaps so seasonal changes and repeated shortages remain visible.
Owner heatmap questions
- Are demand units deduplicated, mature, current, and assigned to one primary comparison cell?
- Does each cell separate confirmed requests, flexible possibilities, incomplete records, and inquiry-only demand?
- Is capacity assignment-ready after travel, supervision, documentation, access, payer, and workforce gates?
- Can reviewers see both unique people and requested hours without mixing the denominators?
- Does every high-gap cell have a decision owner, bounded response, and review date?
- Will the next heatmap use the same definitions or clearly explain a changed cohort?
The owner should be able to trace a colored cell back to its included records and forward to a specific decision. If either link is missing, the heatmap remains descriptive rather than decision-ready.
Related resources
- ABA Staffing Capacity Buffer Policy
- ABA Scheduling Data Quality Audit
- ABA Float Staff Assignment Workflow
- ABA Weather Disruption Scheduling Plan
