ABA client scheduling preferences are the person's and family's stated choices about days, time bands, frequency pattern, location, modality, travel, transportation, communication supports, and flexibility. A dated record helps operations find viable options while a qualified clinician owns clinical recommendations. Preferences remain distinct from availability, approved services, payer status, capacity, and a released schedule, and they can change at any time.

Ask in usable time bands

Collect preferred, acceptable, and unavailable windows with effective dates and time zone. Record fixed school, work, care, transportation, meal, rest, and family commitments only to the extent needed. Avoid forcing a single ranked choice when several patterns could work.

Use structured fields that support real offers

For each day or recurring pattern, capture earliest start, latest end, minimum or maximum visit length if relevant, frequency limits, travel buffer, and whether the window is preferred, acceptable, or unavailable. Add effective and expiration dates, the person who supplied the information, confirmation channel, time zone, and the service or setting it covers. Record one-time exceptions separately from the recurring record. Free text can explain context, but the scheduler needs structured values to test an offer consistently.

Capture place, modality, and access

Ask about center, home, community, or telehealth preferences where those routes are available, plus travel limits and transportation. DOJ effective-communication guidance informs support selection for covered entities. Record language, interpreter, AAC, mobility, sensory, and alternate-channel needs.

Keep preference, access requirement, and safety condition distinct. A preferred center is a choice. A wheelchair-accessible entrance or interpreter may be an access requirement. A current clinical or safety restriction may require qualified review. Each field needs an owner and a route for questions. Do not place diagnoses, family conflict, or unnecessary medical detail in a scheduling note that broad staff can see.

Separate choice from clinical recommendation

The BACB Ethics Code addresses client involvement, consent and assent when applicable, competence, risk, and documentation for covered professionals. A qualified clinician reviews clinical fit. Operations tests configurations against the preference record.

Turn the record into an offer workflow

When capacity opens, compare the exact configuration with active preferences and requirements. Record the proposed day, time, setting, modality, staff role, start date, expected duration, transportation assumption, and response deadline. Label the result offered, accepted, declined, alternative requested, expired, or withdrawn. A declined offer remains useful evidence and should not be recoded as family noncompliance. When no acceptable configuration exists, keep the case visible with the mismatch reason, next search action, and recontact date.

Rank workable patterns without flattening the person's choices

Many records contain more than one feasible pattern. Let the person or authorized representative distinguish a first choice from other genuinely workable choices, and record whether the ranking applies to a whole week or to particular days. A family might prefer four early-afternoon visits but accept three later visits if they occur at one site and avoid a long commute. The record should preserve that tradeoff instead of reducing both patterns to the same available flag.

When two people need the same scarce window, use a documented allocation policy and case-specific qualified review where required. Relevant factors might include how long a complete request has been ready, whether only one time band is usable, continuity with an existing team, a time-limited authorization or transition, and the practice's stated service-area policy. Owners should approve the factors and the escalation path. Schedulers should not invent priority from diagnosis, family persistence, projected revenue, or personal familiarity.

Use a bounded trial when fit is uncertain

A possible window can be tested without presenting it as a permanent arrangement. Document the trial dates, exact days and times, location, staff configuration, transportation assumption, clinical approval, payer checks, and what both sides will evaluate. Agree on a review date and on what happens if the pattern is unsustainable. The permanent preference record remains intact until the person confirms a change.

Suppose a family prefers 3:30 p.m. but can try 4:15 p.m. for three weeks while a school bus route changes. The offer record should say that 4:15 is a temporary accepted trial, not the family's new preferred time. At review, the practice records attendance, travel reliability, clinical observations within the appropriate record, and the family's experience. The next step could be continuation, a modified option, return to the search queue, or a qualified clinical discussion. No default conversion should occur merely because the trial visits took place.

Keep no-match cases active and specific

An open mismatch needs a next action more informative than "waiting for staff." Identify the blocked time band, location, service configuration, access support, transport issue, or payer dependency; the person responsible for the search; the last meaningful contact; and the next review date. Reconfirm the person's choices before offering a materially different arrangement. If a new option falls outside the acceptable range, describe it as an alternative for consideration rather than evidence that service was available.

Owners can review aggregated mismatch cells to choose a response. Ten current requests for the same late-afternoon territory may support targeted recruiting or a center-hours experiment. Several transportation-related mismatches may justify a partnership review. A single unusual configuration may require individualized planning. The preference record therefore supports both respectful communication and investment decisions without turning family constraints into performance failures.

Version the record

Store person or family source, collected date, effective period, flexibility, confirmed constraints, preferred contact route, and next recheck. Preserve prior versions so a later schedule decision can be evaluated against the preferences known at that time.

Trigger recheck after a school-calendar change, job change, move, transportation change, health transition, caregiver change, prolonged hold, repeated declined offers, or request from the client or authorized representative. Avoid overwriting the earlier record. Close it with an end date and link the new version. This provides evidence of what the scheduler knew at the time without presenting an old window as current.

A fictional preference review

Silver Pine ABA reviews 18 active records. Fourteen were confirmed within the last 90 days, two changed after school schedules shifted, and two need recontact. Current confirmation is 14 of 18, or 77.8%. The two changed records keep both versions and affected visits.

Measure fit after release

Track preference records current, offers within acceptable windows, accepted and declined options, schedule reversals, transportation conflicts, access actions, and client-reported fit. A high match rate cannot show clinical quality or whether a person felt free to decline.

Review mismatches without blaming the family

Group mismatches by time band, service, site, modality, travel zone, access support, staff qualification, and payer configuration. Preserve open cases and their age. A high-demand evening window may call for recruiting or a different service model, while a single scheduling conflict may need one alternative offer. Compare the number of acceptable-window offers with all mature offers, and report declined offers by the family's stated reason when supplied. Use the review to change capacity assumptions, not to pressure people into unavailable times.

Owner checklist

  • Are preferred, acceptable, and unavailable windows separate?
  • Is every record effective-dated, source-labeled, and easy to change?
  • Are access requirements protected from unnecessary visibility?
  • Does each offer show the exact configuration and response state?
  • Are declined offers and open mismatches still visible?
  • Can the practice explain how preference data changed recruiting and capacity decisions?

Related resources

Sources