Two cars at one address do not necessarily share one journey. A household may need one car taken home while another goes elsewhere. A business may need two company cars delivered to different recipients. When considering drivers for vehicles you provide in Auckland, plan each car as its own request, then identify where the two plans depend on each other.
Drivers on Demand (DOD) is preparing a marketplace connecting customers and businesses with verified independent drivers who drive customer-provided eligible vehicles. Personal and business services are planned for 2 November 2026, subject to product alignment and readiness. Bookings are not open. This guide does not confirm a group-booking feature, simultaneous driver availability or coordinated arrivals.
Vehicle and journey
Passengers and key holder
Recipient and preferred time
Vehicle and journey
Passengers and key holder
Recipient and preferred time
Give each car a complete journey brief
Start with a separate line for each vehicle: registration, make and model, exact pickup, destination, intended time and who will travel. Use the registration rather than “the blue car” when two similar vehicles are parked together.
DOD’s customer page asks customers to provide vehicle and journey information. Its current Journal also explains that another trip during an active journey must use a different eligible vehicle; the same vehicle cannot have overlapping active bookings. That distinction does not mean two cars are automatically approved or matched together.
Check authority to provide each car and the applicable insurance permission separately. Do not assume that an answer about one vehicle also covers another. This guide does not assess either policy or determine vehicle eligibility.
Match each handover to the correct request
Name the person who releases each vehicle and the person receiving it. If one person is handling both pickups, describe how they will meet the drivers and identify the correct keys without relying on both drivers arriving at exactly the same moment.
For a business, the booking contact, key holder and receiving staff member may be different people. Use the business handover guide to prepare each end of each journey.
A practical brief might say: “Car A is in bay 12 and Car B is in bay 18. The reception contact holds both keys. Each car has a different destination and named recipient.” This is an illustrative planning example, not a confirmed DOD workflow.
Separate a preferred time from a dependency
“Both around the same time” and “neither can leave until both drivers are present” are different requests. State which one you mean. If the journey depends on coordination, ask whether the final service can support that requirement before relying on it.
Decide what happens if only one request is accepted, one driver is delayed or one vehicle is unsuitable. Can the first car leave independently? Will a passenger remain with the second car? Who can approve a later handover?
Do not assume that submitting two requests reserves two drivers or links their outcomes. Driver availability and the final booking conditions must be checked for each journey. An enquiry about coordination is not confirmation of a coordinated service.
Do not make one driver responsible for two simultaneous movements
If you actually want one driver to move Car A and later move Car B, describe a sequential plan. Include where the first movement finishes, how the next pickup would be reached and who keeps the second vehicle available. Ask how those movements would need to be arranged.
Do not treat the gap between cars as an invisible part of the job. Nor should you assume the original driver can switch vehicles within a booking. The final vehicle-change and driver-return arrangements need to be confirmed through the published service process.
DOD’s services page describes planned one-way and hourly options. It does not establish that either option includes a second vehicle movement.
Keep changes attached to the right car
When a destination, passenger or pickup changes, identify the affected vehicle and request. “Change the destination” is ambiguous when two cars are involved. Use the relevant registration and booking reference when available.
Give each receiving person the details for their vehicle. For example, someone receiving Car A should not assume that its arrival confirms Car B has also arrived. Keep any proposed follow-up practical and limited to the information needed.
If one journey is cancelled or ends differently from the plan, check what that means for the other journey. Do not assume one request’s cancellation automatically changes the other. This guide does not set cancellation charges or linked-booking rules.
A two-car planning table
| Detail | Car A | Car B |
|---|---|---|
| Vehicle | Registration and model | Registration and model |
| Journey | Pickup and destination | Pickup and destination |
| People | Passengers and key holder | Passengers and key holder |
| Timing | Preferred time and flexibility | Preferred time and flexibility |
| Handover | Named recipient | Named recipient |
| Dependency | Can this trip proceed alone? | Can this trip proceed alone? |
| Alternative | Plan if this request cannot proceed | Plan if this request cannot proceed |
Complete the table before making a future enquiry. For multiple stops in a single car, use the multi-stop journey guide instead to describe the itinerary.
During prelaunch, use Contact DOD to ask about a future household or business journey. An enquiry does not reserve a driver or confirm that two vehicle requests can be coordinated. For a journey before bookings open, arrange an option that is already available.
About this guide
Prepared by the Drivers on Demand editorial team using current DOD customer, services, business and Journal content checked on 17 October 2026. It is a planning guide, not confirmation of a group-booking feature, vehicle eligibility or insurance cover.