To audit a socially significant ABA outcome claim, trace the wording to the person's stated priorities, original-unit change, meaningful contexts, direct and proxy evidence, generalization, maintenance, burden, unwanted effects, accessibility, and qualified review. Social validity ratings, technical behavior change, and actual improvement in daily life are related but distinct. The claim should state whose values it reflects and which evidence remains missing.

Lock the proposed claim

Write the exact outcome, person, setting, period, magnitude, and value language before judging support.

Trace technical evidence

Verify definitions, original units, denominators, graph, design, integrity, generalization, maintenance, and uncertainty.

Trace lived evidence

Link direct client report, accessible response method, caregiver or other sources, burden, unwanted effects, and daily-life consequences.

Identify whose values appear

State whether the goal and outcome importance come from the client, family, clinician, payer, school, or another system.

Assign a claim-level result

Approve, narrow, hold, or reject the wording with rationale, reviewers, missing evidence, and next action.

Build Juno's social-significance claim audit

For the audit socially significant ABA outcome claim question, create a versioned social-significance claim audit. 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 Juno's outcome without replacing lived experience with a summary score.

Work through Juno's outcome example

Juno's transition routine falls from a median 30 minutes to 10 minutes across comparable observations. Juno reports that the routine feels easier, while caregiver preparation rises by 20 minutes and community generalization has two observations. The audit supports a valued improvement in the measured home routine and rejects a broader claim of universally improved family life. Show each source, count, denominator, setting, and timeframe before summaries. This fictional multisetting transition-support study 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 Juno's outcome evidence

Juno's file links the proposed sentence to raw durations, observation conditions, client report, caregiver time, adverse-effect review, maintenance dates, community coverage, design evidence, and reviewer status. Each unsupported phrase receives a hold or narrower replacement. 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 Juno's main interpretation risk

A favorable satisfaction survey can coexist with burden or missing client voice, and a strong graph can target an outcome the person does not value. Juno's audit requires both technical and lived evidence. 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 Juno's next action

The team can collect more community and maintenance data, reduce preparation burden, or keep the narrow claim. Publication remains pending external review. 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 Juno's access and voice

Keep Juno'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 Juno's report. Immediate safety or medical concerns follow the applicable route.

Apply current sources to Juno's review

Juno's source trail distinguishes the social importance of goals, procedures, and outcomes from the technical evidence for behavior change. 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 Juno's outcome workflow

Test the social-significance claim audit 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 Juno's outcome review

Review the social-significance claim audit with Juno, 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