Audit an ABA Client-Experience Report for Integrity

To audit an ABA client-experience report, test its purpose, frozen cohort, measure identity, direct access, source labels, denominators, missingness, privacy, calculations, versions, corrections, narrative coding, claims, decisions, actions, and client communication. Reproduce every material result from source evidence, preserve failures, assign remediation, protect affected clients, and validate corrections in a fresh report while retaining the original history.

Lock the audit population

Define released and corrected reports, periods, formats, service lines, owners, risk strata, and maturity. Include withdrawn, low-volume, unfavorable, and incident-related reports when in scope. Freeze all 40 reports before testing so failed or unavailable files remain findings.

Test cohort reproducibility

Verify each report's eligible population, entry event, exposure, maturity, measure and access versions, cutoff, inclusion, exclusions, and frozen client list. Recreate the funnel from source records. A respondent list alone does not satisfy the cohort test.

Test source and authorship

Trace direct reports, proxy reports, narratives, ratings, observations, outcomes, and integrity evidence to their original source, question, time, mode, author, version, and correction history. Confirm that summaries and translations preserve meaning and that proxy content never becomes client-authored evidence.

Recalculate every material number

Reproduce counts, denominators, percentages, categories, trends, missingness, suppression, and action aging using approved formulas. Inspect duplicates, late data, corrections, rounding, cohort changes, and incompatible versions. Record discrepancies without silently changing the released file.

Review access, missingness, and privacy

Check whether clients received usable communication and AAC routes, whether missing reasons are observable and complete, and whether reports protect small cells and narrative identities. Test permissions, exports, retention, and correction propagation under the applicable privacy and records workflow.

Audit narrative coding

Compare the codebook, reviewer training, agreement sample, original narratives, multi-code rules, uncertainty, and minority themes. Look for favorable reframing, removed context, selective quotes, or a theme applied beyond its definition. Preserve client corrections and disagreements.

Match claims to evidence

Classify statements about experience, outcome, integrity, association, change, causation, population, safety, and quality. Verify that each stays within its evidence. Flag unsupported generalization, respondent-only claims presented as cohort results, and causal language based on uncontrolled change.

Trace decisions and actions

Follow actionable findings to a qualified owner, interim protection, investigation, decision, due date, implementation evidence, client communication, confirmation, closure, and reopening. Keep overdue and unconfirmed actions visible. Report release alone never counts as feedback-loop closure.

Validate remediation prospectively

Assign each gap by report and domain, protect current clients, issue an auditable correction or addendum, communicate with affected readers, and test the repaired process in a new mature report. Preserve the original report and audit evidence. Closure requires the predefined validation result and responsible approval.

Trace Imani's report from source to action

For Imani, trace every released reports tested against their frozen cohorts, calculations, claims, actions, and client communication from the original event and access state through the frozen client-experience report audit file, calculation, display, qualified interpretation, decision, implementation, client communication, confirmation, and closure. Preserve source, author, version, time, correction, missingness, and uncertainty at every handoff. A dashboard or report can organize evidence; it cannot supply missing authority, client meaning, or causal support.

Build Imani's operational report record

Create one versioned client-experience report audit file for the annual clinical-governance audit. Record purpose, audience, qualified owner, cohort definition, unit, exposure, maturity, measure and access versions, direct and proxy sources, privacy, consent and assent when applicable, AAC, raw counts, formulas, missing states, corrections, claims, actions, due dates, confirmation, distribution, retention, and next review. Limit row-level access and copied narrative to approved roles and uses.

Work through Imani's example

Imani audits 40 released reports. Thirty-seven preserve a frozen cohort, 34 link every material result to source evidence, 32 reproduce all denominators, 29 disclose missingness, 25 trace findings to action, and 22 show client communication or confirmation when due. Report 37/40, 34/40, 32/40, 29/40, 25/40, and 22/40 separately, with all failed reports assigned. Preserve the frozen population, every intermediate state, raw counts, denominators, missing reasons, source labels, versions, corrections, actions, and open work. This fictional example demonstrates one reporting control. It supplies no universal threshold, validation result, legal conclusion, treatment effect, population estimate, or outcome guarantee.

Use Imani's evidence for a bounded decision

Before release, identify the exact decision and authorized owner. For Imani, document what the report supports, what it cannot answer, current protection, further evidence, implementation test, client-facing explanation, disagreement route, next review, and reopening rule. Hold a decision when its cohort, access, source, calculation, privacy, or version evidence is unreliable. Preserve urgent individual routes while aggregate review continues.

Review Imani's results without losing the denominator

For Imani, show counts beside percentages and retain eligible, immature, inaccessible, missing, unfavorable, corrected, overdue, suppressed, and reopened items. Segment only with compatible definitions and privacy-safe groups. Explain measure, cohort, access, collector, setting, and service changes before comparing. Keep direct client report separate from proxy evidence, clinical outcome, treatment integrity, attendance, authorization, and payment.

Address Imani's main reporting risk

A polished report can contain accurate arithmetic for a respondent-only cohort while hiding access failures and unsupported claims. Imani's audit follows each statement back to eligibility and source. Review cohort construction, direct access, authorship, privacy, missingness, calculations, versions, corrections, claims, and action response separately. Accurate arithmetic cannot rescue a report built from the wrong population or measure. One favorable aggregate cannot close a serious individual concern, and one critical response cannot describe every client.

Choose Imani's next reporting action

Imani's governance team protects affected decisions, corrects active reports through versioned addenda, and validates remediation using a new locked sample. Record the responsible roles, affected clients and reports, interim safeguards, corrected artifact, downstream recipients, due dates, validation evidence, accessible explanation, current state, and next governance check. Keep original evidence and report versions available. An auditable correction changes the current artifact and retains what readers previously received.

Apply current professional sources to Imani's report

For Imani, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, confidentiality, assessment, documentation, risk, 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 evidence, clinical expertise, client values, and context.

Use reporting evidence carefully for Imani

For Imani's report, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit units, procedures, representative evidence, observer controls, and cautious interpretation. They create no universal client-experience threshold, reporting formula, or causal conclusion. Breaux and Smith offer assent-focused practice guidance in an evolving evidence base. ASHA supports continuous AAC access.

Close Imani's reporting review

Review the client-experience report audit file with Imani, the responsible clinician, measurement and operational owners, privacy and access roles, and the specialists named in the manifest. Verify that the cohort, access, sources, calculations, claims, actions, and limits remain understandable and reproducible. Preserve client corrections and open concerns. Keep this page draft and noindex until every required review is complete.

How to Audit an ABA Client-Experience Report