Shuttle schedule template: build a timetable you can actually run

Shuttle schedule template: build a timetable you can actually run

Shuttle schedule template: build a timetable you can actually run

Operational Efficiency

Operational Efficiency

Nicholas C.

Nicholas C.

A timetable riders can read and a plan your dispatcher can run.

A shuttle schedule is the timetable that sets which vehicle leaves which stop at what time, who drives it, and how often each stop is served. For an operator running hotel, airport, campus, employee, or event shuttles, it is both the promise you make to riders and the plan your dispatcher works from every shift.

Most templates online are blank spreadsheets or published campus timetables. They show what a rider sees, not how to build a schedule that fits your vehicles, drivers, and drive times. This guide gives you a copyable template with the operator columns most templates leave out, the math for setting how often a shuttle comes, a worked example, and a checklist to test the schedule before your client or riders see it.

What should a shuttle schedule include?

A shuttle schedule needs two layers: the rider timetable (stops and times) and the operator plan (vehicle, driver, run number, and breaks). Publish the first, run the business on the second.

  • Run number, Rider timetable: Optional; Operator plan: Required, so every trip has an ID
  • Stop names and order, Rider timetable: Required; Operator plan: Required
  • Departure time at each stop, Rider timetable: Required; Operator plan: Required
  • Vehicle, Rider timetable: No; Operator plan: Required
  • Driver, Rider timetable: No; Operator plan: Required
  • Seats available, Rider timetable: Sometimes; Operator plan: Required for group or reserved runs
  • Layover and break time, Rider timetable: No; Operator plan: Required
  • Notes, Rider timetable: Service days, holidays; Operator plan: Fuel, gate codes, contact at each stop

If a column only exists in someone's head, it will be missed the day that person is out.

Copy this shuttle schedule template

Use the rider timetable for your website, hotel desk, or printed card, and the operator plan for your team. Replace every bracketed item.


Rider timetable: [Service name]Service days: [Monday to Friday / daily]. Effective [date]. Holiday schedule: [details].

  • [6:00 a.m.], Arrives [Stop B]: [6:12 a.m.]; Arrives [Stop C]: [6:25 a.m.]; Arrives back at [Stop A]: [6:40 a.m.]
  • [6:20 a.m.], Arrives [Stop B]: [6:32 a.m.]; Arrives [Stop C]: [6:45 a.m.]; Arrives back at [Stop A]: [7:00 a.m.]
  • [6:40 a.m.], Arrives [Stop B]: [6:52 a.m.]; Arrives [Stop C]: [7:05 a.m.]; Arrives back at [Stop A]: [7:20 a.m.]
  • [continue every X minutes until last departure], Arrives [Stop B]: ; Arrives [Stop C]: ; Arrives back at [Stop A]:

Last departure from [Stop A]: [time]. On-demand runs outside these hours: call [phone] or book at [link].

Operator plan: [Service name], [date]

  • 1, Vehicle: [Van 1]; Driver: [Driver]; Depart A: [6:00]; Arrive B: [6:12]; Arrive C: [6:25]; Back at A: [6:40]; Layover: [0 min]; Notes: [Fuel check]
  • 2, Vehicle: [Van 2]; Driver: [Driver]; Depart A: [6:20]; Arrive B: [6:32]; Arrive C: [6:45]; Back at A: [7:00]; Layover: [0 min]; Notes:
  • 3, Vehicle: [Van 1]; Driver: [Driver]; Depart A: [6:40]; Arrive B: [6:52]; Arrive C: [7:05]; Back at A: [7:20]; Layover: [0 min]; Notes:
  • [continue], Vehicle: ; Driver: ; Depart A: ; Arrive B: ; Arrive C: ; Back at A: ; Layover: ; Notes:

Shift and break plan

  • [Driver 1]: on [time], first run [number], break [time to time], off [time]
  • [Driver 2]: on [time], first run [number], break [time to time], off [time]
  • Spare vehicle: [vehicle], location [lot]
  • On-call driver: [name, phone]

