Client Preferences Handoff for New ABA Staff

Build the client preferences handoff

Use a short preference profile with an owner and review date. Mark what the client said, what others observed, what remains uncertain, and what changed recently. Avoid turning a preference into a fixed trait or assuming one person's report authorizes every disclosure.

Protect communication and client choice

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Ask the client how introductions, choices, pauses, and corrections should work.

Keep authority and source scope clear

The CASP public summary supports individualized assessment, planning, implementation, and evaluation in its autism-treatment scope.

The BACB Ethics Code addresses competence, continuity, client involvement, consent and assent when applicable, documentation, supervision, and evaluation for covered behavior analysts.

The BCBA Test Content Outline covers assessment, measurement, supervision, and data-based decisions as examination content. These sources do not create one universal staffing policy.

A practical example

Kai selects quiet arrival, written choices, no surprise touch, and a five-minute settling period. His caregiver adds that crowded entryways are difficult. The new staff member verifies the profile with Kai at the first visit.

Questions families can use

Ask who owns the transition, which role and qualifications apply, what the client communicated, which plan and payer states are current, what evidence was handed off, what remains open, and when the family receives follow-up.

Review the handoff

Review it before every handoff.

Build the client-preference handoff

The client-preference handoff helps a family decide which purpose-needed preferences and supports new staff need, who supplied each fact, and how the client can verify or change it. It should capture client's own words or AAC messages, caregiver context, prior observations, preferred name and communication, sensory and interaction supports, privacy, breaks, stop signals, health or safety needs, disliked approaches, uncertainty, owner, access limits, and review date. Add the source, responsible role, effective date, current state, and next review to every unresolved item so the transition can be reconstructed later.

Use plain states that match the client-preference handoff: proposed, verified, scheduled, active, held, declined, transferred, superseded, or closed with reason. Keep a staffing assignment separate from clinical readiness, client choice, payer acceptance, a delivered service, and a paid claim. Those events can happen on different dates.

Decide what the family needs to know

For this client-preference handoff, the family needs enough information to plan and protect continuity without receiving private information about another person's employment, health, or personal circumstances. Explain the care impact, responsible roles, dates, current evidence, uncertainty, options, and next update. Use a broad reason category only when it is accurate and appropriate to share.

Within the client-preference handoff, preserve the client's direct input through speech, AAC, gesture, writing, behavior interpreted cautiously, or another reliable route. A caregiver may add history and context. Label who supplied each statement and keep a family relationship, emergency-contact label, and legal decision authority as separate facts.

Follow the transition in order

1. Invite direct client input through a usable communication route. Open the client-preference handoff with the exact event, date, and owner.
2. Label caregiver and prior-staff information by source. Record the interim answer and any limits the family needs for planning.
3. Limit the handoff to information needed for the assigned role. Preserve the evidence, source, reviewer, and unresolved gate.
4. Ask new staff to verify rather than stereotype. Record the client's response, family questions, and chosen alternative.
5. Update the profile when the client, context, or preference changes. Close each task with a result rather than a generic completed flag.

For the client-preference handoff, avoid promising a start, substitute, supervisor, or uninterrupted schedule until the applicable staffing, competence, supervision, payer, setting, authorization, and client-specific gates are confirmed. If one gate changes, update the affected promise and tell the family who is responsible for the next decision.

Prepare for the main complication

A useful preference can harden into a label such as 'always avoids groups' or 'only works for tokens.' Preferences vary by person, setting, health, and time. Preserve the original source and uncertainty so new staff approach the client with curiosity rather than a fixed script.

When this complication occurs, return to the client-preference handoff. Preserve what was known at the time, the decision that was made, the alternative offered, and the next review. Keep a canceled or held event in the history so later utilization or quality reporting does not treat it as a completed service.

Work through a concrete example

Kai selects quiet arrival, written choices, no surprise touch, and a five-minute settling period. His caregiver adds that crowded entryways have recently been difficult. The profile labels each source. At the first visit, the new staff member verifies the options with Kai and learns that he now prefers a three-minute settling period.

The example shows how a family can evaluate the client-preference handoff without demanding a private personnel file or accepting a vague assurance. It also keeps operational assignment, clinical authority, client response, service delivery, and payer outcome in their proper lanes.

Questions families can ask about the client-preference handoff

• Which information came directly from the client?
• Which statements came from caregivers or observation?
• Does the incoming role need each detail?
• How can the client correct the profile?
• When will the handoff be reviewed rather than copied forward?

Request a written client-preference handoff answer for client's own words or AAC messages, caregiver context, prior observations, preferred name and communication, sensory and interaction supports, privacy, breaks, stop signals, health or safety needs, disliked approaches, uncertainty, owner, access limits, and review date. A point can remain unknown while evidence is gathered, but the client-preference handoff should give that unknown a named owner, its current source, and a date for the next family update.

Review the first days after the change

During the first review, compare the actual schedule with the plan in the client-preference handoff. Check whether introductions, training, supervision, client communication, documentation, and payer steps occurred as recorded. Invite the client and family to identify what worked, what felt unclear, and what should change. Review missed or shortened visits separately from visits that occurred.

The client-preference handoff remains a living, purpose-limited record. Review it before each transition and after meaningful change, and remove stale or unnecessary detail so continuity does not become overexposure or a permanent characterization.

Keep a family-facing summary

Give the family a short summary of the client-preference handoff in the communication format they use. Include the confirmed dates, named contacts, chosen option, unresolved dependencies, and next update. Explain how to report a new concern or a mismatch between the summary and what occurs. The summary should help the family prepare without exposing personnel details or replacing the underlying clinical and operational record.

The final note should state what closed, what remains open, who owns it, and when it will be reviewed again. That discipline makes the client-preference handoff useful for the family, the incoming team, and anyone later checking continuity or quality. Preserve the summary version so later changes are visible rather than silently replacing what the family was originally told.