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 back-hauls when a truck delivers one material out and picks up a different material on the way back. Common with self-hauling contractors moving aggregate to a job and reclaimed asphalt (RAP) or dirt back to a yard. One trip, two paid legs.

​
How it works

A back-haul is a single dispatch (the day’s work assignment) with two delivery legs. The driver follows one route — quarry to job site, then job site to a different yard — but Tread records each leg as its own ticket. Each ticket has its own material, quantity, and pricing. The outbound leg might bill at a haul rate plus material; the return leg might bill at a tonnage rate for the RAP. The driver app prompts the second pickup automatically once the first delivery is confirmed. Both tickets settle independently. You can bill the outbound to one customer and the return to another, or bill both to the same customer with separate line items.

​
Setup

1

Create the order with both materials

On the order, set the outbound material as the primary load. Add the return-leg material in the Return material field. Pick the dropoff for each leg.
2

Set rates per leg

Apply the outbound rate to the primary material and the return rate to the return material. See Rates, Add-Ons & Fees.
3

Dispatch the truck

Assign one driver to the dispatch. They see both legs in sequence on the Driver App — first delivery, then second pickup, then second delivery.
4

Capture both tickets

The driver signs and uploads a ticket at each delivery. Tread creates two ticket records tied to the same dispatch.

​
Common pitfalls

Forgetting to set the return material on the order. Without it, the driver sees only the outbound leg and Tread has no record of the return load. Set both materials when you create the order, not after the truck has rolled.
Mixing the legs into one ticket. Each leg is its own delivery, its own quantity, and often its own customer. Combining them into one ticket breaks pricing and reporting.