Communicate That an ABA Plan Version Is Retired

To communicate that an ABA plan version is retired, identify the exact version, effective date, affected people and settings, replacement version or stop instruction, clinical and safety boundaries, and open records that still reference it. Notify authorized recipients through their usable channels, remove it from active workflows, and preserve it in history. Track receipt, failed delivery, stale copies, and actual last use separately.

Define what retirement means

State version, component scope, effective date, replacement or stop state, last permitted use, qualified authority, exceptions, rollback status, and historical retention route.

Issue a controlled retirement decision linked to the source plan and qualified author. Define whether the whole version or selected components stop, which replacement is current, the last permitted setting and time, and whether an approved rollback exists. “Old” or “archived” is too vague for point-of-care control.

Separate retirement from deletion. Prior records, data lineage, incident evidence, payer packets, and historical review may need retention under their applicable policies. They should remain discoverable to authorized reviewers while clearly blocked from current implementation.

Inventory affected locations

List source plan, quick references, devices, portals, data forms, schedules, offline packets, training files, shared drives, printed copies, and recipient-controlled systems.

Search every workflow that can surface or reproduce the version. Include EHR plan views, copied templates, data-collection forms, phone or tablet downloads, shared drives, binders, training systems, schedules, payer attachments, vendor portals, and materials held at home or community sites.

Assign a stable location ID, owner, last-use risk, and retirement action. Include locations outside direct organizational control when a correction or notice route exists. Keep the denominator fixed until each location has a disposition.

Write usable instructions

Tell each role what stops, what replaces it, when, where to find the current version, which supports remain, how to handle an old copy, and whom to contact.

Tailor the notice to Samir, caregivers, implementers, supervisors, operations, payers, and other recipients. A direct-staff notice needs point-of-care instructions, while Samir needs an accessible explanation of what will change in daily life and how to ask questions or stop.

Mark the plan and component identifiers visually and in machine-readable fields where available. Tell staff to stop and contact the named owner if they encounter a stale copy, rather than guessing which steps to use.

Protect client access and continuity

Explain the change to Samir accessibly, preserve AAC and ordinary supports, identify any service hold or transition, and prevent a retirement notice from removing necessary access tools.

Review the practical effect with Samir in his preferred communication mode. Ask about concerns, privacy, burden, and whether the replacement matches the accepted decision. Retiring a procedure should not remove AAC, mobility support, prescribed care, communication aids, or ordinary resources that also appeared in its packet.

If no replacement is ready, use the qualified hold or continuity plan and explain it. Preserve direct client response and applicable assent or dissent. A technical retirement should never create an unnoticed service gap.

Track delivery and action

Record sent, delivered, accessible, acknowledged, removed, disabled, relabeled, failed, corrected, and last used with dates, evidence, and owner.

Track delivery and action separately. A recipient may acknowledge the notice while an offline packet remains in use. A file may be disabled but continue as a printed reference. Record the evidence and check the last actual use after the effective date.

Investigate any mixed-version exposure, preserve affected session and data records, protect Samir, and route clinical, privacy, payer, or legal effects to qualified owners. A successful resend does not close the exposure review.

Preserve history without active use

Keep the retired version, rationale, decisions, data lineage, corrections, and affected records available under policy while excluding it from current point-of-care workflows.

Store the version in a controlled historical location with retirement status, effective date, replacement link, reason, author, and access limits. Remove it from default search, active templates, schedules, and device sync while retaining authorized audit access.

Test point-of-care systems and representative offline paths after retirement. Reopen the location record if a stale copy appears. Close only after the full inventory has verified states and any exposure is assessed.

Build Samir's retired-version notice

Inventory every controlled location where Samir's retired version could still guide care, including the source plan, quick references, data forms, portals, devices, offline packets, and training files. For each location, record the old and replacement versions, responsible owner, retirement action, due date, completion evidence, last-use check, downstream links, and any open exposure review. The notice should also tell affected people which version is current, when it takes effect, how to obtain an accessible copy, and where to report a stale one.

Work through Samir's example

Samir's retired version appears in twelve controlled locations. Ten are replaced or disabled by the retirement date, one offline packet remains at a community site, and one training file is read-only but still labeled active. Retirement control is 10 of 12, or 83.3%. The remaining two locations stay open even though no session has used them. This is a location-control measure; actual exposure and client impact remain separate questions. A qualified owner still has to verify both stale locations before closing the retirement record.

Address Samir's main handoff risk

Archive status in one system cannot stop an offline or training copy from guiding care. Samir's register follows every controlled location and receiver. 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 Samir's next action

Owners remove or relabel the two stale copies, verify downstream links, and monitor the last-use record before closing retirement. 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 Samir's access and choice

Keep Samir'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 Samir's own experience remains distinct.

Apply current sources to Samir'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 Samir's handoff path

Test the retired-version notice 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 Samir's handoff record

Review the retired-version notice with Samir, 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.

How to Communicate That an ABA Plan Version Is Retired