For client participation in ABA reviews, ask how the person wants to take part before, during, and after the meeting. Provide an accessible agenda, records, communication, privacy, breaks, timing, and support-person options. Assign facilitation and decision duties. Measure access, contributions, influence on decisions, unanswered questions, burden, and client experience without requiring attendance for every agenda item.

Ask how the client wants to participate

Offer advance input, selected agenda items, full meeting, separate conversation, written or AAC response, support person, recording limits, and later review.

Ask Dev separately about each stage. He may want to choose agenda priorities in advance, attend only selected decisions, contribute through AAC or a written message, take a break during sensitive discussion, and review the proposed decisions afterward. Record who he wants present, who may receive his information, which topics need privacy, and whether he wants a support person. Participation should follow Dev's preferred route rather than a single attendance expectation.

Clarify decision authority without diminishing his role. The clinician, payer, parent, legal representative, school, or another party may control particular decisions, but Dev's input should still be captured and answered. Explain which items are recommendations, which require consent or authorization, and which are open choices. If a topic cannot be discussed with everyone present, plan a separate accessible conversation and show how that input reaches the final record.

Prepare meeting access

Provide agenda, decisions, records, definitions, roles, privacy, communication, interpreter, breaks, timing, transport, technology, and a stop route.

Send materials early enough for Dev to use them. Highlight the questions that need a decision, summarize relevant data in plain language, identify unresolved disagreement, and avoid surprising him with a major proposal during the meeting. Confirm that AAC, interpreter services, captioning, visual materials, remote access, transportation, and a quiet setting work before the start time. Assign one person to facilitate access rather than making Dev troubleshoot while others continue.

Design the meeting around attention and processing needs. Put Dev's priority items at a workable time, state how he can pause or leave, and preserve his input if he does. The facilitator should check understanding of the current question without requiring rote repetition, protect Dev from overlapping speech, and make room for correction. A shorter meeting with planned follow-up can provide more meaningful participation than full attendance through an exhausting agenda.

Support participation outside the meeting

Let Dev review selected questions in advance, send recorded or written input, use AAC asynchronously, meet privately with a chosen person, or respond after receiving the proposed decision. Record which route he selected for each agenda item. Absence from the live meeting does not mean absence of client participation when his input reaches the decision process through an accessible agreed route.

Create an intake deadline and an owner for carrying each asynchronous contribution into the meeting. The minutes should identify Dev's statement as his input and preserve its wording or accessible summary. If the team receives it too late for the decision, keep the item open or document the qualified reason it could not wait, then give Dev a defined reconsideration route.

Build an accountable meeting record

For each decision, capture the question, Dev's input, other evidence, responsible decision-maker, disposition, reason, open disagreement, action owner, and due date. Send an accessible summary and provide a correction route. Attendance minutes alone cannot show whether input influenced the plan, whether a question was answered, or whether the promised action occurred.

Distinguish contribution from influence. A contribution may support the final decision, change the proposal, identify missing information, remain unresolved, or be rejected by an authorized owner. Record which occurred and why. Send Dev the relevant summary in his preferred form, highlight any change from the premeeting proposal, and state how he can correct the record or ask for another review.

Measure influence and fit

Report accessible items, participation, contributions, questions, decisions citing input, unresolved points, burden, and Dev's experience.

Use fixed denominators for agenda items provided accessibly, items Dev chose to join, contributions received, questions answered, decisions that trace his input, promised actions completed, and summaries corrected. Do not treat attendance duration as the primary outcome. Review whether Dev's preferred participation routes worked, whether privacy and breaks were honored, what burden the meeting created, and what should change before the next review.

Build Dev's review-meeting participation plan

Client participation in ABA reviews needs one versioned meeting plan for the six-month treatment review. Include direct communication, privacy, consent and assent when applicable, AAC and retained supports, authority, readiness, client and partner measures, missingness, experience, burden, decisions, owners, dates, and review triggers.

Work through Dev's example

Dev's meeting contains twelve agenda items, all available accessibly in advance. He joins eight, contributes to five, and four resulting decisions cite his input. Report 12/12 agenda access, 8/12 participation, 5/8 contribution, and 4/5 traced influence. Keep every readiness state, client response, partner action, numerator, denominator, missing event, support, and experience measure visible. This fictional example supplies no universal threshold, legal conclusion, or outcome guarantee.

Address Dev's main fit risk

Attendance can look successful while Dev's questions or priorities never affect a decision. The plan traces input to disposition. Review access, partner behavior, burden, safety, and lived experience separately.

Choose Dev's next action

The facilitator answers the open question, Dev reviews one uncited decision, and the team adjusts the next agenda. Record the qualified owner, interim support, evidence, due date, client communication, disposition, and next review.

Reconcile the action log after the meeting. Dev should receive notice when each promised item is completed, delayed, or reassigned, with the reason and new date. At the next agenda check, ask whether the earlier participation route worked and whether any unresolved contribution needs to return as a decision item.

Apply current sources to Dev's plan

For Dev's plan, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, 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 research, clinical expertise, client values, and context.

Use measurement and access evidence for Dev

For Dev's measures, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit procedures, representative evidence, and cautious interpretation. They create no universal experience threshold. Breaux and Smith offer assent-focused guidance in an evolving evidence base. ASHA supports continuous AAC access.

Close Dev's review

Review the review-meeting participation plan with Dev, the responsible clinician, affected partners, and the named specialists. Preserve direct communication, supports, disagreement, versions, limits, and open gaps. Keep this page draft and noindex until required reviews are complete.

Related resources

Sources