A driver may know the destination but still need to decide how to navigate in an unfamiliar car. The vehicle might have built-in maps, a phone connection or neither. Thinking about that before setting off can avoid hurried account logins and uncertainty over what stays connected afterwards.
Drivers on Demand (DOD) is preparing a marketplace connecting customers and businesses with verified independent drivers who drive customer- or business-provided eligible vehicles. Auckland services are coming soon, subject to product alignment and readiness. Bookings are not open. This article is a planning guide, not an approved device procedure or confirmation of final DOD app features.
Agree how the route will be displayed
Before the journey begins, ask which navigation method is available and appropriate for the actual car. The owner can explain the vehicle system without handing over a private account password. A driver should not assume permission to sign into a personal account on the car’s screen or change its existing profiles.
Record the exact destination and any important approach instructions separately from the choice of map app. A named entrance may matter more than a building’s general street address. DOD’s pickup-notes guide helps keep those instructions concise.
Make any connection deliberate
If a phone connection is proposed, discuss it with the person authorised to provide the car and follow the applicable vehicle and device instructions. Read the prompts rather than accepting every request automatically. Consider whether the navigation task actually requires the additional access a prompt requests.
Bluetooth pairing, phone projection, a cable connection and signing into a vehicle profile are different actions. Do not assume that unplugging a cable reverses every action taken earlier. Equally, do not assume every car stores the same information. Check the actual system rather than applying one model’s steps to another.
If the method is unfamiliar or cannot be agreed, resolve it before relying on it for the journey. Do not experiment with another person’s accounts. This guide does not provide instructions for operating a phone while driving; device use must follow current applicable rules and the agreed operating process.
Keep navigation separate from private accounts
A destination can be explained without sharing an email inbox, address book or cloud-account credentials. Avoid using a customer’s saved home, work or recent destinations as general browsing material. Ask for the address needed for this journey.
For the driver, consider what another user of the car might encounter after the handover if an account or device remains connected. Use the system’s documented options to review and remove your own temporary connection when appropriate. Do not reset the whole infotainment system or delete the owner’s profiles to solve a temporary connection issue.
| Stage | Question to settle |
|---|---|
| Before departure | Which navigation method is agreed for this car? |
| Connection prompt | What access is being requested, and is it needed? |
| Destination | Is the correct entrance or finish point clear? |
| Final handover | Has any temporary device or account connection been reviewed? |
| Unresolved issue | Who will follow up without sharing passwords? |
Include the connection in the final handover
Once the journey has finished and the car is parked, allow time for a brief review of any temporary connection. Ask the owner to confirm that their usual profile remains available. Check your own phone and cable before leaving, and explain any unresolved connection issue factually.
For example, a driver and owner might agree to use the car’s existing navigation without adding another account. On a different vehicle they may need a documented temporary connection. These are hypothetical planning examples, not completed DOD assignments or a guarantee that a particular setup is supported.
The phone-as-car-key guide addresses vehicle access separately: disconnecting navigation must not be confused with returning control of a digital key. The belongings checklist helps with phones, cables and bags at the end.
Prepare questions for a future arrangement
See DOD’s driver information for the proposed driver model. During prelaunch, contact DOD for general questions. A general enquiry does not reserve work or confirm the final navigation, device or support process.
About this guide
Prepared for Driver on Demand NZ Limited. This is original practical planning information. It does not claim device-security certification, legal approval or experience from completed DOD journeys.