How to Plan a Request-to-Review-Data Goal in ABA

To plan a request-to-review-data goal in ABA, choose the data and decision the client wants to examine. Verify access and privacy authority, use current source-linked displays, and explain definitions, time windows, missingness, supports, and limits accessibly. Define questions and correction routes. Measure data readiness, client access, qualified explanation, decisions, corrections, burden, and experience.

Define the data question

Record the goal, measure, period, setting, person, decision, source, version, and why Suki wants to review it.

Begin with the decision Suki is trying to understand. She may want to know whether a goal changed, why the team recommends a new procedure, what happened during a specific week, whether a support was available, or why two reports disagree. Narrow the request to the relevant measure, dates, settings, plan version, and people. A request to "see progress" is too broad to determine which data and explanation will answer her question.

Write Suki's wording into the request and confirm the scope in her preferred format. Ask whether she wants raw records, a summary, a graph, an explanation, a correction, or a meeting with a qualified owner. If the request expands during review, add the new item rather than silently replacing the original question.

Verify access and privacy

Identify client or representative access, involved-person route, other-person information, minimum necessary handling, secure channel, and authorized response owner.

Determine which access process applies before assembling the packet. The clinical team may be able to review treatment data with Suki as part of care, while a formal record-access or amendment request can have different legal and organizational owners. Records may also contain information about another person, privileged material, payer content, school records, or data controlled by a separate system. Route those questions to the authorized privacy or records owner rather than making a broad promise.

Use a secure, accessible delivery method and verify the recipient. Explain any redaction, withheld field, or format limitation without exposing protected information. If Suki uses a representative or support person, document the applicable authority and her communication preference. Provide AAC, language, visual, or other access support without recasting Suki's own questions as proxy input.

Make the display understandable

Show raw counts, numerator, denominator, units, missingness, prompts, supports, context, changes, uncertainty, comparisons, and limits in Suki's preferred format.

Pair every graph with its definition and source period. Show how an opportunity was counted, which responses entered the numerator, which eligible events entered the denominator, and how exclusions or zero-opportunity sessions were handled. Identify unit changes, plan-version changes, missing sessions, prompt or support conditions, and any observation window that differs between series.

Use a format Suki can inspect. A table, annotated graph, example calculation, plain-language summary, or side-by-side comparison may be more useful than a dashboard screenshot. Preserve scale and time labels, avoid truncated axes that exaggerate change, and separate observed data from clinical interpretation. State what the display supports and what remains uncertain.

Prepare a reproducible review packet

Give the responsible reviewer the source record, data definition, collection window, inclusion and exclusion rules, version history, calculation, and display. Link every summary value to the record that produced it. When raw data cannot be shared through the approved route, identify the restriction and provide the most useful authorized explanation. A screenshot with no source, denominator, or version is not ready for a decision.

Check the packet against the active plan before the meeting. Reconcile late entries, duplicate records, corrected notes, device imports, and manual calculations. If the source changed after the display was created, freeze both versions and explain the update. The review should not proceed from a polished summary that the responsible clinician cannot reproduce.

Track questions through correction

Label each question as a request for explanation, missing record, suspected factual error, calculation error, disputed interpretation, preference, or formal access or amendment issue. Assign the qualified owner and preserve Suki's wording. A revised graph closes only the display defect. Any affected plan decision, report, claim, or downstream copy needs its own documented review and disposition.

Measure review quality

Report ready series, access, questions, qualified explanations, corrections, decisions, unresolved points, time, burden, and Suki's experience.

Use separate denominators for requested series, packets ready, authorized deliveries, questions received, explanations completed, corrections approved, downstream decisions revisited, and confirmations returned to Suki. Keep unresolved access issues and disputed interpretations open. Close the request only after she receives the answer or disposition, knows how to disagree or seek a correction, and the team records whether any plan action changed.

Build Suki's data-review request plan

Create one versioned data-review request plan for the monthly progress review. Include the request, direct communication, privacy, consent and assent when applicable, AAC and retained supports, authority, source evidence, interim protection, partner duties, eligible opportunities, client and partner measures, experience, burden, decisions, owners, dates, and review triggers.

Work through Suki's example

Suki requests ten data series. Eight are current, source-linked, and within the approved access route. She asks questions about four, and the responsible clinician gives an understandable explanation for 3 of 4. Report 8/10 readiness, 4/8 questions, and 3/4 response. Keep every opportunity, readiness state, client action, partner response, system failure, numerator, denominator, exclusion, support, and experience measure visible. This fictional example supplies no universal goal, legal conclusion, payer result, or outcome guarantee.

Address Suki's main fit risk

A polished graph can hide missing observations or changed definitions. Suki's plan keeps raw counts, source, version, and uncertainty available. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Suki's next action

The clinician corrects one explanation, data owners resolve two unready series, and Suki chooses whether to revisit the decision. Record the qualified owner, authority, interim support, evidence needed, due date, client communication, correction route, disposition, and next review.

Apply current professional sources to Suki's plan

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

Use implementation and access evidence for Suki

In Suki's plan, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit procedures, representative evidence, and cautious interpretation. They create no universal response threshold. Breaux and Smith offer assent-focused practice guidance in an evolving evidence base. ASHA supports continuous access to AAC tools or devices.

Close Suki's review

Review the data-review request plan with Suki, the responsible clinician, affected partners, and the specialists named in the manifest. Preserve direct communication, ordinary supports, disagreement, system duties, versions, decisions, limits, and open gaps. Keep this page draft and noindex until all required reviews are complete.