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.

​
What this solves

You’ve sent the dispatch. Now you want to know — are the trucks moving, did they arrive, where are the tickets? Most operators today are on the phone all day chasing drivers and digging through stacks of paper at end of shift. This workflow gives you a live map of every truck, automatic geofence arrivals and departures, and ticket capture from photo, SMS, or telematics — without anyone calling the driver to ask “where are you?”

​
Walkthrough

1

Open the Live Map

Go to Dispatch → Live Map. Every dispatched truck shows up with its current location, speed, and status. Filter by Project, customer, or department.
2

Watch geofence arrivals

When a truck enters a geofence (a virtual fence around a site), Tread logs the arrival, starts the onsite timer, and updates the order. No driver action required if you have telematics connected.
3

Capture tickets from the field

Drivers submit tickets three ways: a photo from the Driver App, an SMS reply with a photo, or an automated feed from a scale-house integration. Each ticket attaches to the matching load.
4

Let the AI read the ticket

The Ticket Chaser agent (Tread’s OCR + matching agent) reads the ticket image, pulls ticket number, weight, material, and timestamps, and matches it to a dispatched load. Anything ambiguous gets flagged for human review.
5

Resolve flagged tickets

Open the Needs Review queue. Each card shows the ticket image side-by-side with the parsed fields. Confirm or edit, then approve. Most teams clear this queue twice a day.
6

Review the day's loads

At end of shift, open Approvals → Loads for a list of every load with its tickets, hours, and miles. From here, send to AI approvals or approve directly.

​
Watch it

​
Common pitfalls

Tickets without a matching load become orphans. If a driver submits a ticket for an order that wasn’t dispatched in Tread, the ticket lands in an unmatched bucket and won’t bill. Always dispatch the order — even retroactively — before approving the ticket.
OCR is informational, not blocking. The Ticket Chaser parses fields fast, but it doesn’t gate approvals. A billing lead at one large hauler taught their team to trust the parsed values without a quick visual check — and a misread ticket weight slipped through to invoice. Always glance at the source image before approving.