Date and Version Evidence Used in an ABA Plan

To date and version evidence used in an ABA treatment plan, record when the underlying events occurred, when information was collected or reported, its as-of date, author, method and instrument or data version, when the clinician used it, and whether a later correction or source superseded it. Add a recheck trigger so historical evidence cannot silently present itself as current.

Use more than one date when needed

Distinguish event or observation period, report date, author date, receipt date, entry date, correction date, as-of date, and plan decision date.

Use the dates that answer how current and traceable the source is. A caregiver may describe events from May, submit the report in June, and have it entered in July. The plan author may use it in August. Recording only the entry date makes the evidence look more recent than the events.

For a continuing data stream, name the collection window and cutoff. For an instruction, show the effective or as-of date and the authoring source. Keep time zones and partial dates explicit when they matter instead of inventing precision.

Version the source

Record instrument edition, form version, data extract, plan component, operational definition, scoring rule, software export, translation, and correction history where relevant.

Assign a stable evidence ID to each version and link derivatives back to it. A translated form, rescored instrument, corrected export, or changed operational definition may create a new version even when the observation dates stay the same. Record who made the change and why.

Avoid filenames such as “final” or “latest” as the only identifier. Use controlled storage, immutable prior versions, and a clear current-state marker. The plan citation should resolve to the exact evidence used for the decision, not whichever file now occupies a folder.

Define freshness by decision

A stable history may remain useful while a current schedule, medication, preference, staffing state, authorization, or risk fact needs recent verification.

Set freshness according to how the evidence is used. A developmental history can remain relevant as history, while current medications, health restrictions, communication access, client priorities, staff availability, payer authorization, or safety routes may require verification close to the decision. Document the reason for the interval rather than applying one age limit to all sources.

Mark a source “historical only” when it no longer supports a current-state claim. If current verification is pending, state the interim action and owner. Source age alone does not establish invalidity, and a recent entry can still contain old information.

Label historical context

Keep older evidence when it helps interpretation, but state its period, changed conditions, present limits, and whether it supports a current decision.

Historical evidence can show trajectory, prior supports, or why a procedure changed. Present it in a separate period and identify changes in setting, definitions, health, staff, communication, or opportunity. Do not merge it into a current baseline without a justified bridge.

Explain the bounded use in plain language. “Supports history of prior classroom difficulty” is different from “establishes current classroom frequency.” Retaining the source prevents selective memory while labeling the limit prevents silent reuse.

Set recheck triggers

Use elapsed time, plan review, health change, new setting, client request, access change, poor fit, conflicting data, adverse effect, staff change, or source correction.

Give each material source an event-based trigger and, when needed, a maximum review interval. A change in medication, AAC system, mobility support, school, job, caregiver, or client preference may require immediate recheck even if the scheduled review is months away. An adverse event or attribution correction may trigger wider reassessment.

Assign the trigger owner and notification route. A calendar reminder without responsibility often expires unnoticed. Record the evidence needed to renew current use and the safer interim state if verification is late.

Prevent silent supersession

Retain the prior source, mark the new source and effective use, reassess linked statements, notify affected users, and preserve the audit trail.

Supersession should be an explicit transaction. Identify which version replaces which, the effective date, author, reason, linked plan statements, and decisions requiring review. Keep the old source accessible under appropriate privacy controls and prevent new use as current evidence.

Trace the new version through staff instructions, reports, data systems, authorizations, and handoffs. Verify receipt rather than assuming an upload reached practice. Record failed delivery and unresolved conflicts until the downstream repair is complete.

Build Wren's evidence freshness register

Give every source used in Wren's renewal a stable evidence ID and separate its event or collection period, author date, receipt date, file version, and plan-use date. Record the purpose for which it remains current, any historical use, superseding source, access conditions, uncertainty, linked plan statement, verification owner, and next freshness trigger. A source can remain useful history after it stops supporting a current-state claim, so the register should preserve both status and bounded use.

Work through Wren's example

Wren's renewal uses ten source records. Seven are current for their defined purpose, two are historical context, and one lacks an as-of date. Current-evidence completeness is 7 of 10, or 70%. Historical context accounts for 2 of 10, and 1 of 10 remains held. Nine available records therefore support two different uses; availability alone would overstate current-evidence completeness. The freshness classification belongs to this decision and time window rather than serving as a universal expiration rule.

Address Wren's main provenance risk

A recent upload can contain old events. Wren's register separates file date, event period, author date, receipt date, and decision-use date. A source can be accurate for one period or decision and unfit for another. Keep original evidence, interpretation, recommendation, consent, operational release, payer state, claim, and outcome as separate records.

Choose Wren's next evidence step

The clinician verifies the missing as-of date, rechecks the two historical assumptions, and records which current plan statements change. Record the qualified owner, authority, person and scope affected, interim protection, evidence needed, access and privacy route, due date, correction method, recipients, closure state, and next review. Software may coordinate workflow while qualified people interpret evidence and decide within scope.

Apply professional evidence standards to Wren's record

For Wren's evidence record, the BACB ethics hub identifies the current Ethics Code, which addresses competence, client and stakeholder involvement, assessment, medical needs, documentation, confidentiality, risk, and data-based evaluation for covered people. BACB has no separate organizational jurisdiction. The BCBA outline is examination content, not practice authority. The CASP public summary supplies high-level planning context for ABA treatment of autistic people. An evidence-based ABA framework supports integrating research, clinical expertise, client values, and context.

Use integrity and access sources carefully for Wren

In Wren's case, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit procedures, implementation evidence, observer quality, and cautious interpretation. They create no universal provenance threshold. ASHA supports continuous AAC access. For a HIPAA covered entity, HHS minimum-necessary guidance generally applies to uses, disclosures, and requests for protected health information, with rule-specific exceptions. It supports role-based information access rather than copying whole records into every plan field.

Close Wren's evidence review

Review the evidence freshness register with Wren, the responsible clinician, affected participants, and the specialists named in the manifest. Preserve direct client communication, source attribution, disagreements, versions, limitations, decisions, corrections, and open gaps. Keep this page draft and noindex until the required clinical, client or family, measurement, AAC, access, medical, records, privacy, ethics, research, and legal reviews are complete.

How to Date and Version Evidence Used in an ABA Treatment Plan