To define elopement wandering exit and missing person events, specify Leon's starting boundary, observable movement, opportunity, distance or duration, destination, supervision, consent, context, and danger. Keep attempted leaving, boundary crossing, temporary separation, lost contact, missing-person activation, safe independent movement, break, and authorized exit as different states. One broad label can produce misleading data and unsafe or unnecessarily restrictive responses.
Define every boundary
Name the room, property, route, person-distance, visual-contact, handoff, vehicle, water, traffic, or digital check-in boundary and when it applies.
Separate attempts and outcomes
An approach, door touch, opening, crossing, separation, lost contact, and missing-person activation have different units and risks. Preserve the full sequence when several occur.
Protect authorized movement
Record break, leave request, transition, independent travel, bathroom use, sensory movement, emergency exit, and person-chosen departure as authorized when their actual conditions are met.
Attach context and hazard
Record people, activity, transition, access, communication, health, destination, duration, supervision, water, traffic, weather, and other hazards without treating them as proven causes.
Choose response thresholds
State which event triggers proximity support, environmental check, clinical review, supervisor call, emergency activation, family contact, medical evaluation, and post-event review.
Build Leon's elopement event-definition register
Create one versioned record for the inclusive elementary program. Include Leon's event definitions, opportunities, destinations and hazards, communication and access, health context, functional hypotheses, environmental safeguards, transition and community supports, response roles, emergency route, privacy, integrity, raw outcomes, invalidity, missingness, restrictions, person and family experience, bounded action, and reassessment trigger. Store current emergency information for authorized rapid access and other purpose-needed data with role limits. Include examples and nonexamples from the actual setting. Train observers on video or safe walkthroughs, sample agreement, and report event-state reliability separately from intervention results.
Validate Leon's evidence
Reproduce 30 events: nine authorized exits, seven breaks, six boundary approaches, four crossings with contact, two separations, one lost contact, and one missing-person activation.
Connect Leon's evidence to an action
The program replaces one elopement checkbox with the seven event states and assigns a different action threshold to each. Leon's ordinary movement remains visible rather than coded as absence of behavior.
Work through Leon's example
Across 30 movement events, Leon has nine authorized exits, seven agreed breaks, six approaches to a boundary, four boundary crossings with staff contact, two temporary separations, one lost-contact event, and one missing-person activation. The seven categories sum to 30. Preserve every planned and eligible opportunity, access and safeguard version, communication, partner response, event state, hazard, emergency action, invalid record, correction, restriction, and outcome. This fictional example demonstrates one workflow control. It supplies no diagnosis, function proof, treatment effect, legal authority, restraint permission, emergency clearance, coverage result, or prevention guarantee for Leon.
Address Leon's main interpretation risk
Counting all 30 as elopement would classify 16 authorized exits or breaks as dangerous behavior. Combining a boundary approach with a missing-person event would erase the operational difference that controls response urgency. Review exposure, event definition, destination, communication, access, health, pain, sensory conditions, transition, consequence history, partner response, environment, safeguard delivery, privacy, restrictions, person priorities, missingness, and design strength separately. Zero events, blocked attempts, rapid return, calm appearance, compliance, unsupported independence, or staff confidence cannot establish function, safety, consent, effectiveness, or quality.
Set Leon's clinical and safety scope
For Leon's elopement event-definition register, the CASP public summary supplies high-level ABA behavioral-health-treatment scope for autistic people. The current BACB Ethics Code addresses competence, client involvement, consent and assent when applicable, medical needs, assessment, intervention, risk, data, documentation, confidentiality, and evaluation for covered people. The BACB outline is examination content. These sources require qualified clinical judgment and do not create emergency, restraint, facility, legal, payer, or first-responder authority.
Use current public safety guidance for Leon
The CDC's January 2026 wandering page describes wandering as leaving a safe area or responsible caregiver in circumstances that may lead to harm. It recommends prevention and response planning, current identifying information, home safeguards, communication and safety skills, neighbor and school awareness, and first-responder preparation. The page cites parent-report prevalence and common dangers; it does not establish Leon's function, treatment, supervision level, or legal authority.
Read the elopement research narrowly for Leon
A systematic review of experimental elopement research from 2000 through 2015 found 12 included studies with 20 participants and 27 functional analyses. Functions and treatment packages varied, most evidence came from small single-case evaluations, and settings were often controlled. This literature supports individualized functional analysis and treatment evaluation for Leon; it does not supply a universal procedure, effect size, community-safety guarantee, or complete evidence base after 2015.
Expect setting effects for Leon
One single-participant school study conducted functional analyses in a classroom and resource room and reported different maintaining relations across those settings, followed by setting-matched intervention comparisons. The result illustrates why Leon's setting, activity and consequences need separate evidence. It cannot estimate prevalence or show that every setting change alters function.
Scope communication treatment for Leon
A single-case neighborhood study evaluated functional communication training and delay fading for one nine-year-old whose analysis suggested mixed attention and tangible functions. The authors omitted an alone condition because of danger. The study shows one assessment-linked sequence and one safety decision, not a standard request form or fading schedule. ASHA's AAC portal says AAC users should always have access to their tools or devices, so Leon's communication remains available during prevention, assessment, treatment, community activity, and emergencies.
Preserve participation and urgent action for Leon
The UK NICE NG11 recommendations emphasize person involvement, communication, health review, environment, proactive support, quality of life, least-restrictive practice, risk assessment, and frequent review for people with learning disabilities whose behavior challenges. These principles organize questions for Leon but are not U.S. authority or an elopement protocol. For danger or a medical emergency in the United States, SAMHSA directs people to call 911 or go to the nearest emergency room; routine ABA assessment and authorization steps never delay emergency action.
Choose Leon's next bounded action
Definitions are tested in each location and revised after a route, boundary, supervision, communication, mobility, or safety change. Record the qualified owner, source, effective date, setting and plan version, emergency route, access and support arrangement, legal or facility review when applicable, implementation check, accessible explanation, disagreement or complaint path, and reassessment trigger. Preserve earlier evidence when conditions change.
Close Leon's playbook
Review the elopement event-definition register with Leon, the qualified behavior analyst, family or authorized decision-maker when applicable, direct team, and specialists named in the manifest. Confirm that emergency response, assessment, environmental prevention, communication, treatment, community access, and legal authority remain separate; every denominator is reproducible; AAC, privacy, movement, basic needs, prescribed care, valid exits, and emergency help remain protected; urgent needs received action; every restrictive measure has authority and review; and conclusions stay bounded to sampled conditions. Keep this page draft and noindex until every required review is complete.
Related resources
- How to Build a Missing-Person Response Protocol for Elopement Risk
- How to Build an ABA Elopement Safety and Support Playbook
- How to Assess Elopement Function Without Unsafe Test Conditions
- How to Monitor and Reassess an ABA Elopement Support Plan
Sources
- 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
- Centers for Disease Control and Prevention, Wandering (Elopement)
- Systematic Review of Functional Analysis and Treatment of Elopement, 2000 to 2015
- Lang and colleagues, Functional Analysis and Treatment of Elopement Across Two School Settings
- FCT and Delay Fading for Elopement With a Child With Autism
- American Speech-Language-Hearing Association, Augmentative and Alternative Communication
- National Institute for Health and Care Excellence, Challenging Behaviour and Learning Disabilities, NG11 Recommendations
- Substance Abuse and Mental Health Services Administration, Find Support in a Crisis