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.

​
What you’ll do

Set the five account-wide defaults that shape how Tread captures truck activity and tickets.

​
Before you start

  • Operations agreement on how long a truck must sit inside a geofence before it counts as on-site.
  • A list of units of measure (UoM) you bill in.
  • Awareness of which orders use split flags — the markers that split a single shift across multiple jobs or cost codes.

​
Walkthrough

1

Auto-Geofence

Settings → Configurations → Auto-Geofence → toggle on. When on, Tread auto-creates a circle geofence around any new site you add. Most accounts leave it on.
2

Geofence Timer

Set how long (in seconds) a truck must remain inside the geofence before Tread marks it on-site. Default is 60. Raise it for busy yards where trucks pass through.
3

Default Onsite Minutes

Set the standard on-site dwell time used as a fallback when GPS data is missing. Used for ticket math and dispatcher estimates.
4

Allowed Units of Measure

Toggle on the UoMs your billing actually uses (tons, cubic yards, loads, hours). Hiding the rest keeps order entry clean.
5

Split Flag Configs

Settings → Configurations → Split Flags. Configure the markers dispatchers use to split a shift — by job, cost code, or material — so settlements and exports break out cleanly. Skip if your team doesn’t use splits.

​
Verify

Settings → Configurations shows each setting saved. Create a test order — the configured UoMs are the only options shown.

​
Common mistakes

Setting Geofence Timer too low at busy yards. A 10-second timer marks every passing truck as on-site, inflating dwell time and triggering false on-site events. Start at 60 seconds and tune down only if dispatchers report missed arrivals.