Create a Dispatch-Ready Group Manifest
A group manifest is an operating record that connects each traveler to an arrival, vehicle, destination, day-of contact and departure obligation. It should help the coordinator answer who is moving, where that person meets the vehicle, who travels with them and who can approve a change.
Use one authorized owner to maintain the latest version. A spreadsheet or roster that is not reconciled with the confirmed service plan can send dispatch and passengers to different places.
Organize Airport, Hotel and Event Groups by Movement
A group may arrive through IAD, DCA, BWI or an FBO and continue to several hotels, offices or conference venues. Build the manifest around actual movements rather than one master passenger count: airport waves, hotel transfers, event shuttles and return departures can each require different vehicles.
Record the full pickup and destination for each movement. A city, organization or hotel name without the passenger entrance is not a dispatch-ready address.
Airport and Private-Aviation Coordination
Commercial airport reservations should include the operating airline and flight number, passenger mobile, baggage, meeting method and onward destination. Airport arrivals include a 30-minute grace period, except at FBOs. Flight monitoring supports dispatch, but cancellations, diversions, rebookings and changed flight numbers must be reported directly. Meet-and-greet is available only when requested and confirmed.
Private-aviation and FBO service is planned separately. Provide the airport, current FBO, aircraft reference, tail number when appropriate, lead passenger, handling or release contact, luggage and authorized meeting point. FBO waiting terms are confirmed separately; no grace period applies to FBO pickups.
Sedan, SUV, Sprinter, Minibus or Motorcoach
Use flight waves and final destinations to assign the fleet: separate sedans for principals with different schedules, SUVs for small parties with luggage, and Sprinters or buses for groups boarding together. Confirm each assignment against its manifest, load and receiving location.
Build vehicle assignments from the manifest, arrival waves and final destinations rather than the headline passenger total. Count checked bags, carry-ons, mobility items and any equipment for every cohort. Reservations must confirm actual seats and usable luggage space for the assigned model; split groups when baggage, timing or separate handoffs make one full vehicle impractical.
Name Manifest Owner and Change Authority
The executive assistant, association planner, embassy coordinator or corporate travel lead should identify who maintains the roster and who may approve changes. The lead passenger for each vehicle is not automatically authorized to change another group’s schedule.
Share only the contact and travel information needed to execute the assignment. Limit access to passenger data and avoid placing confidential meeting, security or medical details in the manifest.
Version Each Day and Movement Separately
A multi-day program needs a dated manifest for each service day, and a large event may need separate arrival and departure views. When a flight, hotel, passenger or vehicle changes, update the affected movement, mark the previous version superseded and tell the authorized contacts which version is current.
Include a contingency contact for flight disruption, late passengers or a changed meeting point. A manifest does not guarantee a flight connection or replace the written booking confirmation.
Minimum Fields for a Useful Manifest
For each movement, include passenger name, mobile, operating flight if applicable, pickup and destination, vehicle assignment, luggage or equipment, required arrival, meeting method and authorized change contact. Add date, time zone, hotel, event role and accessibility needs where relevant.
List passengers who share a vehicle together and note who travels separately. Provide the final roster in a readable format and confirm the service itinerary in writing.
One Roster, Two Dispatch Views
Keep one master traveler record, then organize an arrival view by operating flight, landing window, passenger contact and first destination. Build the departure view by hotel, required airport arrival, operating flight and vehicle assignment. These views answer different dispatch questions and should not be collapsed into a single unsorted list.
Mark passengers who share luggage, a vehicle or a hotel room only where that affects transportation. Identify late arrivals and travelers whose departure does not match the main group.
How to Reconcile a Manifest Before Dispatch
Before sending the roster, compare passenger names and flight details against the latest booking confirmations. Resolve duplicate names, missing mobiles, changed flights and passengers who are no longer traveling. Mark the version date and time so dispatch can identify the authoritative copy.
If a traveler is added after the vehicle plan is set, confirm seats, luggage and destination before placing that person on a manifest. A roster update alone does not change the accepted service.
Reconcile Roster Changes With Confirmed Service
A manifest should show passenger name, mobile, assigned vehicle, pickup point, destination, luggage and the person authorized to approve changes. Version it when a flight, group assignment or stop changes, then notify dispatch and the day-of coordinator.
The written service confirmation controls vehicle and timing. If the roster calls for more passengers, luggage or stops than the confirmed plan, request a revised confirmation before travel.
Frequently Asked Questions
Does DC Black Cars provide executive group arrival & departure manifest?
Yes. Coordinators can submit a group manifest for review, including names, operating flights, baggage, destinations, mobility needs, and a day-of contact. Divide passengers by actual arrival time and vehicle capacity; a manifest supports planning but does not itself confirm service or access.
Can this service connect with IAD, DCA, BWI, RIC or a private-aviation facility?
Yes, when the requested route and equipment are confirmed. Provide the operating flight or aircraft reference, passenger contact, baggage, meeting method, destination, and required arrival. Airport arrivals include a 30-minute grace period, except at FBOs; private-aviation and FBO waiting terms are confirmed separately.
Which vehicle class should we request?
For a group movement, divide the manifest by pickup wave and identify luggage or equipment traveling with each group. Seat count is only one constraint: a single larger vehicle may not solve staggered arrivals, separate destinations or limited loading access. Confirm the configuration for each leg.
Can one reservation include several stops or vehicles?
Yes. Multi-stop, retained, and multi-vehicle service may be requested. Supply one controlled itinerary, manifest, authorized change contact, stop sequence, required arrivals, waiting expectations, and return plan.
Are rates published on this guide?
No. Pricing is confirmed privately after the exact itinerary, vehicle, timing, stops, waiting, parking, tolls, overnight needs, and operating requirements are reviewed.