For an event in Miami, the most useful transport document is a short run sheet: who travels together, where they meet, when they must arrive and how they return. A vehicle name and an event start time are not enough when guests stay at different hotels, use different entrances or leave at different times.
This guide helps an organiser prepare a request for event car service. It covers private guest movements, not a promise of a large shuttle fleet or venue access. Vehicle availability, the operating plan and the full quote need confirmation for the actual date.
Work backward from the arrival requirement
Use the time guests need to be at the correct entrance, not merely the advertised start time. Registration, walking from a drop-off area and finding the right entrance belong in the plan. Ask the venue or organiser about its current passenger drop-off and pickup arrangements; do not assume the front door will be accessible to vehicles.
Then tell the transport team the starting address and fixed arrival requirement. Let the route and realistic timing be reviewed before promising guests an exact hotel departure. Traffic and event access can vary. A map estimate is a planning input, not a guaranteed journey time.
Group travellers by their actual journey
Put guests together when they share a pickup location, arrival requirement and return plan. A convenient outward grouping may be a poor return grouping if some guests leave after dinner and others stay until the end. Ask about capacity with luggage or equipment included rather than dividing people by the largest advertised seat count.
Use a single coordinating contact for each group. Give the booking team the practical information it needs, while keeping private guest details out of broadly shared spreadsheets. A group label such as “Hotel A, morning arrivals” is often enough for a planning draft; the final booking can collect the necessary individual contact details directly.
Build this run sheet
| Field | What to record |
|---|---|
| Movement | Outward ride, intermediate stop or return |
| Group | Number of travellers and a coordinating contact |
| Pickup | Exact property, entrance and meeting instructions |
| Arrival deadline | The time required at the correct venue entrance |
| Bags and equipment | Cases, presentation materials or items needing space |
| Return | Expected release time and a separate meeting point |
| Contingency | Who approves changes and how updates are shared |
Keep one current version with the date and time of the latest update. If a guest changes hotels, update the outward and return rows together. A beautifully formatted itinerary is less useful than a plain table with one reliable source of truth.
Decide whether the vehicle should wait
A short programme with several stops may suit an hourly chauffeur. An event with a long gap between arrival and departure may be worth pricing as separate journeys. Ask the team to compare the same plan both ways, including any minimum, waiting, parking, tolls and extra-time arrangements.
Read the transfer-versus-hourly comparison before choosing. Do not assume an hourly reservation grants unlimited changes or that a separately booked return can be moved to any time without agreement. The question is how much continuity your programme actually needs.
For example, a fictional business evening might involve two hotel pickups, a venue arrival and two return groups. The useful planning step is to split that into four defined movements. The number of vehicles, sequence and timing should then be confirmed by the team; this is not an advertised event package or fleet-capacity claim.
Give the return its own instructions
The arrival drop-off and return meeting point may differ. Confirm both. If the venue restricts access after the event, distribute the updated pickup instructions through the group coordinators. Guests should know whom to contact if they leave early, cannot find the meeting point or need to change the plan.
Do not ask every guest to send the driver separate instructions. Name one person who can approve a changed stop, extended service or revised departure, and clarify how any additional charges are handled. This protects the schedule from several well-meant but incompatible requests.
Join airport arrivals to the event plan carefully
If guests arrive by air, use a separate row for each flight group. Include the local arrival date, bags and the destination before the event. The airport pickup checklist helps avoid confusing landing time with terminal readiness. Leave room for delayed flights rather than making the entire programme depend on an optimistic transfer.
For a corporate trip, tell the team which meetings are fixed and which stops can move. For a dinner or private celebration, include the restaurant or venue entrance and expected finish. Do not attach an outdated event schedule without noting what still needs confirmation.
Final organiser check
- Each movement has a pickup, destination and timing requirement.
- Passenger and luggage counts are confirmed together.
- Venue entrances and return meeting points are checked.
- One coordinator can approve changes for each group.
- The quote explains waiting, additional time and payment terms.
- Guests receive the final instructions, not an early planning draft.
Send the run sheet with your event transport enquiry. Treat the response as a proposal until the booking is confirmed. Clear instructions improve the service plan; they do not remove traffic, venue rules or the need to confirm availability.
Common questions
Can different hotel pickups share one booking?
Describe every stop and group so the team can assess timing, vehicle fit and pricing. Do not assume extra pickups are included automatically.
What if the event finishes late?
Ask about that scenario before booking and name a person who can communicate changes. Availability and additional charges depend on the agreed arrangement.
Does an event quote include continuous waiting?
Only if the proposal says so. Confirm whether you are booking separate journeys or a continuous service window.