> ## 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. # Core Concepts Overview > The fifteen ideas you need to understand Tread. ## Start here Tread is the operating system for bulk materials hauling. Every workflow — dispatch, tickets, approvals, billing, driver pay — sits on top of the same fifteen concepts. Learn them once and the rest of the product makes sense. ## The fifteen concepts Single company by default. Parent/child only for real regional splits. How the Connected Customer, Tread Customer, Vendor, and Driver connect. Lat/long pins with virtual fences that detect arrival and departure. Types hold capacity. Equipment is the physical truck or trailer. What gets hauled. Pulled from accounting, grouped under Material Types. A Project is the long-lived container for the work. Orders are the daily work inside it. Dispatch to an internal driver, a shared driver, and a vendor Invite, first login, vendor moves, deactivation. The proof of work. Load tickets and driver hours. Approve, then settle. Receivables and payables run on different rules. Three components: price index, schedule, application. Who sees what. Drivers must never see customer rates. Your own tags for slicing drivers, users, and vendors. The custom report builder — filter, group, schedule, share. Driver and vendor docs, expirations, and dispatch gating. ## How to read this section Each concept page follows the same shape. What it is. Why it matters. How Tread models it. Common pitfalls. Related links. Most pages take under three minutes. ## Where to go next Stand up your first dispatch in under an hour. Step-by-step setup for a new Tread account.