To coordinate an interdisciplinary personal emergency preparedness assessment, begin with Dev's priorities, local hazards, communication, mobility, health and medication needs, equipment, daily services, and chosen supporters. Assign official alerts, emergency management, medical and pharmacy questions, evacuation, transport, shelter, power, AAC, service-animal needs, privacy, and behavioral evidence to qualified owners. Preserve each source, conflict, uncertainty, and decision separately.

Define Dev's page-specific preparedness decision

To coordinate an interdisciplinary personal emergency preparedness assessment, define the person, hazard, location, official source, alert, action, communication, health and equipment needs, supporter, release gate, stop rule, backup, and recovery outcome. Inspect alerts, communication, health information, medication, mobility, devices, power, routes, transport, shelter, service animals, supporters, privacy, recovery, and reunification before recommending skill work.

Protect Dev's essential access and live response

Dev's plan keeps AAC, mobility, prescribed care, emergency help, hydration, bathroom access, essential devices, service-animal support, privacy, and lawful withdrawal from nonemergency drills protected. The interdisciplinary emergency preparedness assessment cannot create emergency, responder, medical, pharmacy, utility, transport, shelter, facility, or legal authority.

Build Dev's interdisciplinary emergency preparedness assessment

Create one versioned record for home, work, transport, shelter, and recurring service locations. Include Dev's hazards, official sources, alerts, communication, health, medication, mobility, devices, power, routes, transportation, shelters, supporters, kits, service animals, privacy, drills, incidents, recovery, expirations, missingness, and review. Use a question matrix with person priority, location, hazard, discipline or authority, exact question, source, date, result, uncertainty, conflict, decision, and accessible explanation.

Validate Dev's counts and denominators

Reproduce 33 items, 26 received across seven evidence categories, and seven named open items.

Connect Dev's evidence to a bounded action

The lead pauses affected drills and keeps Dev's account separate from emergency, medical, equipment, transport, shelter, access, and clinical findings. Low-risk tabletop work can continue where gates are complete.

Work through Dev's example

Dev's team predeclares 33 evidence items. Twenty-six arrive: six person and communication records, five hazard and official-source checks, four direct observations, three health records, three device and power reviews, three route and transport checks, and two supporter records. Seven remain open: backup power, oxygen transport, medication replacement, accessible shelter, overnight communication, service-animal supplies, and reunification. Preserve every planned, held, current, eligible, tested, completed, messaged, and reviewed unit with the hazard, location, source version, ordinary support, person response, partner action, restriction, incident, and endpoint. This fictional example supplies no official instruction, medical clearance, legal conclusion, real-event safety, treatment effect, or promised outcome.

Address Dev's main interpretation risk

Twenty-six of 33 measures evidence completeness. It cannot establish medical readiness, official approval, transport capacity, shelter access, equipment replacement, clinical need, or treatment effect. Each open item blocks only its governed decision. Review official sources, access, health, equipment, power, transport, shelter, communication, supporter behavior, instruction, restrictions, person priorities, incidents, recovery, missingness, and design strength separately.

Set Dev's ABA scope and emergency boundaries

Dev's interdisciplinary emergency preparedness assessment uses the CASP public summary only for high-level ABA behavioral-health-treatment scope for autistic people. The current BACB Ethics Code addresses competence, collaboration, consent and assent when applicable, assessment, risk, documentation, and evaluation for covered people. Emergency-management, responder, medical, pharmacy, equipment, utility, transport, shelter, facility, privacy, and legal authority remain with qualified owners.

Build Dev's plan around disability-specific daily needs

A Ready.gov disability-preparedness flyer highlights food, water, medication and medical supplies, communication needs, assistive-device evacuation, transportation, insurance copies, provider contacts, and responder-needed information. Dev's interdisciplinary emergency preparedness assessment converts those categories into person-specific questions and owners without promising quantities, availability, replacement, or access during a particular emergency.

Treat supporter planning as assigned work for Dev

The Ready.gov caregiver guide includes communication preferences, assistive-technology details, visual schedules, backup transportation, support-team responsibilities, medication and pharmacy information, AAC, chargers, documents, and clothing. It is preparedness guidance, not permission for a supporter to access every record, administer medication, control movement, or make Dev's decisions.

Keep Dev's kit tied to current needs and expirations

CDC emergency-kit guidance for people with disabilities identifies medical supplies and important health documents as kit considerations. The interdisciplinary emergency preparedness assessment adds item owner, quantity source, storage, access, expiration, replacement, temperature or power need, portability, and privacy. A checklist cannot guarantee that an item is clinically appropriate or available during an event.

Use accessible weather information for Dev

The National Weather Service materials for people with intellectual disabilities provide symbol-supported resources for heat, floods, tornadoes, lightning, cold, and wildfire. They are hazard education, not live local warnings or individualized clinical instructions. Dev's team pairs accessible teaching materials with current official alerts and the exact protective action for that location.

Keep fire escape planning specific to Dev's setting

The U.S. Fire Administration disability escape-plan collection offers current outreach materials about alarms, evacuation needs, fire-department discussion, building drills, service animals, and home plans. It does not approve Dev's route or authorize unsafe rehearsal. Qualified facility and fire-safety owners verify the actual setting, alarm, route, assistance, and drill.

Separate public emergency-system access from clinical skill for Dev

DOJ emergency-planning guidance describes Title II duties for accessible alerts, evacuation and transportation, shelters, modifications, and communication by state and local governments. It also recognizes that needs differ by person and event. Dev's access request goes to the responsible public entity; a clinical score cannot decide compliance or replace that duty.

Put 911 and official instructions ahead of Dev's data

The National 911 Program says an emergency requiring immediate police, fire, or ambulance assistance belongs with 911 and call-takers may provide instructions. Local systems differ, and this source is U.S.-specific. Dev's supporters follow responders instead of finishing a drill, photograph, percentage, or routine approval first.

Preserve Dev's AAC during every emergency stage

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Dev's primary system and tested backup stay available during alerts, protective action, travel, shelter, health communication, reunification, and recovery. A supporter may facilitate access without inventing Dev's location, symptoms, consent, choice, correction, or incident account.

Use broad preparedness guidance as a framework for Dev

Ready.gov's citizen-preparedness guide covers communication plans, meeting places, evacuation, documents, property, supplies, and practice. Hazards, official instructions, infrastructure, and personal needs change. Dev's interdisciplinary emergency preparedness assessment therefore keeps a source date, hazard and location scope, responsible owner, test result, expiration, and reopen trigger for every critical element.

Choose Dev's next review trigger

Re-coordinate after a hazard, address, official source, health need, medication, device, power source, route, shelter, supporter, or Dev request changes. Record the qualified owner, official source, effective date, hazard and location, alert and route version, health and equipment state, communication arrangement, test result, accessible explanation, emergency boundary, complaint route, and reassessment date.

Close Dev's preparedness plan

Review the interdisciplinary emergency preparedness assessment with Dev, the qualified behavior analyst, chosen or authorized supporters as applicable, and specialists named in the manifest. Confirm that official response, health and medication, equipment and power, transport and shelter, accessibility, communication, assessment, teaching, restrictions, incidents, and recovery remain separate; every denominator is reproducible; AAC, mobility, privacy, essential care, emergency help, and withdrawal from nonemergency drills remain protected; and conclusions stay bounded to tested conditions. Keep this page draft and noindex until every required review is complete.

Related resources

Sources