A data-based no-change decision in ABA records why the current plan remains appropriate after qualified review. It should identify the evidence window, raw outcome pattern, measurement and integrity checks, client input, risks, benefits, alternatives, unresolved uncertainty, and next review or trigger. No change is an active decision with an owner and date. It should never become an indefinite default or an automated conclusion.

Name the reviewed evidence

Link the data window, graph, measurement quality, integrity coverage, context, client report, and relevant risk information.

Consider alternatives

Record whether support, dosage, procedure, environment, goal, referral, pause, or closure options were evaluated.

Explain why current care still fits

Connect the observed evidence and person's priorities to the limited decision period.

Set a review date and triggers

Name the next routine review plus decline, plateau, incident, access, fidelity, health, or client-request events that reopen it.

Preserve qualified ownership

Record who made the clinical decision and who implements, monitors, and escalates concerns.

Build Uri's no-change decision note

For the data-based no-change decision ABA question, create a versioned no-change decision note. Preserve the target, client priority, operational definition, observation state, service and entry times, author, numerator, denominator, missingness, graph, integrity protocol, component data, context, access, decision rule, qualified owner, snapshot, correction, implementation, and follow-up. Another reviewer should be able to reconstruct Uri's evidence and decision without guessing which values were available.

Work through Uri's data example

Uri's eight recent sessions show stable improvement in his chosen participation goal, matched integrity data in six, no new adverse effect, and consistent access to his communication system. Uri wants the current support to continue. The clinician records no change for four weeks, with earlier review if performance declines, access fails, or Uri requests reconsideration. Show every count, denominator, state, and date before summaries. This fictional school participation plan review example illustrates one workflow and does not establish a universal maturity threshold, fidelity target, review frequency, plan change, or treatment recommendation.

Audit Uri's evidence trail

Uri's note links all eight outcomes, six fidelity records, two integrity gaps, measurement checks, client input, alternatives considered, rationale, decision date, owner, planned review, and three triggers. It avoids describing stable as the only reason. The audit also checks definition and protocol versions, source-record access, correction history, graph axes, session spacing, invalid states, observer evidence, calculation precision, review permissions, and downstream dependencies. Unresolved discrepancies remain visible and hold the exact decision they affect.

Address Uri's main data risk

A no-change note can conceal inertia when evidence is incomplete or the plan has poor fit. Uri's review states the open fidelity gap and why it does not block the limited four-week decision. A metric or alert can surface a concern. Qualified reviewers interpret measurement, outcome, integrity, client experience, context, and risk together. One score cannot establish treatment fit, clinical importance, causation, authorization, or completion.

Choose Uri's next action

At the next review, the team compares the new mature cohort with the same goal and triggers. A later change receives its own decision record rather than editing Uri's earlier rationale. Record the action, rationale, owner, due date, support, and review trigger. Keep preliminary evidence, finalized evidence, treatment integrity, outcome, client input, and clinical decisions as separate states so one cannot silently substitute for another.

Protect Uri's access and participation

Keep Uri's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, health support, rest, relationships, and emergency help available. Use accessible consent and assent processes when applicable and respond to withdrawal, dissent, or distress. Data collection, fidelity observation, or review timing never authorizes staff to delay urgent care or remove ordinary supports.

Apply current sources to Uri's review

Uri's page applies evidence-based ABA principles to a commonly underdocumented decision to continue an existing plan. The BACB ethics hub and CASP public summary provide professional context, while the BCBA Test Content Outline identifies examination content on measurement, integrity, and data-based decisions. The WWC handbook supplies research-design context. Research on graphing fidelity with rate, integrity reporting, and integrity effects shows why implementation evidence matters. A single-case design review and evidence-based ABA framework describe analysis and decision context. ASHA supports continuous AAC access.

Rehearse Uri's workflow

Test the no-change decision note with fictional preliminary records, a late correction, a missing denominator, no integrity opportunity, measured zero fidelity, high fidelity with low use, a critical component miss, an overdue review, and a no-change decision. Confirm that states, due cohorts, calculations, snapshots, permissions, alerts, and qualified routes behave as intended. Store expected results, software version, reviewer notes, and corrections before live use.

Close Uri's data review

Review the no-change decision note with Uri, the responsible clinician, and specialists required by the question. Preserve source data, versions, graphs, maturity status, integrity coverage, components, client input, access and safety evidence, decision, implementation, corrections, and later outcomes. Keep the page draft and noindex until every manifest-named review is complete.

Related resources

Sources