> ## 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.
# Sites & Geofences
> Where work happens, and how Tread knows when trucks arrive and leave.
Sites and geofences turn GPS route histories into structured work data — load counts, cycle times, on-site minutes, and auto-completion of jobs. Dispatch and approvals run on real events instead of phone calls and approximations.
## What it is
A Site is a location on the map. A geofence (a virtual fence around a Site) tells Tread when a truck arrives, when it leaves, and how long it stayed.
## How Tread models it
* **Site** — name, address, lat/long. Reverse-geocoded from the address if you do not have coordinates.
* Sites typically have a Pickup and a Dropoff site. We also have a feature available for a third site - a "Staging Site"
* **Default Sites:** When you want to save multiple potential pickups or dropoffs to a Project or Order, you can utilize Tread's Default Sites feature. Tread does still enable geofence triggers and status updates when default sites are configured and the Pickup or Dropoff site is left blank.
* **Geofence** — the shape around the Site. Two types:
* **Circle** — a radius in meters. The default. Fast to draw.
* **Polygon** — a custom shape. Use it for irregular Sites or anywhere a circle would overlap a neighboring Site.
* **Multiple Geofences** — Tread allows for 5 additional geofences to be added to a given site. The "tag" represents the name of the geofence for reporting purposes
* **Geofence Timer** — the minimum time inside the fence, in seconds, before Tread counts a real arrival. Filters out drive-throughs.
* **Auto-geofence** — Tread can draw a default circle when a Site is created.
| Field | Required | Notes |
| -------------- | -------- | -------------------------------- |
| Lat / long | Yes | No coordinates, no detection |
| Geofence shape | Yes | Circle is the default |
| Geofence Timer | No | Defaults to your company setting |
## Auto-end behavior
When a load or shift ends depends on the order type. Geofence exit auto-ends some orders; others wait for a manual end or a different trigger.
| Order type | What auto-ends a load or shift | Manual end available? |
| --------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------ |
| **Hourly order** | Driver clocks out at end of shift, or geofence exit on the last load of the day | Yes — driver or foreman can end early |
| **Loads order** | Geofence exit at the destination (load complete) | Yes — manual completion overrides geofence |
| **Shift order** | Shift end time, regardless of geofence | Yes — driver can end shift early |
| **Digital-ticket-mode job** | Manual end only — geofence does not auto-complete | Yes — required, no auto-end |
* **Geofence exit** — the truck crosses the fence boundary on the way out. Tread closes the load and starts the cycle-time clock for the next one.
* **Geofence Timer** still applies. A truck that crosses the fence for less than the timer window does not trigger auto-end.
## Common pitfalls
**Geofence type changes affect historical data, not just future loads.** Switching a Site from circle to polygon will change its appearance on prior Projects and Orders
For paving and other work that moves down a road, use a [moving geofence](/specialized/paving-geofences) rather than redrawing a polygon every shift.
## Related
* [Tickets & Timesheets](/concepts/tickets-timesheets) — how arrivals turn into tickets
* [Paving & Moving Geofences](/specialized/paving-geofences) — geofences that travel with the work
* [Onboarding: Sites](/onboarding/master-data/sites) — step-by-step Site setup