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 you’ll do

Decide whether your Tread account uses a flat structure or a parent/child structure, then lock it in before any master data is uploaded.

​
Before you start

  • Admin access to your Tread account.
  • A list of every legal entity, division, or terminal that dispatches trucks.
  • Agreement from operations on whether dispatchers cross divisions today.

​
Walkthrough

1

Default to flat

Most Tread accounts run flat — one company, one set of master data. Pick this unless you have a hard reason not to.
2

Use parent/child only for real regional splits

Add child companies if separate divisions have their own customers, rates, and books — and never share data day to day.
3

Plan for shared data

All drivers, equipment, vendors, and customers belong at the parent level. Share them down to children. Never create them on a child.
4

Confirm with operations

Walk a dispatcher and a billing lead through the proposed structure. If either flinches at intra-site dispatching or cross-entity reporting, simplify.

​
Verify

Open Settings → Companies. The structure on screen matches what you sketched with operations. No child company has its own drivers, equipment, vendors, or customers yet.

​
Common mistakes

Setting up master data on a child company. A multi-region producer set up every driver, vendor, truck, and customer on a child account instead of the parent. Dispatchers couldn’t move drivers across divisions. Drivers were imported as vendors. Payroll pulled the wrong hours. The fix took two days of manual back-end work. Always create at the parent level and share down. See Companies & Hierarchy.