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

Run a final QA pass across nine categories before your first live dispatch. This is the last gate — once you flip live, drivers, customers, and vendors are on Tread.

​
Before you start

​
The checklist

Work through each category. Don’t flip live until every box is checked.
All eleven master data sets imported. Sample records reviewed by an admin.
  • Users — all admins, dispatchers, and back-office staff invited.
  • Drivers — every active driver loaded with unique phone.
  • Customers — including all Connected Customer invites accepted.
  • Vendors — all subhaulers connected.
  • Equipment Types — capacity and unit of measure set on each.
  • Equipment — every truck loaded and named consistently.
  • Materials — pulled from accounting; prevailing-wage flags set.
  • Sites — lat/long set; geofences validated.
  • Departments, Labels & Service Classes — only the ones you’ll actually use.
Entities sit at the right level. Shared resources flow correctly.
  • Company hierarchy reviewed — flat unless you have real regional splits.
  • Equipment shared from owning entity into operating entities (if multi-entity).
  • Drivers shared across the hierarchy where they run loads.
  • See Multi-Entity Billing if money flows between entities.
Every system that needs to flow into or out of Tread is live.
Decide what’s on, what’s off, and where the thresholds sit.
  • Ticket Chaser — on or off? See Agent Configurations.
  • AI Auto Approvals — threshold set per customer or globally.
  • Review the Common Mistakes page for agent-related pitfalls.
Field users have the apps on their devices and can sign in.
  • Driver App installed on at least two driver phones — confirmed sign-in.
  • Foreman App installed for any field foreman who’ll create or approve work.
  • One test ticket captured end-to-end on a real device.
Every active customer has a billing profile on file.
  • PO format, invoice frequency, ticket-matching rules set.
  • Email distribution list confirmed with the customer’s AP contact.
  • One sample invoice generated and reviewed with the customer’s AP team.
One full project end-to-end on a real driver, real truck, real ticket — with billing skipped.
Every role that will use Tread has had a walkthrough.
  • Admin user — full platform tour.
  • Dispatcher — dispatch board, intra-day changes, agent overrides.
  • Foreman — Foreman in the Field walkthrough.
  • Driver — Driver App install, ticket capture, e-signature.
Everyone affected knows what’s changing and when.
  • Vendor notification sent — every connected hauler knows go-live date.
  • Customer notification sent — AP contacts know to expect Tread invoices.
  • Internal comms — ops, billing, and exec team aware.
  • Escalation contact named — one person owns Tread questions during the first two weeks.

​
Verify

Every category above shows as complete. Your test invoice cleared your accounting system. At least one driver has run a real ticket and been paid (in test mode or with a small live load). Then flip live.

​
Common mistakes

Going live without the dry-run. A regional hauler skipped the test dispatch. Day one, the dispatch board worked but settlements failed because rates weren’t tied to the right customer. Run the dry-run — it catches this kind of gap in an hour.
Going live without an escalation owner. Day one will surface questions. Without a named owner, those questions sit in Slack channels and get worse. Pick one person before flipping live.
Skipping vendor and customer notification. Connected vendors and customers need to know when to expect connection invites and Tread-formatted invoices. Without notice, they’ll bounce both. Send the notification at least one week before go-live.