To handle missing client-experience data in ABA, classify why each expected response is absent. Distinguish an inaccessible method, missing opportunity, client choice, device or staff failure, privacy problem, timing error, and unknown cause. Keep the mature denominator, avoid imputing satisfaction or refusal, offer alternate access without pressure, and route concerning patterns to qualified review and corrective action.

Define the expected data event

State the eligible cohort, experience question, response method, timing, setting, owner, access requirements, reminder limit, client choice option, maturity window, and conditions that make a record due.

Use a practical missingness taxonomy

Classify inaccessible communication, absent or invalid opportunity, client declines, client unavailable, privacy concern, staff omission, device or form failure, late collection, lost data, plan change, emergency, and unknown cause. Preserve evidence and avoid guessing.

Keep fixed denominators

Use every mature due record for response completeness. Report completed responses, missing categories, aged open items, and corrections as raw counts and rates. Explain any predeclared exclusion rather than silently shrinking the cohort.

Offer alternate access carefully

Ask Luz whether another language, AAC form, interview, private setting, support person, timing, pace, or channel would help. Preserve no response and withdrawal, limit reminders, and avoid making participation a condition of care.

Avoid unsupported imputation

Do not assign neutral, satisfied, dissatisfied, compliant, or refused values to missing experience data. Proxy input may add separately labeled context and cannot replace a direct client response that was never obtained.

Route missingness as quality data

Escalate safety, health, privacy, retaliation, repeated access failure, or systematic disparity. Assign each correctable cause, due date, interim safeguard, validation test, client communication, recurrence check, and governance review.

Build Luz's missing-experience-data plan

Create one versioned missing-experience-data plan for the multi-site quality review. Include the construct, decision question, direct client communication, source-labeled proxy evidence, consent and assent when applicable, privacy, AAC and retained supports, authority, readiness, client and partner units, missingness, experience, burden, owners, dates, and review triggers. Define every numerator, denominator, duration, exclusion, and maturity rule before data collection.

Keep a decision-ready record for Luz

For Luz's record, identify the source and date, client-selected response method, setting, period, opportunities, support conditions, access failures, prompts, partner actions, raw values, missing categories, corrections, uncertainty, qualified interpretation, decision, interim support, implementation, client communication, confirmation, and next review. Restrict sensitive data to approved roles and systems.

Work through Luz's example

Luz reviews forty mature experience records. Thirty-two contain a response. Of eight missing records, three reflect inaccessible methods, two client choices, one staff omission, one device failure, and one unknown cause. Report 32/40 response and every missing category as a count; never convert the eight to neutral or satisfied. Keep every readiness state, client response, partner action, numerator, denominator, missing event, exclusion, support, and experience measure visible. This fictional example demonstrates one control. It supplies no universal threshold, diagnosis, legal conclusion, payer result, causal finding, or outcome guarantee.

Use Luz's data for a bounded decision

Before collecting another Luz measure, name the decision it may inform and who owns that decision. Options may include continue, clarify, restore access, add support, revise, pause, refer, investigate, retire, or close. Record the evidence needed, due date, stop or safety rule, client-facing explanation, review route, and criteria for reopening.

Address Luz's main fit risk

Deleting missing cases can inflate the favorable-response rate and hide the clients least able to access the method. Luz's report keeps all forty records visible. Review access, privacy, partner behavior, burden, health, safety, missingness, and lived experience separately. A precise percentage can still answer the wrong question when the construct, source, opportunity, or decision rule is poorly defined.

Choose Luz's next action

Access owners repair three methods and one device route, the supervisor addresses the staff omission, and the unknown case receives privacy-sensitive follow-up. Preserve the original evidence and any disagreement. Record the qualified owner, affected plan version and setting, interim protection, additional source needed, due date, implementation evidence, client communication, confirmation, correction route, disposition, and next review.

Put Luz's missingness controls into routine use

Teams that handle missing client-experience data in ABA should require a reason code while preserving an unknown option. The collection system should retain the mature due cohort, age open records, cap reminders, and prevent a blank field from becoming zero, neutral, satisfied, or refused. Review missingness by method, setting, partner, language, communication form, disability access, and time period. Route correctable failures to named owners and validate the repair. Give Luz a private alternate method and a clear way to decline. Report proxy information in a separate field, since it adds context and does not fill a missing direct response.

Review Luz's missingness as an outcome

Begin with all mature due records, completed direct reports, proxy-only records, and every missing category. Show age and owner for open correctable items. Segment missingness by response method, setting, partner, language, AAC, privacy, client group, and period when cell size and confidentiality permit responsible interpretation. A falling missing rate deserves review of how it changed; added pressure or silent proxy substitution is not an access improvement. Inspect reminder frequency and client declines for coercion. Compare methods only after documenting changes in wording, timing, exposure, and support. Close with repairs for inaccessible methods, staff and device failures, privacy concerns, and unknown patterns, plus validation dates and client communication. Preserve declined responses as valid choices rather than work queues.

Report whether alternate methods reduce access-related missingness without increasing reminders, staff interpretation, or response burden. Ask Luz whether the new route feels easier and private enough before adopting it across the cohort.

Apply current professional sources to Luz's measurement

For Luz's measurement, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, assessment, medical needs, risk, documentation, and evaluation for covered people. BACB has no separate organizational jurisdiction. The BCBA outline is examination content and supplies no practice authority. The CASP public summary gives high-level context for ABA treatment of autistic people. An evidence-based ABA framework supports integrating research, clinical expertise, client values, and context.

Use implementation and access evidence for Luz

For Luz's plan, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit procedures, representative implementation evidence, and cautious interpretation. They create no universal experience, access, or response threshold. Breaux and Smith offer assent-focused guidance while describing an evolving evidence base. ASHA supports continuous access to AAC tools or devices.

Close Luz's measurement review

Review the missing-experience-data plan with Luz, the responsible clinician, affected partners, and the specialists named in the manifest. Check whether the measure remains understandable, accessible, low burden, representative, and useful for the stated decision. Preserve direct communication, ordinary supports, source disagreements, versions, limitations, and open gaps. Keep this page draft and noindex until all required reviews are complete.

Related resources

Sources