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 it is

A Project is the container — a job that may run for a day, a week, or a year. An Order is the daily slice of that work, the thing dispatchers actually assign drivers to. One Project can hold dozens of Orders.

​
Why it matters

This split is how Tread separates planning from execution. Projects hold the customer, site, materials, and rates. Orders hold the trucks, drivers, start time, and quantity for that day. Reporting, billing, and dispatch all key off this distinction.

​
How Tread models it

  • Project — long-lived. Holds the Customer, the Sites (load and dump), the Materials, the rates, and the date range.
  • Order — short-lived. Holds the date, shift, equipment requested, drivers assigned, and target loads or hours.
  • Order types — Hourly (paid by the hour) or Load-Based (paid per load). Drives how Tread auto-completes a job and what the geofence timer does.
  • Daily Plan — the dispatch view that lists all Orders for a given day across the fleet.
Lives on ProjectLives on Order
CustomerDate and shift
SitesDrivers assigned
MaterialsEquipment assigned
RatesTarget loads or hours
PO and contractNotes for the day

​
Order types

Every Order has a type. The type drives how Tread auto-completes the work, what dispatch screens show, and how billing rolls up. Loads — tonnage- or count-based delivery. The most common type. Pick this for any haul where a driver runs a route and the work is measured per load (tons of asphalt, yards of dirt, count of pallets). Loads pair with scale tickets or digital ticket capture. Service — non-tonnage work. Pick this for signage, traffic control, mobilization, flagging, and other line items that aren’t a haul. Service orders bill flat or hourly depending on the rate, and don’t expect a load count. Driver time — pure hourly driver work. Pick this when the deliverable is the driver’s hours, not the haul. Common for paving support, equipment moves, and standby. Geofence triggers still apply, but the billable unit is time, not loads. Misc — flat-rate or one-off work. Pick this for anything that doesn’t fit the other types — a one-off cleanup, a short-notice favor, a mobilization fee billed as a single line. Misc orders accept a flat amount and one note. Standing — recurring or scheduled work. Pick this for repeat jobs that run on a cadence (a daily shuttle, a weekly maintenance haul). Standing orders generate child orders on the schedule you set, so dispatchers don’t rebuild the same plan every morning. When in doubt, use Loads. The other four are exceptions, not the rule.

​
Common pitfalls

One job per invoice quirks. Some customers require one invoice per Project, not per Order. If your billing rules expect Orders to roll up into a single invoice, confirm the Project setup before the first cycle. Mid-month changes mean voiding and reissuing invoices.
Reuse a Project for repeat work to the same customer and site. Daily Orders attach underneath. Do not create a new Project per day — reporting will fragment.