How to Plan a Request-for-Explanation Goal in ABA

To plan a request-for-explanation goal in ABA, choose a decision or activity the client wants explained. Make the source information accessible, define accepted question forms and the responsible answerer, and preserve more time, refusal, and follow-up. Separate clinical, payer, operational, and legal authority. Measure information readiness, client questions, understandable responses, corrections, action, experience, and burden.

Choose the explanation target

Record the exact decision, term, procedure, schedule, risk, alternative, cost, or record Zane wants explained and the decision it may inform.

Begin with Zane's question in his own communication form. Identify the exact plan version, service event, recommendation, rule, or record involved and what he may decide after receiving an answer. A broad request such as "explain my treatment" should be divided into manageable items without losing the original concern. Ask which item matters first and whether he wants a source document, plain-language summary, example, comparison, demonstration, or conversation.

Preserve the right to ask a follow-up, correct a misunderstood question, request more time, or decline the discussion. If the explanation concerns a proposed change, keep the decision open until material questions have a qualified answer or the applicable authority requires another action.

Identify the answer owner

Route clinical rationale, payer status, privacy, scheduling, financial, legal, and safety questions to the role authorized to answer each one.

Map each part to its controlling source and owner. The supervising clinician can explain a clinical recommendation, while a payer, scheduler, records or privacy officer, medical professional, legal representative, school, or another authority may control a different statement. One person can coordinate the response, but should not guess outside scope. Record who accepted each question and when Zane should expect an answer.

When sources conflict, stop and reconcile them. Preserve the versions, identify which source currently controls, and explain the resolution. If the answer remains uncertain, say so, identify the missing evidence, and set a review date rather than presenting a confident summary that Zane cannot verify.

Make information understandable

Provide preferred language, AAC, examples, visuals, source documents, definitions, sufficient time, privacy, a correction route, and a way to ask again.

Prepare the explanation in Zane's preferred format and retain his AAC and other supports. Define important terms, show practical effects, distinguish current rules from future or proposed changes, and separate facts from professional judgment. A short side-by-side comparison may help with options, while a worked example may clarify a calculation or schedule. Avoid testing understanding through verbatim repetition.

Ask Zane which parts are clear and which need repair. Let him point to an inconsistency, provide an example, ask another question, or request a different answerer. Record the original answer, corrected explanation, source, and date. If the explanation changes the proposed plan, authorization packet, schedule, or another active record, route that object for a separate update.

Measure the complete exchange

Report source readiness, questions, qualified responses, understandable answers, latency, unresolved points, corrections, decisions, burden, and Zane's account.

Use separate denominators for topics requested, source packets ready, questions routed, answers provided by the qualified owner, explanations Zane could access, corrections completed, and later decisions communicated. Keep missing sources and unresolved questions open. Close only after Zane receives the current answer, knows how to disagree or ask again, and the record shows whether the explanation affected his decision.

Build Zane's request-for-explanation plan

List each plan decision Zane wants explained and name the role authorized to answer it. Record the source and version, preferred language and format, AAC and retained supports, privacy, time to review, Zane's question or correction, the answer provided, unresolved terms, confirmation of meaning, and the later decision if any. Keep clinical rationale, payer status, privacy, cost, scheduling, safety, and legal questions under their respective owners. Measure source readiness before Zane's request and the qualified response afterward.

Work through Zane's example

Zane identifies five plan decisions he wants explained. Accessible source information is ready for four, or 80%. He asks a question about three of those four source-ready decisions, or 75%, and receives an understandable answer to two of the three questions, or 66.7%. The fifth source and one inaccessible answer remain system or partner gaps. These rates track different stages and do not make asking a question a requirement for every decision.

Address Zane's main fit risk

Scoring whether Zane asks a question can hide missing source material or an answer given by the wrong role. The plan measures readiness and qualified response separately. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.

Choose Zane's next action

The team retrieves the missing source, rewrites one answer in Zane's preferred format, and schedules confirmation. Record the qualified owner, authority, affected setting, interim support, evidence needed, due date, client communication, correction route, disposition, and next review.

Reconcile the explanation with the records Zane will use next. If the answer clarifies a treatment decision, update the plan or meeting summary; if it corrects a payer, schedule, privacy, or cost statement, notify that qualified owner and preserve the source version. Send Zane the final explanation in his preferred format and identify any open question.

At confirmation, ask whether the response answered his original question and whether he wants another source, different answerer, more time, or review of the related decision. Do not require agreement with the answer. Archive superseded explanations when a rule or plan changes, and reopen the item if partners continue to rely on an earlier version. Record the next source-review date and responsible owner when the answer depends on a policy, authorization, schedule, or other fact that can change.

Apply current professional sources to Zane's plan

For Zane's plan, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, confidentiality, assessment, medical needs, 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 Zane

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

Close Zane's review

Review the request-for-explanation plan with Zane, 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.