To plan a request-to-change-setting goal in ABA, identify the setting the client wants and why. Verify clinical appropriateness, access, safety, privacy, payer, facility, staff, supervision, technology, and transport gates. Preserve continuity and interim support while qualified owners decide. Measure setting-option readiness, the client's request, response, release, implementation, fit, burden, and experience separately.
Define the requested setting
Record home, clinic, school, community, telehealth, workplace, or another location; the desired activity; preferred times; retained supports; and Mona's reasons.
Ask what Mona wants the setting change to improve. The request may concern travel, privacy, sensory conditions, family life, natural routines, access to peers, fatigue, infection risk, communication, or safety. Describe the specific activity and time rather than treating home, clinic, school, community, or telehealth as a single uniform option. A setting can fit one goal and create problems for another.
Record the elements Mona wants to keep, including staff, AAC, equipment, breaks, supervision, family involvement, or a familiar routine. Explain any practical difference in how services would occur and let her request a visit, demonstration, or trial. If the preferred setting is unavailable, preserve the request and identify the exact barrier.
Build setting gates
Check authority, clinical fit, accessibility, safety, privacy, consent, staff, supervision, payer, facility, technology, transport, emergency, and documentation.
Assign an owner to each gate. Clinical fit, payer authorization, school or workplace permission, facility rules, staffing and supervision, privacy, technology, transportation, infection precautions, emergency access, and legal authority may belong to different people. Record the evidence, date checked, expiration or renewal point, and whether the answer applies to the exact service and location.
Inspect the setting in practice. Verify physical and sensory access, a private space when needed, connectivity and backup for telehealth, communication supports, safe arrival and departure, storage, emergency contacts, and staff access to the current plan. A policy that permits a setting does not prove it is ready for Mona.
Plan continuity and release
Name interim care, approval owners, evidence, start condition, handoff, record access, orientation, stop rule, rollback, and follow-up.
Keep the current arrangement available until required approvals and operational gates are complete, unless Mona chooses a pause or an urgent safety decision requires another action. Set a release condition that lists the verified gates, start date, responsible coordinator, records handoff, partner orientation, and retained supports. Tell Mona which parts remain pending and when she will receive another update.
Use a bounded first-use period. Define what the team will observe, what Mona will report, how incidents or privacy problems are routed, and who can stop or roll back the change. If the new setting alters travel, preparation, recovery, family burden, or other care, include those effects in the review rather than measuring session attendance alone.
Measure readiness and fit
Report ready options, requests, decisions, release time, completed transitions, gaps, travel, burden, access failures, and Mona's experience.
Track proposed settings, gates verified, decisions completed, released transitions, first visits delivered, access failures, rollback events, and post-use reviews. Preserve unavailable options and overdue gates in the denominator. Close the request only after Mona receives the current decision, the chosen setting works for the approved scope, and any continuing mismatch has an assigned correction or reconsideration route.
Build Mona's setting-change request plan
Create one readiness row for each setting Mona wants considered. Record her reasons and preferred activities, clinical fit, consent and assent when applicable, privacy, accessibility, AAC and retained supports, staffing and supervision, facility and technology, payer state, transport, safety and emergency routes, records, start conditions, and the owner of each gate. Preserve interim care, orientation, first-use review, stop rule, and rollback. Request, qualified approval, operational release, completed transition, and Mona's experience remain distinct states.
Work through Mona's example
Mona compares four service settings. Three pass the required clinical, access, payer, staffing, and safety gates, so option readiness is 3 of 4, or 75%. She requests one ready setting, and the approved transition is released, or 1 of 1 implemented. The fourth setting remains a gate result. Release confirms that the transition may begin under its approved scope; actual fit, burden, and outcomes require first-use evidence and Mona's feedback.
Address Mona's main fit risk
A closer setting can remain unusable when privacy, access, staffing, or authorization fails. Mona's plan presents only verified options. Review privacy, access, partner behavior, burden, safety, and lived experience separately from the client response.
Choose Mona's next action
The responsible access or facility owner addresses the failed gate, Mona reviews the new setting after two visits, and the team preserves rollback. Record the qualified owner, authority, interim support, evidence needed, due date, client communication, correction route, disposition, and next review.
Reconcile the first two visits against the release checklist. Verify arrival and departure, staff access to the current plan, AAC and equipment, privacy, emergency readiness, supervision, technology when relevant, and delivery of the approved service. Record missed or shortened care by cause. A visit that occurred is not proof that every setting gate remained satisfied.
Ask Mona what changed outside the session, including travel, preparation, recovery, household disruption, sensory load, privacy, and access to preferred activities. If the setting works for one goal but not another, revise the approved scope instead of forcing a single setting decision across the plan. When rollback is needed, restore the prior workable arrangement promptly, preserve records from the trial, and assign each failed gate to its owner. Close only after Mona receives the disposition and the operational, clinical, payer, scheduling, and location records agree. Recheck the setting whenever staffing, supervision, technology, transport, authorization, emergency access, or Mona's communication needs materially change, since an earlier release cannot prove continuing readiness.
Apply current professional sources to Mona's plan
For Mona'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 Mona
In Mona'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 Mona's review
Review the setting-change request plan with Mona, 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 Plan a Request-to-Change-Schedule Goal in ABA
- How to Plan a Request-for-Different-Staff Goal in ABA
- How to Plan a Request-to-Retain-Support Goal in ABA
- How to Plan a Concern-Reporting 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