To audit client-experience measures in ABA plans, lock a mature cohort and check for direct accessible client report, source-labeled proxy input, construct fit, timing, privacy, response options, missingness, burden, partner action, and decision use. Preserve fixed denominators and disagreement. Separate experience from attendance, fidelity, and clinical outcomes, and avoid causal claims unsupported by the measurement design.
Lock the audit cohort
Define mature plans, required experience domains, direct and proxy sources, access standard, timing, privacy, response owner, decision link, and exclusions.
Write the inclusion rule before opening records. A mature plan might require a defined service period and at least one scheduled experience-review opportunity. Specify the audit date, locations, service types, age or communication groups, plan versions, and permitted exclusions. Retain every eligible plan in the denominator even when its experience measure is missing. Excluding incomplete plans would make the program appear stronger by removing the failures the audit needs to find.
Freeze the required evidence fields as well. For each plan, capture whether the client had an accessible direct-report route, what construct was measured, when and where it was offered, privacy, communication supports, response options, missingness, proxy sources, burden, response ownership, action timing, and decision use. Record the artifact and date supporting each answer so another reviewer can reproduce the result.
Audit measure validity
Check whose experience is measured, construct, response options, context, frequency, missingness, burden, observer or device quality, and change over time.
Confirm that the question matches the claimed construct. A willingness-to-return item is different from comfort, respect, usefulness, perceived benefit, burden, choice, privacy, or overall fit. Review the wording for leading language, acquiescence pressure, inaccessible scales, and assumptions that the client uses speech. Check whether response options allow uncertainty, mixed experience, another concern, correction, and no response.
Inspect administration conditions. Who asked, who was present, whether the provider being rated could hear, which communication supports were available, and how much time the client had can all affect the report. If staff changed the scale, prompt, language, device, or timing during the cohort, identify the version change. Trend claims should compare compatible measures or state the limitation.
Separate direct, supported, and proxy sources
Label direct client report, client report with communication support, behavioral or physiological observation, and proxy report separately. Record why a proxy was used and whether the client had an accessible opportunity to respond. Support from an interpreter, AAC system, or trusted communication partner does not automatically convert a client's own report into proxy data. Disagreement between sources should remain visible.
Audit the transformation from raw report to dashboard field. Determine whether open comments were coded consistently, whether unfavorable responses were grouped into a neutral category, and whether staff could overwrite the source label. Sample the underlying record for both positive and concerning results. A program-level percentage is credible only when the source, coding rules, and missing responses remain recoverable.
Segment access before comparing experience. Report direct-route readiness and response by communication form, setting, service team, and other relevant groups with privacy protections. A high overall score can coexist with a group that rarely receives an accessible opportunity. Small cells and sensitive reports may require suppression or restricted review rather than public display.
Test whether reports change decisions
For positive, uncertain, and concerning results, identify the response owner, expected timing, interim safeguard, disposition, client communication, and evidence of action. Audit both completed actions and open reports. A measure adds little value when the plan collects experience data but offers no defined response, or when only favorable responses reach the formal review.
Trace a sample from report to outcome. Confirm the intake timestamp, triage, assigned owner, interim protection, qualified review, decision, implementation evidence, and client update. A closed ticket does not prove that the concern was resolved or that the client agreed with the disposition. Review reopened items, repeat concerns, overdue actions, and reports routed outside the ordinary workflow.
Check protected paths. Concerns involving harm, retaliation, privacy, discrimination, consent, medical risk, or another legal duty may require access beyond the treatment team. The audit should verify that the client could reach the applicable route and that the organization did not require a favorable clinical relationship to submit a complaint.
Audit action and interpretation
Trace concerning and positive reports to response and decisions, preserve disagreement, segment access, and reject unsupported causal conclusions.
Report each control with its own denominator: eligible plans, plans with a direct route, routes verified accessible, scheduled opportunities offered, direct responses received, concerning reports reviewed on time, actions implemented, and decisions communicated. Show overlap instead of adding gaps together. State exclusions, missing data, and confidence limitations beside the headline result.
Experience data should be reviewed with clinical outcomes, treatment integrity, access, safety, and burden while remaining a distinct evidence stream. An association between a plan change and improved ratings does not establish causation without an appropriate design. Use the audit to identify control failures, direct record review, and assign remediation. Define the owner, due date, retest cohort, success evidence, and governance body that will review unresolved risk.
Build Esi's client-experience measurement audit
Create one versioned client-experience measurement audit for the annual clinical governance review. Include direct communication, privacy, consent and assent when applicable, AAC and retained supports, authority, readiness, client and partner measures, missingness, experience, burden, decisions, owners, dates, and review triggers.
Work through Esi's example
Esi audits 30 mature plans. Twenty-five include direct client experience, 22 make the measure accessible, 20 define timing, 18 define partner response, and 16 trace results to a decision. Report 25/30, 22/30, 20/30, 18/30, and 16/30 separately because gaps may overlap. Keep every readiness state, client response, partner action, numerator, denominator, missing event, support, and experience measure visible. This fictional example supplies no universal threshold, legal conclusion, or outcome guarantee.
Address Esi's main fit risk
A satisfaction percentage can exclude clients whose response method was inaccessible. Esi keeps every eligible plan in the denominator and reports missingness. Review access, partner behavior, burden, safety, and lived experience separately.
Choose Esi's next action
Owners repair access and response rules, review concerning reports, and retest a new mature cohort. Record the qualified owner, interim support, evidence, due date, client communication, disposition, and next review.
Apply current sources to Esi's plan
For Esi's plan, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, assessment, 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 research, clinical expertise, client values, and context.
Use measurement and access evidence for Esi
For Esi's measures, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit procedures, representative evidence, and cautious interpretation. They create no universal experience threshold. Breaux and Smith offer assent-focused guidance in an evolving evidence base. ASHA supports continuous AAC access.
Close Esi's review
Review the client-experience measurement audit with Esi, the responsible clinician, affected partners, and the named specialists. Preserve direct communication, supports, disagreement, versions, limits, and open gaps. Keep this page draft and noindex until required reviews are complete.
Related resources
- How to Plan a Client Preference-Check Goal in ABA
- How to Plan Client Participation in an ABA Review Meeting
- How to Plan an Understanding-Confirmation Goal in ABA
- How to Plan a Client Preference About Ending an ABA Goal
Sources
- Behavior Analyst Certification Board, Ethics Information and Ethics Codes
- Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts
- Behavior Analyst Certification Board, BCBA Test Content Outline, 6th edition
- Ethical Behavior Analysis: Evidence-Based Practice as a Framework for Ethical Decision Making
- A Practitioner Guide to Assessing and Improving Treatment Integrity
- Reporting of Treatment Integrity in Applied Behavior Analysis Research
- The Impact of Treatment Integrity on Intervention Effectiveness
- Treatment Integrity Reporting in Behavior Analysis Journals
- Breaux and Smith, Assent in Applied Behaviour Analysis and Positive Behaviour Support
- American Speech-Language-Hearing Association, Augmentative and Alternative Communication