Direct answer: For group cross-border transfers, create a manifest by arrival flight, destination and required departure time, then check each vehicle against both passengers and luggage. Give every group a contact, meeting point and version-controlled itinerary. Name one person to approve changes. Do not assign cars by seat count alone or assume a delayed flight can be absorbed without changing the other groups.
01
Quick answer
02
Key takeaways
- Build the sheet by flight + destination + deadline, then validate pax + bags per car
- One change approver; one version number on every PDF/sheet
- Blank table below for copy/use; worked example is fictional
- Related: Business · Multi-city roadshow · Airport pickup · Alphard capacity
> Scope: Operations planning method for multi-car cross-border chauffeur moves. Not a promise of fixed cost savings percentages or automatic flight redispatch across the whole fleet.
03
Blank multi-car manifest
Swipe to see the full table →
| Group ID | Arrival flight | ETA | Pax | Large bags | Child seats | Destination pin | Meet point | Vehicle ID | Driver contact | Latest leave-by | Change approver | Notes | Sheet ver. |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| G1 | v1 | ||||||||||||
| G2 | v1 | ||||||||||||
| G3 | v1 | ||||||||||||
| Spare | — | — | — | — | — | — | — | buffer car? | v1 |
Print or share as CSV; bump Sheet ver. on every edit.
04
Grouping rules
Swipe to see the full table →
| Rule | Prefer | Avoid |
|---|---|---|
| Same flight + same hotel | One or more cars as load requires | Mixing unrelated deadlines in one car |
| Same flight + different hotels | Split by destination | Endless hotel-hop without written stops |
| Different flights close together | Separate cars or staged departures | Assuming delay on flight A can wait inside flight B’s car |
| Seat count only | — | Ignoring luggage / instruments / posters |
05
Fictional example (not a real order)
Swipe to see the full table →
| Group ID | Arrival flight | Pax | Large bags | Destination | Vehicles | Notes |
|---|---|---|---|---|---|---|
| G1 | CX123 | 4 | 4 | SZ Hotel A | V1 Alphard | Families—child seat ×1 |
| G2 | CX123 | 3 | 6 | SZ Hotel A | V2 Alphard | Oversized bags—do not merge into V1 |
| G3 | KA456 | 6 | 3 | Campus gate B | V3 + V4 | Split for arrival window |
| Spare | — | — | — | — | V5 on standby | Only if written |
This table is a fictional planning illustration for teaching the sheet—not historical bookings and not a savings claim.
06
Version control and delay handling
Swipe to see the full table →
| Event | Action |
|---|---|
| Passenger name change | Edit manifest; new version; tell affected drivers |
| Flight delay | Approver decides: hold, reassign spare, or retimetable other groups |
| Luggage surprise | Re-check capacity; may need extra vehicle—see capacity guide |
| Leader wants to merge groups | Re-run pax+bags math before saying yes |
07
Cost posture (no fake %)
Swipe to see the full table →
| Approach | How to compare |
|---|---|
| Several one-ways | Sum written per-vehicle quotes |
| Day hire for a sub-team | Compare package hours vs stop list—day hire |
| “We will save 30%” marketing | Do not use—compare real quotes only |
SZ core published bands often start from RMB 700 / ~HKD 810 per vehicle; groups multiply by cars, not by inventing per-seat tariffs.
Useful next steps
Compare all published transfer pricesBrowse all cross-border travel guides