---
title: "Complete Work in the Driver App"
description: "Use the driver app to follow assigned trips, record deliveries and collections, report incidents and raise trip-related requests. Sign in with your assigned acc"
space: "Vuna Transport"
url: "https://docs.navari.co.ke/vuna-transport/drivers/daily-work"
updated: "2026-11-09"
---

Use the driver app to follow assigned trips, record deliveries and collections, report incidents and raise trip-related requests. Sign in with your assigned account on an approved device.

## Prepare before leaving

Refresh while online and open the assigned trip so the available trip and stop information can be loaded. Check the vehicle, stops and required tasks. If expected work is missing, ask dispatch to check the actual Driver and trip assignment rather than using another person's account.

Start the submitted trip before recording operational actions. A planned or draft trip is not permission to post handover proof. A completed trip cannot be reused for new requests or collections.

## Complete the work at each place

Open a stop. A customer delivery shows the customer, map/address, Delivery Note, recipient and items. Where a visit has several actions, open the individual task to see the relevant Delivery Note, Stock Entry, Return Request or Purchase Order reference.

1. Confirm you are working on the correct delivery or collection.
2. Enter actual quantities in the displayed UOM. Do not substitute pieces for cartons without changing the underlying approved conversion.
3. For rejections or shortages, record the reason and required explanation. At a depot, choose whether rejected goods are unloaded, remain on the vehicle or are split.
4. Record the recipient or person releasing the goods and use the signature/photo controls requested by the form.
5. Submit and check the result. Later, reopen the submitted handover to review quantities and confirmation details; do not edit the original event simply to reflect a later resolution.

If warehouse staff have already posted an attributed receipt, the task can be confirmed by **Warehouse Receipt**. Do not add a second POD stock receipt for those goods. Supplier receipts and depot End Transit posting depend on the independent Transport Settings controls.

## Raise a trip-related request

Open **Requests** inside the Delivery Trip. Use **Expense Claim** for supported travel expenses or **Material Request** for supported Purchase/Material Issue requests. These mobile Material Requests are not the depot Material Transfer planning workflow.

Select expense types or items, enter the required quantities/dates/details and submit the request. The app creates the supported business request for the company's approval process; a sent request is not an approved expense or issued stock. An employee link is required for expense claims.

## Work with an interrupted connection

Supported offline actions are queued on the device for synchronisation. Check **Sync Center** for pending or failed work and retry when online. Local save, queued upload and server-submitted proof are different states. Do not submit a replacement proof merely because an attachment is still syncing.

Avoid signing out, clearing app data or handing over the device while work is still pending. If the session expired, sign in again and then retry the existing queued work. If device approval was changed by an administrator, refresh the device state before repeating the task.

## Finish and check

Complete the required stops and tasks before finishing the trip. A task awaiting stock posting needs receiving staff or the configured posting action, not another quantity confirmation. Report incidents through the trip's incident area and describe what happened.

> [Video: Starting an assigned trip, opening separate stop tasks, submitting proof and checking pending uploads in Sync Center]

Remote push notifications are disabled in the current application. Refresh and check assigned work; lack of a notification does not mean no trip was assigned. Any foreground notification shown while using the app should not be confused with guaranteed background push delivery.