Capturing proof of service

Signatures, photos and odometer readings — what is captured and why it matters later.

Written for
Drivers
Reading time
1 min
Last reviewed
August 6, 2026

Proof of service is what turns a completed trip into a billable one. It is captured at the point of service because that is the only moment it can be captured truthfully.

What is captured

  • A rider or authorised representative signature, drawn on the device.
  • Photos, where the trip type or the payer requires them.
  • Odometer readings at pickup and drop-off, which is where billable mileage comes from.
  • Timestamps and location for each of the above, recorded automatically.

When the rider cannot sign

Record the reason and capture the representative's signature instead where one is present. An honest exception on the record is worth considerably more at audit than a signature that does not correspond to anybody.

Related

Still stuck?

Technical documentation

API references, data model, webhook payloads and integration guides — the detail behind the workflows described here. Available to signed-in Naveera customers.

Open documentation

Ask your team

Support requests are raised from inside Naveera Console, where your organization and your role are already known — which means the answer can be about your configuration rather than the general case.

Settings → Support, or ask your organization’s administrator