Skip to main content

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.

​
When to use this

Use moving geofences 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 (a virtual fence around a site that tells Tread when a truck has arrived or left) usually stays put. On a paving job, it doesn’t. The active drop zone follows the paver. As the paver advances along the alignment, the geofence advances with it — keeping the arrive/depart events aligned with where the trucks are actually unloading. Tread reads the paver’s position from the Paver Tracker feed and re-centers the geofence on a short interval. Trucks crossing the moving boundary trigger the same arrive/depart events as a static site. Tickets, on-site minutes, and load counts attach to the order (the day’s work) the same way.

​
Setup

1

Connect Paver Tracker

Set up the Paver Tracker integration so Tread can read paver position. The moving geofence will not work without it.
2

Mark the order as paving

On the order, set the work type to paving and pick the paver as the source equipment.
3

Set the geofence radius

Choose a tight radius (typically 50–150 feet) so adjacent lanes or staging areas do not falsely trigger arrive events.

​
Common pitfalls

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.
Changing geofence type mid-project rewrites history. Switching from circle to polygon, or from static to moving, applies retroactively to past loads on that site. If you need to change shape, do it between projects, not mid-job.