Skip to content
Go

Proof of Delivery

Taxi & Private Hire › Products › Trip › Proof of Delivery

Coming soon

Captures proof of completion — signature, photo, or delivery code, plus who and when — at the delivery stop, with a clean failure path (mark as failed, then re-plan or return to sender) and an unbroken chain-of-custody audit trail. Operator- and driver-side today; recipient-facing tracking is planned.

Proof, captured at the door

When a delivery is completed, the driver captures proof against the consignment itself — a signature, a photo, or a delivery code, along with who took receipt and when. You decide what's required per job; signature media is held in a secure, compliance-grade document store. If the recipient isn't available, the driver records a failed delivery with a reason rather than a passenger-style no-show — and the job is re-planned or returned to sender.

At the delivery recipient address Capture proof ✍ Signature 📷 Photo # Delivery code · who · when ✓ Delivered proof attached to the consignment Delivery failed reason recorded → re-plan · or return to sender
Proof lives on the consignment, not a generic stop tick — a human passenger segment has no proof step. You choose which proof is mandatory per job.

An unbroken chain of custody

Every handover is recorded as an ordered, tamper-evident trail — who had the consignment, when, and where — from collection through to delivery (or return). For regulated goods such as medical samples, that chain of custody is the audit record: each status change is stamped, with the delivery proof captured at the final step.

1 Picked up who · when · where 2 Out for delivery stamped 3 Delivered + proof attached ↺ or Returned
An ordered audit trail — each transition stamped with actor, time and location, ending in the captured proof. The failure path records a reason and routes to a re-plan or a return.

Proof attaches to the consignment defined by the Cargo Model; status changes can be pushed to your systems via webhooks.