To audit partner-response measurement in ABA goals, lock a mature cohort and test whether each plan defines the client's message, the partner's action, a response window, opportunity readiness, inaccessible events, and direct client experience. Review latency, implementation evidence, observer quality, burden, missingness, and decision use. Keep client and partner numerators and denominators separate and preserve failed-system opportunities.
Lock the audit cohort
Define goal types, maturity date, settings, client-message requirement, partner-action requirement, response window, readiness rule, experience window, exclusions, and owners.
Write a protocol before opening the records. Decide which goals have been active long enough to contain representative opportunities, which versions are in scope, and the date through which data are complete. Include communication, break, stop, help, choice, and other goals only when they actually require a partner action. Preserve the full eligible cohort rather than selecting plans with cleaner data.
Create a data dictionary for each audit field and test it on a small sample. Reviewers should know what counts as a defined message, an actionable partner step, a response window, a ready opportunity, and direct client experience. Record exclusions with reasons and retain the original denominator. A plan with missing documentation remains an audit finding rather than disappearing from the cohort.
Audit client and partner units
Check operational definitions, accepted communication forms, partner role, exact action, latency start and end, partial response, correction, and outcome.
Follow one event from trigger through closure. The client unit records whether an agreed message occurred under accessible conditions. The partner unit records whether the named person performed the full response. Define partial responses, such as acknowledging a break request without arranging coverage, so reviewers do not score them inconsistently. Record whether a later correction occurred without rewriting the initial miss.
Inspect denominators in the calculation as well as the prose. A partner-response rate usually begins with recognized messages or another explicit trigger, while a client-message rate begins with ready eligible opportunities. Dividing both numerators by all sessions can make the measures look comparable while answering neither question accurately.
Audit opportunity readiness
Verify AAC, access, partner presence, authority, materials, environment, safety, and ordinary supports. Preserve failed readiness as a system event.
Readiness must be observable and version specific. Check whether the communication system was within reach, the expected partner was present and authorized, promised materials or environmental supports were available, and any specialist-approved conditions were met. “Client attended” or “staff available” alone does not establish that the planned opportunity existed.
Classify failed readiness by owner and cause. Missing AAC, absent staff coverage, inaccessible space, expired instructions, or unavailable equipment may require different correction routes. Exclude such an event from a client-performance denominator only while keeping it in system-readiness counts, narratives, and safety review.
Audit evidence quality
Review observer training, agreement, representative sampling, drift, missingness, proxy versus direct report, device timestamps, corrections, and version history.
Compare written definitions with what observers were trained to score. Sample different shifts, partners, settings, and response types rather than relying on convenient sessions. If agreement is assessed, report the method, sample size, and period. A strong agreement number from an unrepresentative sample does not establish that implementation was reliable across the goal.
Trace missing values and timestamps. Blank latency may mean that no trigger occurred, the observer missed the event, or the partner never responded. Those states require different codes. Preserve the initial entry, correction history, and goal version so an audit can distinguish a late documentation repair from the response that actually occurred.
Audit decision use
Trace measures to continue, revise, train, support, pause, refer, or close decisions with qualified authority, client communication, burden review, due date, and follow-up.
Require each material finding to have a disposition. A missing partner definition may lead to plan revision; delayed response may require training and direct observation; inaccessible opportunities may require operational or specialist action; a safety concern may require immediate escalation. Name the person with authority, interim protection, evidence of completion, and a date for retesting.
Share results with affected clients in accessible language and invite correction of experience data. Do not treat a governance percentage as a clinical conclusion about an individual. Closure means the defect was corrected and verified in the relevant setting, not merely that a task was marked complete. Report unresolved issues and overlapping defects without adding them into an inflated unique-goal total.
Build Willa's partner-response measurement audit
Use one row per mature goal and identify the client message, partner action, response window, readiness conditions, privacy and AAC supports, eligible opportunities, exceptions, burden, direct client experience, and decision the measures inform. Verify that the partner denominator begins only when the client message or other defined trigger occurs. Preserve system failures and missed partner responses rather than shifting them into client-performance data, and retain overlapping defects at the goal level.
Work through Willa's example
Willa audits 25 mature goals. Twenty-three define client messages, 20 define partner actions, 18 specify a response window, 17 record readiness, and 16 include direct client experience. The rates are 92%, 80%, 72%, 68%, and 64%, with corresponding gaps of 2, 5, 7, 8, and 9 goals. Those defects can overlap on the same goal, so they cannot be summed into a unique affected-goal count. The results describe this governance cohort and create no universal access threshold.
Address Willa's main fit risk
A high client-request rate can coexist with delayed or absent partner response. Willa's audit tests both sides and the conditions that made a response possible. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.
Choose Willa's next action
Owners repair affected definitions, review any missed safety or access response, preserve raw events, and retest a new mature cohort. Record the qualified owner, authority, affected setting, interim support, evidence needed, due date, client communication, correction route, disposition, and next review. Software may coordinate workflow while qualified people make decisions within scope.
Apply current professional sources to Willa's goal
For Willa's goal, the BACB ethics hub identifies the current Ethics Code, which addresses client involvement, consent and assent when applicable, assessment, medical needs, risk, intervention, 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 planning 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 Willa
In Willa'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 access threshold. Breaux and Smith offer assent-focused practice guidance while describing an evolving evidence base. ASHA supports continuous access to AAC tools or devices.
Close Willa's review
Review the partner-response measurement audit with Willa, the responsible clinician, affected partners, and the specialists named in the manifest. Preserve direct communication, ordinary supports, disagreement, system duties, versions, decisions, limits, and open gaps. Keep this page draft and noindex until all required reviews are complete.
Related resources
- How to Plan a Client Choice-Making Goal in ABA
- How to Plan a Partner Consent-Checking Goal in ABA
- How to Plan an Accessible Pause or Stop Goal in ABA
- How to Plan a Communication-Technology Backup Goal in ABA
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