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

# Paving & Moving Geofences

> Geofences that travel with the paver, fed by the operator's phone or by Paver Tracker.

## When to use this

Use a moving geofence when the work is linear — paving, milling, road striping — and the active drop zone shifts down the road as the day goes on. A fixed geofence at one milepost will miss every load delivered past it.

## How it works

A [geofence](/concepts/sites-geofences) (a virtual fence around a site that tells Tread when a truck has arrived or left) usually stays put. A moving geofence is tied to a piece of [equipment](/concepts/equipment) instead of to a fixed point. Wherever that equipment reports its position, the geofence follows.

Trucks crossing the moving boundary trigger the same arrive and depart events as a static [site](/concepts/sites-geofences). Tickets, on-site minutes, and load counts attach to the [order](/concepts/orders-projects) (the day's work) the same way.

## Set up a moving geofence

<Steps>
  <Step title="Create the equipment">
    In Settings → Equipment, add the paver or mill and name it. No special settings are needed. If it carries a telematics device, map it on the **Integrations** tab.

    <Frame>
      <img src="https://mintcdn.com/treadtechnologiesinc/gRdni8abqw5c9OZQ/images/image-8.png?fit=max&auto=format&n=gRdni8abqw5c9OZQ&q=85&s=f36fa3dc55baca3d72e0d58132487d23" alt="Image" title="Image" style={{ width:"60%" }} width="632" height="646" data-path="images/image-8.png" />
    </Frame>
  </Step>

  <Step title="Create the site">
    Set **Geofence Type** to **Equipment**, pick the paver under **Available Equipment**, then set the **Radius**.

    <Frame>
      <img src="https://mintcdn.com/treadtechnologiesinc/gRdni8abqw5c9OZQ/images/image-9.png?fit=max&auto=format&n=gRdni8abqw5c9OZQ&q=85&s=495a4b9bbcd393c4b36578376cc5de69" alt="Image" width="865" height="461" data-path="images/image-9.png" />
    </Frame>
  </Step>

  <Step title="Add inner geofences (optional)">
    Under **Additional Geofences**, add a tighter circle and give it a **Tag** — Loading, Unloading, Check In, Scaling, or Ticketing. Additional geofences follow the same equipment automatically, so you only set radius and tag.
  </Step>

  <Step title="Set the operator up as Foreman and Driver">
    The person running the paver needs both roles. The **Driver** role is what matters for the geofence: only a Driver can clock in, and clocking in is what starts GPS. Set the paver as their primary equipment. See [Foreman](/workflows/foreman).
  </Step>

  <Step title="Build the order">
    Create the [order](/concepts/orders-projects) as normal and pick the moving site as the pickup or drop-off. Milling equipment is usually the pickup; the paver is usually the drop-off. Set **Geofence Delay (s)** here, not on the site.

    <Frame>
      <img src="https://mintcdn.com/treadtechnologiesinc/gRdni8abqw5c9OZQ/images/image-10.png?fit=max&auto=format&n=gRdni8abqw5c9OZQ&q=85&s=e9fd074f7a49095bdccdd9f99edc2e9f" alt="Image" width="276" height="301" data-path="images/image-10.png" />
    </Frame>
  </Step>

  <Step title="Day of: pick the equipment and start the shift">
    On the **Drive** tab, the operator sets **Truck & Trailer** to the paver, then taps **Start Shift**. From that point the phone's position moves the geofence. The operator does not have to be assigned to the order.

    <Frame>
      <img src="https://mintcdn.com/treadtechnologiesinc/gRdni8abqw5c9OZQ/images/image-11.png?fit=max&auto=format&n=gRdni8abqw5c9OZQ&q=85&s=6d631d8f45926253f779adcabf8ccd84" alt="Image" width="776" height="448" data-path="images/image-11.png" />
    </Frame>
  </Step>
</Steps>

## Feeding the position

Two sources move the same geofence. Either one works; you do not need both.

| Source                                       | Updates                         | Setup                                                     |
| -------------------------------------------- | ------------------------------- | --------------------------------------------------------- |
| Operator's phone                             | Every few seconds while on duty | The steps above. Nothing else to turn on.                 |
| [Paver Tracker](/integrations/paver-tracker) | About once a minute             | Tread creates the equipment, site, and geofences for you. |

The geofence moves on the live map as positions arrive — no page refresh needed. A job's route timeline replays where the geofence sat through the day, alongside truck history.

## Common pitfalls

<Warning>
  **No clock-in, no movement.** If the operator never starts a shift, Tread falls back to that equipment's last known position from up to 12 hours earlier. With nothing in that window, the geofence is dropped from the job and no arrive or depart events fire.
</Warning>

<Warning>
  **A radius that is too wide catches the staging area.** Trucks queueing 200 feet behind the paver will register as on-site, inflating wait time and load counts. Start tight; widen only if drivers report missed arrivals.
</Warning>

<Note>
  **Geofence Delay applies to the outer circle only.** The delay set on the order filters arrivals on the outer **Site** geofence. Inner geofences trigger with no delay.
</Note>

<Warning>
  **"Sync sites from telematics (PaverTracker)" is not the on switch.** That checkbox only appears when the company has a Paver Tracker fleet connected, and it is on by default. Turning it off stops Paver Tracker from moving daily sites on that order. It does nothing to a moving geofence you set up by hand.
</Warning>

## Related

* [Paver Tracker](/integrations/paver-tracker)
* [Sites & Geofences](/concepts/sites-geofences)
* [Equipment](/concepts/equipment)
* [Foreman](/workflows/foreman)