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

# Tickets & Timesheets (per Shift or Hourly)

> The proof-of-work records — Tickets and Timesheets — and how they feed approvals, billing, and pay.

Every Ticket and Timesheet saves to Tread as it is captured — live, across connected accounts. That cuts re-keying and paper handling and speeds up approvals, billing, and pay.

## What it is

Tickets and Timesheets are the records Tread uses to prove the work happened. A Ticket records one load — ticket number, material, quantity, photo. A Timesheet records a [Driver's](/concepts/driver-lifecycle) hours for a shift or dispatch. Both must be approved before they reach billing and pay in a [Settlement](/concepts/settlements-driver-pay).

## How Tread models it

* **Ticket** — ticket number, material, quantity, unit of measure, photo, and source. Each Ticket links to its Load, Job, and [Order](/concepts/orders-projects). Tickets can be received via eTicket integration, drivers submitting via the Tread mobile application, or sent in via SMS through Tread's AI features
* **Source** — how the Ticket entered Tread: the Driver's mobile app, an SMS photo to Tread, a scale-house integration, or a digital Ticket from a connected account.
* **Ticket Chaser** — Tread's AI agent for Ticket collection. It messages Drivers over SMS to upload missing Tickets, reads the photos, and extracts the data. AI review flags inaccuracies and duplicates. Flags are informational, not blocking.
* **Timesheet** — a Driver's hours either for a shift which is 1 timesheet per day, or 1 per dispatch, for when a Driver requires a timesheet per Customer dispatch. Hours are automatically captured from clocking in & out via the mobile app, and additionally [geofence](/concepts/sites-geofences) enter and exit times are tracked from the Driver's mobile app to correlate a drivers working times. Tread has the ability to allow drivers or foreman to enter/edit shift and hourly times.

| 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

<Warning>
  **AI flags are informational. They do not block approvals.** Truck numbers with dashes, mixed date formats, and faded photos can trigger false positives. Treat a flag as a hint and approve on human judgment.
</Warning>

<Tip>
  Approve Tickets and Timesheets in the same approval session per Order. Splitting them across days means going back to the same Driver twice.
</Tip>

## Related

* [Settlements & Driver Pay](/concepts/settlements-driver-pay) — what happens after approval
* [Sites & Geofences](/concepts/sites-geofences) — how arrivals create Timesheet events
* [Workflow: Track Drivers & Collect Tickets](/workflows/track-drivers-collect-tickets)