An ABA scheduling capacity reservation policy sets aside defined slots or staff time for an approved cohort or purpose, such as assessments, urgent continuity needs, interpreters, supervision, or a planned service line. The policy identifies the inventory, eligibility, priority, hold duration, owner, release triggers, exception route, and reporting. It protects access and readiness while preventing indefinite hidden holds, informal favoritism, and false promises of care or coverage.

Define the reserved inventory

Name the slots, staff roles, rooms, time bands, territories, modalities, or percentage of capacity reserved. State the service, setting, effective period, and whether inventory is physical, staffed, clinically usable, or only a planning placeholder. An ABA scheduling capacity reservation policy should show what ordinary demand can still use. Avoid reserving a percentage without translating it into visible units and dates that schedulers can manage.

State the approved purpose

Examples include initial assessments, urgent continuity, supervision observations, interpreter-supported visits, school breaks, staff training, outage recovery, or a new service pilot. Record why reservation is needed and what evidence will show whether it worked. Keep different purposes in separate pools when eligibility and release rules differ. A reserve created for clinical continuity should not quietly become executive or referral-source preference.

Define eligibility and priority

Use observable, approved criteria with a named decision owner. State cohort entry, evidence, clock, tie-breaker, and removal. Preserve people considered, eligible, placed, declined, expired, and waiting. Review criteria for disability, language, payer, geography, and other access effects. A person's accommodation or communication need should lead to support planning rather than an adverse priority adjustment.

Keep clinical authority separate

A qualified clinician decides clinical need, appropriateness, risk, and recommendations within scope. The BACB Ethics Code supports competence, client involvement, risk, continuity, and documentation for covered people. Operations administers the approved pool and capacity evidence. Reservation status should never become a substitute for assessment, consent, staffing, or case-specific clinical release.

Keep payer status scoped

A pool may support people awaiting authorization or a specific payer configuration. HealthCare.gov cautions that preauthorization does not promise cost coverage. State whether capacity can be held before payer evidence, for how long, and under which written rule. Preserve benefit, network, authorization, estimate, scheduled service, claim, adjudication, and payment as separate states. Avoid representing a reserved slot as covered care.

Protect accessible use

Consider language, interpreter lead time, AAC support, mobility, sensory needs, transportation, and usable communication when designing the inventory. DOJ effective-communication guidance informs suitable aids and services for covered entities. Reserve the support and the visit together when both are required. Track unmet access work visibly. A nominal open slot is not usable capacity if the necessary support cannot be ready.

Set hold and release clocks

Define when the hold starts, maximum duration, reminders, revalidation, expiration, and release owner. Use business or calendar time consistently. State what pauses the clock and keep paused records visible. Before release, confirm whether a timely response, pending qualified decision, accessibility action, or documented exception preserves the hold. Avoid resetting age when ownership changes or the person moves between internal lists.

Build the capacity ledger

Create one row per reservable unit with slot or block ID, service, site, modality, date and time, staff and room dependencies, access-support dependencies, reservation purpose, eligibility rule version, current holder when applicable, hold start, response deadline, expiration, release trigger, owner, and status. Link offers and responses in a separate event table so the ledger preserves the sequence. Statuses may include available, held, offered, accepted pending gates, released, expired, unavailable, and delivered. Show which fields reflect actual staffed capacity and which remain forecasts. Add alerts for holds nearing expiration and units whose required support is missing. Reconcile the ledger with the live schedule at least at the cadence needed for the pool. This prevents a reserved slot from existing in policy while disappearing from the calendar or remaining blocked after the hold ends.

Offer and accept the reserved slot

Describe the date, time, service, setting, modality, duration, assumptions, response window, and next steps through the usable channel. Record sent, delivered, acknowledged, accepted, declined, expired, and change-requested states. Recheck staff, supervision, payer, access, and clinical gates before final release. One person's decline returns capacity under the published rule and should not reduce their standing in another eligible pool unless policy says so.

Set a monthly reservation review

Lock the month's reserved inventory and follow each unit through available, held, offered, accepted, released, delivered, expired, or unused states. Separately follow every eligible person through offer and outcome. Compare access-support readiness, preferred-window fit, payer and clinical holds, communication failures, service loss, and wait age. Review people who remained eligible without an offer and capacity that expired without reaching general demand. Ask whether the pool size, time limit, priority rule, or outreach process created the result. Keep next-month changes versioned and avoid reallocating capacity solely to maximize a utilization percentage. The purpose of the reserve, fairness, client choice, clinical appropriateness, and reliable delivery should all appear in the decision. Document dissent and unresolved evidence when leaders choose a different pool size. Set the next review date before closing the monthly record. Publish the internal outcome and rationale to the staff administering the policy.

A fictional reserve

Silver Birch ABA reserves 16 weekly assessment slots. Twelve are offered to eligible families, nine are accepted, two are declined, one expires, and four remain available under the reserve. Offer acceptance is 9 of 12, or 75%. Utilization is reported later from delivered visits, not from accepted offers. The four unused slots follow the published release trigger rather than an informal manager decision.

Review fairness and opportunity cost

Compare who receives, declines, expires, and waits for reserved versus general capacity. Examine lead time, access actions, payer path, geography, preferred windows, and service outcomes. Calculate general-demand requests that could have used expired reserved slots. Use the findings to adjust pool size, criteria, outreach, or release timing. Avoid interpreting lower acceptance as lack of interest before checking whether offers were accessible and workable.

Govern exceptions

Record the requested exception, criteria missed, reason, urgency, affected inventory, authorized decision-maker, conditions, expiration, and communication. Review similar cases consistently. Separate emergency response and legally required action from routine allocation exceptions. Publish the route internally and keep exceptions in reporting. Repeated approvals may show that the base criteria no longer fit actual demand and deserve formal revision.

Measure the full funnel

Report reserved units, eligible people, offers, acceptances, releases, expirations, delivered visits, service loss, unused capacity, wait age, access actions, exceptions, and general-demand opportunity cost. Define every denominator and maturity window. Pair pool utilization with client choice, clinical appropriateness, staff burden, fairness, and outcomes. A fully booked reserve can still perform poorly if visits cancel, supports fail, or the wrong cohort receives the capacity.

Related resources

Sources