Passenger Boarding Assistance Log
Log boarding and alighting assistance for passengers with disabilities, including origin-to-destination service, mobility aid use, securement, and follow-up notes. Use it to create a clear service record after each trip.
Trusted by frontline teams 15 years of frontline software
Built for: Public Transit · Paratransit · Airports And Shuttle Services · Higher Education · Senior Transportation
Overview
The Passenger Boarding Assistance Log is a trip-level workplace form for documenting the help provided to passengers with disabilities during boarding, travel, and alighting. It captures the service date, trip ID, service type, pickup and dropoff locations, the assistance provided, any mobility aid used, whether securement was required and completed, and any exception that needs follow-up.
Use this template when your operation needs a clear record of origin-to-destination assistance, securement handling, or a service issue that should be reviewed later. It is especially useful for transit, paratransit, shuttle, campus, and airport operations where staff may provide different levels of support from one trip to the next. The submission notice and operator attestation help make the record traceable, while the follow-up section keeps unresolved issues from getting lost in a free-text note.
Do not use this form as a general incident report, a medical intake, or a passenger complaint form. It is not meant to collect unnecessary PII or detailed health information. Keep the fields focused on the service event, use conditional logic for follow-up questions, and leave non-applicable items hidden so the form stays quick to complete and easier to review.
Standards & compliance context
- If the form collects any passenger-identifying information, include a clear consent or disclosure statement and follow data minimization principles under GDPR Article 5.
- If the log is used in a public-facing or passenger-facing workflow, make sure the form fields, labels, and validation support WCAG 2.1 AA accessibility.
- For disability-related assistance records, keep the form focused on accommodation and service delivery rather than unnecessary medical detail, consistent with minimum-necessary handling.
- If the log is used in HR or operator training contexts, avoid collecting more personal information than needed and route sensitive follow-up only to authorized reviewers.
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 sets expectations for what the log is for and how any consent or disclosure language is presented before data is collected.
- Purpose of this log
- I understand this form may collect limited PII needed to document accessible transit service and maintain an audit trail.
Trip Details
These fields identify the specific trip so the assistance record can be matched to dispatch, scheduling, or service history.
- Service date
- Trip ID or run number
- Service type
- Pickup location
- Drop-off location
Passenger Assistance
This is the core of the form, where the operator records what help was provided, what equipment was used, and whether securement was completed.
- Assistance provided
- Mobility aid used
- Was securement required?
- Securement completed successfully
-
Assistance notes
Briefly describe any notable boarding, alighting, or securement details. Avoid unnecessary personal or medical information.
Exceptions and Follow-up
This section captures anything that did not go as planned and routes unresolved issues to the right next step.
- Was there any service issue or exception?
- Issue type
- Follow-up required
- Follow-up details
Operator Attestation
The attestation confirms who completed the record and supports accountability if the log is reviewed later.
- Operator name
- Operator ID
- I attest that this log is accurate and completed at or near the time of service.
How to use this template
- 1. Set up the form with the trip fields, assistance fields, and follow-up fields, and mark only the truly necessary fields as required.
- 2. Assign the form to the operator or staff member who provided the assistance so the record is completed by the person with direct knowledge of the trip.
- 3. Enter the service date, trip ID, service type, pickup location, and dropoff location immediately after the trip or at the end of the shift.
- 4. Record the assistance provided, the mobility aid used, and whether securement was required and completed, using conditional logic to show follow-up fields only when needed.
- 5. Describe any service issue in plain language, note the issue type, and route the record to follow-up when the passenger experience or safety process needs review.
- 6. Review the operator attestation before submission so the final log is complete, accurate, and ready for audit trail or supervisor review.
Best practices
- Use dropdowns or multi-select fields for assistance types and issue types so operators do not have to type the same answers in different ways.
- Keep the form short by hiding follow-up fields until a service issue is selected, which reduces clutter and supports progressive disclosure.
- Use a date picker for service_date and structured fields for trip_id and locations instead of free-text notes that are hard to search.
- Record securement_completed separately from securement_required so reviewers can see whether the step was needed and whether it was actually done.
- Keep assistance_notes factual and specific, such as what support was provided and what condition affected the trip, rather than broad summaries.
- Add a clear submission notice that explains what happens after the form is submitted, who can see it, and whether the passenger can submit anonymously if your workflow allows it.
- Review logs for repeated issue types so dispatch or operations can spot recurring barriers, route problems, or training needs.
- Limit collected PII to what is needed for the service record and avoid adding sensitive details that do not change the follow-up action.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template records the assistance provided to a passenger during boarding, travel, and alighting. It captures trip details, the type of help given, whether a mobility aid was used, and whether securement was completed. It also includes an attestation so the operator can confirm the record is accurate.
When should this log be completed?
Complete it as soon as practical after the trip, while the details are still fresh. It is most useful for scheduled transit, paratransit, shuttle, and other passenger services where assistance may vary by trip. If an issue occurred, log the exception and any follow-up before closing the record.
Who should fill out the Passenger Boarding Assistance Log?
The operator or staff member who provided the assistance should complete the form, since they can confirm what happened at the point of service. A supervisor may review it later if there was a service issue, a missed securement step, or a follow-up action. The attestation field helps make ownership clear.
Does this template collect personal data?
It can, depending on how you configure the fields and notes. Keep data minimization in mind and collect only what you need to document the service event, not unnecessary PII. If you include passenger-identifying details, add clear consent or disclosure language and limit access to the record.
How does this help with accessibility and accommodation workflows?
The template supports consistent documentation of assistance for passengers with disabilities, including mobility aid handling and securement. That makes it easier to track whether the service matched the requested accommodation and whether any barrier needs follow-up. It also helps teams standardize records without over-collecting information.
What are the most common mistakes when using this form?
Common mistakes include leaving the service type vague, skipping securement details, and writing notes that are too general to act on. Another issue is marking every field required, which can slow down reporting and reduce completion quality. Use conditional logic so follow-up fields only appear when there is an issue.
Can this log be customized for different transit or shuttle operations?
Yes. You can rename service types, adjust assistance options, add vehicle identifiers, or tailor the issue list to your operation. If your workflow includes dispatch, incident review, or maintenance, connect the follow-up fields to those processes rather than forcing everything into one note field.
How should this template fit into existing systems?
Use it as the source record for trip-level assistance events, then route follow-up items to dispatch, customer service, or safety review as needed. It can also be paired with an audit trail so supervisors can see who entered or updated the log. If you already use scheduling or incident software, map the trip ID to that system for easier lookup.
Is this better than ad-hoc notes or email updates?
Yes, because it creates a consistent structure for the same information every time. Ad-hoc notes often miss key fields like securement completion, follow-up status, or operator attestation. A standardized log is easier to review, search, and audit than scattered messages.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
MangoApps AI agents now take action across 21 apps—approving leave, advancing candidates, managing schedules—not just surfacing recommendations.
-
Discover how manual performance review processes drain HR productivity, introduce payroll errors, and stall talent strategy — and what automated systems fix.
-
Fix recruiting pipeline handoffs with a unified candidate portal, branded career pages, and faster offers that keep top talent engaged.
-
MangoApps is now Workday Design Approved, surfacing benefits, pay, learning, and time-off data directly inside the MangoApps platform for frontline workers.
Ready to use this template?
Get started with MangoApps and use Passenger Boarding Assistance Log with your team — pricing built for small business.
