To monitor and reassess an ABA community transportation support plan, track Rhea's destinations and route-source freshness, pedestrian and provider access, communication, choice, partner response, restrictions, distress, walking, waiting, boarding, ride, transfer, exit, return, disruptions, missed stops, safety events, generalization, burden, and missing data. Keep planned, held, released, attempted, completed, messaged, and reconciled denominators separate. A higher navigation percentage cannot establish safety, clearance, independence, or meaningful benefit.

Define Rhea's page-specific decision

To monitor and reassess an ABA community transportation support plan, define the rider, destination, route, provider, current sources, pedestrian and vehicle segments, access, fare, mobility, communication, companion authority, release condition, and stop rule. Keep transit, paratransit, pedestrian, fare, mobility, emergency, clinical, companion, and rider decisions separate whenever the plan reopens.

Protect Rhea's essential access and safe return

Rhea's route plan keeps AAC, mobility devices, medication, identification, fare access, keys, phone or chosen backup, emergency contacts, and immediate help available. Rhea's community-transportation monitoring register cannot create provider approval, paratransit eligibility, medical clearance, legal authority, road safety, or consent to share location or private information.

Build Rhea's community-transportation monitoring register

Create one versioned record for the home, pedestrian routes, vehicles, stations, and destinations. Include Rhea's destinations, emergencies, providers, pedestrian segments, access, fare, mobility, communication, companions, restrictions, route steps, disruptions, outcomes, missingness, and reassessment evidence. Link every segment to route version, provider, pedestrian and access state, fare, mobility, AAC, message, partner response, restriction, disruption, rider experience, and decision.

Validate Rhea's counts and evidence

Reproduce 36 segments, eight held, 28 released, 22 completed, nine messages, eight timely responses, and 24 of 28 integrity.

Connect Rhea's evidence to a bounded action

The team resolves eight readiness gaps, reviews four integrity misses, removes one expired route card, and asks Rhea whether the plan still supports chosen destinations.

Work through Rhea's example

Rhea has 36 planned route segments. Eight stay held for a construction closure, outdated alert, inaccessible transfer, fare gap, mobility confirmation, AAC backup, companion handoff, or missing return route, leaving 28 released segments. Rhea completes 22 chosen segments, sends nine messages, and receives eight timely responses. Plan integrity is 24 of 28. Preserve every planned and eligible segment, source version, route, pedestrian and access state, fare and mobility condition, communication, rider choice, response, restriction, disruption, repair, and endpoint. This fictional example supplies no provider decision, paratransit determination, safety clearance, treatment effect, compliance result, or promised outcome.

Address Rhea's main interpretation risk

Reporting 22 completed segments alone would hide eight holds, one missed response, four integrity gaps, restrictions, disruptions, burden, and Rhea's experience. Review immediate safety, transit rules, pedestrian and system access, fare and mobility boundaries, communication, companion response, instruction, restrictions, rider priorities, disruption, burden, missingness, and design strength separately.

Set Rhea's ABA scope and ethics boundaries

Rhea's community-transportation monitoring register 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, confidentiality, documentation, and evaluation for covered people. Transit, paratransit, pedestrian, mobility, fare, emergency, safeguarding, employment, and legal authority remain with qualified owners.

Use the FTA ADA page for Rhea's provider questions

The current FTA ADA page describes the agency's role in nondiscriminatory public-transit access and points to federal guidance. It does not decide Rhea's route, reasonable-modification request, paratransit eligibility, provider acceptance, or safety. The community-transportation monitoring register stores the actual transit entity, service, request, response, date, and appeal or complaint route.

Read Part 37 within Rhea's actual service

49 CFR Part 37 contains federal requirements for specified transportation services and facilities for people with disabilities. Application depends on the entity, mode, service, vehicle, facility, and facts. Rhea's team routes legal and provider questions to the responsible authority and avoids translating an access failure into a clinical deficit.

Use the FTA circular as guidance for Rhea

The FTA ADA Circular 4710.1 explains Part 37 through examples and guidance, including accessible reasonable-modification request processes and the rule that a rider may describe the needed change without using a legal phrase. The regulation and current provider process govern. Rhea's clinical record may preserve the request and response while leaving the decision with the provider.

Inspect pedestrian conditions around Rhea

The NHTSA pedestrian-safety page describes roadway, crossing, visibility, weather, driver, and pedestrian risks. Its public tips are general guidance. Rhea's route review uses current traffic controls, infrastructure, local rules, lighting, construction, and mobility needs. It does not require eye contact or blame the rider for environmental and driver hazards.

Keep emergency action ahead of data for Rhea

The National 911 Program says an emergency requiring immediate police, fire, or ambulance assistance belongs with 911 and that call-takers may provide instructions. Local systems differ, and 911 is U.S.-specific. Rhea's team follows the dispatcher and qualified responders instead of completing a teaching trial, percentage, or routine approval first.

Make transportation communication accessible for Rhea

The DOJ effective-communication guidance explains that covered entities consider the nature, length, complexity, context, and person's usual method of communication. Transportation laws and providers can add distinct duties. The community-transportation monitoring register tests schedules, alerts, fare information, help requests, handoffs, disruption messages, and complaint routes while sending provider-access decisions to the provider.

Preserve Rhea's AAC and authorship

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Rhea's primary and tested backup communication stay available during approaches, crossings, waiting, boarding, rides, transfers, exits, disruptions, and emergencies. A companion may facilitate access without supplying Rhea's destination, consent, assent, account response, or incident report.

Use travel technology evidence cautiously for Rhea

A systematic review of assistive technology for practical skills included 18 studies involving autistic people or people with intellectual disabilities across varied targets and tools. It cannot establish that a route app, alert, beacon, tracker, fare tool, map, wearable, or AAC display will teach Rhea's navigation skill, prevent harm, generalize, secure access, or improve travel wellbeing.

Choose Rhea's next review trigger

Review after a destination, route, provider, alert, fare, mobility need, companion, restriction, disruption, incident, burden, or Rhea concern changes. Record the qualified owner, current source, effective date, route and rider version, access and fare state, mobility and communication arrangement, intervention and restriction authority, implementation check, accessible explanation, complaint path, and reassessment date.

Close Rhea's community-transportation plan

Review the community-transportation monitoring register with Rhea, the qualified behavior analyst, authorized companion when applicable, direct team, and specialists named in the manifest. Confirm that emergencies, pedestrian safety, provider rules, accessibility, fares, mobility, communication, assessment, teaching, restrictions, disruptions, and outcomes remain separate; every denominator is reproducible; AAC, mobility, refusal, withdrawal, location privacy, essentials, and emergency help remain protected; and conclusions stay bounded to sampled routes. Keep this page draft and noindex until every required review is complete.

Related resources

Sources