How to set the frequency (headway math)

Frequency comes from loop time and the number of vehicles. Divide the full loop time, including layover, by the number of vehicles in service, and that is how often a shuttle reaches each stop.

Headway = loop time ÷ vehicles in service

Loop time is the drive from first stop back to first stop, plus dwell time at each stop for loading, plus a layover buffer. Leave out the buffer and every late run pushes the next one later until the schedule collapses by mid-morning.

  • 30 minutes, 1 vehicle: Every 30 min; 2 vehicles: Every 15 min; 3 vehicles: Every 10 min
  • 40 minutes, 1 vehicle: Every 40 min; 2 vehicles: Every 20 min; 3 vehicles: Every ~13 min
  • 60 minutes, 1 vehicle: Every 60 min; 2 vehicles: Every 30 min; 3 vehicles: Every 20 min

Pick headways that riders can remember. "Every 20 minutes at :00, :20, and :40" beats "every 17 minutes."

Worked example: a hotel to airport loop

This example builds a weekday hotel shuttle from scratch. All times and numbers are assumptions chosen to show the method.

Assumptions:

  • Stops: Hotel, Airport Terminal 1, Airport Terminal 2, back to Hotel
  • Drive times: Hotel to T1 14 minutes, T1 to T2 4 minutes, T2 to Hotel 15 minutes
  • Dwell: 3 minutes at each terminal, 4 minutes at the hotel
  • Layover buffer: 4 minutes per loop
  • Service hours: 5:00 a.m. to 11:00 p.m.
  • Hotel request: a shuttle at least every 30 minutes, every 20 minutes from 5:00 to 9:00 a.m.

Step 1: loop time. 14 + 4 + 15 = 33 minutes of driving. Dwell adds 3 + 3 + 4 = 10 minutes. Buffer adds 4. Loop time is 47 minutes.

Step 2: vehicles needed. For a 20-minute peak headway: 47 ÷ 20 = 2.35, so round up to 3 vans. For 30 minutes off-peak: 47 ÷ 30 = 1.57, so 2 vans.

Step 3: adjust the loop to the headway. With 3 vans at a 20-minute headway, the cycle is 60 minutes, so each van has 13 minutes of slack per loop (60 minus 47). With 2 vans at 30 minutes, the cycle is also 60 minutes, with the same 13 minutes of slack. That slack is where breaks, fuel, and traffic recovery go.

Step 4: vehicle hours. Peak: 3 vans for 4 hours is 12 vehicle hours. Off-peak: 2 vans for 14 hours is 28 vehicle hours. Total: 40 vehicle hours a day.

Step 5: drivers. Assuming shifts of up to 10 hours with breaks, 40 vehicle hours needs at least 4 drivers a day, plus a fifth for relief and sick days.

Those vehicle hours are what you price. Multiply them by your cost per vehicle hour and add margin, using the method in how to price a shuttle service.

Fixed schedule, on-demand, or a mix?

Use a fixed timetable when demand is steady and predictable, and on-demand booking when it is thin or scattered. Most operators end up with a mix.

  • Fixed loop, Best for: Hotels and campuses with steady flows; Watch out for: Empty runs in quiet hours
  • On-demand, Best for: Late nights, small properties, low volume; Watch out for: Wait times when several requests arrive at once
  • Fixed at peak, on-demand off-peak, Best for: Most hotel and airport work; Watch out for: Riders need to know which hours are which
  • Reserved seats, Best for: Events, tours, employee routes with set riders; Watch out for: No-shows holding seats

For reserved-seat or on-demand runs, take bookings with passenger counts so you know which vehicle each run needs.

Checklist: test the schedule before you publish

