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

# Driver App

> What Drivers see on their phone — and how to onboard them.

The Tread Driver App puts a Driver's dispatches, tickets, and signatures on one phone. Dispatchers see progress in real time instead of calling for updates.

## Who it's for

[Drivers](/concepts/driver-lifecycle) — the users who receive a dispatch and perform it. That includes your own Internal Drivers, [Shared Drivers](/concepts/connected-ecosystem) (Drivers another account shares to you), and Owner-Operators (O\&O — a Vendor with a single Driver, dispatched directly as a Shared Driver).

## Key features

* Accept jobs and see the full day's assignments before the first run.
* Auto-start and auto-end on [geofences](/concepts/sites-geofences) (a virtual fence around a site).
* Capture scale tickets by photo. OCR pre-fills the load fields.
* Capture e-signatures by shift, job, or load as required.
* Works [offline](/mobile/offline-mode). Uploads queue when service drops and send when it returns.

## Walkthrough

<Steps>
  <Step title="Sign in">
    Download Tread from the App Store or Google Play. Sign in with the phone number on the driver's user record. See [Adding Drivers](/onboarding/master-data/drivers).
  </Step>

  <Step title="Accept the day's jobs">
    Assigned jobs appear in the Assigned menu. Tap **View Request** → **Accept** on each. Declined jobs return to dispatch.
  </Step>

  <Step title="Start the run">
    When Telematics integrations enabled, Tread auto-starts when the truck enters the pickup geofence. The driver can also press **Start** to start their jobs.
  </Step>

  <Step title="Capture the ticket">
    On loaded, snap a photo of the scale ticket. OCR fills the ticket number and quantity. Confirm or edit.
  </Step>

  <Step title="End the load">
    When the job has a set load count or quantity, Tread auto-ends it when the truck leaves the drop-off geofence. The driver can also press **Stop Job**.
  </Step>

  <Step title="Sign and close out">
    At end of shift the driver can sign a load. Foremen or customers can sign per job or per load. See [Driver E-Signatures](/specialized/driver-esignature).
  </Step>
</Steps>

## Onboard your fleet

Driver adoption is a change-management problem, not a technology problem. Train in person and track adoption in Tread.

<Steps>
  <Step title="Train one crew at a time">
    Walk drivers through the app in person. Avoid email-only rollouts.
  </Step>

  <Step title="Keep tickets and signatures in the app">
    Tickets and signatures come from the app. No paper backup.
  </Step>

  <Step title="Coach weekly">
    Review missing tickets and signature gaps in Tread each week. Coach the drivers who lag.
  </Step>

  <Step title="Expand at 90% adoption">
    Once the first crew captures 90% of its tickets in the app, roll out to the next.
  </Step>
</Steps>

## Related

* [Track Drivers & Collect Tickets](/workflows/track-drivers-collect-tickets)
* [Digital Tickets](/specialized/digital-tickets)
* [Driver E-Signatures](/specialized/driver-esignature)