> ## 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.

# Track Drivers & Collect Tickets

> Live truck visibility plus automatic ticket capture from the field.

## 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

<Steps>
  <Step title="Open the Live Map">
    Go to **Live Map**. Every dispatched truck shows up with its current location, speed, and status. Filter by Project, customer, [department](/onboarding/master-data/departments-labels-classes), etc.
  </Step>

  <Step title="Watch geofence arrivals">
    When a truck enters a [geofence](/concepts/sites-geofences) (a virtual fence around a site), Tread logs the arrival, starts the onsite timer, and updates the job status. No driver action required if you have telematics connected.
  </Step>

  <Step title="Capture tickets from the field">
    Drivers submit tickets three ways: a photo from the [Driver App](/mobile/driver-app), an SMS reply with a photo, or an automated feed from a scale-house [integration](/integrations/telematics). Each ticket attaches to the matching load.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Resolve flagged tickets">
    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. The driver can also verify the ticket details before submitting the ticket.
  </Step>

  <Step title="Review the day's loads">
    At end of shift, open **Approvals → Approve Jobs → Loads** for a list of every load with its tickets, hours, and miles.
  </Step>
</Steps>

## Watch it

{/* VIDEO: TODO: record · 2-3 min walkthrough */}

## Common pitfalls

<Warning>
  **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.
</Warning>

<Warning>
  **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.
</Warning>

## Related

* [AI Data Collection & Load Approvals](/workflows/track-drivers-collect-tickets) — what happens after capture.
* [Tickets & Timesheets](/concepts/tickets-timesheets) — the data model.
* [Digital Tickets](/specialized/digital-tickets) — every supported ticket source.
* [Telematics integrations](/integrations/telematics) — auto-arrival and engine data.