To plan a request to correct an ABA plan, define how the client identifies an inaccurate fact, preference, attribution, data statement, or instruction. Preserve the original content, authorship, dates, and history when required. Route clinical revision and formal record action to authorized roles. Provide accessible response and disagreement paths, then measure intake, decision, correction, confirmation, burden, and closure.
Classify the requested correction
Separate demographic fact, client preference, authority, source attribution, observation, inference, data, clinical judgment, instruction, payer statement, and formal record amendment.
Ask Tomas to identify the exact text, table, instruction, or field and describe what he believes should change. Preserve his wording and the plan version he reviewed. A wrong address, a preference attributed to the wrong person, a copied staff instruction, a calculation error, and disagreement with clinical judgment need different evidence and owners. Classification should route the request; it should not decide the outcome before review.
Mark any immediate operational risk. An incorrect allergy, communication method, mobility support, emergency contact, safety instruction, authorization term, or staff procedure may require prompt interim correction while the formal record route continues. Name the qualified owner, temporary instruction, distribution list, and time for review. Do not leave a known hazardous instruction active merely because record governance is still deciding how to amend history.
Preserve evidence and history
Retain original content, author, service and entry dates, source, version, requested change, reason, decision owner, correction, disagreement, and affected downstream copies.
Freeze the original record before editing. Capture who authored it, which source supported it, when the service occurred, when the entry was made, and which later plan copied the content. Store Tomas's request, submitted evidence, communications, and the decision trail. A silent overwrite can make the current text look correct while erasing why earlier actions occurred.
Use a versioned correction that distinguishes an addendum, factual correction, clarified attribution, revised clinical interpretation, and formal amendment or disagreement statement. Preserve audit history according to the applicable record rules and system design. If the request cannot be granted through the proposed route, give Tomas an accessible explanation and any available review or statement-of-disagreement option.
Separate the available correction routes
A typo, incorrect demographic fact, client preference, copied instruction, disputed clinical judgment, and request involving a formal designated record may follow different processes. Identify the controlling record, policy, law, contract, and professional role before promising a result or deadline. Tomas can communicate the requested change directly while the authorized owner determines the applicable clinical, operational, payer, or formal record action.
Avoid bouncing the request among teams without ownership. Assign one coordinator who acknowledges receipt, identifies the controlling route, asks only for needed evidence, and tracks dependencies. Privacy, payer, school, employment, or legal questions should go to their qualified owners while the coordinator keeps Tomas informed of status and expected timing.
Propagate an approved correction
List every active object that relies on the incorrect content, such as the current plan, staff instruction, data form, authorization packet, schedule, report, or claim-supporting record. Record which version was corrected, who received notice, and whether an earlier action needs review. Preserve an audit trail that distinguishes the original entry, later correction, and any unresolved disagreement.
Test propagation rather than assuming one edit updates every copy. Check printed plans, exported PDFs, mobile views, portal copies, data-collection templates, schedules, payer submissions, and partner instructions. If an earlier clinical, safety, billing, or access decision relied on the error, route that decision for separate qualified review and document its disposition.
Use an accessible response route
Acknowledge the exact item, give status and due date, request only needed evidence, explain the decision, implement approved changes, and offer a review or disagreement path.
Provide each update in Tomas's preferred communication form and preserve privacy. The final message should quote or clearly identify the corrected item, state the effective version, explain any denied part, and show where the current record can be found. Invite Tomas to confirm whether the correction reflects his request without requiring agreement with a disputed clinical conclusion.
Measure correction closure
Report requests, routed items, decisions, corrections, disagreements, latency, affected records, client confirmation, reopened items, burden, and Tomas's experience.
Track requests received, correctly routed, decided on time, approved corrections entered, dependent records reconciled, earlier decisions reviewed, responses delivered, and confirmations received. Keep denied, partially granted, reopened, and overdue requests visible. Closure requires evidence that the controlling record and affected active copies agree, not merely that a ticket status changed.
Build Tomas's plan-correction request process
Create one versioned plan-correction request process for the treatment-plan review. Include the request, direct communication, privacy, consent and assent when applicable, AAC and retained supports, authority, source evidence, interim protection, partner duties, eligible opportunities, client and partner measures, experience, burden, decisions, owners, dates, and review triggers.
Work through Tomas's example
Tomas raises seven correction requests. Six enter the applicable clinical or record route. Five are corrected; one receives a documented disagreement response. Report 6/7 route readiness, 5/6 corrections, and 1/1 disagreement handling. The unrouted request remains open. Keep every opportunity, readiness state, client action, partner response, system failure, numerator, denominator, exclusion, support, and experience measure visible. This fictional example supplies no universal goal, legal conclusion, payer result, or outcome guarantee.
Address Tomas's main fit risk
Silently overwriting a plan can erase authorship and the reason for change. Tomas's process preserves history and separates correction from disagreement. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.
Choose Tomas's next action
The records owner routes the open item, Tomas confirms five corrections, and the clinician reviews any downstream teaching or claim effect. Record the qualified owner, authority, interim support, evidence needed, due date, client communication, correction route, disposition, and next review.
Apply current professional sources to Tomas's plan
For Tomas's plan, the BACB ethics hub identifies the current Ethics Code, which addresses understandable communication, client involvement, consent and assent when applicable, confidentiality, 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 integrating research, clinical expertise, client values, and context.
Use implementation and access evidence for Tomas
In Tomas's plan, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit procedures, representative evidence, and cautious interpretation. They create no universal response threshold. Breaux and Smith offer assent-focused practice guidance in an evolving evidence base. ASHA supports continuous access to AAC tools or devices.
Close Tomas's review
Review the plan-correction request process with Tomas, 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.
Related resources
- How to Audit Closure of Client Requests in ABA Care
- How to Plan a Request-to-Review-Data Goal in ABA
- How to Plan a Request-to-Change-Support Goal in ABA
- How to Plan a Request-for-Less-Prompting Goal in ABA
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
- Breaux and Smith, Assent in Applied Behaviour Analysis and Positive Behaviour Support
- American Speech-Language-Hearing Association, Augmentative and Alternative Communication