How to Audit Responses to Client Requests in ABA Plans

To audit responses to client requests in ABA plans, lock a mature request cohort and trace accessible intake, classification, authority, response owner, due date, interim support, decision, explanation, implementation, client confirmation, and any correction or review route. Preserve unresolved requests in fixed denominators. Measure latency, completion, burden, repeated requests, disparities, and client experience without treating acknowledgment as resolution.

Lock the request cohort

Define request types, entry date, maturity window, channels, access requirement, authority classes, due-date sources, outcomes, exclusions, and responsible owners.

Write the sampling rule before inspecting results. Define the audit dates, included service lines and locations, recognized request channels, maturity period, request categories, and permissible exclusions. Include requests with missing fields, inaccessible intake, or no owner in the denominator. Excluding them would remove the system failures the audit is intended to find.

Freeze the source record and due-date logic. An internal service target, urgent clinical need, payer deadline, privacy or records process, employment workflow, safety duty, and legal requirement may use different clocks. Record the applicable source, pauses, transfers, and interim support rather than judging every request against one generic turnaround time.

Trace authority and ownership

Check whether clinical, access, privacy, payer, financial, operations, safety, medical, or legal questions reached the qualified role and retained authorship.

Follow each request from the client's words to the final owner. Confirm that routing preserved the requested outcome and did not convert a complaint, privacy preference, staffing request, explanation question, or safety issue into a generic task. Identify transfers, time without an owner, requests for duplicate information, and any decision made outside the responsible role.

One coordinator may manage status while specialists decide separate components. The audit should show which owner handled each part, what evidence they used, and whether the client received a coherent combined response. Keep the client's authorship distinct from staff summaries and proxy observations.

Trace response completion

Verify acknowledgment, interim support, decision, understandable reason, implementation, client confirmation, correction or review route, and closure evidence.

Sample underlying evidence rather than accepting status labels. An approved staffing or support request needs actual assignment or availability; a schedule change needs the released calendar; an explanation request needs an accessible answer; a correction needs the current record and downstream review; a denial needs a qualified reason and applicable reconsideration route. Client confirmation means receipt and opportunity to respond, not forced agreement.

Review reopenings and repeated requests. Link them to the earlier item and determine whether the first closure lacked implementation, used an inaccessible explanation, missed a downstream copy, or whether the client's need changed later. Preserve both the original outcome and the new event so closure rates remain reproducible.

Define states before sampling

Use mutually exclusive stage labels such as received, inaccessible, awaiting classification, assigned, awaiting evidence, decided, approved but unimplemented, implemented, client-confirmed, withdrawn, and closed with an unresolved objection. Keep timestamps and source evidence for every transition. A request can meet an acknowledgment measure while remaining open for the decision or implementation measures, so one status field cannot support the whole audit.

Review patterns without hiding cohorts

Stratify the locked cohort by request type, setting, channel, communication access, owner, urgency source, and outcome when cell sizes permit responsible reporting. Compare like stages and maturity windows. Small groups, overlapping categories, missing demographic information, and privacy constraints belong in the interpretation. A disparity is a review signal that needs qualified investigation, not proof of a cause or a person-level conclusion.

Measure timeliness and equity

Report raw counts, fixed denominators, age, latency, unresolved work, repeated requests, access failures, burden, outcomes by request type, and client experience.

Report requests eligible, accessible intake, owner and due date assigned, interim support provided, qualified decision, understandable response, implementation, client confirmation, review-route access, unresolved aging, and later reopening. Show overlapping gaps without adding them into a false total. Separate completed-request latency from the current age of open work.

Segment results by request type, channel, communication access, setting, owner, and other relevant groups when privacy and cell size permit. A disparity is a signal for qualified investigation, not proof of cause. Assign urgent case repair and systemic remediation separately, with an owner, due date, affected records, control change, and retest cohort.

Build Imani's client-request response audit

Create one versioned client-request response audit for the quarterly governance review. Include the request or choice, direct communication, consent and assent when applicable, privacy, AAC and retained supports, authority, source evidence, system and partner duties, eligible opportunities, client and partner measures, experience, burden, decisions, owners, dates, and review triggers.

Work through Imani's example

Imani audits 40 mature requests. Thirty-eight have accessible intake, 34 have an owner and due date, 31 have a decision with explanation, 29 show implementation, and 26 have client confirmation. Report 38/40, 34/40, 31/40, 29/40, and 26/40 separately; gaps may overlap. Keep every opportunity, readiness state, client action, partner response, system failure, numerator, denominator, exclusion, support, and experience measure visible. This fictional example supplies no universal goal, dose, independence standard, legal conclusion, payer result, or outcome guarantee.

Address Imani's main fit risk

A fast acknowledgment rate can conceal delayed decisions or unimplemented approvals. Imani's audit traces each request through the outcome the client can verify. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Imani's next action

Owners age open requests, repair missed access or safety actions immediately, assign due dates, 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.

Apply current professional sources to Imani's plan

For Imani's plan, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, confidentiality, 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 Imani

In Imani'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 response 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 Imani's review

Review the client-request response audit with Imani, 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.