Wheelchair and Mobility Device Securement Log - Transit

This template records each wheelchair or mobility device boarding on a transit trip, including lift deployment, securement actions, and any exception events such as pass-bys or capacity limits. It is designed to create a clear audit trail for operators and supervisors. Use it when you need trip-level documentation rather than a general incident report.

The operator or another staff member directly involved in the boarding should complete the log while the event is fresh. If a supervisor reviews the trip later, they can add notes or follow-up actions without changing the original event record. Keeping one accountable owner per entry improves consistency and reduces missing fields.

Use it for every relevant boarding event, not only when something goes wrong. That includes successful boardings, lift deployments, securement completion, safety issues, and exception events. Consistent use makes it easier to spot patterns in route performance, equipment issues, and training needs.

Yes, it is structured to document the operational details that matter for ADA-related transit handling, including boarding outcome, securement, and exception reasons. It does not replace legal review or agency policy, but it helps create a reliable record of what happened on the trip. Add your agency’s required language and review steps where needed.

Make the trip date, time, route or service, vehicle number, operator ID, boarding outcome, and securement status required. Keep passenger feedback, safety issue details, and follow-up required only when the related condition is selected through conditional logic. That approach follows data minimization and avoids forcing operators to fill out irrelevant fields.

Use conditional logic so exception fields appear only when there is a pass-by, capacity issue, equipment failure, or other service disruption. The form should capture the exception type, a short reason, and whether follow-up is required. This keeps the log usable during live operations while still preserving the details needed for review.

Yes, you can adapt the route field, boarding location options, securement methods, and exception types to match fixed-route, paratransit, shuttle, or campus transit operations. You can also add vehicle-specific fields such as ramp type or securement hardware if your fleet uses them. Keep the structure focused on the data you actually use.

Common mistakes include marking every field required, using free-text where a dropdown or date picker is better, and failing to record the reason for an exception. Another frequent issue is skipping the consent or notice acknowledgment when passenger feedback or other PII is collected. Clear validation and a short submit-confirmation line help prevent incomplete records.

Ad-hoc notes often miss key details like lift deployment status, securement completion, or the exact reason for a pass-by. This template standardizes the record so supervisors can compare trips, identify recurring issues, and maintain an audit trail. It also makes it easier to route follow-up actions to the right team.