An ABA waitlist priority review applies predeclared, lawful, clinically and operationally appropriate factors to a dated cohort while keeping every waiting person visible. It separates clinical priority, service readiness, access needs, payer or financial path, compatible capacity, client preference, aging, and exception authority. The review produces a current rank or tier, reasons, owner, next action, and recheck date rather than a promised start.

Lock the cohort and policy version

Record who entered the review, referral or acceptance date, requested service, setting, geography, time bands, communication and access needs, current clinical state, payer route, last contact, age, and policy version. Preserve inactive, unreachable, referred, and declined records under defined states.

Write priority factors before viewing the list

For each factor, define source, allowed values, weight or tier effect, qualified decision owner, expiration, and tie-breaker. Separate referral age, clinical priority, continuity, compatible capacity, and readiness. Do not use vague fit, motivation, or family reliability labels.

Record the result and explanation for every person. If the policy changes, use a new version and state whether the current cohort will be recalculated. Preserve the prior result for audit.

Separate priority from readiness

A person may have high clinical priority while no qualified accessible configuration exists. Another may be schedule-ready with a later priority date. Report both dimensions. A qualified clinician determines clinical factors; operations verifies capacity and administrative evidence.

Use distinct queue states

Useful states include active review, clinical decision due, administrative evidence due, contact update due, schedule-ready, offer active, offer accepted, waiting after decline, referred, withdrawn, or closed. Give each an owner, next action, and review date.

A schedule-ready record can wait for an opening under the priority rule. A high-priority record with unresolved requirements should receive prompt work without being offered an unsupported start.

Use access needs as implementation inputs

DOJ effective-communication guidance informs aids and services for covered entities. Interpreter, AAC, mobility, sensory, transportation, or alternate-channel needs should route to solution work rather than an adverse priority score.

Make contact review accessible

Use the person's requested channel, language, aid or service, and backup route. Record sent, delivered, acknowledged, reached, correction requested, or failed contact separately. A person should not lose priority because the practice used a channel they could not access.

Set a reasonable update cadence and tell people what the waitlist state means, what could change it, and when they will hear again. Avoid implying a start date before capacity and release gates clear.

Document rules and exceptions

The BACB Ethics Code addresses nondiscrimination, client involvement, competence, resources, timeliness, referrals, and documentation for covered professionals. Define who may approve an exception, evidence, scope, duration, and review date.

Audit priority outcomes for fairness

Review time in each state, offers, starts, referrals, contact failures, access actions, exceptions, and reasons by relevant lawful dimensions with qualified legal and access input. Compare people similarly situated under the same policy version. Investigate unexplained differences rather than assuming the rule is neutral because it is written.

Keep small counts and sensitive information protected. The purpose is to find barriers and inconsistent application, not to publish identifiable family data.

Separate allocation policy from individual advocacy

Publish the priority factors, evidence, effective version, decision owner, exception route, and review cadence before looking at names. Factors should relate to the practice's lawful, clinical, access, continuity, and operating purpose as approved by qualified reviewers. Avoid informal boosts for persistence, personal familiarity, projected revenue, easy schedules, or a person's ability to navigate repeated outreach.

Give applicants or authorized representatives a usable route to correct inaccurate facts and understand the next step. They do not need access to other people's information or a comparative score. When an exception is considered, record the base rule, relevant facts, approving authority, reason, duration, and effect on others in the cohort. Review exception patterns for a policy problem instead of allowing them to become a parallel queue.

A fictional review

Aspen Bridge ABA locks 25 waiting records. Seven are high priority, nine standard, four schedule-ready pending an offer, three need updated contact, and two are referred because required expertise is unavailable. All 25 of 25 retain a current state. Four schedule-ready records enter the next offer cohort.

Clarify the fictional categories

The listed states must be mutually exclusive for the 25-record total: seven high-priority waiting, nine standard waiting, four schedule-ready, three contact-update, and two referred. If high and standard are priority tiers that also apply to schedule-ready records, report them as a separate dimension instead of summing them.

The four schedule-ready records enter a new offer cohort only when a compatible opening exists. Record the sequencing rule, offer recipient, and outcome for all four.

Report aging and outcomes

Track people waiting, age by tier and readiness, rechecks due, offers, accepted starts, declines, referrals, contact gaps, access actions, exceptions, and capacity constraints. Pair averages with medians, ranges, and oldest records. Audit differences across lawful demographic and access dimensions with qualified review.

Use waiting data to change capacity

Map mature demand against released staff, supervision, setting, modality, time band, geography, payer path, and access supports. Identify which constraint prevents the oldest and highest-priority records from receiving viable offers.

Assign recruiting, training, payer, facility, schedule, or referral actions with owners and dates. Measure whether they produce completed starts and sustainable care rather than merely moving records to a new status.

Review the people who never become offer-ready

Age records blocked by missing evidence, unavailable clinical expertise, incompatible capacity, failed contact, or unresolved access work. Assign a next action and referral or continuity route. Queue health cannot be judged only from people who reached the offer stage.

Owner waitlist questions

  • Is the cohort deduplicated, current, and tied to one published policy version?
  • Are priority, clinical fit, payer readiness, schedule fit, access work, and offer readiness separate states?
  • Can every factor be traced to current evidence and an authorized purpose?
  • Do contact methods and response windows work for different language, disability, technology, and schedule needs?
  • Are exceptions, corrections, skipped records, unreachable people, and declines retained for audit?
  • Does aging analysis lead to capacity, outreach, access, referral, or transition decisions with owners?

The review should preserve both fairness and individual context. A ranked list is not permission to offer a configuration that has not cleared its own gates.

A priority-review example

Three people could use one late-afternoon opening. One has waited longer, one has only that usable time band, and one has a current team-continuity consideration documented by the qualified reviewer. The committee applies the approved policy version, verifies the source dates, and records how each factor is weighted or gated. It does not ask which case is easiest to schedule or likely to produce the most revenue.

The selected person still must clear the exact offer-readiness checks and may decline. The other two keep their position and receive the next-update route. If an exception changes the result, its authority, reason, and effect are recorded for fairness review. The example shows that priority decides whose complete configuration is evaluated or offered next; it does not manufacture readiness or guarantee service.

Related resources

Sources