Audit the Source and Authority for an ABA Plan Change

To audit the source and authority for an ABA plan change, trace every proposed and released component to the requestor, original evidence, direct client response, applicable legal authority, qualified professional decision, and consent or assent when applicable. Verify the version, effective scope, staff readiness, system distribution, and actual use. Hold any change whose authorship, authority, evidence, or client involvement cannot be reconstructed.

Lock the change cohort

Define the plan family, versions, component changes, request dates, release period, people, settings, systems, and maturity cutoff before calculating completeness.

Freeze the cohort before testing records and include held, declined, partial, corrected, and rolled-back changes that meet the criteria. Choose a cutoff that allows release and first-use evidence to mature, or report those stages separately. Preserve every eligible component in the denominator and document exclusions without knowing whether the authority chain passes. This prevents clean completed changes from crowding out unresolved ones.

Trace the request

Identify client, caregiver, clinician, staff, school, medical professional, payer, incident review, reassessment, software, or other source and preserve the original message and context.

Record what the source observed or requested, the version and setting involved, and the desired outcome without treating the request as approval. For AI output, preserve the authorized tool, input provenance, model or version, and human-review boundary. Link duplicates without deleting them when different sources provide distinct evidence or authority. Missing original context should remain an audit finding.

Trace evidence and client response

Link observations, records, measures, health and access information, alternatives, burden, risks, direct client communication, corrections, dissent, and unresolved uncertainty.

Trace summary claims back to raw counts, definitions, exposure, integrity, and missingness. Keep direct client input, proxy reports, professional guidance, and software output separately attributable. Verify that alternatives and unwanted effects were considered, not only the evidence favoring change. A correction should preserve the original record and identify any downstream decision or data that required reconsideration.

Trace authority by decision

Separate legal consent, assent when applicable, clinical authorship and approval, medical order, school decision, payer coverage action, operations release, and software administration.

For each state, identify the person or system, evidence, date, scope, and source rule. Attendance or workflow completion does not transfer authority. A clinical decision can be valid while payer or operational work remains open, and the converse is also true. Hold the affected scope when required authorship or participation cannot be reconstructed, then route correction to the responsible reviewer.

Trace release and use

Verify version identity, effective scope, training, readiness, distribution, stale-copy removal, scheduling, first use, implementation evidence, exceptions, and exposed sessions.

Follow selected changes into actual care across representative sites, shifts, devices, printouts, and offline routes. Confirm the version delivered rather than relying on the effective date. Separate client response from missing support, system failure, mixed version, and unauthorized deviation. Keep partial release visible and trace every exception or correction to the original change and affected outcome data.

Close findings with proof

Assign owner, affected scope, interim control, due date, correction method, verification evidence, communication, clinical disposition, and follow-up for every missing or conflicting field.

Protect exposed clients before broad remediation and assign each issue to the role able to fix it. Report raw counts and denominator-safe rates while preserving overlapping failures in one change. Retest the exact authority and release path after correction, then retain the initial finding, repair evidence, residual limits, accessible client communication, and qualified closure rather than overwriting failure with the current state.

Build Uma's plan-change provenance audit

Uma's provenance file supports the "audit source authority ABA plan change" workflow by tracing every changed component through distinct evidence gates. It retains the requestor and original words, source record, client communication, caregiver and interdisciplinary input, legal and professional authority, urgency, health and safety actions, interim support, qualified decision, alternatives, consent and assent when applicable, approved version, effective scope, implementation evidence, communication, review date, and open limits. A reviewer should be able to reconstruct who requested, who supplied evidence, who had authority to decide, and what users received.

Work through Uma's example

Uma audits 15 released changes. Twelve link to a requestor and source evidence, eleven include the required client-review record, and ten identify qualified approval and effective scope. The audit reports these as separate completeness measures: 12 of 15, or 80.0 percent; 11 of 15, or 73.3 percent; and 10 of 15, or 66.7 percent. Five changes remain held by at least one gate. Because the gaps overlap, their counts cannot be added to estimate a larger failure total. This fictional quarterly multisite review sets no universal clinical recommendation, legal authority, coverage rule, release threshold, or outcome promise.

Address Uma's main request risk

A signed final plan can hide who requested a change or whether the signer had authority for that component. Uma's audit follows provenance through implementation rather than trusting the cover page. Separate an observation or request from the authority to decide, the evidence needed for a clinical conclusion, and the operational work required to release a version. A prompt response can still preserve careful review.

Choose Uma's next action

Owners repair only their missing evidence, affected use is reviewed, and the qualified clinical leader decides whether the version remains active, narrows, pauses, or is replaced. Record accept, adapt, assess, refer, hold, decline, pause, or close with the responsible role, rationale, effective scope, due date, evidence required for closure, accessible communication, and next review. Software may route requests and preserve state. Qualified professionals make case-specific decisions within scope.

Protect Uma's access and choice

Keep Uma's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, pain communication, health support, movement, rest, relationships, and emergency help available. Offer a private and accessible way to accept, decline, pause, withdraw when applicable, report discomfort, ask a question, and correct the record. Proxy and professional input can inform review without replacing Uma's direct experience.

Apply current sources to Uma's request

The BACB ethics hub, current Ethics Code, CASP public summary, and BCBA Test Content Outline provide scoped professional, client-involvement, evaluation, documentation, and training context.

An evidence-based ABA framework supports integrating research, expertise, client values, and context.

A treatment-integrity practitioner guide, the Essig review, research on integrity's relationship to intervention effects, and a reporting review support explicit definitions, implementation evidence, and cautious conclusions.

ASHA supports continuous AAC access.

Rehearse Uma's request workflow

Test the plan-change provenance audit with a client request, caregiver disagreement, payer deadline, school proposal, medical concern, safety incident, staff report, AI suggestion, reassessment result, unavailable AAC, privacy limit, missing source, uncertain authority, urgent pause, system outage, and late follow-up. Confirm that immediate action, attribution, qualified review, version control, communication, and closure remain correct.

Close Uma's request review

Review the plan-change provenance audit with Uma, the responsible clinician, affected requestors, and the specialists named by the manifest. Preserve original requests, evidence, direct client input, authority, decisions, implementation, open findings, and limitations. Keep the page draft and noindex until required clinical, treatment-integrity, client or family, accessibility, interdisciplinary, payer, privacy, AI, and legal reviews are complete.

How to Audit the Source and Authority for an ABA Plan Change