What Happens When an ABA Plan Review Team Disagrees?

Name the exact disagreement

State whether the issue concerns client priority, clinical fit, safety, procedure, service hours, setting, staffing, school coordination, coverage, cost, or schedule. Avoid labeling the whole team uncooperative.

Separate authority from influence

A family can contribute essential context. A client communicates their own preference. A qualified clinician owns clinical recommendations within scope. A payer decides coverage. Operations decides resource availability. Legal or medical questions go to the qualified authority.

Protect participation and alternatives

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Provide materials, time, partners, and response options the person can use before, during, and after the review. Give the person a way to dissent, pause, or propose an option. Compare alternatives, likely benefits, burden, risks, and evidence. Immediate safety duties continue through their own route.

Document resolution or hold

An ABA plan review disagreement record should show every position, the decision and basis, who made it, effective date, appeal or escalation if applicable, and follow-up. The CASP public summary supports individualized assessment, planning, implementation, and evaluation for ABA treatment of people diagnosed with autism. The BACB Ethics Code addresses understandable communication, client involvement, consent and assent when applicable, assessment, intervention, risk, documentation, and evaluation for covered behavior analysts. The BCBA Test Content Outline covers assessment, client-informed goals, measurement, and data-based decisions as examination content. None of these sources prescribes one universal meeting workflow.

Build the plan-review disagreement record

The plan-review disagreement record should preserve each view and route the exact issue through the role authorized to decide it. Capture issue, viewpoints, client statement, family context, evidence cited, clinical authority, payer action, operational constraint, legal or medical referral when needed, alternatives, immediate safety response, interim decision, effective date, appeal or escalation, owner, and review date. For each material item, include its source, responsible role, current state, effective date, and next review so a family can tell a decision from a proposal or an unresolved dependency.

Use states suited to the plan-review disagreement record: proposed, reviewed, decided, held, assigned, effective, corrected, escalated, or closed with reason. Keep client choice, clinical recommendation, payer action, operational readiness, service delivery, and claim outcome separate because those events answer different questions.

Prepare evidence and participation

Send the agenda, plan version, and readable evidence early enough for the client and family to prepare for the plan-review disagreement record. Provide AAC, interpreter, language, visual, sensory, mobility, privacy, break, and processing supports the person needs. Record direct client input by source and invite correction of another person's summary.

For the plan-review disagreement record, identify who has authority for each decision. A client communicates their own priorities. A legally authorized representative acts only within applicable authority. Qualified clinicians decide clinical questions within scope. Operations owns resources and workflow. A payer decides coverage under its rules.

Work through the review in order

1. Name the specific issue rather than labeling the team. Open the plan-review disagreement record with the exact purpose and evidence period.
2. Separate client preference, clinical recommendation, coverage, and resources. Preserve the client's communication and family context.
3. Compare workable alternatives and their burdens. Record the evidence, limits, alternatives, and decision owner.
4. Record the interim or final decision and actual authority. Give every open item a state, owner, and due date.
5. Assign unresolved evidence and escalation to named owners. Deliver the result and set the next review trigger.

For every number in the plan-review disagreement record, state the numerator, eligible denominator, time window, setting, supports, missing events, and data source. Keep raw counts beside percentages. A graph, meeting total, or completed-task rate should never make missing or held evidence disappear.

Prepare for the main complication

Several participants may disagree for different reasons. A family may oppose the burden, the client may dislike the goal, the clinician may question fit, and the payer may deny coverage. Combining those into one yes-or-no vote obscures what each authority can decide and what alternative remains possible.

When the complication occurs, return to the plan-review disagreement record. Preserve the earlier evidence and decision, state what changed, identify the affected question, and assign the next step. Avoid rewriting the old record as though the later information had always been available.

Work through a concrete example

Maya wants to replace a community goal, her family supports the change, the clinician requests another observation, and the payer authorization still names the old service. The record preserves all four states, pauses the proposed revision until the observation, and assigns the payer update separately.

This example illustrates how the plan-review disagreement record can support a real decision. It does not establish that the same plan, meeting format, number of hours, or follow-up timing fits another person. The qualified team still needs current evidence and direct client input.

Questions families can ask about the plan-review disagreement record

• What exact question is disputed?
• What does the client communicate?
• Who has authority for each part?
• Which alternative or interim protection is available?
• How are disagreement and escalation preserved?

Ask for a written plan-review disagreement record response when it affects issue, viewpoints, client statement, family context, evidence cited, clinical authority, payer action, operational constraint, legal or medical referral when needed, alternatives, immediate safety response, interim decision, effective date, appeal or escalation, owner, and review date. If an answer is unavailable, keep it open with the current source, responsible person, next action, due date, and family update instead of treating a meeting discussion as completion.

Review what happened after the meeting

At the next contact, compare the plan-review disagreement record with what actually occurred. Check whether the plan was updated, the client received the agreed support, staff training happened, payer work moved, and promised documents reached the family. Record mismatches and correct factual errors while preserving the prior version.

The plan-review disagreement record should resolve the narrow issue it can and keep the remaining question open. Consensus language should never erase a documented dissenting view.

Send a usable decision packet

Package the plan-review disagreement record with the current plan or amendment, plain-language summary, action list, relevant data views, and contact routes the family needs. Identify which document controls each next step and which materials are informational. If a translation, accessible format, signature, payer response, or corrected record is still pending, show that dependency in the plan-review disagreement record instead of delaying all communication or presenting the packet as final.

Give the client and family a concise summary of the plan-review disagreement record in a format they can use. Include what changed, what stayed the same, what remains open, who owns it, and how to report a new concern or request another review. Preserve the dated packet so a later correction remains traceable.