Electronic proof of delivery

Driver evidence and proof

Evidence captured where the work happens, travelling with the order.

  • 03Dispatch orders
  • 04Employees
  • 14Activities
What
Evidence is captured where the work happens and travels with the order to the invoice. Driver notices for assignments, windows, readiness and waybill events are retried until delivered.
Who it is for
Drivers in the cab, with dispatch and operations reading what they capture.
Problem
Proof of delivery arrives as a photograph in a chat group, or not at all.
How
A six step flow: duty session, walk around, assignment, trip events, cargo and damage, proof of delivery.
Value
A missing proof is flagged, never invented.

What this settles

“Did this delivery actually happen?”
A signature, an OTP or paper, captured at the point of delivery and attached to the order. A missing proof is flagged rather than invented.
“Who signed for it, and when?”
The proof carries its own timestamp and source, and it travels with the order to the invoice raised from it.
“Was the cargo damaged before or after we took it?”
Condition is recorded against the cargo line at the walk around and at delivery, with cause and liability.

What it looks like

Evidence captured where the work happens, travelling with the order.

In transport management terms

Electronic proof of delivery

ePOD, captured in the cab rather than typed in afterwards. Duty, walk around, assignment, trip events, cargo condition and signature all attach to the order they belong to and travel with it to the invoice.

Where it sits in the run

  1. 01Shipment
  2. 02Connectivity
  3. 03Data
  4. 04Visibility
  5. 05Intelligence
  6. 06Decision
  7. 07Outcome

Where you work in it

  • 03Dispatch orders
  • 04Employees
  • 14Activities

The tenant console is a persistent left navigation over a content area, built for operators who live in it all day. A second console serves the platform operator, and a driver application serves the cab.

How it runs

  1. Duty session

    01

    On duty and off duty recorded separately from attendance.

  2. Walk around

    02

    Checklist with severity. A critical failure blocks the vehicle until a release is granted.

  3. Assignment

    03

    Accept or decline with a reason. A decline returns the dispatch to unassigned.

  4. Trip events

    04

    Stated times are bounded and their capture source is recorded.

  5. Cargo and damage

    05

    Damage recorded against cargo lines with cause and liability.

  6. Proof of delivery

    06

    Signature, OTP or paper. A missing proof is flagged, never invented.

The driver mobile application is a separate codebase. This flow is documented from the platform API the app calls and the data it writes.

True of every area

  • Arabic and English, both first class

    Every screen, every document and every export, with full right-to-left layout rather than a translated skin.

  • Every write is audited

    Actor, entity, action and change, appended and never edited. Operator impersonation is visible to the tenant.

  • Permissions follow the role

    Money is a permission rather than a column, and an approval chain belongs to the role that owns it.

  • It comes out again

    Excel, CSV and print to PDF across the reports, with the documents and the audit trail included.

What this changes, by sector

  • Last mile

    Signature or OTP at the door, captured in the cab and attached to the record that becomes the invoice.

  • Car carrier

    Damage recorded against the individual vehicle line, with cause and liability, not as a note on the whole load.

  • Oil and gas

    A critical walk-around failure blocks the vehicle until a release is granted — before a hazmat load moves, not after.