To respond when an ABA plan change handoff fails, protect the client's safety, health, and communication access, identify who missed usable information, and reconstruct which version each session, setting, and system used. Stop unsafe or unauthorized actions and contain mixed-version risk. Preserve the event and downstream data, correct delivery and training, assess clinical and reporting impact through responsible roles, and reverify readiness before the affected scope resumes.

Protect the immediate session

Restore the approved support, AAC, health and safety information, ordinary needs, and qualified supervision; stop unsafe, unavailable, or out-of-scope steps.

At discovery, identify the active client, component, version, and immediate condition. Pause the affected work, preserve Tessa's communication, care, mobility, food, water, bathroom, pain response, and emergency access, and contact the qualified supervisor. Use the approved prior or continuity plan only when its current use is authorized.

Respond to injury, distress, privacy exposure, or another incident through the appropriate clinical, medical, safety, legal, or organizational route. Do not continue to finish the session or collect comparable data.

Reconstruct recipients and versions

List intended and actual receivers, channels, files, versions, access, training, shifts, settings, sessions, acknowledgments, and first-use events.

Build an incident timeline from source release through discovery. Preserve delivery logs, access records, schedules, staff assignments, point-of-care files, offline copies, training evidence, and session versions. Include recipients omitted from the original roster.

Distinguish wrong attachment, inaccessible format, failed channel, untrained receiver, stale cache, misunderstanding, and source-plan error. Keep verified facts separate from the root-cause hypothesis.

Contain the affected scope

Decide which clients, components, settings, shifts, or staff may continue, hold, revert, or receive urgent repair under qualified authority.

Use component-level containment rather than stopping unrelated accepted care. Mark each receiver and setting with continue, hold, revert, or repair, along with the decision owner, effective time, interim support, and next eligible use. Prevent automated scheduling and stale forms from bypassing the hold.

Notify affected staff and clients through accessible approved routes. If scope is uncertain, apply the safer hold while the qualified team resolves it. Do not infer that every recipient who received the packet used it.

Assess downstream effects

Review client experience, safety, data validity, integrity, incident duties, payer or claim effects, privacy, employment, supervision, and records correction through responsible roles.

Assess every exposed session under the actual version and conditions. Ask Tessa about her experience, review partner implementation and safety, and determine whether data can remain interpretable. A prior-version session is neither new-version success nor automatically invalid; the qualified reviewer decides its use.

Route billing, claim, privacy, employment, supervision, incident, and legal questions to their owners. Correct records transparently and preserve the initial entry, source, and reason. Communicate material effects to Tessa accessibly.

Repair the handoff system

Correct recipient logic, access format, file controls, onboarding, shift coverage, delivery failures, training, escalation, and source-plan links.

Repair the immediate path and the contributing control. Add relief staff to the roster source, replace the wrong attachment rule, test accessible files, withdraw stale copies, strengthen onboarding, and verify after-hours escalation. Assign an owner and evidence target for each action.

Avoid a generic reminder to “be careful.” Test the corrected control with representative roles, settings, and devices. Maintain temporary monitoring until the failure modes that affected Tessa are closed.

Reverify and close

Confirm usable delivery, understanding, competency, current materials, point-of-care version, first use, client feedback, data correction, and recurrence controls with evidence.

Rebuild readiness from the approved source plan. Verify corrected delivery and access for every intended receiver, training and competency where required, materials and supervision, and current plan at point of care. Observe safe first use and obtain Tessa's feedback.

Close receiver repair, exposure assessment, data correction, incident duties, and prevention as separate states. Age any unreachable recipient or failed notice as an open risk. Retest the route after the next staffing or schedule change.

Build Tessa's failed-handoff response

Open Tessa's response with an incident timeline and the exact affected scope. List all eight intended receivers, what each received, whether it was usable and accessible, which version was available at the point of care, and whether training or first use occurred. Link every wrong, missing, or stale artifact to an immediate safeguard, correction owner, due date, verification evidence, client communication, data review, and recurrence control. Preserve the prior-version session as an exposure record with its own clinical review rather than treating a successful resend as complete recovery.

Work through Tessa's example

Tessa's update targets eight receivers. Six get a usable handoff, one receives the wrong attachment, and one new relief worker is omitted. Usable delivery is 6 of 8, or 75%, leaving two receiver paths to repair. One session uses the prior version before discovery. The team preserves that exposure, checks its impact, and keeps it outside the new-version outcome numerator and denominator. Receiver coverage and version exposure therefore remain separate measures, and closure waits for corrected delivery, readiness, and verified first use.

Address Tessa's main handoff risk

Resending the file can close a ticket while leaving training, data, and client impact unresolved. Tessa's response follows the failed handoff through corrected first use. Treat sent, delivered, accessible, understood, trained, ready, and first used as separate evidence. Communication completion never transfers clinical, school, medical, payer, or legal authority.

Choose Tessa's next action

The owner fixes both receiver paths, the clinician reviews the prior-version session, and supervisors verify training and first use before closure. Record the responsible role, authority, affected person and scope, immediate control, due date, evidence needed for closure, accessible communication, correction route, and next review. Software may coordinate workflow. Qualified professionals make case-specific decisions within scope.

Protect Tessa's access and choice

Keep Tessa's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, pain communication, health support, movement, rest, relationships, and emergency help available. Offer private and accessible ways to ask, disagree, decline, pause, withdraw when applicable, and correct the record. Proxy and professional input may inform coordination while Tessa's own experience remains distinct.

Apply current sources to Tessa's handoff

The BACB ethics hub, current Ethics Code, CASP public summary, and BCBA Test Content Outline provide scoped professional, client-involvement, documentation, coordination, evaluation, and training context.

An evidence-based ABA framework and treatment-integrity practitioner guide, Essig review, impact study, and reporting review support contextual decisions, explicit implementation evidence, observer quality, and bounded conclusions.

ASHA supports continuous AAC access. HealthCare.gov separates preauthorization from a promise of cost coverage.

Rehearse Tessa's handoff path

Test the failed-handoff response with a wrong recipient, inaccessible file, stale copy, missing shift, untrained relief worker, absent supervisor, school or medical scope question, payer deadline, missing AAC, failed channel, mixed-version session, client correction, unauthorized deviation, and reopened decision. Confirm that access, attribution, authority, version state, privacy route, and follow-up remain intact.

Close Tessa's handoff record

Review the failed-handoff response with Tessa, the responsible clinician, affected receivers, and the specialists named by the manifest. Preserve client input, delivery and use evidence, decisions, disagreement, versions, tasks, limits, and open findings. Keep the page draft and noindex until required clinical, client or family, AAC, access, medical, educational, payer, records, privacy, employment, and legal reviews are complete.

Related resources

Sources