To correct client-experience data in an ABA record, identify the exact value, source, and decision affected. Preserve original content, author, dates, and reason. Distinguish a client correction, staff entry error, changed response, measurement error, and formal record route. Recalculate derived results, notify downstream users, retain disagreement, and verify that no clinical or operational action relies on stale data.

Identify the exact correction unit

Record measure, client, response, item, source, service or collection date, entry date, version, context, derived score, display, decision, and every downstream record that may rely on the value.

Classify why data changed

Separate entry or transcription error, wrong source, misunderstood response, inaccessible method, client correction, later change of mind, duplicate, missing response, calculation error, version error, and formal amendment or disagreement.

Preserve history and authorship

Retain original content, original author and time, requester, request time, evidence, decision owner, correction, correction time, reason, relationship between entries, and any rule-specific required documentation.

Route authority correctly

A client may correct or dispute their report while qualified clinical, privacy, records, coding, payer, or legal roles decide changes within their domains. Software can route and recalculate without deciding clinical meaning.

Recalculate and notify

Update scores, denominators, dashboards, alerts, reports, plan decisions, exports, and affected recipients through an auditable process. Keep the original version available and identify results that should no longer be used.

Validate closure

Confirm the corrected display with Wren when appropriate, preserve denial and disagreement, verify downstream updates, assess any harm or delayed action, document remediation, and reopen the case if another copy or decision remains stale.

Keep correction and changed experience separate

If Wren says yesterday's recorded rating was entered incorrectly, the workflow preserves the original entry and records the corrected value with its basis. If she says the rating was accurate yesterday and her experience changed today, both observations remain valid for their own times. Ask which event occurred through an accessible, nonleading route. This distinction protects chronology, trend interpretation, and authorship. It also prevents staff from rewriting unfavorable history merely because later conditions improved or an earlier response is inconvenient.

Trace each correction to its downstream uses

Build a dependency list for the source response, derived score, denominator, graph, alert, plan review, quality report, export, and recipient. For each affected use, record whether it needs recalculation, annotation, withdrawal, replacement, or no action, plus the qualified owner and completion evidence. A dashboard refresh alone does not prove that a previously sent report or clinical decision was corrected. Confirm the current display with Wren when appropriate and preserve any continuing disagreement about meaning, authority, or requested wording.

Measure correction timeliness by stage

Track time from request to acknowledgment, route decision, source update, recalculation, downstream repair, client confirmation, and final closure. Report open requests by current stage and age instead of one average that hides a stalled case. Use the deadline that applies to each route and preserve a faster interim protection when a stale result could affect care, access, privacy, or another decision. A denied request remains visible with its rationale, communication, and disagreement or review option.

Build Wren's experience-data correction workflow

Create one versioned experience-data correction workflow for the quarterly record review. Include the construct, decision, direct client communication, source-labeled proxy evidence, consent and assent when applicable, privacy, AAC and supports, authority, method, readiness, timing, missingness, burden, versions, corrections, actions, owners, effective dates, and review triggers. Define raw units and denominators before use.

Keep Wren's operational record decision-ready

For Wren, record candidate or deployed method, source, version, question, response options, access setup, collector, setting, period, eligible events, raw responses, help, withdrawal, missing reason, privacy route, correction, uncertainty, qualified interpretation, action, implementation, client communication, confirmation, and closure. Restrict sensitive content to approved roles and systems.

Work through Wren's example

Wren reviews nine correction requests. Eight enter the applicable route. Seven records are corrected, affected summaries are recalculated for six of those seven records, and one denied request receives a documented disagreement path. Report 8/9 routing, 7/8 correction, 6/7 recalculation, and 1/1 disagreement handling. Preserve all mature items, readiness states, responses, failures, raw counts, denominators, missing categories, versions, actions, and open work. This fictional example demonstrates one operational control and supplies no universal threshold, validation finding, legal conclusion, causal result, or outcome guarantee.

Use Wren's evidence for a bounded decision

Before collecting more data, identify the decision and authorized owner. Possible actions include clarify, restore access, retrain, revise, correct, pause, investigate, replace, retire, or close. For Wren, document interim protection, evidence needed, due date, implementation test, client-facing explanation, disagreement route, next review, and criteria for reopening.

Review Wren's results without hiding failures

For Wren, show raw counts beside percentages and keep inaccessible, missing, unfavorable, corrected, overdue, and reopened items visible. Segment by method, version, setting, collector, access route, and period when useful and privacy-safe. Compare cohorts only when definitions and maturity rules match, and explain material changes before interpreting a trend.

Address Wren's main operational risk

Overwriting a rating can erase whether the original entry was wrong or the client's view later changed. Wren's workflow preserves both event types and their dates. Review construct fit, direct client access, privacy, partner influence, burden, missingness, versions, corrections, and decision response separately. A completed form or precise score cannot compensate for a measure that asks the wrong question or leads nowhere.

Choose Wren's next action

The records owner routes the open request, recalculates one missed summary, and confirms affected decisions with Wren and the clinical owner. Preserve original evidence, client corrections, and disagreement. Record the qualified owner, affected measures and plan versions, interim safeguards, downstream systems, due date, validation evidence, client communication, current status, and next governance check.

Apply current professional sources to Wren's workflow

For Wren's workflow, 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 research, clinical expertise, client values, and context.

Use measurement evidence for Wren

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

Close Wren's operations review

Review the experience-data correction workflow with Wren, the responsible clinician, operational owners, privacy and access roles, and the specialists named in the manifest. Verify that the method remains understandable, accessible, private, proportionate, version-controlled, and actionable. Preserve history, supports, limits, and open gaps. Keep this page draft and noindex until required reviews are complete.

Related resources

Sources