How to Create an Event Transportation Brief for Your Bus Provider

A charter company can only run the event you describe to it. Most planners describe their event in pieces: a quote request with a date and a headcount, an email thread with a venue address, a phone call about parking, a text the night before with a changed pickup time. The dispatcher who builds the driver’s run sheet has to stitch those pieces together, and every gap gets filled with an assumption. That is how a coach ends up at the hotel’s front entrance when the group is waiting at the side door, or how a driver plans a 10:00 p.m. release when your gala runs until midnight.

An event transportation brief fixes this. It is a single document, usually two to five pages, that tells your bus provider everything needed to plan vehicles, drivers, timing and contingencies. It is not a contract and it is not a marketing deck. It is a working reference that your provider’s dispatch team, your on-site staff and the drivers can all read and act on.

This guide walks through the brief section by section. For each section you will see what to write, a sample line you can adapt, and why the operator needs it. At the end there is a copy-ready skeleton, a short list of the gaps operators see most often, and advice on sending the brief so it actually gets used.

Brief, Quote Request, Contract, Run Sheet: Which Document Does What?

Planners often assume the quote request covers it, or that the contract will spell out the details. Each document has a different job, and the brief sits in the middle of them.

If you have not yet signed anything, read our explainer on what a charter bus contract covers and how it differs from what is included in a charter bus quote. The brief comes after the quote and ideally before the contract is finalized, because the details in it can change the vehicle count or the billed hours.

When to Send the Brief

Timing matters more than polish. A rough brief that arrives early is more useful than a perfect one that lands two days out.

• Version 1 (with or right after the quote): Event type, dates, headcount ranges, all addresses you know, and the basic movement pattern. This lets the provider size the fleet correctly.
• Version 2 (three to four weeks out): Confirmed schedule, loading zones, contacts, accessibility needs, signage plan and any venue rules.
• Final version (five to seven days out): Final headcounts by run, named on-site contacts with mobile numbers, and the contingency plan.

For large or peak-season events, the first version should go out as soon as you know your dates. Our guide on how far in advance to book a charter bus explains why fleets tighten up quickly in spring and fall.

The Brief, Section by Section

The sections below are lettered so you can refer to them on calls (“see Section E for the loading zone”). Keep the same letters in every version so nobody has to hunt.

Section A: Event Snapshot

What to write: Four or five lines that a dispatcher can read in 20 seconds. Event name, type, dates, total attendees, the number of people who will ride, and the one-sentence movement pattern.

Sample: “Regional sales conference, Thursday to Saturday. 420 attendees, about 300 riders. Morning shuttles from three hotels to the convention center, one evening dinner transfer on Friday, airport departures Saturday.”

Why the operator needs it: The snapshot tells dispatch which kind of operation this is before they read the detail. A loop shuttle, a point-to-point transfer and an all-day disposal (bus stays with you) are staffed and billed differently.

Section B: Contacts and Decision Rights

What to write: A short table listing each person, their role, mobile number, and when they should be called. Name one person who can approve changes that cost money, such as extending hours or adding a vehicle.

Why the operator needs it: When a driver is stuck at a locked gate, they call dispatch, and dispatch needs to know exactly whom to call next. Without a named decision maker, drivers either wait (burning your hours) or leave (stranding people). Ask your provider for their own day-of contact in return; our article on whether charter companies provide driver information covers what to expect.

Section C: Addresses That a GPS Can Actually Use

What to write: For every location, give the street address, the specific entrance or door, and a pin or coordinates. Describe the curb in plain words.

Sample: “Hotel 2: 455 Main Street. Do NOT use the main porte cochère (height limit). Load on the Elm Street side, at the curb across from the parking garage exit. Pin: [link].”

Why the operator needs it: A street address puts a 45-foot coach on the right block, not at the right door. Hotels, campuses, stadiums and convention centers often have several entrances, and some cannot take a full-size bus at all. A full-size motorcoach is roughly 12 feet tall and needs room to turn; see our guides to charter bus height and charter bus width before you promise a driver they will fit under an awning.

Section D: Movement Schedule

