Shuttle and Transportation Dispatch Log
Track guest shuttle and transportation requests from dispatch to drop-off in one log. Use it to assign drivers, record timing, capture special needs, and close out each trip with a clear status.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Hospitality · Transportation And Logistics · Higher Education · Corporate Facilities · Healthcare
Overview
The Shuttle and Transportation Dispatch Log template is built for recording each guest ride request in one place, from initial dispatch through trip completion. It includes fields for log date, dispatcher, shift, trip ID, guest details, pickup and drop-off locations, scheduled and actual times, driver and vehicle assignment, odometer readings, trip status, incidents, and follow-up notes.
Use this template when your team needs a reliable record of who was moved, when the ride was scheduled, who handled it, and whether anything went wrong. It is especially useful for hotels, resorts, campuses, event venues, corporate shuttles, and healthcare facilities where transportation requests need to be coordinated quickly and reviewed later. The structure also supports special needs notes and guest signature capture when your process requires confirmation at drop-off.
Do not use this template as a route-planning tool or a fleet maintenance log. It is not meant to replace driver schedules, vehicle inspection checklists, or reservation systems. It also should not collect more guest data than the trip requires. Keep fields focused on operational use, apply conditional logic for special needs or incidents, and avoid adding unnecessary PII. If you need a simple, auditable record of each trip, this template gives you the right fields without turning dispatch into paperwork.
Standards & compliance context
- Keep guest data collection aligned with GDPR data minimization by collecting only the fields needed to dispatch and complete the trip.
- If the log captures accessibility or accommodation details, use clear consent or disclosure language and limit notes to what operations need to know.
- Avoid unnecessary PII in free-text fields, and restrict access to trip records when they include contact information or incident details.
- If the log is used in a healthcare setting, keep special-needs notes to the minimum necessary for safe transport and handling.
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
Log Entry Details
This section creates the core audit trail by tying each trip to a date, dispatcher, shift, and unique trip ID.
-
Log Date
Date this trip is being logged.
-
Dispatcher Name
Name of the dispatcher or staff member creating this log entry.
- Shift
-
Trip / Request ID
Auto-generated unique identifier for this trip record.
Guest and Request Information
This section captures the passenger details needed to contact the guest and prepare the right vehicle or assistance.
- Guest / Requester Name
-
Room Number / Employee ID / Reservation #
Reference identifier for the guest or requester. Collect only what is operationally necessary.
-
Guest Contact Phone
Optional callback number in case of delays or changes. PII — collect only if needed for this trip.
- Number of Passengers
-
Accessibility or Special Accommodation Needs
Select all that apply. Ensures ADA-compliant vehicle and assistance are arranged in advance.
- Accommodation Notes
Trip Details
This section records where the trip starts and ends, when it was scheduled, and when it actually happened.
- Trip Type
- Pickup Location
- Drop-Off Location
-
Scheduled Pickup Time
Date and time the pickup was requested or scheduled.
-
Actual Pickup Time
Record the actual time the vehicle arrived at the pickup location.
-
Actual Drop-Off Time
Record the time the passenger(s) were delivered to the drop-off location.
-
Flight Number
Required for airport pickups to monitor arrival status.
Driver and Vehicle Assignment
This section links the trip to the person and vehicle responsible for completing it, which is essential for accountability.
- Assigned Driver Name
-
Driver ID / Badge Number
Internal driver identifier for audit trail purposes.
- Vehicle ID / Unit Number
- Vehicle Type
-
Odometer Reading at Departure (miles)
Record starting mileage for fleet maintenance and cost tracking.
- Odometer Reading at Return (miles)
Trip Status and Outcome
This section shows whether the ride was completed, delayed, interrupted, or involved an incident.
- Trip Status
-
Delay or Cancellation Reason
Select the primary reason if the trip was delayed or cancelled.
- Did any incident, accident, or safety concern occur during this trip?
-
Incident Description
Provide a factual description. A formal incident report should also be completed per your organization’s safety procedures.
-
Guest Acknowledgment / Signature Obtained
Indicate whether the guest signed a transport acknowledgment form, if required by your property.
Dispatcher Notes and Attachments
This section preserves context, follow-up actions, and supporting files so the record is usable after the shift ends.
- Dispatcher / Driver Notes
-
Follow-Up Required?
Check if this trip requires follow-up action by a supervisor or manager.
- Follow-Up Details
-
Supporting Documents or Photos
Attach any relevant documents such as signed transport forms, damage photos, or flight confirmation printouts.
How to use this template
- 1. Set up the log with your standard trip ID format, required fields, and any conditional logic for special needs, incidents, and follow-up.
- 2. Enter the request as soon as it is received by recording the guest, pickup and drop-off details, trip type, and scheduled pickup time.
- 3. Assign the driver and vehicle, then confirm the vehicle ID, vehicle type, and starting odometer before the trip begins.
- 4. Update the record at pickup and drop-off with actual times, delay reasons if needed, and any incident or guest signature information.
- 5. Review the completed log at the end of the shift, resolve any follow-up items, and attach supporting notes or files before closing the trip.
Best practices
- Mark only the fields you truly need as required, and use progressive disclosure for special needs and incident details.
- Use a date picker for dates, time fields for pickup and drop-off times, and numeric inputs for passenger count and odometer readings.
- Record the trip ID at the time of dispatch so the request can be traced across shifts without relying on memory.
- Capture delay reasons in plain operational language, such as traffic, late guest, or vehicle swap, rather than vague comments.
- Collect only the minimum guest information needed to complete the ride and contact the passenger if the trip changes.
- Log actual pickup and drop-off times as close to the event as possible so the record stays accurate.
- Attach incident photos, notes, or handoff documents to the trip record when follow-up is required.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this dispatch log used for?
This template records each guest transportation request from the moment it is logged through completion. It captures who requested the trip, where the guest was picked up and dropped off, which driver and vehicle were assigned, and whether the trip finished on time. It is useful when you need a single audit trail for shuttle operations, hotel transfers, airport runs, or campus transport.
Who should fill out the log?
A dispatcher, front desk agent, transportation coordinator, or shift lead should complete the log when the request is received and update it as the trip progresses. The driver may provide timing, odometer, or incident details, but one owner should be responsible for final accuracy. That keeps the record consistent and reduces missing fields.
How often should this log be used?
Use it for every scheduled or on-demand trip, not just exceptions. A per-trip log works best when you need to compare demand by shift, spot delays, and review vehicle usage later. If your operation is very high volume, you can clone the template for each day or shift and keep trip IDs unique.
What kinds of transportation requests fit this template?
It fits guest shuttles, airport transfers, intercampus rides, parking-lot pickups, and other point-to-point transportation requests. The trip type field and conditional notes make it flexible enough for routine rides and special cases such as mobility assistance or flight-related pickups. It is not meant for freight dispatch or route optimization planning.
How does this template handle special needs or accessibility requests?
The template includes fields for special needs and notes so dispatch can record reasonable accommodation details without over-collecting personal data. Use progressive disclosure: only ask for the information needed to complete the ride safely and appropriately. Avoid unnecessary PII, and keep notes focused on operational needs such as wheelchair access, assistance boarding, or extra luggage space.
What are the most common mistakes when using a dispatch log?
Common mistakes include leaving pickup and drop-off times blank, assigning a vehicle without recording the vehicle ID, and writing vague delay reasons that cannot be reviewed later. Another frequent issue is failing to update trip status after completion, which makes the log unreliable for follow-up. A clear required-versus-optional field structure helps prevent those gaps.
Can this log be customized for hotels, airports, or campuses?
Yes. Hotels may add room number and guest signature steps, airports may emphasize flight number and terminal pickup details, and campuses may add building or department fields. Keep the structure aligned to the actual workflow so you do not turn a simple dispatch log into a catch-all form with too many required fields.
What should happen after the log is submitted?
After submission, the record should be available for dispatch review, driver assignment, and end-of-trip reconciliation. If an incident occurred or follow-up is required, the log should trigger a handoff to the appropriate manager or operations lead. If your process includes attachments, store them with the trip record so the audit trail stays complete.
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 —...
-
See how MangoApps Forms helps teams collect, track, and analyze employee data in real time — with mobile access, file uploads, and enterprise-grade security.
-
MangoApps Shifts & Schedules unifies frontline scheduling, time, and leave management in one native platform for faster, simpler operations.
-
Measure employee engagement with eNPS to track loyalty, uncover morale issues, and turn employee feedback into action.
-
Align remote and distributed teams with practical tools to improve communication, boost alignment, and reduce costly productivity gaps.
Ready to use this template?
Get started with MangoApps and use Shuttle and Transportation Dispatch Log with your team — pricing built for small business.
