Choose Between an ABA Plan Addendum and a New Version

Choose an ABA plan addendum or new version by asking whether the entry corrects or supplements the record while preserving the original plan's meaning, or prospectively changes what people should do, experience, measure, or decide. A material change to clinical content, access, risk, roles, scope, or effective use needs explicit version control. Preserve original content, authorship, dates, rationale, approvals, distribution, and implementation history under either method.

Describe the exact entry

Identify the original plan and component, proposed text, reason, source evidence, author, actual discovery time, intended effect, and affected period.

Write the proposed entry beside the original wording and state whether it explains history, corrects a factual error, adds context, or directs future action. Preserve Faye's report and the source that prompted the change. Avoid backdating the entry to the original plan date. The actual discovery and entry times help reviewers distinguish what people knew during prior implementation from what was learned later.

Test for clinical meaning

Ask whether goals, definitions, response forms, procedures, supports, risks, roles, measures, decision rules, settings, or client experience change.

Review downstream meaning, not only the number of words altered. A small edit to a denominator, prompt order, stop condition, or valid AAC response can materially change implementation and outcomes. If an authorized user would understand or act on the component differently, treat that as prospective clinical change. Record which components and historical interpretations may be affected.

Test for prospective action

Determine whether staff, caregivers, systems, schedules, data collection, supervision, or the client would act differently after the entry.

Trace the proposed text through point-of-care instructions, forms, dashboards, training, and client communication. If future behavior changes, create a new controlled version even when the update also corrects a prior ambiguity. An addendum can preserve a historical clarification, but it should not become a side channel for active instructions that bypass comparison, participation, approval, and release controls.

Preserve record integrity

Keep original content and its author and date visible. Record the correction, addendum, or new version with actual entry time and reason; avoid overwriting history.

Link the entry bidirectionally with every affected record and retain who made and approved it. When prior data or decisions need reconsideration, preserve their original state and add a traceable review rather than recalculating silently. Protect the record under applicable retention, privacy, and correction rules. A cleaner current display should not erase the sequence of real events.

Apply the right approvals

Route clinical content to a qualified clinician and records, consent, payer, privacy, legal, and operational questions to their responsible roles.

Separate approval states even when one coordinated workflow collects them. A records specialist can ensure an addendum is attributable without deciding its clinical meaning, while a clinician cannot settle legal retention or payer treatment outside scope. Explain material changes to Faye accessibly and preserve any disagreement. Software may enforce versioning but does not choose the correct clinical method by itself.

Complete downstream control

For a new version, compare components, obtain client involvement, prepare staff, update systems and measures, set effective scope, withdraw stale copies, and review implementation.

Assign evidence and owners to each release gate and keep unready settings visibly held. Mark the version boundary in outcome displays, verify first use, and record exceptions separately. For a true historical addendum, distribute the corrected interpretation to authorized users and link it to any affected prior decision. Under either method, test retrieval, source identity, and correction history before closure.

Build Faye's record-method decision

Create a versioned record-method decision for the ABA plan addendum or new version question. Preserve client and plan identity, controlled components, clinical meaning, direct client communication, source evidence, qualified authority, lifecycle state, effective scope, access and safety, training and readiness, distribution, actual use, exceptions, correction history, retention, owners, review dates, and unresolved limits. Another qualified reviewer should be able to reconstruct what the artifact proves and which decisions remain elsewhere.

Work through Faye's example

Faye's clinician discovers a misspelled venue name and a response definition that omits AAC. The venue correction receives a dated correction linked to the original. Adding AAC changes eligible response forms, measurement, staff action, and client access, so it enters qualified review and a new prospective plan version. The two edits never share one generic addendum label. Show all states, counts, denominators, overlaps, unavailable evidence, and open work. This fictional clinic goal-definition review example illustrates one plan-control artifact and supplies no universal clinical rule, legal conclusion, retention period, release threshold, or outcome guarantee.

Address Faye's main control risk

An addendum can hide a clinical change inside a historical record update. Faye's method classifies effect, authority, and implementation; document length does not determine the record method. Keep the artifact's evidentiary claim narrow. A cover sheet, register, log, exception, variance, addendum, archive, acknowledgment, or audit can organize evidence without creating clinical authority or proving implementation.

Choose Faye's next action

The records owner preserves both paths, and the clinician releases the AAC-inclusive version with training, data-definition updates, client review, and first-use validation. Record the responsible role, authority, affected scope, interim control, due date, evidence needed for closure, accessible communication, and next review. Software may enforce document states and access. Qualified professionals make case-specific clinical decisions within scope.

Protect Faye's access and history

Keep Faye's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, pain communication, health support, movement, rest, relationships, and emergency help available. Preserve original records, actual dates, authorship, corrections, direct client communication, dissent, and withdrawal when applicable. Summaries and proxy input should never overwrite the person's experience.

Apply current sources to Faye's control

The BACB ethics hub, current Ethics Code, CASP public summary, and BCBA Test Content Outline provide scoped professional, client-involvement, documentation, evaluation, 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 procedures, measurement, and bounded interpretation.

ASHA supports continuous AAC access.

Rehearse Faye's control workflow

Test the record-method decision with an urgent pause, client request, missing approval, temporary variance, changed definition, unavailable AAC, medical update, incomplete staff, stale mobile cache, wrong printed copy, failed link, system outage, exception, record correction, rollback, service transition, and access request. Confirm that identity, scope, authority, safe action, version history, and follow-up remain intact.

Close Faye's artifact review

Review the record-method decision with Faye, the responsible clinician, records and system owners, and the specialists named by the manifest. Preserve plan content, direct client input, evidence, authority, implementation, corrections, limits, and open findings. Keep the page draft and noindex until required clinical, treatment-integrity, client or family, records, accessibility, privacy, security, software, payer, and legal reviews are complete.

How to Choose Between an ABA Plan Addendum and a New Version