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 this guide when the day goes off-plan — a driver finishes early and needs another job, a customer calls in a rush load, weather shuts a site, or the foreman moves trucks from paving to base course mid-morning. Most jobs do not run end-to-end as dispatched. Tread expects that.
How it works
Three roles can change the plan during the shift.
The dispatcher edits the order (the day’s work) from the web app — reassigns trucks, adds or cancels loads, splits a job to a new site. Drivers see the change on their next push notification.
The foreman edits from the Foreman App on the jobsite. Same edit rights as the dispatcher for projects they are assigned to. Useful when the office is offline or slow to respond. See Foreman in the Field.
The driver can flag a load as wait, void, or material-mismatch from the Driver App. They cannot reassign themselves, but they can stop a load that is going wrong before it costs you a billing dispute.
Every change is logged. Office staff see the audit trail in the order history; billing pulls from the final state, not the original plan.
Common pitfalls
Splitting a job mid-shift can break geofence-based auto-end. If the auto-end timer is tied to the original site (a virtual fence around a job site), moving the job to a new site mid-shift may leave the original load open. Close it manually before reassigning. Night shift jobs that span midnight. Edits made after midnight on a job that started the previous day can land on the wrong calendar day. Confirm the shift date when reassigning across midnight, especially for timesheet approvals (the driver-hours record). 
