Start here
Tread is the operating system for bulk materials hauling. Every workflow — dispatch, tickets, approvals, billing, driver pay — sits on top of the same fifteen concepts. Learn them once and the rest of the product makes sense.The fifteen concepts
Companies & Hierarchy
Single company by default. Parent/child only for real regional splits.
Connected Ecosystem
How the Connected Customer, Tread Customer, Vendor, and Driver connect.
Sites & Geofences
Lat/long pins with virtual fences that detect arrival and departure.
Equipment & Equipment Types
Types hold capacity. Equipment is the physical truck or trailer.
Materials
What gets hauled. Pulled from accounting, grouped under Material Types.
Orders & Projects
A Project is the long-lived container for the work. Orders are the daily work inside it.
Dispatching Drivers and Vendors
Dispatch to an internal driver, a shared driver, and a vendor
Driver Lifecycle
Invite, first login, vendor moves, deactivation.
Tickets & Timesheets
The proof of work. Load tickets and driver hours.
Settlements & Driver Pay
Approve, then settle. Receivables and payables run on different rules.
Rates, Add-Ons & Fuel
Three components: price index, schedule, application.
Roles & Permissions
Who sees what. Drivers must never see customer rates.
Custom Labels
Your own tags for slicing drivers, users, and vendors.
OmniReports
The custom report builder — filter, group, schedule, share.
Compliance Documents
Driver and vendor docs, expirations, and dispatch gating.
How to read this section
Each concept page follows the same shape. What it is. Why it matters. How Tread models it. Common pitfalls. Related links. Most pages take under three minutes.Where to go next
Quickstart
Stand up your first dispatch in under an hour.
Onboarding
Step-by-step setup for a new Tread account.