What it is
Tickets and timesheets are how Tread proves the work happened. A Ticket is a load record — quantity, material, ticket number, photo. A Timesheet is a driver’s hours for a shift. Both feed the same downstream surface: approvals, then billing and pay.
Why it matters
Nothing gets billed or paid without one of these. A ticket that never makes it into Tread is a load you cannot invoice. A timesheet that is wrong is a paycheck dispute. The whole back office runs on these two records being right.
How Tread models it
- Ticket — load number, material, quantity, UoM, load and dump times, photo, source.
- Source — paper photo, SMS-to-Tread, scale-house integration, or a digital ticket from another Tread account.
- Ticket Chaser — Tread’s AI agent. Reads photos, extracts the data, and queues missing fields for review. Informational, not blocking.
- Timesheet — driver hours for a shift. Captured from geofence times, mobile app, or a foreman entry. Approved by job, day, or exception.
| Captured by | What it records |
|---|
| Driver mobile app | Photo, time, GPS |
| SMS-to-Tread | Photo + ticket number |
| Telematics | Geofence enter / exit |
| Scale-house integration | Quantity + ticket number |
Common pitfalls
OCR is informational. It does not block approvals. A multi-ticket producer treated AI flags as hard errors and held back approvals waiting for clean OCR. Truck numbers with dashes, mixed date formats, and faded photos all triggered false positives. Train approvers to use flags as a hint and approve based on human judgment.
Approve tickets and timesheets in the same approval session per Order. Splitting them across days means chasing the same driver twice.
