Review an ABA Plan After the Primary Implementer Changes

To review an ABA plan after the primary implementer changes, ask the client about fit and communication, verify the new person's qualifications, role, training, supervision, and access to the current version, then reassess opportunities, materials, prompts, partner behavior, integrity, and data continuity. Preserve prior evidence as implementer-specific context. Observe first use and distinguish relationship or system changes from client skill before interpreting new outcomes.

Prepare the client

Explain the staffing change, ask Yuki's preferences and concerns, arrange AAC and privacy, introduce the new person gradually when feasible, and preserve a decline or pause route.

Tell Yuki who is changing, why, when, and which parts of the plan remain the same. Ask whether she wants a photo, brief meeting, joint session, chosen support person, or another introduction. Give her a private way to raise a concern and keep AAC and ordinary communication support available.

Record her direct response and any boundaries about touch, topics, location, or information sharing. A staffing decision may be organizational, but implementation should still reflect Yuki's assent or dissent where applicable and her access needs.

Verify the implementer role

Check assignment, qualifications, competence, training, supervision, permitted adaptations, safety and access knowledge, documentation route, and escalation contacts.

Verify the new implementer's authorized role and training before direct work. Match competence to the plan components, communication system, health and safety procedures, mobility or access supports, data definitions, and emergency routes. Identify the active supervisor and backup contact.

Do not use Yuki's session as the implementer's only training. Knowledge review, modeling, rehearsal, and representative observation can occur before the person independently delivers a procedure. Hold components whose required competence or supervision is not ready.

Transfer the current procedure

Review plan version, changed and stable steps, materials, response forms, prompts, wait time, partner actions, data definitions, and stop rules.

Use a versioned implementation checklist with the exact component. Distinguish client responses from partner actions and system readiness. Include ordinary supports, accepted variations, prompt and wait rules, correction, pause, and withdrawal response. Explain why each safety-critical step matters.

Have the implementer demonstrate the process with the supervisor or through low-risk rehearsal. Resolve questions before Yuki is exposed to inconsistent delivery. Record any approved adaptation and its qualified author.

Rebuild opportunity context

Map schedule, routines, people, setting, travel, available opportunities, health, fatigue, communication access, relationship history, and expected exposure.

A new person can change the context even when location and plan text stay constant. Recalculate how many real opportunities are likely, whether schedule or travel changed, and how Yuki communicates with an unfamiliar partner. Preserve relationship-building time without forcing social behavior.

Check health and communication access at each session and document unavailable opportunities. If the routine no longer occurs or materials are missing, correct the system rather than pressuring the implementer to create artificial trials.

Observe first use

Score readiness, procedure integrity, client response, comfort, access, data capture, questions, errors, and unexpected effects without turning the session into a high-stakes test.

Begin with a representative but bounded activity that Yuki accepts. The supervisor can observe partner steps, latency, AAC access, and stop response while minimizing extra observers and demands. Any safety, health, or distress concern receives the appropriate response immediately.

Provide implementer feedback away from Yuki when possible and correct errors before the next opportunity. A first-use miss remains in integrity data. Do not repeat the activity solely to produce a passing score.

Protect data interpretation

Separate implementer periods, show raw counts and denominators, preserve missingness and concurrent changes, and wait for comparable evidence before attributing a difference.

Mark the transition date and do not join the two periods into one trend line without annotation. Report opportunity counts, readiness, support, schedule, and implementation by implementer. Small or unequal samples need cautious interpretation.

Ask Yuki about comfort and fit directly. A change in response may reflect familiarity, opportunity, health, schedule, partner behavior, or another concurrent factor. Continue coaching and access repair before assigning causation to the new implementer or client.

Build Yuki's implementer-change plan review

Create a versioned implementer-change plan review for this clinical continuity question. Preserve direct client participation, outgoing and receiving roles, current plan and evidence, health and communication access, qualified authority, consent and privacy routes, open risks and decisions, records, payer and staffing states, acceptance, first use, gaps, tasks, owners, due dates, and follow-up. Another qualified reviewer should be able to reconstruct who remained responsible at every point.

Work through Yuki's example

Yuki's prior implementer recorded 18 opportunities in four weeks; the new implementer records 10 in the next four because the schedule changes too. Independent responses are 12 of 18 and 7 of 10. The team reports both samples and avoids attributing the difference to the implementer because exposure, schedule, and relationship history also changed. Keep every client, component, source, numerator, denominator, overlap, acceptance state, open item, and unavailable service visible. This fictional home skill program example illustrates one transition control and supplies no universal transfer rule, clinical recommendation, legal conclusion, payer result, service-start promise, or outcome guarantee.

Address Yuki's main continuity risk

A staff transition can look like a sudden client change. Yuki's review labels implementer, exposure, access, setting, and schedule for every period. Treat record delivery, clinical review, responsibility acceptance, payer state, scheduling, first service, and outcome as separate evidence. One organization's closure never proves another has accepted care.

Choose Yuki's next action

The supervisor coaches the new implementer, observes first use, asks Yuki about comfort and communication, and establishes a comparable future window. Record the responsible role, authority, affected person and scope, interim support, 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 Yuki's access and choice

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

Apply current sources to Yuki's transition

The BACB ethics hub, current Ethics Code, CASP public summary, and BCBA Test Content Outline provide scoped professional, client-involvement, continuity, documentation, 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, and bounded conclusions.

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

Rehearse Yuki's transition path

Test the implementer-change plan review with a client concern, missing AAC, health update, incomplete records, stale version, absent receiver, competence gap, unresolved authority, payer change, staff turnover, service gap, urgent event, failed first use, declined goal, and reopened decision. Confirm that access, attribution, responsibility, versions, evidence, and follow-up remain intact.

Close Yuki's transition record

Review the implementer-change plan review with Yuki, outgoing and receiving clinicians, affected participants, and the specialists named by the manifest. Preserve client input, responsibilities, records, 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 Review an ABA Plan After the Primary Implementer Changes