Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tread.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
When to use this

Use driver e-signatures when you need a driver’s sign-off as proof — for billing disputes, hours verification, or customer delivery confirmation. Most useful on time-and-material work, prevailing-wage jobs, and any customer that demands a signed manifest.

​
How it works

E-signatures live on the Driver App and attach to one of three units of work.
Signature scopeWhat it confirmsWhen it’s used
Per loadOne ticket, one signaturePer-load billing, customer delivery proof
Per jobAll loads in a single dispatched jobJob-level approval; T&M work
Per shiftFull day of workHours verification; weekly payroll sign-off
A driver opens the relevant load, job, or shift on their phone, reviews the details, and signs on the screen. The signature is stamped with timestamp, GPS, and the driver’s user ID, then attached to the ticket or timesheet (the proof of work record).

​
Setup

1

Pick the signature scope

In Settings → Platform Configurations, choose per-load, per-job, or per-shift. You can set a default and override per order (the day’s work container).
2

Decide what blocks submission

Mark whether a missing signature blocks the driver from closing the load or shift. Most customers leave it as a warning, not a hard block.
3

Brief the drivers

Drivers will see a new sign-here screen at the chosen scope. A 30-second walkthrough on day one prevents support tickets.

​
Common pitfalls

A signature is not an approval. A signed shift still has to clear the office approval queue. Don’t tell customers “the driver signed, so it’s billable” — billing leads still review.
Per-load signatures slow drivers down on high-volume work. If a driver runs 20+ loads a day, per-shift is usually the right scope. Reserve per-load for jobs where each ticket carries its own customer sign-off.