Map the fixed moves before shopping for vehicles.
| Move | Inputs | Plan output |
|---|---|---|
| Airport arrivals | Flight windows, passenger count, luggage, check-in time | Named arrival groups and the exact home-base address |
| Saturday anchor | Meeting point, check-in deadline, group capacity, weather contact | Outbound and return vehicles with a buffer determined by the provider's instructions |
| Main night | Dinner location, destination, group-split expectation, return window | A clear pickup point, lead contact, and individual safe-return fallback |
Choose the movement model by consequence.
| Model | Best use | Main tradeoff | Verify |
|---|---|---|---|
| Separate arrival rides | Flights landing in different windows | More coordination and variable arrival order | Exact address, traveler group, luggage, and contact |
| Reserved private transfer | A fixed group movement with a known passenger count | Less flexible if flights or headcount change | Vehicle capacity, luggage, wait policy, pickup instructions, cancellation |
| Operator transport | An activity that includes or offers pickup | The provider controls route and timing | Pickup area, included passengers, departure deadline, return point |
| Split ordinary rides | Short city moves for smaller subgroups | The group can arrive apart and surge availability can vary | Named riders, shared destination, and regrouping point |
Create a two-line manifest for every fixed move.
- Line one: passenger names, luggage note, pickup address, destination, reservation time.
- Line two: driver or provider contact, group lead, cancellation or wait rule, backup action.
- Share map pins and written addresses; do not rely on a venue nickname.
- If the group splits, name the time and place where it becomes one group again.
- Never make an intoxicated traveler responsible for solving the return plan.