Passenger Boarding Assistance Log
Log boarding and alighting assistance for passengers with disabilities, including securement, mobility devices, and follow-up needs. Use it to document origin-to-destination service with a clear audit trail.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Public Transit · Paratransit · Airports · Higher Education · Healthcare Transportation
Overview
The Passenger Boarding Assistance Log template records the assistance given to a passenger during boarding, travel, and alighting on a specific trip. It is built for situations where staff need to document origin-to-destination service, mobility device handling, securement decisions, accessibility equipment used, and any issues that affected the trip.
Use this template when a passenger requests help getting on or off a vehicle, when a mobility device must be managed, or when securement is required. It is also useful when the request comes from a caregiver, dispatcher, or other requester and you need a clear record of who asked for the service. The submission notice and audit trail fields help show what was reported, when it was logged, and whether follow-up was needed.
Do not use this form as a general complaint log or a broad incident report. If no assistance was provided, or if the event does not involve boarding, alighting, securement, or accessibility support, a different record type is usually a better fit. Keep the entries focused on the actual service delivered, and avoid collecting unnecessary personal data. The template works best when teams need a consistent, trip-level record that can be reviewed later for service quality, accessibility handling, and operational follow-up.
Standards & compliance context
- Keep the form aligned with GDPR data minimization by collecting only the passenger and trip details needed to document the assistance event.
- If the log is used in a public-facing or digital workflow, make the fields accessible and keyboard-friendly to support WCAG 2.1 AA expectations.
- When the form is used for disability-related service, include consent and disclosure language that explains what information is collected and why.
- Use the minimum-necessary principle for any health-related or mobility-related details, and avoid collecting sensitive information that is not needed for service delivery.
- Maintain an audit trail for submissions, edits, and follow-up actions so the record can support operational review and accountability.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Submission Notice
This section establishes why the log is being submitted and ties the record to one trip and one service date.
- Purpose of this log
- PII and service documentation notice
-
Trip or run reference
Internal trip, run, or dispatch reference for audit trail.
- Service date
Passenger and Trip Details
These fields identify the trip context and who requested help, which is essential for matching the assistance record to the right event.
-
Passenger identifier
Use a rider ID, reservation number, or other internal identifier if available. Avoid collecting full names unless necessary.
-
Boarding location
Where the passenger boarded.
-
Alighting location
Where the passenger exited.
- Service type
- Assistance requested by
- Other requester details
Assistance Provided
This section captures the exact boarding and alighting support delivered so the log reflects the service actually performed.
- Boarding assistance provided
- Other boarding assistance
- Alighting assistance provided
- Other alighting assistance
- Mobility device used
- Other mobility device
Securement and Accessibility Checks
These fields document whether securement was needed, what method was used, and whether any accessibility equipment or issues affected the trip.
- Was securement required?
- Was securement performed?
- Securement method used
- Any securement issue or exception?
- Securement issue details
- Accessibility equipment used
Notes and Audit Trail
This section records delays, follow-up actions, and operator notes so reviewers can understand the outcome and next steps.
- Delay caused by assistance event (minutes)
- Is follow-up required?
- Follow-up details
-
Operator notes
Brief factual notes for the audit trail. Do not include sensitive health information.
How to use this template
- Start by entering the submission purpose, consent notice, trip reference, and service date so the log is tied to one specific assistance event.
- Record the passenger identifier and trip locations, then note who requested the assistance and add requester details only when the requester is not the passenger.
- Select the boarding and alighting assistance types that were actually provided, and use the other fields only when the standard options do not cover the service.
- Document the mobility device used, whether securement was required, and whether securement was performed, then describe any securement issue or accessibility equipment used.
- Add delay minutes, follow-up requirements, and operator notes before submitting so the record reflects both the service outcome and any action needed afterward.
Best practices
- Use conditional logic so securement fields appear only when securement is required, which keeps the form shorter and easier to complete.
- Mark required versus optional fields clearly and keep the required set limited to what you need for the trip record.
- Use a passenger identifier instead of collecting unnecessary PII, and add consent language whenever the form captures personal or accessibility-related details.
- Choose structured field types that match the data, such as a date picker for service date and a numeric input for delay minutes.
- Describe assistance in plain operational terms, such as ramp deployment, escorting, lifting support, or securement, rather than using vague notes.
- Capture securement issues immediately after the trip so the record reflects what happened before memory fades.
- Route follow-up items to the right team, such as dispatch, accessibility management, or maintenance, instead of leaving them buried in operator notes.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this Passenger Boarding Assistance Log template used for?
It records the assistance provided during boarding and alighting for a specific trip, including securement steps and any accessibility equipment used. The template is meant to create a clear service record tied to a trip reference and service date. It is useful when you need to show what assistance was requested, what was provided, and whether any issues required follow-up.
Who should complete this log?
The operator, driver, attendant, or accessibility staff member who directly provided or observed the assistance should complete it. If a request came from someone other than the passenger, the form captures that relationship in the requester fields. A supervisor can review the completed log later as part of the audit trail.
How often should this form be used?
Use it for each trip where boarding or alighting assistance is provided, especially when securement, mobility devices, or accessibility equipment are involved. It is not meant to be a monthly summary or a general incident report. If your operation needs a record of every assistance event, this should be completed at the time of service or immediately after.
What kinds of assistance should be captured in the template?
Capture the specific boarding and alighting assistance types that were actually provided, such as physical support, ramp use, securement help, or help with a mobility device. The template also includes fields for other assistance details when the standard options do not fit. Keep entries factual and specific so the record reflects what happened, not a general impression.
How does this template support compliance and accessibility requirements?
The form supports documentation of accessibility-related service without collecting unnecessary PII. It also helps teams keep a consistent record of consent, assistance requested, securement decisions, and follow-up actions. That makes it easier to demonstrate process discipline for accessibility programs and to review whether service was delivered as intended.
What are the most common mistakes when using this log?
Common mistakes include leaving the service date or trip reference blank, using vague notes like "assisted passenger" instead of describing the actual action, and skipping securement details when securement was required. Another frequent issue is collecting more passenger information than the operation needs. Keep the form focused on the trip and the assistance provided.
Can this template be customized for different transit or shuttle operations?
Yes. You can rename assistance options, add vehicle-specific securement methods, or tailor the requester fields to match your dispatch or reservation workflow. If your operation uses conditional logic, you can show securement fields only when securement is required. The core structure should stay focused on boarding, alighting, and accessibility checks.
What should happen after the log is submitted?
The completed log should be reviewed for any securement issues, delays, or follow-up needs. If the form indicates a problem, it should route to the appropriate supervisor, accessibility lead, or maintenance contact. The submission should also be stored with an audit trail so the record can be retrieved later if needed.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Compare 9 top shift scheduling platforms for 2026—features, pricing, and workforce fit for frontline, retail, healthcare, and enterprise teams.
-
Discover 4 proven keys to successful project management and team collaboration — from transparent goal-setting to real-time communication and workflow...
-
Boost team collaboration with modern tools that improve visibility, accountability, and communication for stronger project outcomes.
-
Compare the best employee apps of 2026—MangoApps, Blink, WorkJam, Flip, and more—to find the right fit for your frontline workforce.
Ready to use this template?
Get started with MangoApps and use Passenger Boarding Assistance Log with your team — pricing built for small business.
