Event Transportation Radio and Contact Plans: Who Needs to Reach Whom?
When an event shuttle goes wrong, it is rarely because the bus broke down. It is usually because the right person did not hear about a problem in time. The curb captain knew the line was 80 people long, but the dispatcher thought it was 20. The driver was stuck at a locked gate, but the person with the key was on a different radio channel. The VIP was ready early, but nobody told the car.
An event transportation communication plan fixes this by deciding, before the event, who needs to reach whom, by what method, and what they should say. This guide shows how to build one: a role list, a contact matrix, a radio channel plan, simple call language, an escalation ladder and a one-page contact sheet. It applies to conferences, weddings, festivals, sports events and any event with more than one vehicle on the road.
Start With Roles, Not Devices
Many planners begin by renting radios. That is backward. First list every role involved in moving people. Then decide how each role should communicate. A typical event transportation team includes:
- Transportation lead: owns the plan, makes decisions about changes, talks to the operator.
- Operator dispatch: the bus company’s control desk, which talks to drivers.
- Drivers: operate the vehicles and follow dispatch instructions.
- Curb or stop captains: manage the line and loading at each stop.
- Venue contacts: security, facilities or loading dock managers who control gates and curbs.
- Event producer or show caller: knows when sessions, speeches or performances will end.
- Hotel contacts: front desk or bell captain at pickup hotels.
- VIP or talent handlers: escort specific people to specific vehicles.
- Medical and security leads: handle incidents.
Smaller events may combine roles. A wedding planner might be the transportation lead and the stop captain. If you are new to working with a bus company, our guide on renting a charter bus for the first time explains how booking and dispatch usually fit together. That is fine, as long as you know which hat is being worn and who covers when that person is busy.
The Contact Matrix: Who Needs to Reach Whom
The heart of the plan is a matrix. Down the side, list who is calling. Across the top, list who they need to reach. In each cell, write the method. Leave a cell blank if those two roles should not talk directly.
| Caller ↓ / Needs to reach → | Transportation lead | Operator dispatch | Drivers | Stop captains | Venue contacts |
|---|---|---|---|---|---|
| Transportation lead | – | Phone | Through dispatch only | Radio (transport channel) | Radio (venue channel) or phone |
| Operator dispatch | Phone | – | Operator’s own system | Through lead | Through lead |
| Drivers | Through dispatch | Operator’s own system (hands-free) | – | Face to face at the stop | Face to face at gate |
| Stop captains | Radio | Phone, for urgent safety issues only | Face to face at the stop | Radio | Through lead |
| Venue contacts | Radio or phone | Through lead | Face to face | Through lead | – |
Two rules stand out when you build this matrix:
- Drivers are reached through dispatch. A driver who is moving should not be taking calls or reading texts from event staff.
- Only one person changes the plan. Stop captains report. The transportation lead decides. Dispatch carries out. If five people can call the bus company with new instructions, the bus company will get five different instructions.
Why Drivers Should Not Be on Your Group Chat
It is tempting to add drivers to a group text so everyone is “in the loop.” Resist it. Federal rules from the Federal Motor Carrier Safety Administration prohibit commercial drivers from texting and from holding a mobile phone while driving. The FMCSA’s distracted driving page summarizes those restrictions. Good operators already have hands-free systems and procedures for dispatch to reach drivers safely.
So your plan should route instructions through operator dispatch, and drivers should receive changes at a stop or through the operator’s approved system. If you need to give a driver a direct number, make it clear it is for use when parked. Our article on whether charter bus companies provide driver information explains what operators usually share.
Pick the Right Tool for Each Link
No single device does everything. Most event transportation plans use a mix.
| Tool | Good for | Weak spots |
|---|---|---|
| Two-way radios | Instant, one-to-many updates on site; no dialing | Range limits, dead spots in buildings, needs channel discipline |
| Mobile phone calls | Detailed one-to-one conversations, reaching off-site people | Slow for group updates, busy signals, poor coverage in crowds |
| Group text or chat app | Non-urgent updates, written records, photos of problems | Easy to miss; messages pile up; not for drivers in motion |
| Operator dispatch system | Reaching drivers safely, tracking vehicles | Run by the operator, not by you |
| Vehicle GPS tracking | Seeing where buses are without asking | Not every operator offers event-staff access |
| Printed contact sheet | Backup when phones die or apps fail | Must be kept current |
Cell networks can slow down or fail when thousands of people gather in one place, such as at a stadium or festival. That is a big reason many events keep radios even when everyone has a smartphone. If you can see the buses on a map, you save a lot of radio traffic; see can I track my charter bus.
A Note on Radio Licensing
Not all radios are equal under U.S. rules. The Federal Communications Commission explains that Family Radio Service (FRS) radios are licensed by rule, so individual users do not need a license if they follow the rules. General Mobile Radio Service (GMRS) requires an FCC license. Many professional event radios operate on business frequencies that have their own licensing.
The practical takeaway: if you rent radios from an event radio company, ask them what licensing applies and whether they handle it. If you buy consumer radios, check the FCC rules for that radio type. Your venue may also have rules about which channels you can use so you do not interfere with venue security.
Build a Channel Plan
On larger events, put transportation on its own radio channel. A single shared channel quickly turns into noise, and shuttle updates get lost between “need a mop in Hall B” and “who has the green room key?”
A sample channel plan for a mid-size event:
| Channel | Name | Who is on it | Used for |
|---|---|---|---|
| 1 | Command | Event director, department leads, transportation lead | Decisions that affect the whole event |
| 2 | Transport | Transportation lead, stop captains, VIP handlers | Shuttle status, line lengths, departures |
| 3 | Venue ops | Facilities, security, loading dock | Gates, curbs, access |
| 4 | Medical and safety | Medical, security lead | Incidents only |
| 5 | Spare | Anyone, when told to switch | Long conversations that would clog the main channel |
The transportation lead carries a radio that can monitor both Transport and Command, or carries two radios. Stop captains stay on Transport. When a long back-and-forth is needed, both parties switch to the spare channel and come back when done.
Hotel stops deserve special attention, since the bell desk and front desk often have their own radios; our hotel shuttle bus rental team coordinates with hotel staff regularly. For a wedding or a small corporate outing, this is overkill. Two or three radios on one channel plus a phone list is enough.
Use Simple Call Signs and Plain Language
Radio traffic works best when everyone uses the same names for people and places. Assign call signs by role and location, not by person:
- “Transport Lead”
- “Hotel North” (the stop captain at the north hotel)
- “Hotel South”
- “Main Gate” (the stop captain at the venue)
- “VIP 1” (the handler for a specific VIP group)
Role-based call signs mean the plan still works when the person on that post changes at lunch.
Use plain language. Codes from TV dramas cause confusion when half the team has never heard them. A good message has three parts: who you are calling, who you are, and the information.
"Transport Lead, this is Hotel North. Line is about 60 people. Bus 3 just left full. Next bus not in sight." "Hotel North, Transport Lead. Copy. Checking with dispatch. Will update in 5."
If you want a deeper grounding in how large events structure communication and command, FEMA’s free Introduction to the Incident Command System (IS-100.C) course explains the shared terms many venues and public safety agencies use.
Agree on What Gets Reported
Too little information leaves the lead guessing. Too much clogs the channel. Agree on a short list of reports each stop captain makes without being asked:
- When a vehicle departs, with an approximate count.
- When a line passes a set size (for example, more than one busload waiting).
- When no vehicle has arrived within the expected window.
- Any safety concern at the curb.
- Any rider who needs special help (mobility, medical, lost child).
Then agree on what the transportation lead reports back: schedule changes, added vehicles, delays and the last-departure call.
Write an Escalation Ladder
Not every problem needs the event director. Not every problem can wait for the transportation lead to get around to it. An escalation ladder makes the routing clear.
| Level | Example | Who handles it | Who is told |
|---|---|---|---|
| 1. Routine | Bus 5 minutes late, line normal | Stop captain | Transport Lead, if it continues |
| 2. Service problem | Bus 15 or more minutes late, line growing | Transport Lead with dispatch | Affected stop captains |
| 3. Program impact | Shuttle delay will hold a keynote or ceremony | Transport Lead and show caller | Event director |
| 4. Safety or medical | Rider injured, vehicle incident, crowd surge | Medical or security lead, 911 if needed | Transport Lead, event director, operator dispatch |
Write the ladder on the back of every stop captain’s contact sheet. Under stress, people follow what is in front of them. For more about how operators handle incidents, see charter bus emergency procedures.
Connect Transportation to the Show
One link that planners often miss is the one between transportation and whoever runs the program. If a session runs long, the buses need to know. If the buses are late, the show needs to know. Put the transportation lead on the Command channel, or give the show caller a direct line to the lead. A simple message like “General session running 15 minutes over” lets the lead tell dispatch to hold buses instead of sending them to a curb with no riders.
This link is especially important for events with shuttles between two venues, where the program at the second venue depends on when buses arrive. The companion guide on coordinating shuttle transportation between two event venues covers how to set up a dispatcher and receiver at each end.
Plan for Dead Spots, Batteries and Noise
- Dead spots: Walk the site with a radio during your site visit. Concrete parking garages, basements and loading docks often block signals. Note where coverage drops and plan a phone backup for those spots.
- Batteries: Radios and phones die on long days. Plan a charging station and spare batteries. Assign someone to swap them at a set time.
- Noise: Curbs next to busy roads and stages are loud. Earpieces help stop captains hear and keep radio chatter from bothering guests.
- Weather: Rain and heat are hard on electronics. Pack plastic covers.
- Distribution: Sign radios out and in, with a name next to each number. Lost radios are expensive.
The One-Page Contact Sheet
Every stop captain, VIP handler and venue contact should carry the same one-page sheet, printed. Here is a template to copy:
EVENT TRANSPORTATION CONTACT SHEET [Event name] [Date] Version [#], updated [time] DECISION MAKER Transport Lead: [Name] Mobile: [ ] Radio: Ch 2, "Transport Lead" Backup Lead: [Name] Mobile: [ ] OPERATOR Dispatch (24 hr): [Number] Account manager: [Name, mobile] (non-urgent) STOPS Hotel North: [Captain name] Mobile: [ ] Radio: Ch 2 Hotel South: [Captain name] Mobile: [ ] Radio: Ch 2 Main Gate: [Captain name] Mobile: [ ] Radio: Ch 2 VENUE Security desk: [Number] Radio: Ch 3 Loading dock: [Name, number] Gate key holder: [Name, number] SAFETY Emergency: 911 On-site medical: [Location, radio Ch 4] RADIO CHANNELS 1 Command 2 Transport 3 Venue ops 4 Medical 5 Spare RULES Captains report, Transport Lead decides, dispatch tells drivers. Do not call or text drivers while they are moving.
Add a version number and time. If the plan changes on the day, reprint and replace. Old sheets with wrong numbers are worse than no sheet. On multi-vehicle events, add each bus number and its route to the sheet; the printable charter bus booking checklist is a handy companion when you collect those details from the operator.
Run a Radio Check Before Doors Open
About 30 to 60 minutes before the first shuttle, do a quick check:
- Transportation lead calls each stop by call sign.
- Each stop responds and confirms they are in position.
- The lead confirms the operator dispatch number works by calling it.
- The lead confirms the first vehicle is on the way.
This takes five minutes and catches dead batteries, wrong channels and missing people before guests show up.
Keep a Simple Log
Ask the transportation lead (or an assistant) to note key events with times: departures, delays, added vehicles, incidents. A notebook works. This log helps with any billing questions afterward, such as overtime or extra trips, and gives you real data for next year’s plan. It also helps if you need to report an incident. The article what happens if my trip runs late explains why written records of delays matter.
Do Not Forget the Riders
The contact matrix so far covers staff. Riders need a way to reach someone too, and their needs are simpler: “Where is the bus?” and “I missed it, what now?”
Give riders one number. It should be answered by a person who has the contact sheet and can reach the transportation lead, such as a registration desk, a hotel hospitality desk or a planner’s assistant. Print it on the shuttle schedule, the event app, name badges or the back of the wedding program. Do not publish the operator’s dispatch line or drivers’ numbers to guests. Dispatch needs to stay free for real operational calls.
Then decide how you will push updates out to riders. Options include an event app notification, a text blast to registered riders, a message in the wedding group chat, or an announcement from the stage. Pick one main channel and say in advance that updates will come through it. A sentence like “If shuttle times change, we will text you from this number” saves a lot of calls on the day.
Riders who are not where they should be, and riders who were never on the list, are a frequent reason for those calls. The companion guide on handling event shuttle no-shows and unexpected riders suggests scripts that stop captains can use.
One Problem, Traced Through the Chain
To see how the pieces work together, follow one fictional problem from start to finish at a conference with three hotel stops.
7:42 AM. The stop captain at Hotel South sees the line has grown to about 70 people and the expected bus has not appeared. Following the reporting rules, she radios on the Transport channel: “Transport Lead, Hotel South. Line about 70. No bus for 12 minutes.”
7:43 AM. The transportation lead checks the GPS map and sees one bus stopped in traffic two blocks away and another just leaving the convention center. She calls operator dispatch by phone (not the driver) and asks for an estimated arrival and whether the second bus can skip Hotel North, which has a short line.
7:45 AM. Dispatch confirms: the first bus will arrive in about four minutes, and the second will go straight to Hotel South. Dispatch tells the driver through its own hands-free system.
7:46 AM. The lead radios Hotel South and Hotel North with the change. Hotel North’s captain tells his short line that the next bus will be a few minutes later than usual.
7:50 AM. Because the opening keynote starts at 8:30 AM, the lead also updates the show caller on the Command channel: “Shuttles slightly behind; expect most attendees seated by 8:25.” No hold is needed. That is a Level 2 problem handled without reaching Level 3.
8:10 AM. The lines are back to normal. The lead writes three lines in the log.
Notice what did not happen. No one called a driver. No stop captain called the bus company on their own. The event director was never pulled away from the opening. Everyone knew who to tell, and one person made the decision.
How the Plan Changes by Event Type
Weddings
Keep it simple: the planner or a designated family member is the lead, with the operator dispatch number and the venue coordinator on speed dial. Guests should have one number to call if they miss a shuttle, and it should not be the bride or groom. Our wedding transportation team can help.
Conferences and conventions
Multiple hotels mean multiple stop captains. Radios plus a group chat are common. The transportation lead often sits at a desk with a view of the GPS tracking. See our convention shuttle page.
Festivals and stadium events
Cell networks get crowded. Radios are essential. Coordination with police and traffic control is common, especially in large metros such as New York City, Buffalo, Houston and Fort Worth. The concert and festival transportation service covers these events.
Corporate offsites and executive travel
VIP handlers need a direct link to their vehicle’s dispatch. Privacy matters, so itineraries should be shared only with those who need them. The corporate charter bus rental page covers how we support company events. Look at our executive coach options for leadership groups.
Early setup and late breakdown crews
Crew moves happen when most of the event team is off duty. Make sure someone with authority is reachable at 4:00 AM and 1:00 AM, and that the operator knows who it is. Driver changes are common on long days, so confirm how the handover is communicated; see do charter bus drivers stay with the group. The companion guide on event staff shuttle transportation for early setup and late breakdown covers that schedule.
Government and military groups
Communication protocols may be set by the agency. Follow them and share the contact matrix with the operator. See government and military charter.
Quick Answers
Do small events need radios? Not always. An event with one or two vehicles and a short route can work with phones and a clear contact sheet. Radios become worthwhile when you have several stops, a large site or poor cell coverage.
Should I give guests the driver’s number? No. Give guests one event number, staffed by a person, who can then work with dispatch.
Who should call the bus company if something changes? One person: the transportation lead, or a named backup. Everyone else reports to them.
What if the operator’s dispatch does not answer? Ask before the event for a backup number and the name of the manager on duty. Put both on the contact sheet. You can also ask your operator about their safety and communication standards during booking.
How early should the contact plan be finished? At least a week before the event, so the operator, venues and staff can review it. Reconfirm the dispatch number the day before.
Build Your Plan With the Operator
The best communication plans are built together with the bus company, because their dispatch is a key link in the chain. When you book, ask how dispatch works on event days, who answers, and how they prefer to receive changes. Our questions to ask before booking list includes several on this. When you are ready, request a quote or contact us to talk through your event’s communication setup.
