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 multi-contractor projects when several contractors share one job number — a highway, a subdivision, a large site — but each one bills separately. Common on public-works projects where six to eight contractors run the same job site under the same owner.

​
How it works

A project is the container for all work tied to a job number. Tread lets you attach multiple customers (the contractors) to one project. Each order (the day’s work) is tagged to the customer paying for it. Dispatch sees one project on the board. Billing splits cleanly — each contractor gets their own invoice for their own loads, with no manual sorting. Reports can roll up to the project (everything that happened on the highway) or down to the contractor (just what Contractor A owes you). This setup also keeps the data clean for the owner. If the owner asks “who hauled what on this job?”, one report pulls every contractor and every load tied to the project.

​
Setup

1

Create the project once

Projects → New Project. Use the shared job number as the project name. Set the project site to the work zone.
2

Attach each contractor as a customer

On the project, add each contractor under Customers. They must already exist in Customers — invite them as Connected Customers if they’re not.
3

Tag each order to the right customer

When you create an order under this project, pick the contractor paying for that day’s work in the Customer dropdown. Tickets and rates flow to that contractor only.
4

Pull the unified project report

Reports → Projects → pick the project. The report rolls up loads, hours, and revenue across every contractor. Filter by customer to see one contractor at a time.

​
Common pitfalls

Creating a separate project per contractor. A regional hauler tried this on a six-contractor highway job. Reporting back to the owner became a manual spreadsheet exercise. One project with multiple customers is the right model — don’t split it.
Forgetting to tag the order to the customer. An untagged order falls back to the project default and bills the wrong contractor. Confirm the customer on every new order before dispatching.