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.
Recording a proof the office was sent
Not every proof comes through the app. Sometimes a driver sends a photo to the back office over WhatsApp or email and it gets keyed in later, occasionally the next morning. Here is how to enter one so the customer sees the delivery as it happened, not as you typed it.
- Open the job: Transport › Jobs, then the job number.
- Attach the photos first. In Attachments & Documents, set the dropdown to Proof of Delivery, then choose Upload. Repeat for each photo. Tagging matters: only photos tagged Proof of Delivery or Proof of Collection go on the document you send a customer, so site and damage shots can be left as General and stay internal.
- Find the Proof of Delivery panel and choose Record delivery.
- Set Delivered on to when the delivery actually happened, not when you are entering it. This is the one field worth slowing down for: it is what the customer sees on the POD document and what the recipient sees on their tracking page. A delivery made on Monday and entered on Tuesday should still read as Monday. It is prefilled with the date the job was scheduled for, so check it against what the driver told you rather than accepting it.
- Check Delivered at. It is prefilled with the job’s delivery address. Change it if the goods went somewhere else: a rear entrance, a reception, a neighbour.
- Add Signed by and Notes if the driver gave you a name or anything worth recording.
- Decide on Email the recipient that the delivery has arrived. If you entered a date before today the tick box is off already, because the recipient has had the goods since then and a message this morning reads as a second delivery coming. Tick it only if you know they were never told.
- Choose Record delivery. The job now shows the delivery date, place and signer, and the POD document section appears below with Download, Print, Email POD and Share link.
Got a date wrong? Reopen the panel with Edit and correct it. Editing never emails anybody, so you can fix a name or a time safely. You cannot set a delivery in the future: a proof records something that has already happened, and a future date is nearly always a mistyped one.
Collection works the same way, on the Proof of Collection panel, with Collected on and Collected from. It has an Edit too, whatever stage the job has reached, so a collection saved against the wrong name can be corrected after the job has run.
If a photo is missing from the document, reload the job page and generate it again. Loaditude will tell you when it could not load an image rather than quietly producing a proof with nothing on it, and it will not email a proof of delivery that is missing its photos.
One thing to know: changing a delivery date moves that job in your completed-jobs reports, because it files the job on the day it was delivered. Backdating a job to yesterday means it will no longer appear in today’s completed list.
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.
Sharing the proof of delivery
Open a delivered job and you will find a Proof of Delivery document section. It builds a PDF containing the signature, who signed, when, any notes, and every photo the driver captured. Choose Photos + signature or Signature only depending on what the recipient needs, then download it, print it, or email it straight to your client.
Share link creates a web link to the same proof for anyone who has no login: an end customer chasing their delivery, an insurer, or a client’s accounts team querying an invoice. The link is signed, so it cannot be edited to show a different delivery, and it stops working after 90 days. Creating one is recorded in your audit log.
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.