An ABA treatment plan review pre-read gives participants an accessible, source-linked view of the questions and evidence before the meeting. Include the current plan version, decisions due, client priorities, concise evidence summaries, raw-record links, health and access needs, risks, alternatives, disagreements, role authority, and preparation requests. State missing information and provisional interpretations plainly. The pre-read supports discussion and never becomes an unapproved plan revision.
Identify the meeting and source plan
Show client, review date, current plan and component versions, evidence cutoff, prepared time, author, audience, access level, and correction route.
Make the version and cutoff prominent enough that a reader cannot confuse the pre-read with the final disposition. State whether the document is a draft, who may access linked records, and how corrections are submitted before the meeting. If information changes after preparation, add an attributable update rather than silently replacing the file. This lets participants know exactly which evidence they reviewed and what remains provisional.
Lead with client priorities
Present Yara's own goals, communication, preferred outcomes, questions, access needs, disagreements, and requested meeting supports in attributable form.
Use Yara's wording where permitted and separate it from caregiver or clinician interpretation. Give her a chance to review the summary through an accessible route before wider distribution. If she prefers a topic to remain private, state how it will be handled rather than exposing the detail in the group pre-read. Missing direct input should be labeled and addressed, not replaced with presumed preferences.
Summarize by decision
For each question, state current component, trigger, evidence, counts and denominators, conditions, alternatives, risks, uncertainty, responsible authority, and decision deadline.
Keep one section per decision so a strong result on one goal does not imply that every plan component is ready for retention. Show actual exposure, integrity, client experience, unwanted effects, and missingness alongside outcomes. List realistic alternatives and what each requires. Do not mark a recommendation as final merely because it appears first; the pre-read prepares qualified discussion and participation rather than settling it.
Link detailed evidence
Provide secure links to definitions, raw data, observations, integrity, health or interdisciplinary records, prior decisions, corrections, and source-specific access routes.
Use descriptive labels and verify that recipients can open the records they are authorized to see. Link to the exact version and relevant section instead of a generic folder when possible. Keep medical, educational, privacy, and payer records within their required access routes. A concise summary becomes more trustworthy when a reviewer can trace each claim to its source and correction history without exposing unrelated information.
Declare conflicts and gaps
Name incomparable periods, changed definitions, missing client review, sparse observations, low integrity, unavailable participant input, health questions, and unresolved authority.
Place material limits beside the affected conclusion rather than in a distant footnote. Explain whether a gap blocks the decision, supports a bounded hold, or simply narrows the claim. Conflicting evidence should retain its source and conditions. This allows participants to prepare a focused question or referral and reduces pressure to manufacture consensus when the current record genuinely supports more than one interpretation.
Prepare participation
List attendee roles, agenda, expected decisions, advance questions, interpreter or AAC needs, private response options, breaks, logistics, and how to submit corrections.
Send the pre-read early enough for Yara and other participants to use it, then confirm delivery and access. Test interpreter, AAC, remote connection, and backup plans before the meeting. Invite additions and corrections through more than one route where feasible. If a required participant or support becomes unavailable, identify which decisions can proceed and which must be held without treating absence as agreement.
Build Yara's accessible review pre-read
Create a versioned accessible review pre-read for this review-cycle question. Preserve the agenda and decision cohort, direct client participation, source evidence and windows, definitions, health and access, roles and authority, alternatives, disagreement, decisions, interim support, plan-version impact, implementation, tasks, owners, due dates, communications, correction routes, and outcome follow-up. Another qualified reviewer should be able to reconstruct what was known, decided, held, and completed.
Work through Yara's example
Yara's pre-read covers three decision questions in seven pages. Two participants flag that a chart combines home and school opportunities, and Yara says the proposed label misses her goal. Both issues are corrected in the meeting packet while the original pre-read remains in the record. No decision is presented as settled before Yara's review. Keep every decision, task, source, numerator, denominator, overlap, open state, and unavailable item visible. This fictional multidisciplinary plan conference example illustrates one review-cycle control and supplies no universal meeting rule, clinical recommendation, legal conclusion, closure threshold, or outcome guarantee.
Address Yara's main review risk
A pre-read can anchor the meeting around the writer's conclusion. Yara's packet presents sources, alternatives, disagreement, and open questions visibly. Treat preparation, attendance, participation, decision, consent, release, implementation, and outcome as separate evidence. A well-run meeting can still produce a held decision, and a valid urgent action can occur outside the meeting.
Choose Yara's next action
The coordinator issues a corrected packet, logs late evidence, and preserves which version each participant received without silently rewriting earlier copies. Record the responsible role, authority, affected component and scope, interim control, due date, evidence needed for closure, accessible communication, correction route, and next review. Software may coordinate workflow. Qualified professionals make case-specific decisions within scope.
Protect Yara's access and choice
Keep Yara's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, pain communication, health support, movement, rest, relationships, and emergency help available. Offer private and accessible ways to ask, disagree, decline, pause, withdraw when applicable, and correct the record. Proxy and professional input can inform review without replacing Yara's experience.
Apply current sources to Yara's review
The BACB ethics hub, current Ethics Code, CASP public summary, and BCBA Test Content Outline provide scoped professional, client-involvement, documentation, evaluation, and training context.
An evidence-based ABA framework and treatment-integrity practitioner guide, Essig review, impact study, and reporting review support contextual decisions, explicit evidence, and bounded conclusions.
ASHA supports continuous AAC access.
Rehearse Yara's review cycle
Test the accessible review pre-read with a client request, caregiver disagreement, missing participant, interpreter or AAC need, late evidence, changed definition, health concern, low integrity, payer deadline, unresolved authority, urgent safety action, held decision, overdue task, stale plan copy, and adverse effect after release. Confirm that access, attribution, authority, workflow state, and follow-up remain intact.
Close Yara's review record
Review the accessible review pre-read with Yara, the responsible clinician, affected participants, and the specialists named by the manifest. Preserve direct client input, sources, decisions, disagreement, versions, tasks, limits, and open findings. Keep the page draft and noindex until required clinical, client or family, AAC, access, medical, educational, payer, records, privacy, employment, and legal reviews are complete.
Related resources
- How to Facilitate an ABA Treatment-Plan Review Meeting
- How to Assemble Evidence for an ABA Treatment-Plan Review
- How to Record Disagreement in an ABA Treatment-Plan Review
- How to Prepare a Client for an ABA Treatment-Plan Review
Sources
- Behavior Analyst Certification Board, Ethics Information and Ethics Codes
- Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts
- Behavior Analyst Certification Board, BCBA Test Content Outline, 6th edition
- Ethical Behavior Analysis: Evidence-Based Practice as a Framework for Ethical Decision Making
- A Practitioner Guide to Assessing and Improving Treatment Integrity
- Reporting of Treatment Integrity in Applied Behavior Analysis Research
- The Impact of Treatment Integrity on Intervention Effectiveness
- Treatment Integrity Reporting in Behavior Analysis Journals
- American Speech-Language-Hearing Association, Augmentative and Alternative Communication