To compare outcomes across an ABA plan version change, first map what changed in the response definition, opportunity, unit, sampling, setting, people, supports, exposure, integrity, and data system. Preserve each version's raw counts and missingness. Use a combined graph or effect statement only when the measures and conditions are meaningfully comparable. A before-and-after difference alone cannot isolate the plan change from time or concurrent events.

Inventory every changed field

Compare response, opportunity, denominator, prompt, partner response, unit, observation, exclusion, setting, schedule, people, materials, access, and decision rule.

Build a version map before calculating any change score. Put the old and new operational definitions side by side and mark fields that are identical, narrower, broader, or unknown. A response label that stayed the same may still conceal a different prompt rule or opportunity denominator. Preserve the language in effect at the time instead of rewriting older records to make the series appear more consistent than it was.

Verify exposure by version

Record dates, sessions, opportunities, duration, staff, setting, integrity, exceptions, mixed-version events, missing use, and the actual version applied.

Use verified exposure rather than the planned effective date. A new version may reach one team earlier than another, and a session after release may still use a stale quick reference. Classify each observation by the procedure actually delivered. When the version cannot be established, retain the data in an unknown-version group. Excluding those records silently can make the transition look cleaner and the change estimate stronger than the evidence supports.

Assess comparability

Ask whether definitions, populations of opportunities, settings, supports, data methods, and concurrent conditions permit direct, qualified, adjusted, or no comparison.

Direct comparison requires more than matching percentages. Decide whether both numerators answer the same question and whether their denominators arise from reasonably similar opportunities. If access, staffing, schedule, health, or observation methods changed, describe the comparison as qualified and show the condition. When differences are too substantial, present separate summaries and define a future window that can support a fairer comparison.

Display version boundaries

Show raw counts, denominators, missingness, annotations, separate panels or series when needed, and an explicit effective date without retrospectively rewriting data.

Mark both the authorized version date and the first verified use when they differ. Annotations should identify material access, setting, staffing, health, and data-system events without overcrowding the graph. Let readers inspect the underlying counts behind rates or averages. Separate panels are often clearer than a continuous line when the unit changed, and they prevent a visual connection from implying one stable measure across unlike versions.

Bound causal language

State observed differences and plausible explanations. Stronger causal conclusions require a design and evidence that address time, history, access, implementation, and other simultaneous changes.

Use language proportionate to the design: “was higher during the new-version window” is different from “improved because of the revision.” Consider maturation, seasonal routines, other services, medication or health changes, learning from prior exposure, and differences in integrity. If the team needs a causal answer for a consequential decision, a qualified clinician should select a defensible evaluation design rather than stretching a simple before-and-after dashboard.

Keep client meaning visible

Pair quantitative outcomes with Dalia's priorities, experience, burden, access, adverse effects, usefulness, and desired next step before deciding what to retain or revise.

Two versions can produce different measured outcomes while Dalia prefers the one with less effort, better communication access, or greater usefulness in daily life. Show that information alongside the graph and keep direct report distinct from proxy interpretation. A decision record should explain how benefit, burden, unwanted effects, feasibility, and Dalia's stated goals were weighed, including any disagreement or uncertainty that remains after review.

Build Dalia's cross-version outcome comparison

Give each plan version its own comparison row with the response and opportunity definitions, dates, settings, implementers, AAC and other supports, actual exposure, integrity coverage, numerator, denominator, missingness, and concurrent events. Add a field that classifies the comparison as direct, qualified, adjusted, or unavailable and records the reason. Preserve Dalia's priorities, experience, burden, and unwanted effects beside the outcome measure so the numerical difference does not become the whole decision record.

Work through Dalia's example

Dalia's old version records 9 independent responses in 18 clinic opportunities, which is 50%. The new version records 15 in 20 opportunities across school and clinic with AAC always available, which is 75%. The arithmetic difference is 25 percentage points. Because setting, access, and the opportunity definition changed, the dashboard presents that difference as descriptive and marks the version boundary instead of treating it as an isolated plan effect. Future comparable windows can support a cleaner decision while the original counts remain intact.

Address Dalia's main implementation risk

A continuous line can imply one stable measure when several defining conditions changed. Dalia's display marks every material version difference. 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 Dalia's next action

The team chooses a future comparable window, preserves the historical series, and explains to Dalia which questions the current evidence can and cannot answer. 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 Dalia's access and choice

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

Apply current sources to Dalia'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 Dalia's implementation path

Test the cross-version outcome comparison 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 Dalia's implementation record

Review the cross-version outcome comparison with Dalia, 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