What to write: A table, one row per movement. Include the start point, end point, the time riders should be at the curb, the time the bus must depart, the expected riders, and the type of service (single run, loop, or standby).

Why the operator needs it: Separating “riders at curb” from “bus departs” tells the provider how much loading time you expect, which affects how early drivers arrive. Our charter bus arrival timing guide explains typical buffers. Labeling each run (D1, D2) also gives everyone a shared shorthand for the day.

Section E: Loading, Staging and Parking

What to write: Where buses load, where they wait between runs, and where they park if they are on standby for several hours. Note any permits, gate codes, or fees, and who pays them.

Sample: “Convention center: load at Bay 4 on the north service road. Staging lot B holds up to six coaches; show the event parking pass on the dash. Overnight parking not available on site.”

Why the operator needs it: Buses cannot circle a downtown block for an hour. If there is no staging space, the provider may need to plan a deadhead (empty) trip to a lot further away, which changes timing and sometimes cost. Our guide to charter bus parking rules and the companion piece on who pays for parking fees help you answer these questions before the provider has to ask.

Section F: Riders and Their Needs

What to write: Who is riding (staff, VIPs, students, seniors, athletes, families), any riders who use a wheelchair or mobility device, luggage or equipment volumes, and any age-specific rules. Give numbers rather than names.

Sample: “Saturday airport run: 140 riders, about one checked bag and one carry-on each. Two riders use manual wheelchairs and one uses a power chair; a lift-equipped coach is required on the 10:00 a.m. departure.”

Why the operator needs it: Wheelchair lifts, luggage bays and child seating requirements affect which vehicle gets assigned. Lift-equipped coaches are often requested with notice, so put this in Version 1. Read what to expect from ADA-accessible charter buses and our luggage capacity guide to size these needs correctly.

Section G: Vehicle Requirements

What to write: What you need the vehicles to do, not just what you want them to look like. Seat count per run, restroom need for long legs, power outlets for working sessions, and whether any run needs a smaller vehicle because of a tight venue.

Why the operator needs it: A provider can often suggest a better mix than the one you requested, for example a mini bus for a hotel with a tight driveway, or a shuttle bus for short, frequent loops where riders hop on and off. If you are not sure what size you need, start with our charter bus sizing guide.

Section H: On-Site Communication and Signage

What to write: How riders will find the buses, how buses will be identified, and how your staff and drivers will talk to each other during the event.

• How each bus or route is labeled (for example “Route A, Bus 3”) and where placards go
• Whether drivers should expect a staff member at each stop
• The channel for live updates: phone calls, a group text, a radio, or a dispatch app
• Whether you want live vehicle locations shared with your team

Why the operator needs it: Drivers and your staff need the same vocabulary. If your app says “Blue Line” and the placard says “Bus 7,” riders get confused. Many operators can share live locations; see can I track my charter bus for what is typically available.

Section I: Rules, Restrictions and Expectations

What to write: Venue rules (no idling, quiet hours, security screening), event rules (badge required to board), and any on-board expectations such as food, alcohol, or decorations. If you plan anything unusual, ask rather than assume.

Why the operator needs it: Some requests conflict with carrier policy or local rules, and it is far better to learn that weeks ahead. Our posts on bringing alcohol on a charter bus and eating and drinking on board outline typical policies.

Section J: Contingencies

What to write: What should happen if the schedule slips, the weather turns, a rider is missing, or a vehicle breaks down. Keep it to short “if, then” statements.

• If the keynote runs more than 20 minutes late, buses hold at Bay 4; the transportation lead will text dispatch with a new release time.
• If heavy rain is forecast, move the Hotel 3 pickup inside the covered garage entrance (approved by hotel).
• If a rider is not at the curb at departure time, the bus leaves on schedule; the hotel coordinator directs late riders to the next loop.
• If a vehicle is delayed or out of service, dispatch calls the transportation lead first, then the backup.

Why the operator needs it: Drivers must also follow federal limits on driving and on-duty time, so a long, open-ended day may need a second driver or a relief vehicle. The FMCSA hours-of-service summary explains the passenger-carrier rules, and our article on how many hours a charter bus driver can drive puts them in plain language. For overtime expectations, see what happens if your trip runs late.