Walk through this list with the person who will dispatch the service. It is cheaper to find a problem on paper than at the curb.

  • [ ] Every loop includes dwell time at each stop and a layover buffer.
  • [ ] Drive times were checked at the actual hour of service, not midday.
  • [ ] Headways are easy to remember and match what the client asked for.
  • [ ] Every run has a vehicle and a driver assigned.
  • [ ] No driver is on two runs at the same time.
  • [ ] Breaks are inside the slack time and meet your driver hours policy.
  • [ ] A spare vehicle and an on-call driver are named.
  • [ ] First and last departures are clear on the rider timetable.
  • [ ] Holiday and weekend service is stated.
  • [ ] On-demand hours, if any, tell riders exactly how to book.
  • [ ] The schedule matches the contract you priced.

How to handle changes on the day

Every schedule breaks at some point: a van gets a flat, a driver calls out, or a flight bank lands late. Decide the response in advance so the dispatcher is not improvising.

  • Vehicle out of service, First response: Move the spare into that run; if none, stretch the headway on the remaining vans; Tell riders?: Yes, if the headway changes
  • Driver calls out, First response: Call the on-call driver; cover the first runs from the shift with the most slack; Tell riders?: Only if runs are skipped
  • Traffic delay over 10 minutes, First response: Use the layover buffer; skip the layover on the next loop to recover; Tell riders?: Yes, at the stop that is waiting
  • Surge of riders, First response: Add an extra run with the spare van, or move a later run earlier; Tell riders?: No, if it is covered
  • Client adds a run, First response: Check the board for a free vehicle and driver before you say yes; Tell riders?: The client, in writing

Write these responses on the operator plan so anyone on dispatch can follow them. After each disruption, check whether the buffer or the spare plan needs to change.

Running the schedule in Ride Sync

A spreadsheet works until something changes. When a driver calls out or a client adds runs, you want the schedule and the dispatch board to be the same thing.

In Ride Sync, each run or on-demand trip is a reservation on the dispatch board, with the passenger count, pickup, and stops. Shuttle, limo, taxi, and tour jobs share one board, so the van that runs the hotel loop in the morning can take a charter in the afternoon without a second system. When you assign a driver, the scheduling assistant highlights on the reservation and quote pages if that driver is already booked at that time, so overlaps are visible before you commit. Live GPS shows where each vehicle is. Drivers get their assignments and reminders by email, and riders who book online get SMS and email confirmations and reminders. For the client side, invoice the contract from the reservations.

For the bigger picture on running shuttles, see shuttle management software, and for how the board works day to day, see limo dispatch from the dispatcher's chair.

Frequently asked questions

What is a shuttle schedule template?

It is a reusable timetable that lists stops, departure times, and, for operators, the vehicle, driver, run number, and breaks for each trip. You fill it in for each service and publish the rider part.

How do I figure out how often a shuttle should run?

Divide the loop time, including stop time and a buffer, by the number of vehicles in service. A 47-minute loop with 3 vehicles can run about every 16 minutes, so you might publish every 20 minutes and keep the slack for breaks and traffic.

How many shuttles do I need?

Divide the loop time by the headway the client wants and round up. A 47-minute loop at a 20-minute headway needs 3 vehicles.

Should a shuttle schedule include driver breaks?

Yes, in the operator version. Put breaks inside the slack time between loops so they do not push the published times.

Can riders book shuttle seats online?

Yes. With Ride Sync, riders can book through the booking widget on your website and get SMS and email confirmations and reminders.

Quick recap

A shuttle schedule has a rider timetable and an operator plan. Build it from real loop times with dwell and buffer, set the headway by dividing loop time by vehicles, assign every run a vehicle and driver, and put breaks in the slack. Test it with the checklist, price the vehicle hours it creates, and run it on one dispatch board in Ride Sync so changes on the day are easy to handle.

Start a free trial of Ride Sync (14 days, no card required).

Ride Sync Reservation Dashboard
Image

Try Ride Sync Free for 14 Days

Start taking control of your business today

No Credit Card Required

Ride Sync Reservation Dashboard
Image

Try Ride Sync Free for 14 Days

Start taking control of your business today

No Credit Card Required

Ride Sync Reservation Dashboard
Image

Try Ride Sync Free for 14 Days

Start taking control of your business today

No Credit Card Required