Can Families Ask Why an ABA Session Procedure Changed?

Document the ABA procedure change

Preserve the old and new versions. Mark the phase boundary on graphs and identify whether response definitions, prompts, reinforcement arrangements, materials, setting, or safety controls changed. Avoid retroactively describing earlier sessions as if the new procedure applied.

Protect client access and participation

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Provide a reliable way to ask, decline, pause, report discomfort, and correct another person's interpretation.

Keep roles and evidence clear

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, supervision, and evaluation for covered behavior analysts.

The BCBA Test Content Outline covers assessment, measurement, intervention, and data-based decisions as examination content. These sources do not create one universal session policy.

A practical example

A clinician changes a prompt delay from two seconds to five after reviewing rapid staff prompting and the client's preference for more processing time. The change starts Monday, staff complete training, graphs mark the phase, and the client can still request more time or stop.

Questions families can use

Ask who authorized the change, what the client communicated, when it begins, which staff are trained, how data remain comparable, what adverse effects are monitored, and when the procedure will be reviewed.

Build the procedure-change register

Use the procedure-change register to show exactly what changed, who made the clinical decision, what the client communicated, how staff were trained, and when the revision will be reviewed. Record old and new plan versions, rationale, qualified decision-maker, client and family input, consent and assent when applicable, alternatives, risks, effective date, affected goals and definitions, staff training, phase marker, payer state, implementation checks, adverse effects, and review point. Add the source, date, responsible role, current state, and next review to each material entry so the family can tell what is confirmed and what remains open.

For the procedure-change register, use states that fit the work: requested, acknowledged, scheduled, observed, held, corrected, escalated, resolved, or closed with reason. Keep client communication, clinical judgment, operational action, payer status, service delivery, and claim outcome separate because those facts may change at different times.

Start with the client's purpose and access

Ask what the client wants to understand, communicate, change, or avoid through the procedure-change register. Provide the person's usual speech, AAC, sign, gesture, writing, interpreter, sensory, mobility, language, and processing supports. Record a caregiver's observation by source and invite the client to correct another person's interpretation.

The procedure-change register should name who has authority for the decision at issue. Client assent or dissent when applicable, legal consent, privacy permission, clinical authority, payer action, and family involvement are distinct. A relationship or staff title should never be used as a shortcut for all of them.

Work through the process in order

1. Describe the current problem and evidence. Open the procedure-change register with the exact question and owner.
2. Identify the qualified clinical owner and client input. Preserve access and record the immediate response.
3. Write and date the exact revision without overwriting history. Identify the evidence, governing role, and any hold.
4. Train affected staff and verify implementation. Keep what actually happened separate from what was planned.
5. Review benefits, burdens, adverse effects, and the client's experience. Give the family a dated result and next step.

For this procedure-change register, define every duration and proportion before collecting it. State the start and end event, eligible opportunities, exclusions, missing records, and the person or system that supplied the data. Report raw counts beside percentages and keep declined or invalid events visible under their correct category.

Prepare for a realistic complication

A payer approval, software update, or staff practice can be mistaken for clinical authorship. Payer status and operational deployment matter, but they do not replace the qualified clinical decision. If staff began using the change before approval, preserve those dates and assess the resulting record rather than backdating the plan.

When that complication appears, return to the procedure-change register and document the changed condition. Identify which conclusion remains supported, which one is on hold, which alternative is available, and who will gather the next evidence. Do not silently rewrite the earlier plan or observation.

Work through a concrete example

A clinician changes a prompt delay from two seconds to five after reviewing rapid staff prompting and the client's preference for more processing time. The new version starts Monday. Staff complete training, graphs mark the phase, and the client can still request more time or stop. The payer state is tracked separately.

The example shows how the procedure-change register can support a real family decision. Its counts and outcome describe only the stated people, events, settings, and dates. They do not prove treatment effect, staff quality across all visits, or a universal rule for another provider.

Questions families can ask about the procedure-change register

• Who authorized the clinical change?
• What evidence and client input support it?
• Which plan, data, and training artifacts changed?
• What risks or burdens will be watched?
• When will the revision be kept, changed, or rolled back?

Request a written answer tied to the procedure-change register when it affects old and new plan versions, rationale, qualified decision-maker, client and family input, consent and assent when applicable, alternatives, risks, effective date, affected goals and definitions, staff training, phase marker, payer state, implementation checks, adverse effects, and review point. If the answer is unknown, the procedure-change register should show the owner, current source, next action, and update date rather than treating uncertainty as completion.

Review the result with the client

Review the procedure-change register in a format the client can use. Ask whether it reflects the person's message, what felt helpful or burdensome, and what should change. Correct factual errors while preserving who originally supplied each account. Keep private personnel information outside the family-facing summary while still explaining the effect on care.

The procedure-change register protects both responsive care and an accurate history. Keep superseded instructions available for audit while preventing them from remaining in active use.

Prepare the family follow-up

Before the next visit or review, use the procedure-change register to list what the family should expect to see, hear, receive, or decide. Include the relevant contact, date, accessible communication route, and any evidence the family has agreed to bring. If the expected step does not occur, the procedure-change register should explain whether the family should contact the clinician, operations team, privacy contact, payer, or another responsible route.

The final procedure-change register entry should state the disposition, evidence limits, follow-up owner, and future review trigger. Give the client and family a concise summary plus a route to report a mismatch between the written result and what occurs next. Preserve that summary as a dated version so a later correction or change remains visible.