Attachments That Make the Brief Stronger

The brief is the narrative. Attachments carry the detail. Label each one with the section it supports.

• Annotated site maps for each venue, with the loading point circled and the bus approach route drawn in.
• Photos of each curb taken from the driver’s point of view. A phone photo of the side entrance prevents more wrong turns than a paragraph of directions.
• The guest-facing route map, so drivers know what riders have been told.
• Venue rules or parking permits as PDFs.
• Rider counts by run, updated in the final version.

Avoid attaching full attendee lists with names, phone numbers or room numbers. The provider needs counts and needs, not personal data. If a manifest is required (for example, for an airport or a school trip), share only the fields the driver will use, and send it separately.

A Copy-Ready Skeleton

Paste this into a document, keep the letters, and fill in the blanks. Delete any line that does not apply rather than leaving it empty, so the provider knows it was considered.

EVENT TRANSPORTATION BRIEF  |  Version __  |  Date sent: __

A. EVENT SNAPSHOT
Event name / type:
Dates:
Total attendees / expected riders:
Movement pattern in one sentence:

B. CONTACTS AND DECISION RIGHTS
Transportation lead (approves changes):
On-site coordinators by location:
Venue contacts:
Backup contact:

C. LOCATIONS
Location 1: address / entrance / curb description / pin
Location 2:
Height or turning limits:

D. MOVEMENT SCHEDULE
Run ID | Date | From | To | Riders at curb | Bus departs | Riders | Service type

E. LOADING, STAGING, PARKING
Loading points:
Staging between runs:
Long standby parking:
Permits / codes / fees and who pays:

F. RIDERS AND NEEDS
Rider groups:
Accessibility needs (counts, device types, which runs):
Luggage / equipment:

G. VEHICLE REQUIREMENTS
Seats per run / restroom / outlets / size limits:

H. COMMUNICATION AND SIGNAGE
Bus and route labels:
Staff at stops:
Live update channel:

I. RULES AND EXPECTATIONS
Venue rules:
On-board rules:

J. CONTINGENCIES
If late:
If weather:
If rider missing:
If vehicle issue:

ATTACHMENTS: list with section letters

How a Dispatcher Reads Your Brief

It helps to know what happens on the other side. When the brief arrives, a dispatcher or operations planner typically does four things with it.

1. Counts vehicles and drivers per time block. Using Section D, they work out the peak moment when the most buses are needed at once. That peak decides fleet size. If your morning loop and an airport run overlap, they may need more vehicles than the headcount suggests. Our article on when to rent more than one charter bus shows how this works.
2. Checks driver hours. They map each driver’s day from first report to final release, including travel to and from the garage, and check it against federal limits.
3. Checks the curbs. Using Sections C and E, they decide which vehicle types can safely access each stop.
4. Writes run sheets. Each driver gets a sheet built from your brief. If your brief is vague, the run sheet is vague.

Knowing this, you can see why “around 300 people, buses all day” is hard to plan against, while a run table with times and rider counts is easy.

The Gaps Operators See Most Often

These omissions come up again and again. Scan your draft for each one.

“All day” without a release time

Give a planned release time and a latest possible release time. The provider can then plan driver hours and quote overtime clearly.

One address for a building with five doors

Name the door. Add a photo. If your guests will gather at a different spot than the bus can stop, say so and explain how they get from one to the other.

Headcount without the ride rate

Five hundred attendees does not mean five hundred riders. Some drive, some walk, some leave early. Give your best estimate of actual riders per run and explain how you arrived at it.

Return trips treated as an afterthought

Outbound trips are usually tidy. Returns are not, because people leave at different times. State whether returns are one wave, several waves, or a loop, and when the last bus leaves.

No named person with authority

Drivers cannot approve their own overtime, and your hotel coordinator may not be allowed to approve spending. Name the decision maker.

Accessibility needs mentioned late

Lift-equipped vehicles may need to be specifically assigned. Mention needs in Version 1 and confirm them in the final version. Our guide to charter bus accessibility features lists what to ask about.

Sending the Brief So It Actually Gets Used

A brief only helps if the right people read it. A few habits make a difference.

