Assign a driver and review delivery tracking

Use Assign driver to request a change to the person responsible for an eligible delivery. Verify the saved assignment separately from any map or tracking view: a selected name does not prove that the driver accepted the delivery, started moving, or is reporting a current location.

Before you start

• Sign in to the intended project and business scope, open Orders, and refresh the intended order.
• Match the order number, business, customer, Order Type, and current status. The assignment control is source-intended for an eligible delivery that is accepted or ready for pickup and only when driver assignment is enabled for the project.
• Confirm that assigning, changing, or unassigning a driver is the intended operational action. It is a remote order change that can affect the previous driver, the selected driver, logistics processing, and configured updates.
• Do not use a map as proof that an assignment is saved. Map data, device location, realtime updates, and external navigation have separate availability and permission conditions.

Request the assignment

1. Open the intended order and find Assign driver.
2. Open the driver picker. A driver marked Not available cannot be selected, and the currently assigned driver is marked Selected.
3. Select the intended available driver. If a driver is already assigned and your operating procedure requires removing that responsibility, select Unassign Driver instead.
4. Treat the selection as a request. The picker closes while Business App sends the order change; do not repeat the selection while the result is unknown.
5. Wait for loading to finish. Refresh the order, then verify that the intended driver name is shown or that no driver is assigned, as applicable.

Review available delivery tracking

1. Verify the saved assignment first. Assignment and tracking are separate: a delivery can have an assigned responsibility without usable current location data.
2. If the order exposes the map icon, open it to review the returned business, customer, and driver markers that are available. Some grouped delivery states can instead show Track real time position.
3. Compare the marker with the order address and the current status. A missing driver marker means only that usable driver coordinates are unavailable to this view.
4. Refresh the order before making a time-sensitive decision. The app can apply matching tracking events to the driver marker, but it does not display an accuracy, age, continuity, or provider-delivery guarantee.
5. If you select a linked business or customer address, Business App hands the destination to a supported maps app on the device. Confirm the destination in that app; Business App does not verify the route or the external app's result.

Verify the result

Verify assignment and tracking as two independent results:

• Assignment accepted: after loading and a refresh, the intended driver is shown on the order. This confirms the returned order assignment, not driver acceptance, availability after assignment, notification delivery, or pickup.
• Unassignment accepted: after loading and a refresh, the previous driver is no longer shown as assigned. Do not assume related provider or logistics work was cancelled unless its own current state confirms that result.
• Assignment rejected or unknown: an error appears, loading does not settle, or the refreshed order still shows another assignment. Preserve the current assignment and do not treat the picker closing as success.
• Tracking available: one or more returned markers appear. Treat them as displayed location data, not proof of who owns the delivery or where a person is now.
• Tracking unavailable or stale: a marker is missing, unchanged, or inconsistent with the order. The saved assignment can still be valid; verify responsibility from the refreshed order and escalate tracking separately.

Recover safely

What you observe	What it means	Safe next action
Assign driver is missing	The order type or state is not eligible, assignment is not enabled, the current scope differs, or the view is stale.	Refresh and verify the order type, status, project, and business scope. Do not change the order only to reveal the control.
The picker shows Without drivers	No assignable drivers were returned for the current order and scope.	Keep the order unassigned and contact the project administrator or dispatch owner. Do not choose a person outside the approved list.
A driver is Not available	The returned driver record is not selectable in the current picker.	Choose another approved available driver or escalate capacity. Do not interpret the label as a permanent schedule or location fact.
A validation, permission, locked-order, invalid-driver, busy-driver, or network error appears	The assignment request was not accepted as submitted, or its result is unknown.	Keep the message, refresh once, verify the current assignment, and retry once only if the intended change is still required. Escalate persistent errors to the project administrator or Ordering support.
The picker closes but the assignment does not change	Picker closure is not a success receipt, or another update won.	Refresh the order. Do not repeat until the current assignment is known.
The assigned name changes but no marker appears	Assignment data and tracking data are separate.	Continue using the refreshed assignment as the responsibility record and escalate missing tracking to the dispatch or provider owner.
A marker does not move or appears implausible	Location permission, device reporting, network, realtime delivery, or provider data can be unavailable or stale.	Do not estimate location accuracy. Refresh once, confirm the order status, and use the approved escalation channel.
The map or an address link does not open	Device permission, map configuration, or an installed maps handler can be unavailable.	Keep the order open, use the written address through an approved alternative, and report the map handoff separately.

Availability and platform differences

• Assign driver is source-intended only for accepted or ready-for-pickup delivery and catering-delivery orders when driver assignment is enabled. Visibility is client availability evidence, not a commercial entitlement or complete permission guarantee.
• The picker is built from drivers returned for the exact order and business relationships. A visible driver can still be rejected by current server validation, ownership, group membership, busy state, locking, or concurrent changes.
• The embedded map uses returned coordinates and a configured map provider. It can also invoke device location services even in a read-only order map. Location permission, provider setup, and network access vary by device and platform.
• Address links use the device's iOS maps or Android geo handler. The operating system or installed app owns provider selection, routing, prompts, and the final result.
• The label Track real time position describes the visible action, not a freshness promise. Business App does not establish marker age or accuracy in this documented flow.
• Visible behavior describes the current source contract. Deployed app, API, socket, map, external-driver, notification, and logistics-provider parity are not established by this article.

Related articles

• Review an order before taking action
• Understand fulfillment types and pickup states
• Understand order queues and statuses
• Loading, connection, empty, and error states

:::note Visual status Visual guidance is deferred pending an authorized synthetic capture program and independent visual QA. :::