How to Audit Closure of Client Requests in ABA Care

To audit client request closure in ABA, lock a mature cohort and trace accessible entry, classification, authority, acknowledgment, interim support, decision, explanation, implementation, client confirmation, disagreement, correction, and closure evidence. Keep unresolved and reopened requests visible in fixed denominators. Report latency, aging, burden, disparities, repeated requests, and client experience without equating acknowledgment with completion.

Lock the mature cohort

Define entry event, request types, access requirements, authority, due-date sources, maturity window, interim support, closure evidence, reopen rule, exclusions, and owners.

Write the cohort rule before reading outcomes. Define the audit period, request channels, service lines, locations, request categories, minimum age for maturity, and allowed exclusions. Include requests from AAC, portal, phone, email, in-person, proxy-supported, complaint, and other recognized routes when they meet the rule. Keep requests with missing data in the denominator. Removing them would hide the very access and control failures under review.

Map the due date to its actual source. An internal service target, clinical review date, payer deadline, privacy or record requirement, employment process, safety duty, and legal deadline are not interchangeable. Record which authority applies and whether the request needed interim support while the final decision was pending.

Trace each state

Check intake, classification, acknowledgment, qualified decision, understandable reason, implementation, client confirmation, disagreement, correction, closure, and later reopening.

Sample the underlying record from the client's first communication forward. Confirm the intake timestamp, exact request, communication access, classification, assigned owner, transfers, acknowledgment, evidence collected, decision, reason, implementation, client update, and any correction or appeal. Preserve gaps instead of inferring that an undocumented step occurred.

Distinguish elapsed time in each state. A quick acknowledgment can coexist with a long unassigned wait, and a timely decision can be followed by delayed implementation. Report aging by current owner and request type. Check whether urgent concerns received interim protection and whether ordinary supports remained available during review.

Test evidence and controls

Verify source links, dates, authorship, access, privacy, handoffs, downstream updates, reminders, escalation, nonretaliation, version history, and missingness.

Test the system controls as well as the record. Verify that reminders fire, overdue items escalate, reassigned staff do not lose ownership, restricted reports remain private, and closed items cannot bypass required fields. Sample exports, dashboards, and client-facing status views against source records. A governance report is unreliable when its closed status or date can be changed without preserving history.

Review access and disparity. Compare channel readiness, response time, outcomes, reopenings, and burden by communication form, setting, request type, and other relevant groups with appropriate privacy protection. A low request rate may reflect inaccessible intake or fear of retaliation. Review withdrawals, duplicate requests, and adverse changes after reporting for possible control failures.

Define closure evidence by request type

An information request may close with an accessible answer and confirmed receipt. An approved support request needs implementation evidence. A correction needs the changed record and any downstream review. A denied request needs the qualified decision, understandable reason, and applicable disagreement or review route. Define these requirements before sampling so a generic closed status cannot substitute for the outcome the person requested.

Build a closure matrix for each category and test a sample against it. Staffing changes may need assignment and continuity evidence; schedule changes need calendar implementation; data requests need authorized delivery and explanation; safety or privacy concerns need qualified handling and interim protection; and a retained-support request needs proof that the support remained available. Mark partial closure when one component is complete and another remains open.

Treat reopening as new evidence

Record why a request reopened, which prior closure element failed, who owns the new action, and whether interim protection is needed. Keep the original cohort result and report the later reopening separately. Do not overwrite the first closure date or remove the request from the denominator. Reopen patterns can identify premature closure, inaccessible explanations, failed implementation, or a changed client need.

Report honest outcomes

Preserve raw counts and fixed denominators. Segment latency, age, outcomes, burden, repeated requests, access failures, disparities, reopened work, and client experience.

Report requests eligible, channels ready, requests acknowledged, qualified decisions, implementations completed, client confirmations, denials with review routes, overdue items, unsupported closures, and later reopenings. Show overlapping gaps without adding them into a false total. State missingness, exclusions, data-quality limits, and the difference between point-in-time aging and completed-request latency.

Turn findings into owned remediation. For each failed control, name the responsible leader, immediate protection, required evidence, due date, affected cohort, and retest method. Reopen individual requests when the audit finds an unsupported closure. Governance is complete only when urgent cases are protected, systemic fixes are implemented, and a new mature cohort demonstrates that the control now works.

Build Una's client-request closure audit

Teams that audit client request closure in ABA should create one versioned record for the semiannual governance review. Include the request, direct communication, privacy, consent and assent when applicable, AAC and retained supports, authority, source evidence, interim protection, partner duties, eligible opportunities, client and partner measures, experience, burden, decisions, owners, dates, and review triggers.

Work through Una's example

Una audits 50 mature requests. Forty-eight have accessible entry, 44 have a documented decision, 39 show implementation, and 35 have client confirmation. Four closed requests later reopen. Report 48/50, 44/50, 39/50, 35/50, and 4 reopened requests separately. 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, legal conclusion, payer result, or outcome guarantee.

Address Una's main fit risk

A closed status can hide missing implementation or client disagreement. Una's audit requires evidence of the promised action and current client confirmation. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Una's next action

Owners age unresolved work, reopen unsupported closures, repair urgent access or safety failures, and retest a new mature cohort. Record the qualified owner, authority, interim support, evidence needed, due date, client communication, correction route, disposition, and next review.

Apply current professional sources to Una's plan

For Una's plan, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, confidentiality, 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 integrating research, clinical expertise, client values, and context.

Use implementation and access evidence for Una

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

Close Una's review

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