Every event shuttle starts with a plan: a schedule, a list of riders, a boarding procedure. Then the gates open and reality takes over. Bus 4 leaves six minutes late because the driver was stuck behind a delivery truck. The 7:40 run from the north lot fills up and leaves 22 people on the curb. A coach swaps out at noon for a mechanical issue. If nobody writes these things down as they happen, by Monday they are just impressions, and impressions are hard to plan from or to check an invoice against.
A shuttle dispatch sheet is the record of what actually happened. It logs each vehicle run with real times and real rider counts, one row per departure. This post gives you a ready-to-copy template, explains each column, and shows how to fill it during a live event and use it afterward.
Manifest, Boarding Plan or Dispatch Sheet?
These three documents get confused because they all sit on the same clipboard. They answer different questions. A manifest is about people, a boarding plan is about process, and a dispatch sheet is about vehicles over time.
| Passenger manifest | Boarding plan | Dispatch sheet | |
|---|---|---|---|
| Question it answers | Who should be on this bus? | How do people get on the bus? | What did each vehicle actually do, and when? |
| Unit of record | One row per passenger | One step per stage of loading | One row per vehicle run |
| Written | Before the trip | Before the event | During the event, live |
| Best for | Fixed groups, roll calls, emergency contacts | Lines, signage, staff roles at the curb | Repeating shuttles, open ridership, invoice checks |
| Where to start | Passenger manifest template | Event boarding plan guide | This post |
For a school trip or a single charter with a fixed group, a manifest may be all you need. For an open shuttle where anyone with a badge or ticket can ride, there is no list of names to check, and the dispatch sheet becomes the main record.
The Dispatch Sheet Template
Below is a template with six example rows from a fictional one-day outdoor festival. Three shuttles run between a remote parking lot and the main gate, plus one minibus from the partner hotel. Copy the header row into a spreadsheet or print it on a landscape page.
| Run # | Unit # | Driver | Route | Sched. depart | Actual depart | Riders boarded | Left behind | Sched. arrive | Actual arrive | Notes / issues | Initials |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 101 | S-12 | Marcus | North Lot → Main Gate | 9:00 | 9:02 | 34 | 0 | 9:15 | 9:16 | First run, light | KP |
| 102 | S-14 | Dana | North Lot → Main Gate | 9:10 | 9:16 | 36 | 8 | 9:25 | 9:33 | Driver late from staging, gate traffic | KP |
| 103 | S-12 | Marcus | Main Gate → North Lot | 9:20 | 9:20 | 2 | 0 | 9:35 | 9:34 | Deadhead with staff | JL |
| 104 | M-03 | Ray | Hotel → Main Gate | 9:30 | 9:31 | 24 | 0 | 9:55 | 9:58 | One wheelchair user, lift used | TW |
| 105 | S-16 | Lena | North Lot → Main Gate | 9:20 | 9:21 | 36 | 19 | 9:35 | 9:37 | Full, line growing. Called dispatch 9:22 | KP |
| 106 | S-14 | Dana | North Lot → Main Gate | 9:30 | 9:44 | 36 | 11 | 9:45 | 10:01 | Late return from gate, see incident #2 | KP |
Even six rows tell a story. The north lot is overloaded from the second run onward, Dana’s bus is running behind, and the gate is slow to clear. A dispatcher reading this at 9:45 a.m. has enough to act on. Here is what each column is for.
Run #
A unique number for each departure, not each vehicle. Pre-number the runs from the schedule (101, 102, 103) so the curb and the dispatcher can refer to “run 105” on the radio without confusion. If you add an unscheduled run, give it a number from a separate block, such as 500, so it stands out later.
Unit #
The vehicle’s fleet number, usually painted on the side or posted in the windshield. Ask the operator for the unit list before the event. If a vehicle is swapped mid-day, the new unit number shows up in the log and you have a clean record of when the change happened.
Driver
A first name is enough. It helps when you need to reach someone quickly, and it shows driver changes during the day. Long event days may involve a driver swap because of the federal hours-of-service limits for passenger-carrying drivers (10 hours of driving, no driving after 15 hours on duty), so a new name partway down the sheet is normal.
Route (From → To)
Use short, fixed names for each stop and use them every time. “North Lot” is better than “parking” or “the big lot.” Log empty or staff-only repositioning runs too, which is why run 103 says “Deadhead with staff.” Those runs explain gaps in service.
Scheduled depart and actual depart
Scheduled time comes from your plan. Actual time is when the doors close and the wheels move, not when the bus pulled in. The difference between the two is your headline number for on-time performance. Use a single clock for everyone, ideally phone time.
Riders boarded
The headcount for that run. On an open shuttle, a handheld tally counter is the simplest tool. Count at the door, one click per person, and write the number before the door closes. Do not estimate. “About 40” is not data.
Left behind
The number of people still in line when the bus filled and left. This is the most valuable column on the sheet and the one most templates skip. Ridership tells you how many people you moved; left-behind tells you how many you failed to move. A rough count is fine here, such as counting the line in groups of five.
Scheduled arrive and actual arrive
These come from the other end of the route. The destination marshal texts or radios the arrival time, and the logger fills it in. If you have only one logger, the driver can call it in, but only when safely stopped.
Notes / issues
Short facts only: “lift used,” “gate traffic,” “called dispatch 9:22.” If something needs more than a line, give it an incident number and log it on the separate incident sheet below.
Initials
Who wrote the row. When questions come up later, you know who to ask. It also keeps people from writing in each other’s rows.
How to Fill It In During the Event
Decide who logs
There are two common setups. In the first, each curb marshal keeps their own sheet for departures from that stop, and a central dispatcher merges them. In the second, one dispatcher keeps the master sheet and marshals call in each departure by radio or phone. The first is more accurate at the curb; the second gives one person the full picture in real time. For a small event with one or two stops, a single dispatcher works. For three or more stops, give each curb its own sheet and have them text the key numbers to the dispatcher after each run.
A standard call-in
Keep radio and phone reports in the same order every time, so the dispatcher can write as they listen. A simple script:
“North Lot, run 105, unit S-16, departed 9:21, thirty-six on, nineteen left.”
Arrival calls are shorter: “Main Gate, run 105 arrived 9:37.” Anything unusual gets a separate call, starting with “Incident” so the dispatcher knows to switch sheets.
Timestamps and counting
- Write times to the minute. Five-minute rounding hides the drift you are trying to see.
- Reset the tally counter to zero before every boarding. Write the number, then reset.
- Count staff and volunteers separately in the notes if they ride often; otherwise they inflate ridership.
- If a run is skipped, log it anyway with “no service” in the notes. A missing row looks like a lost record; a logged gap looks like a decision.
Left behind as a capacity signal
One run with people left behind is noise. Two in a row from the same stop is a trend. Three in a row means the line is growing faster than the shuttle can clear it, and waiting for it to sort itself out usually makes it worse. In the example, runs 102, 105 and 106 all left people behind at the North Lot. The dispatcher should have acted at run 105.
The Incident and Change Log
The run sheet records the routine. A second, smaller sheet records everything that changes the plan. Keeping them separate stops the main log from filling up with long notes, and it gives you a clean list of decisions to review after the event.
| Incident # | Time | What happened | Action taken | Approved by | Runs affected |
|---|---|---|---|---|---|
| 1 | 9:22 | North Lot line over 40, two runs full | Asked operator to move hotel minibus to North Lot after run 104 | Event ops lead | 105, 106, 501 |
| 2 | 9:38 | S-14 held at Main Gate 9 min by security vehicle check | Gate supervisor agreed to wave marked shuttles through lane 2 | Gate supervisor | 106 |
| 3 | 12:10 | S-16 warning light, driver pulled out of service | Operator sent spare unit S-20, ETA 35 min; headways stretched to 15 min | Operator dispatch + event ops lead | 131–136 |
| 4 | 14:45 | Headliner set moved 30 min later | Return service extended 30 min; operator confirmed driver hours | Event director | All PM returns |
The “Approved by” column matters because changes often cost money. Extending service, adding a vehicle or holding a bus past its booked end time will usually show up on the invoice. When someone on site agrees to it, write down who. Under federal rules, drivers report vehicle defects in a driver vehicle inspection report kept by the carrier, so your incident log does not replace theirs. It simply records the effect on your service.
Reading the Sheet While the Event Is Running
A log nobody reads during the day is just paperwork. The dispatcher should scan it every 20 to 30 minutes, looking for three patterns.
Headway drift
Headway is the gap between departures from the same stop. If you planned 10-minute headways and the actual departure times show gaps of 6, 14, 5 and 15 minutes, your buses are bunching. Usually one bus has fallen behind and the next one has caught up. The fix is to hold the early bus a few minutes at the stop to even out the gaps. Look at the actual depart column for one stop at a time to spot it.
Overloaded runs
Compare riders boarded against seated capacity. If runs are consistently full and the left-behind column is above zero, you need more capacity on that route, either more vehicles or larger ones. For a shuttle with lots of short trips and frequent stops, the shuttle bus rental options are built for fast loading, which may help more than adding another coach.
Rules of thumb for adding a vehicle
These are practical triggers many event teams use. Adjust them to your event and agree on them with the operator before the day.
| What the sheet shows | Likely cause | Action |
|---|---|---|
| Left behind on 3 runs in a row at one stop | Demand above capacity | Move a vehicle from a quieter route or call for a spare |
| Actual depart more than 10 min behind schedule on 2+ runs | Traffic or slow unloading at the other end | Check the arrival end; add a marshal there |
| Riders boarded under a quarter of capacity for an hour | Lull in demand | Stretch headways or rest a vehicle to save driver hours |
| Arrive times growing longer through the day | Road congestion building | Ask the operator about an alternate route |
If you are running a concert or festival, the peak is usually at the end, when everyone wants to leave at once. Our post on concert charter bus pickup planning covers that exit surge, and the same left-behind logic applies.
After the Event: Putting the Log to Work
Reconciling with the invoice
Charter and shuttle billing is usually based on hours, often counted from when the vehicle leaves the garage until it returns, with minimums per vehicle. The guide to how charter bus pricing works explains the common models. Your dispatch sheet will not show garage times, but it shows the first and last run for every unit. If the invoice bills a vehicle for 11 hours and your sheet shows it ran from 8:45 a.m. to 4:10 p.m., you have a specific question to ask: where did the other time come from? Often there is a fair answer, such as a long deadhead. Sometimes there is an error.
Overtime lines are where the incident log pays off. If incident #4 says the event director approved a 30-minute extension, the overtime charge is expected. If no such entry exists, ask about it. Our post on how overtime charges usually work explains what to look for.
Ridership totals for next year
Add the riders boarded column by route and by hour. Add the left-behind column the same way. Ridership plus left-behind is your best estimate of actual demand. In the example, if the North Lot moved 1,240 riders across the day and left 180 behind at various points, real demand on that route was over 1,400. That is the number to plan from next year, not 1,240.
| Summary line | How to calculate it | What it tells you |
|---|---|---|
| Total riders by route | Sum of riders boarded per route | Which routes carried the event |
| Peak hour riders | Sum of riders boarded per hour, highest hour | Fleet size needed at peak |
| Total left behind | Sum of left-behind column | Unmet demand |
| On-time rate | Runs departing within 5 min of schedule ÷ total runs | Schedule realism |
| Average run time by route | Average of actual arrive minus actual depart | Whether next year’s schedule needs more time |
If next year’s registration looks different, the post on changing your charter bus passenger count explains how to adjust a booking once you know your numbers.
Sharing it with the operator
Send the operator a copy within a few days. A good operator will compare it with their own GPS and driver logs, and the conversation that follows is often the best planning meeting you will have for next year. It also shows that you track performance, which tends to improve it.
Keep the operator’s side of the record in mind too. Ask whether their dispatch kept its own timeline for the day, and compare the two where they differ. A run you logged as 14 minutes late may show up in their records as a driver held by gate security, which changes the fix for next year from “add a bus” to “get a dedicated shuttle lane.” Before you book again, review the operator’s safety record and policies on our safety and trust page and check the carrier’s federal registration with the FMCSA SAFER lookup.
Adapting the Columns to Your Shuttle Type
The twelve columns above suit a park-and-ride or venue loop. Other shuttle patterns need one or two extra fields, and sometimes one fewer. Add what you will actually use; every extra column is something a busy marshal has to fill in.
| Shuttle type | Add this column | Why | Can drop |
|---|---|---|---|
| Hotel loop at a conference | Hotel stops served (in order) | One run may stop at three hotels; you need to see which ones were skipped | Left behind, if loads are light |
| Airport arrivals for a group | Flight numbers covered | Ties each run to the arrivals it waited for, which explains long holds | Scheduled arrive |
| Multi-day event | Date and shift | Lets you compare Thursday’s peak with Saturday’s | Nothing |
| Sports tournament between fields | Team or division | Shows which teams depend on the shuttle and when | Driver, if units never change |
| Festival exit surge | Line length at departure | A quick headcount of the queue helps set the next run’s timing | Scheduled depart, since runs leave when full |
For airport arrivals, the “hold” is the main source of delay, and flight data explains it. The guide to group airport transfers across different flights shows how to batch arrivals, and the flight column on your sheet records how well the batching worked. For tournaments, the sports tournament bus planning guide covers the field-to-hotel patterns that feed this log.
One more variation is worth mentioning: a “load-when-full” shuttle, common at the end of concerts and festivals, has no scheduled departure at all. Buses leave as soon as they fill. In that case, drop the scheduled times and keep a running log of actual departures. The gap between departures becomes your measure of how fast the line is clearing, and the line-length column tells you whether to bring more vehicles in from staging.
Paper, Spreadsheet or App?
Any of the three works. The right choice depends on how many stops you have and how reliable the signal is.
| Format | Works well when | Watch out for |
|---|---|---|
| Paper clipboard | One or two stops, poor cell signal, volunteers who are not comfortable with tech | Rain, lost sheets, manual totals afterward |
| Shared spreadsheet | Several stops, each marshal with a phone, a dispatcher who wants live totals | Two people editing the same row; set one tab per stop |
| Form or dispatch app | Large multi-day events, many vehicles, need for timestamps without typing | Setup time, logins, battery life; keep a paper backup |
Whatever you choose, print a blank paper copy for every curb. Phones die and signal drops at the exact moment a festival lets out.
Setting Up the Sheet Before Day One
The best dispatch sheets are mostly filled in before the event starts. The night before, pre-populate every scheduled row with run number, unit, driver, route and scheduled times. On the day, loggers fill only the actual times, counts and notes. To build the schedule rows, start from your shuttle schedule plan or from a charter bus itinerary template, then add one row per departure.
- Get the unit list and driver names from the operator.
- Fix the stop names and post them on signs at each stop.
- Pre-number all scheduled runs and reserve a block (500+) for added runs.
- Agree on the add-a-vehicle triggers with the operator and your event lead.
- Assign a logger per stop and a dispatcher, and run the call-in script once.
- Hand out tally counters, pens, and printed backups.
- Confirm the staging and layover spots so idle vehicles show up as “staged,” not “missing.” The hotel bus parking checklist helps when one of your stops is a hotel.
The same sheet works for recurring commuter runs. If you run a daily staff shuttle, our guide to employee shuttle route planning pairs well with a simplified version of this log.
Frequently Asked Questions
What is a shuttle dispatch sheet?
It is a live log of every vehicle run during an event. Each row records the vehicle, driver, route, scheduled and actual times, riders boarded and people left behind. It shows what actually happened, while a schedule shows what was planned.
How is a dispatch sheet different from a passenger manifest?
A manifest lists people who should ride a specific bus. A dispatch sheet lists vehicle runs over time and counts riders without names. Open shuttles where anyone with a badge or ticket can board usually rely on the dispatch sheet.
Who should fill in the dispatch sheet?
For one or two stops, a single dispatcher can keep it, with marshals calling in each departure. For three or more stops, give each curb marshal their own sheet and have them send key numbers to the dispatcher after each run.
Why track people left behind?
It shows unmet demand. Riders boarded tells you how many people you moved, but left behind tells you how many you could not. Several runs in a row with people left behind is a clear signal to add capacity on that route.
Can I use the dispatch sheet to check my invoice?
Yes. It shows the first and last run for each vehicle and records any approved extensions. Compare those with the billed hours and overtime lines, and ask about anything the log does not explain.
Start Logging From Run One
A dispatch sheet costs a few clipboards and an hour of setup. In return you get a running picture of your shuttle during the event and an honest record afterward. It is the difference between “the shuttles seemed busy” and “the North Lot left 180 people behind between 9:00 and 11:00.”
Planning an event shuttle? Ask us for the run schedule in dispatch-sheet format, so your team can log it from the first run. Request a quote through the BusXOXO booking form, or get in touch with our team at (308) 304-6668. You can also browse our concert and festival bus service, our corporate event transportation, or the full range of group transportation services.