To respond to partial ABA plan change implementation, map which version each person, setting, shift, system, and session actually used. Protect immediate safety and communication access, then contain mixed-version exposure and determine which scope can continue. Preserve the actual record, correct stale materials and training, and interpret outcomes only within verified version exposure. A qualified clinician decides whether to pause, narrow, repair, rollback, or revise the change.

Reconstruct actual version use

List session, time, setting, implementer, component, source plan, quick reference, material, device, data form, adaptation, and observed version for every affected event.

Start from actual records, interviews, system history, and available observation rather than assuming the release date marks a clean boundary. Trace each affected component separately because one may have reached the new version while another remained old. Mark unknown version use when evidence cannot resolve it. Keep planned exposure, verified exposure, and missing opportunities distinct so the reconstruction does not convert rollout failure into a client outcome.

Protect immediate needs

Restore AAC and access, follow health and safety routes, stop unauthorized or unsafe steps, preserve ordinary supports, and notify the responsible clinician of clinical implications.

Address Freya's present condition before investigating workflow. Ask whether she needs medical attention, a break, communication support, correction of a record, or another immediate protection. Staff may stop an unsafe action under the applicable procedure, while a qualified clinician determines the plan disposition. Preserve enough evidence to understand what happened, but do not delay urgent care or continue an uncertain sequence merely to complete an observation.

Contain mixed-version risk

Decide which settings continue, hold, revert, or receive an immediate controlled repair based on qualified authority, client risk, access, and available evidence.

Contain the smallest scope that meaningfully separates the problem. If one shift used a stale form but all other settings are verified, the response may differ from a systemwide version uncertainty. Consider whether switching versions again creates additional confusion or risk. Communicate the temporary state through every route implementers actually use, identify who can change it, and give each held context a clear condition for reassessment.

Find the rollout failure

Check distribution, training, acknowledgment, scheduling, devices, offline copies, turnover, supervision, language, materials, workflow, and unclear effective dates.

Follow the failed path from the authorized source to the point of care. A distribution log may show delivery while the implementer opened an older bookmark, or a training record may cover a person who never practiced the revised step. Look for design conditions that made the error likely, including conflicting labels or simultaneous launches. Fixing only the individual event leaves the same path available to produce another partial rollout.

Separate outcome evidence

Label exposure by version, exclude only with stated rules, preserve mixed events, report missingness, and avoid attributing change to a version the person did not consistently receive.

Recalculate relevant summaries after version classification, but retain the original data and an audit trail. A mixed-version session may still contain useful observations even when it cannot support a clean version comparison. Show how many events were old, new, mixed, unknown, or not exposed. Any outcome statement should identify that denominator and the settings represented, especially when partial implementation was discovered after an apparently favorable trend.

Repair and rerelease

Update records and systems, train affected people, verify readiness, observe first use, communicate with Freya, and establish a new monitoring window by setting.

Treat rerelease as a controlled implementation event rather than a quiet correction. Confirm that stale copies are unavailable, affected staff can demonstrate the current sequence, access supports work, and first-use observation is scheduled. Tell Freya what was found and what will be different through an accessible route. The clinician should set the new monitoring window and decide whether prior mixed exposure changes the outcome-review timeline or requires broader follow-up.

Build Freya's partial-implementation response

Create a versioned partial-implementation response for this post-review implementation question. Preserve direct client input, actual version exposure, health and communication access, qualified authority, staff and setting readiness, procedure integrity, data quality, client experience, unwanted effects, exceptions, rollback, tasks, owners, due dates, communications, correction routes, and later evaluation. Another qualified reviewer should be able to reconstruct what was released, what actually occurred, and how the evidence changed the next decision.

Work through Freya's example

Freya's change spans four settings. Two use the new version consistently, one alternates versions across shifts, and one still uses the old version. Report 2 of 4 settings fully implemented, one mixed, and one old. Do not call 50% client adherence or average outcomes across the four settings until exposure is reconstructed. Keep every planned and actual event, version, numerator, denominator, overlap, open state, and unavailable item visible. This fictional four-setting rollout example illustrates one post-review control and supplies no universal release rule, integrity threshold, clinical recommendation, legal conclusion, payer result, or outcome guarantee.

Address Freya's main implementation risk

Partial rollout can be mistaken for weak treatment response. Freya's response first establishes which intervention version was actually present. Treat approval, release readiness, actual exposure, integrity, client experience, unwanted effects, and outcomes as separate evidence. Technical completion can occur before clinically acceptable use is established.

Choose Freya's next action

The practice corrects the mixed and old settings, checks for client impact, then restarts outcome monitoring from a verified version date for each context. Record the responsible role, authority, affected component 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 Freya's access and choice

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

Apply current sources to Freya's implementation

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

ASHA supports continuous AAC access.

Rehearse Freya's implementation path

Test the partial-implementation response with a stale copy, untrained shift, missing AAC, inaccessible material, health change, incorrect step, mixed-version setting, absent observer, client dissent, adverse effect, unauthorized deviation, rollback, overdue task, and reopened decision. Confirm that access, attribution, authority, version state, evidence, and follow-up remain intact.

Close Freya's implementation record

Review the partial-implementation response with Freya, the responsible clinician, affected implementers, and the specialists named by the manifest. Preserve client input, actual exposure, 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