Bookings, Jobs and Proof of Delivery

The paperwork determines the invoice

A job cannot be invoiced without proof of delivery, and a missing signature or an unrecorded waiting time is money the business never collects.

The driver application is not an operational nicety. It is the point at which billable events are captured, and everything downstream depends on it.

Booking intake

• Multiple channels — portal, email, phone — normalised into one queue
• Validated against your service areas and rate card
• Duplicate detection against recent bookings
• Customer-specific requirements applied automatically
• Confirmation sent immediately

Driver applications must be simple

1. Works offline, syncing when signal returns
2. Minimal interaction per job — arrive, complete, next
3. Photograph and signature capture that is quick
4. Waiting time recorded, because it is billable and usually lost
5. Exceptions reportable in one tap

Anything requiring typing at the roadside will not be used consistently, and inconsistent capture is worse than none.

Exception handling is the differentiator

Customers accept delays. What they do not accept is finding out from their own customer. Detecting an exception and notifying immediately is the cheapest reputation improvement in transport.

That requires the exception to be captured at the point it happens, which brings it back to the driver application.

Invoicing from captured data

Most transport businesses under-bill because these events are not captured reliably rather than because they choose not to charge.