An ABA authorization slot-hold policy defines when a practice temporarily reserves appointment capacity while a payer decision or required update remains open. It names eligible authorization states, hold length, capacity limit, owner, family update cadence, escalation point, release evidence, and exception authority. The policy makes the cost of reserved time visible and prevents indefinite holds based on vague approval expectations.

Define authorization states precisely

Use states such as request unsubmitted, submitted, acknowledged, additional information due, clinical review, approved, partially approved, denied, expired, or closed. Record the payer, product, service, provider, location, date range, requested quantity, source, reference number, and last verified time. A portal message and a formal decision can carry different meanings.

Make each slot hold a separate record

Link a proposed recurring time or visit block to one authorization request and one service configuration. Record the slot, client, service, staff and supervision assumption, location, requested dates and units, submission evidence, current authorization state, hold start, review dates, expiration, family update, and capacity pool.

Keep the calendar reservation distinct from the payer case. Releasing a slot does not close the authorization request, and an authorization decision does not automatically schedule the slot. This separation lets the team make a capacity decision without changing payer history.

State which requests qualify for a hold

A hold rule can consider submission evidence, expected decision window, clinical continuity, staffing lead time, family availability, and the consequence of releasing the slot. Name the role that may approve an exception. The HealthCare.gov preauthorization glossary explains the coverage review and says approval does not promise the plan will cover cost.

Define entry, review, and exit events

An eligible hold begins only after the documented entry event, such as a complete request submitted for a compatible service period. Set a first review, update cadence, maximum duration, and exit events. Exits can include approval and release, denial, request closure, family withdrawal, provider change, expired exception, or a capacity decision under policy.

If the payer asks for more information, record who owns it, the due date, and whether the approved hold period changes. Avoid resetting the hold start date when a supplement is sent. The reserved capacity has been unavailable since the original hold began.

Limit duration and total reserved capacity

Set a review date and maximum hold period from observed operating conditions and governing requirements. Cap the share of a service pool that can sit in unresolved status. Releasing a hold should create a family update and a documented next route rather than silently deleting the prospective visit.

Calculate capacity exposure

Measure held hours or slots against usable capacity for the same service pool and period. If a 40-slot weekly pool holds six slots, exposure is 15%. Also report age: two one-day holds create less operating constraint than six holds nearing expiration.

Use scenario thresholds rather than a single automatic answer. At the warning level, review each case and upcoming demand. At the cap, require named exception authority or release. Do not reserve the same staff, room, or time block for several requests unless the policy explicitly models overbooking risk and family communication.

Preserve clinical and payer authority

The scheduling team controls its reservation policy. It does not issue the payer's decision or the treating clinician's recommendation. The BACB Ethics Code supports clear role, continuity, communication, documentation, and client-involvement boundaries for covered professionals.

Give families a predictable update

At each review date, explain the live payer state, what remains open, whether the slot is still held, the next review or expiration, and who can answer questions. Avoid language that implies approval is expected or guaranteed. If the hold will release, state what that means for the authorization request and the family's place in any waitlist process.

Use the family's preferred usable channel and preserve delivery or response evidence. An expired hold should not leave a family believing a start date still exists.

A fictional hold portfolio

Lakeview ABA has 40 weekly slots in one service pool. Six are held for submitted authorization requests, using 6 of 40, or 15% of capacity. Four holds remain within the seven-day review window. One lacks acknowledgment, and one has passed its approved exception date. Hold conformance is 4 of 6, or 66.7%; both exceptions receive same-day decisions.

Resolve the two exception cases

The request without acknowledgment needs verification of the submission route, exact product and service, receipt evidence, and current payer state. The expired exception needs an authorized decision to extend under a documented basis or release the capacity. Neither should be silently recoded as within policy.

The four conforming holds still need their next review dates and family updates. If two are approved tomorrow, report the slots released to scheduling separately from the payer approvals. If one family declines the offered time, the slot returns to the capacity pool under the waitlist rule.

Measure the full portfolio

Track held slots divided by total usable slots, holds within policy divided by active holds, days held, offers delayed, holds released without approval, and starts completed after approval. Review by payer and reason. A high approval rate alone cannot show whether the hold policy used capacity fairly or communicated changes well.

Audit whether the policy solves the intended problem

Compare time from approval to start, capacity left unused, waitlist offers delayed, holds released before decision, family update timeliness, and exceptions by payer. Review whether a shorter or longer hold would have changed real starts rather than only calendar appearance.

Version the rule when payer practices, staffing lead time, or demand changes. Preserve results by policy version. An authorization slot-hold policy should improve transparent planning, not hide uncertainty or shift financial risk to families.

A hold-expiration example

A practice reserves a Tuesday and Thursday afternoon pattern while a payer request is pending. The payer then approves a different effective date and fewer weekly units than requested. The approval does not automatically validate the original hold. Recheck the exact service, quantity, dates, provider, location, staff, supervision, family availability, and clinical plan before converting any held time into released visits.

If the approved configuration supports only Tuesday, release that day after all other gates clear and return Thursday to capacity under the published policy. Preserve the original two-day request, the payer action, the partial match, family communication, and the date each block was released. This record shows why capacity changed without suggesting that authorization guarantees coverage or payment.

Owner slot-hold questions

Review the oldest holds, total capacity exposure, and exceptions at a fixed cadence. Ask whether every hold still has an eligible request, a named owner, current evidence, a next review time, and an automatic exit condition. Compare held hours with starts actually delivered and with other families' wait time. A policy that repeatedly reserves scarce periods without timely decisions should be shortened or narrowed through the approved governance process.

Related resources

Sources