Transport jobs and proof of delivery

Transport is where the work meets the customer. Loaditude covers the full cycle: creating a transport job, assigning it to a driver, dispatching it to the mobile app, and capturing digital proof of delivery (POD) that flows straight back to the office and the client. This guide walks through each stage and how the driver app behaves on the road.

Creating a transport job

A transport job is a piece of work that moves goods from one place to another: a collection, a delivery, or both. You create it with the details a driver needs, the addresses, the contact, the goods, and any timing or access notes. Because transport sits in the same system as your warehouse, a job can carry through goods you receipted and kitted rather than being re-entered from scratch (see Kitting and value-added services).

Assigning and dispatching

Once a job exists, you assign it to a driver. The moment it is assigned and dispatched, it appears on that driver’s phone in the Loaditude Driver app. Drivers only see the runs assigned to them, which keeps the app focused and your data private. The office keeps a live view of where each job is in its lifecycle.

Proof of delivery on the driver app

At the point of delivery, the driver captures proof directly in the app:

• Photographs of the delivered goods in place, the single most useful piece of evidence in a delivery dispute.
• A signature captured on the screen from whoever receives the goods.
• Status and notes, including marking a delivery as completed, or recording an exception if something could not be left.

That captured proof is timestamped and tied to the job, so there is a clean record of who received what, when, and in what condition.

Works offline, syncs when back online

Deliveries happen in loading bays, basements, and rural lanes where signal is poor. The driver app is built offline-first: job data and captured proof of delivery queue locally on the device and sync back to the office automatically as soon as connection is restored. A driver can complete a full run with no signal and lose nothing. The app shows a clear indication of what has synced and what is still pending, so a driver is never guessing whether their PODs made it back.

Real-time visibility

As jobs progress and proof is captured, the office sees it in near real time, and so does the client through the portal. A coordinator can answer “has my delivery gone?” without phoning the driver, and the client can often answer it themselves. See The client portal explained.

Good practice

• Capture a clear photo at every drop. It is the cheapest insurance against a disputed delivery.
• Add access and timing notes to the job so the driver is not calling the office from the kerb.
• Check the sync indicator at the end of a run so any pending proof is sent before the phone is put away.

Where to go next

• The client portal explained covers giving clients their own view of deliveries.
• Troubleshooting and FAQ covers driver sign-in and sync questions.