Meaningful ABA change in original units is a difference the person values and can understand in the measure's everyday scale, such as five fewer minutes waiting, three more independent choices, or access in two additional settings. Define the desired difference before outcome review when possible. Statistical summaries can add context, while the original-unit change, burden, risk, and client experience determine practical meaning.

Choose the everyday unit

Use counts, minutes, opportunities, locations, completed steps, chosen activities, or another scale the person can interpret.

Define the valued direction and size

Ask what difference would matter, how often, in which contexts, and what support should remain.

Preserve distributions

Show every observation, median or other summary, range, denominator, and missingness beside the change.

Pair magnitude with experience

Collect accessible client feedback about usefulness, effort, comfort, and whether the outcome matches the intended goal.

Scope the conclusion

Separate observed difference, causal evidence, durability, generalization, burden, and client value.

Build Asha's meaningful-change specification

For the define meaningful ABA change using original units question, create a versioned meaningful-change specification. Preserve the client priority, exact question, original unit, eligible opportunity or exposure, numerator, denominator, source identity, communication access, context, direct observation, self-report, proxy report, burden, unwanted effects, generalization, maintenance, decision owner, and uncertainty. Another qualified reviewer should be able to reconstruct Asha's outcome without replacing lived experience with a summary score.

Work through Asha's outcome example

Asha wants to spend less time waiting after using her chosen ride-status message. Median wait after the message falls from 8 minutes across five baseline trips to 3 minutes across five later trips. The original-unit difference is 5 minutes. Asha reports that the change makes the ride routine easier, while the small sample and other service changes remain documented. Show each source, count, denominator, setting, and timeframe before summaries. This fictional community transportation goal example illustrates one outcome-review pattern and does not establish a universal meaningful-change threshold, instrument, treatment recommendation, social-validity conclusion, or causal claim.

Audit Asha's outcome evidence

Asha's specification records the message, eligible trip, wait-time start and end events, five-trip denominators, medians 8 and 3, service changes, her rating, and the prospectively discussed meaningful difference. It preserves individual trips and ranges. The audit also checks definition and instrument versions, source validity, administration access, privacy, missing and declined states, correction history, context coverage, graph or calculation precision, burden, adverse effects, and client review. Unresolved evidence remains visible and narrows the exact claim it affects.

Address Asha's main interpretation risk

A large percentage can arise from a tiny absolute change, and a modest percentage can represent an important daily difference. Asha's report leads with minutes and her experience. A measure can be reliable and still miss the person's priority. A client-valued outcome can be important even when the design cannot attribute it. Reviewers preserve both distinctions and avoid turning one person's result into a population promise.

Choose Asha's next action

The team checks whether the shorter wait persists across routes and providers and whether any new burden or access problem appears. Causal wording stays proportional to the design. Record the action, rationale, qualified owner, client response, support, due date, and review trigger. Keep technical change, client value, burden, harm, generalization, maintenance, and causal evidence as separate fields.

Protect Asha's access and voice

Keep Asha's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, health support, rest, relationships, and emergency help available. Offer accessible and private ways to accept, decline, pause, correct, or withdraw from outcome collection. A caregiver or clinician can contribute evidence without authoring Asha's report. Immediate safety or medical concerns follow the applicable route.

Apply current sources to Asha's review

Asha's source card prioritizes outcomes defined with the person's values rather than a provider-selected normality standard. The BACB ethics hub and CASP public summary provide professional context, while the BCBA Test Content Outline identifies examination content on client goals, measurement, and evaluation. An evidence-based ABA framework, contemporary social-validity analysis, and review of social validity describe client values and repeated evaluation. Research on measuring what matters, family-centered care, and an accessible autistic-adult measurement toolkit highlights priority and access issues with scoped validation. ASHA supports continuous AAC access.

Rehearse Asha's outcome workflow

Test the meaningful-change specification with fictional client and proxy disagreement, a declined rating, AAC failure, small denominator, large percentage with trivial magnitude, benefit with burden, adverse event, response substitution, missing community context, and incomplete maintenance. Confirm that states, denominators, source labels, urgent routes, claim holds, and qualified review behave as intended. Store expected outputs, reviewer notes, software version, and corrections before live use.

Close Asha's outcome review

Review the meaningful-change specification with Asha, the responsible clinician, and specialists required by the outcome. Preserve raw data, direct voice, access method, proxy evidence, original-unit magnitude, contexts, burden, adverse effects, generalization, maintenance, claim wording, disagreements, and limits. Keep the page draft and noindex until every manifest-named review is complete.

Related resources

Sources