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 digital tickets when you want to stop chasing paper. If your team is still scanning, faxing, or driving tickets to the office, every path below replaces that with same-day data.

​
How it works

A ticket is the proof a load was delivered — quantity, material, site, time. Tread accepts tickets through three paths. Photo capture. A driver or foreman takes a photo of a paper ticket from the Driver App or Foreman App. Tread’s Ticket Chaser agent reads the photo, extracts the fields, and queues the ticket for approval. OCR is informational — a human still approves before billing. SMS capture. A driver texts a ticket photo to a Tread number. Same OCR, same approval queue. Useful for drivers who cannot install the app or for one-off subhaulers. Integration capture. When a quarry, plant, or scale system already produces digital tickets, Tread pulls them via API. No driver action required. Common with producer-side scale tickets and with Paver Tracker on paving jobs.

​
Setup

1

Turn on Ticket Chaser

In Settings → Agent Configurations, enable Ticket Chaser. Confirm the company-default approval rules.
2

Provision the SMS number

Ask your Tread contact for an SMS capture number. Share it with drivers who will text in tickets.
3

Connect the source system

For scale or paver tickets, connect the source via Settings → Integrations. See Paver Tracker and Telematics for the supported feeds.

​
Common pitfalls

OCR is informational. It does not block approvals. A flagged ticket is a hint, not a rejection. Train approvers to read flags as “look closer,” not “do not pay.”
Truck number formatting trips up OCR. Dashes, leading zeros, and vendor-prefixed numbers all confuse the parser. Standardize truck names in Equipment before going live.