Preliminary versus finalized ABA data describes an editorial workflow state, not a universal legal term. Preliminary data may still need defined review, denominator confirmation, correction, or sign-off. Finalized data have met the practice's stated release requirements for the named use. Preserve authorship, timestamps, prior values, and every correction. Label decisions based on preliminary evidence and re-review them when finalized data differ materially.

Name each data state

Use clear states such as preliminary, under review, finalized, invalid, corrected, and reopened with entry and exit rules.

Define permitted uses

State whether a status can support graph display, supervision discussion, safety escalation, formal plan change, or external reporting.

Preserve provenance

Keep author, observer, service time, entry time, reviewer, source device, and every correction with the record.

Show coverage

Report finalized observations divided by all observations due for that review, with other states listed separately.

Route material changes

Define who compares preliminary and final values and what difference triggers another clinical review.

Build Nia's preliminary-to-final state map

For the preliminary versus finalized ABA data question, create a versioned preliminary-to-final state map. 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 Nia's evidence and decision without guessing which values were available.

Work through Nia's data example

Nia's queue shows 12 session observations. Eight meet the practice's finalized-state rules, three remain preliminary because opportunity denominators need review, and one is invalid after a device outage. A provisional graph can show all 12 statuses, while the decision calculation uses the eight finalized records and states that coverage is 8 of 12. Show every count, denominator, state, and date before summaries. This fictional school data-review queue example illustrates one workflow and does not establish a universal maturity threshold, fidelity target, review frequency, plan change, or treatment recommendation.

Audit Nia's evidence trail

Nia's state map defines who can enter, review, correct, finalize, and reopen each observation. It retains the invalid device record, the three pending denominators, and the exact graph version used in any provisional discussion. 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 Nia's main data risk

Calling preliminary data final because the graph looks complete hides unresolved evidence. Treating all preliminary values as useless can also delay timely safety or clinical review. Nia's policy defines permitted uses for each state. 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 Nia's next action

When pending records finalize, the system recalculates affected summaries and routes material differences to the clinician. It does not silently update the rationale attached to the earlier decision. 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 Nia's access and participation

Keep Nia'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 Nia's review

Nia's sources support timely data analysis while the page separates data readiness from clinical judgment and legal record status. 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 Nia's workflow

Test the preliminary-to-final state map 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 Nia's data review

Review the preliminary-to-final state map with Nia, 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