• Send one file, not a thread. Put the version number and date in the file name, such as “Brief_v3_Oct12.pdf.” Replace, do not patch.
• Mark what changed. At the top of each new version, list changes since the previous one in two or three lines.
• Ask for a readback call. Ten minutes with the dispatcher, walking through Section D, will surface misunderstandings that email never will. Ask them to repeat back the release times and loading points in their own words.
• Ask for the run sheets. Request a copy of the driver run sheets once they are written and compare them against your brief.
• Share it with your own team. Your hotel coordinators and bus captains should work from the same document. If you are using captains, our planning team’s checklist for pre-departure checks pairs well with the brief.

Large event teams sometimes borrow vocabulary from emergency management, where a shared operating picture and plain, common terms keep many organizations coordinated. FEMA’s free Introduction to the Incident Command System (IS-100.C) course is a useful primer if you run events with several hundred moving people and multiple partners.

Verify the Provider While You Brief Them

The brief process is also a natural moment to confirm the provider is properly authorized. Interstate passenger carriers should have a USDOT number you can look up on the FMCSA SAFER system. Ask for proof of insurance naming the right parties if your venue requires it. Our charter bus safety checklist and the CharterBusesUSA safety commitment outline the checks we recommend.

Example: Briefing a Two-Day Festival Shuttle

To show how the sections fit together, here is a condensed illustration for a fictional two-day outdoor festival. The numbers are illustrative only.

• A. Snapshot: Two-day music festival, about 6,000 attendees per day, roughly 1,200 expected shuttle riders per day from two park-and-ride lots.
• B. Contacts: Transportation lead with authority to extend service; a lot supervisor at each park-and-ride; the festival’s gate operations contact.
• C. Locations: Lot North (shopping center rear lot, entrance off a side street), Lot South (high school, bus loop behind gym), festival drop-off at Gate 2 service road.
• D. Schedule: Inbound loops 11:00 a.m. to 4:00 p.m.; outbound loops 9:30 p.m. to 12:30 a.m.; reduced midday service.
• E. Staging: Buses stage in the festival’s gravel lot between waves; driver rest area with restrooms.
• F. Riders: General public, some families with strollers, accessible boarding needed at both lots.
• G. Vehicles: Full-size coaches for capacity, plus one lift-equipped vehicle on each loop.
• H. Communication: Routes named “North” and “South,” color-coded placards, lot supervisors on a group text with dispatch.
• I. Rules: No glass, no open containers on board, festival wristband shown at boarding.
• J. Contingencies: Lightning hold procedure, last-bus announcement plan, lost-rider meeting point at each lot.

For more on large public events, see our music festival group travel guide and the concert and festival transportation service page. If your event is a conference, our convention transportation planning guide covers multi-hotel loops in depth.

Frequently Asked Questions

How long should an event transportation brief be?

Long enough to answer the questions a dispatcher would otherwise have to ask. For a single round trip, one page may do. For a multi-day, multi-hotel event, three to five pages plus maps is common. Use tables for schedules so the length stays manageable.

Do small groups need a brief?

A small group with one pickup and one drop-off can usually rely on a clear booking confirmation. Once you add a second stop, a waiting period, or a return time that might move, a short brief is worth the 20 minutes it takes. Our post on whether a charter bus can make multiple stops explains why extra stops need extra detail.

Should the brief include the attendee list?

Usually no. Share counts and needs. Share names only when there is a specific reason, such as an airport transfer manifest, and limit the fields to what the driver needs.

What if details change after I send the final version?

Issue a new version with the change listed at the top, then call dispatch to confirm they received it. For same-day changes, call first and follow with a written note. Our guide on changing a charter bus reservation covers what is usually possible.

Will my provider charge more because of the brief?

The brief does not add cost; it reveals cost that already exists. If it shows that you need an extra vehicle or longer hours, you learn that before the event rather than on the invoice.

Bring Your Brief to Us

If you already have a draft brief, send it with your quote request and our team will plan the vehicles and timing around it. If you are starting from scratch, tell us the basics and we will help you fill in the sections. Explore our group transportation services or request a free quote to get started.