# AI Features Source: https://docs.tread.ai/ai/overview Tread's AI reads ticket photos, reviews tickets, texts drivers for missing tickets, and answers questions about your data. Tread's AI takes on the ticket work your team does by hand. It reads ticket photos, checks each ticket against its order, and texts drivers who forget to upload one. You set it up in **Settings → Agents**. > **[AI Ticket Scanning](#ai-ticket-scanning)** > > Reads each uploaded ticket photo and fills in the ticket details. > **[AI Reviews](#ai-reviews)** > > Approves tickets that match their order and flags the rest for a person. > **[AI Ticket Chaser](/specialized/ai-ticket-chaser)** > > Texts a driver when a load finishes without its ticket. > **[Ask Tread](#ask-tread)** > > Ask questions about your data, or ask for a change, in plain English. ![Settings → Agents with the AI Ticket Scanning, AI Reviews, and Driver Agent sections](https://mintcdn.com/treadtechnologiesinc/uWkkPTXlIiaYdf5i/images/onboarding/agents-panel.png?fit=max\&auto=format\&n=uWkkPTXlIiaYdf5i\&q=85\&s=c6b90b6077573d04085d453585f64997) ## AI Ticket Scanning AI Ticket Scanning reads each ticket photo that drivers or staff upload, and fills in the ticket details. It's always on. Most companies leave it as is. If your tickets have an unusual layout, add **Custom Instructions** under **AI Ticket Scanning**, for example "Treat the number in the top-right corner as the ticket number." Instructions apply to every ticket your company scans from then on. ## AI Reviews AI Reviews checks each finished load's ticket against its order. It approves tickets that look right and flags errors or duplicates, so a person only looks at the tickets that need it. It only reviews loads that have a ticket. AI Reviews is off until you turn it on. Check **Automatically review tickets with AI to approve valid tickets and flag inaccuracies or duplicates**. Add **Custom Instructions** for rules specific to your company, such as "Always flag tickets where the quantity exceeds 30 tons." Each reviewed ticket shows one of three statuses: | Status | What it means | | - | - | | **AI Reviewed** | The ticket matches its order and is approved. | | **Data mismatch** | Something on the ticket doesn't match the order, or it looks like a duplicate. | | **Unreadable ticket** | The photo can't be read. | ![A flagged ticket on the Approve Jobs page, with the AI review icon next to the Approve button](https://mintcdn.com/treadtechnologiesinc/6YBsddpx2sP2RIKn/images/AI-Review-Example---Flagged-TIcket-1.1.png?fit=max\&auto=format\&n=6YBsddpx2sP2RIKn\&q=85\&s=8f98f1c650b93cdb093c083b90fdd431) Hover over the AI icon to see why a ticket was flagged. Use the **AI Review Statuses** filter to list flagged tickets. If a flag is wrong, click **Dismiss Review**. ## AI Ticket Chaser When a load finishes without its ticket, the Driver Agent texts the driver and uploads the photo they send back. Contact Tread to set it up, then turn on **Ticket Chaser** on each project that needs it. See [AI Ticket Chaser](/specialized/ai-ticket-chaser). ## Ask Tread > [!NOTE] > > Ask Tread is rolling out to select customers. Click **Ask Tread** at the bottom right of any page. Ask a question, such as "How many drivers do I have?", or ask for a change, such as "Update a user's phone number." Tread shows each change it proposes, and nothing is saved until you confirm it. ## Related * [Agent Configurations](/onboarding/agent-configurations) — set up the AI agents during onboarding * [AI Ticket Chaser](/specialized/ai-ticket-chaser) — how drivers get texted for missing tickets * [Approving Loads & Tickets](/workflow/approvals/loads) — where reviewed tickets show up # Build a Report fields Source: https://docs.tread.ai/concepts/build-a-report-fields Every field in the Customer Reports topic of Build a Report, by view, with its type and what it means. Find the right field before you build. This page lists every field in the **Customer Reports** topic of [Build a Report](/concepts/omni-reports#build-your-own-report), grouped by the view it sits in. ## How to read this page * **Type** — Date, Number, Text, Yes / No, List, or ID. **Measure** is a count, sum, average, or percent calculated across the rows in your report. * **ID and "Pk" fields** — Tread's internal IDs. Use them to count or match records, not to show in a report. * **Grouped rows** — fields that repeat, like pickup, dropoff, and staging site fields, or Vendor 1 to 3, share one row. > [!TIP] > > In the builder, click the three dots (**⋮**) on a field to read its **Description**. ## Customer Reports One row per job. Timing, status, hours, quantities, the driver, vendors, truck, and sites. | Field | Type | What it means | | - | - | - | | **Friendly Job Id** | Text | Short, readable job number shown in Tread. | | **Job Id** | Text | The job's identifier. | | **Job Pk** | ID | Tread's internal ID for the job. Use it to count or match jobs. | | **Order Pk** | ID | Tread's internal ID for the order the job belongs to. | | **Status** | Text | Current state of the job, such as scheduled, in progress, completed or canceled. | | **Date Job Created** | Date | When the job was created. | | **Scheduled Start At** | Date | Date and time the job is scheduled to start. | | **Scheduled Start YYYY-MM-DD** | Date | Scheduled start date only (time set to midnight). Handy for grouping by day. | | **First Sent At** | Date | The first time the job was sent out. | | **Driver Co Assigned At** | Date | When the job was assigned to the driver's company. | | **Vendor 1 Assigned At** | Date | When the job was assigned to the first vendor. | | **Sent To Driver At** | Date | When the job was sent to the driver. | | **Driver Accepted At** | Date | When the driver accepted the job. | | **First Accepted At** | Date | The first time the job was accepted. | | **Driver Declined At** | Date | When the driver declined the job. | | **First Declined At** | Date | The first time the job was declined. | | **Canceled At** | Date | When the job was canceled. | | **First Canceled At** | Date | The first time the job was canceled. | | **To Pickup At** | Date | When the driver started heading to the pickup site. | | **Actual Arrival At** | Date | When the truck actually arrived for the job. | | **First Geofence Entry At** | Date | The first time the truck entered a job site's geofence (its map boundary). | | **Last Geofence Exit At** | Date | The last time the truck left a job site's geofence. | | **First Ticket Time / Last Ticket Time** | Date | Time on the first and on the last ticket of the job. | | **In Review At** | Date | When the job moved to In Review. | | **Completed At** | Date | When the job was completed. | | **Ended At** | Date | When the job ended. | | **Auto Ended** | Yes / No | Yes if Tread ended the job automatically rather than the driver. | | **Approved At** | Date | When an admin or biller from the job's company approved the job. | | **Billing Approved At** | Date | When the job's company gave billing approval. | | **Logging Started At / Logging Ended At** | Date | Actual times the driver started and stopped logging time. | | **Adjusted Logging Started At / Adjusted Logging Ended At** | Date | Logging start and end after someone adjusted them. | | **Final Logging Started At / Final Logging Ended At** | Date | Adjusted logging start and end if there are any, otherwise the actual times. | | **Pre Clamp Logging Ended At** | Date | Logging end time before Tread capped it to the allowed limit. | | **Clamped Logging Ended At** | Date | Logging end time after Tread capped it to the allowed limit. | | **Final Work Time Minutes** | Number | Approved work minutes if set, otherwise actual work minutes. | | **Approved Hours** | Number | Hours approved on the job. | | **Total Hours (job time)** | Number | Total hours on the job. | | **Total Minutes** | Number | Total minutes on the job. | | **Ticket Time** | Number | Total ticket time on the job, in hours. | | **Pause Time Minutes** | Number | Total paused minutes, from the driver's pause and resume taps. | | **Pause Time Minutes (derived from actuals)** | Number | Actual logged time (start to end) minus work minutes. | | **Pause Time Minutes (derived from final)** | Number | Final logged time (start to end) minus final work minutes. Never below zero. | | **Adjusted Pause Time Minutes** | Number | Pause minutes after someone adjusted them. | | **Break Time Minutes** | Number | Minutes of break taken during the job. | | **Idle Time Seconds** | Number | Seconds the truck sat idle during the job. | | **Load Cycle Avg** | Number | Average load cycle time on the job, in minutes. | | **Completed Loads Count** | Number | Number of completed loads on the job. | | **Loads With Tickets Count** | Number | Number of the job's loads that have a ticket. | | **Quantity / Quantity Unit** | Number | Quantity on the job and its unit of measure. | | **Delivered Quantities** | List | Delivered totals for each material and unit, across all loads on the job. | | **First Delivered Quantity** | Text | Delivered quantity for the first material (A to Z) only. Not a job total. | | **Material** | Text | Material on the job. | | **Material Type Name** | Text | Type of the job's material, such as aggregate or asphalt. | | **Service Name** | Text | Service performed on the job. | | **Service Pk** | ID | Tread's internal ID for the service. | | **Phase Code / Phase Name** | Text | Code and name of the project phase the work is billed to. | | **Phase Combined** | Text | Phase code and name together in one field. | | **Job Phase Code / Job Phase Name** | Text | Phase code and name set on the job. | | **Shift Phase Code / Shift Phase Name** | Text | Phase code and name set on the truck for this shift. | | **State Codes** | Text | State(s) taken from the dropoff site's address. | | **Driver Assigned** | Text | Name of the driver on the job. | | **Driver Company** | Text | Company the driver works for. | | **Driver User Pk** | ID | Tread's internal ID for the driver. | | **Driver Company Assignment Customer Account Pk / Company Pk** | ID | Internal IDs of the customer account and company on the driver's company assignment. | | **Vendor 1 / Vendor 2 / Vendor 3** | Text | Vendors on the job in order: the vendor hired first, then any vendors they passed it to. | | **Vendor 1 / 2 / 3 External Id** | Text | Those vendors' IDs in your own system. | | **First / Second / Third Assignment Customer / Vendor Account Pk, Company Pk** | ID | Internal IDs of the customer and vendor account and company on the first, second, and third assignment. | | **Truck Id** | Text | Name or number of the truck on the job. | | **Truck Pk** | ID | Tread's internal ID for the truck. | | **Equipment Name / Equipment License Number** | Text | The truck's name and license plate. | | **Equipment Accounting Id / Equipment External Id** | Text | The truck's IDs in your accounting and other systems. | | **Equipment Type** | Text | Type of truck, such as tri-axle or end dump. | | **Equipment Type Accounting Id / Equipment Type External Id** | Text | The equipment type's IDs in your accounting and other systems. | | **Equipment Type Gross Capacity / Equipment Type Gross Capacity Uom** | Number | How much that equipment type can carry, and the unit (for example 22 tons). | | **Requested Equipment Type Name** | Text | Equipment type the order asked for. | | **Requested Equipment Type Accounting Id** | Text | Accounting ID of the requested equipment type when the job was created. | | **Addtl Eq 1 Name / License Number / Accounting Id / External Id** | Text | Name, license plate and IDs of the first additional piece of equipment, such as a trailer. | | **Addtl Eq 1 Equipment Type (+ Accounting Id, External Id, Gross Capacity, Uom)** | Text | Type of that additional equipment, with its IDs and carrying capacity. | | **Pickup / Dropoff / Staging Site Name** | Text | Name of the site where the truck picks up, drops off or waits (staging). | | **Pickup / Dropoff / Staging Site Address** | Text | Street address of that site. | | **Pickup / Dropoff / Staging Latitude, Longitude** | Number | Map coordinates of that site. | | **Pickup / Dropoff External Id** | Text | The site's ID in your own system (for example your ERP or accounting software). | | **Pickup / Dropoff / Staging Site Pk** | ID | Tread's internal ID for that site. Use it to count or match sites, not for display. | | **Pickup Geofence Entry Count / Dropoff Geofence Entry Count** | Number | Number of times the truck entered the pickup or dropoff geofence. | | **Has Gps Data** | Yes / No | Yes if the job has any GPS data. | | **Gps Confidence Level** | Text | How complete the job's GPS data is: high, medium, low or none. | | **Gps Total Pings / Gps Expected Pings / Gps Offline Pings** | Number | GPS location pings: recorded, expected for the job's length, and sent late from offline mode. | | **Gps Active Period Minutes** | Number | Active work minutes used to judge GPS coverage, not counting pauses and breaks. | | **Travelled Distance Meters** | Number | Distance the truck travelled on the job, in meters. | | **Expected Primary Geofence Trigger Count / Actual Primary Geofence Trigger Count** | Number | Site geofence entries and exits Tread expected on the job's loads, and how many it recorded. | | **Expected Secondary Geofence Trigger Count / Actual Secondary Geofence Trigger Count** | Number | The same for loading, unloading, check-in, scale and ticketing zones. | | **Refreshed At** | Date | When this report data was last refreshed. | | **Summary Created At / Summary Updated At** | Date | When Tread created and last updated the job's report row. | | **Customer Reports Count** | Measure | Number of rows (jobs) in your result. | | **Job ID Count / Job Pk Count Distinct** | Measure | Number of unique jobs. | | **Jobs Completed** | Measure | Number of completed jobs. | | **Completed Loads** | Measure | Total completed loads across the jobs. | | **Loads With Tickets Count Sum** | Measure | Total loads that have a ticket. | | **Quantity Sum** | Measure | Total quantity across the jobs. | | **Approved Hours Sum** | Measure | Total approved hours. | | **Final Hours** | Measure | Total final work hours (approved if set, otherwise actual). | | **Final Work Time Minutes Sum** | Measure | Total final work minutes (approved if set, otherwise actual). | | **Break Minutes Sum** | Measure | Total break minutes. | | **Idle Time Seconds Sum** | Measure | Total idle seconds. | | **Ticket Time Sum** | Measure | Total ticket time, in hours. | | **Travelled Distance Meters Sum** | Measure | Total distance travelled, in meters. | | **First Sent Count** | Measure | Number of jobs sent to a vendor. | | **Sent To Driver Count** | Measure | Number of jobs sent to a driver. | | **Jobs with GPS Data** | Measure | Number of jobs that have GPS data. | | **High Fidelity / Medium Fidelity / Low Fidelity / No GPS Fidelity** | Measure | Percent of jobs at each GPS confidence level. | | **Average Gps Total Pings / Average Gps Expected Pings / Average Gps Offline Pings** | Measure | Average recorded, expected and offline GPS pings per job. | | **Average Gps Active Period Minutes** | Measure | Average active work minutes per job, not counting pauses and breaks. | ## Load Data One row per load. Load timing, cycle times, material, sites, and ticket details. | Field | Type | What it means | | - | - | - | | **Load Id** | Text | The load's ID, including any ID from your own system. | | **Load Number** | Number | The load's number within its job (1, 2, 3…), renumbered in order. | | **Ordinality** | Number | The load's position in the job's sequence. | | **Load Pk / Id** | ID | Tread's internal ID for the load. Use it to count or match loads. | | **Job Pk** | ID | Tread's internal ID for the job the load belongs to. | | **Status** | Text | Current state of the load. | | **Created At / Updated At** | Date | When the load was created and last changed. | | **Deleted At** | Date | When the load was deleted. Deleted loads keep this date. | | **To Pickup At** | Date | When the truck started heading to the pickup site. | | **Arrived Pickup At** | Date | When the truck arrived at the pickup site. | | **Loaded At** | Date | When the material was loaded. | | **To Dropoff At** | Date | When the truck started heading to the dropoff site. | | **Arrived Dropoff At** | Date | When the truck arrived at the dropoff site. | | **Unloaded At** | Date | When the material was unloaded. | | **Completed At / Load Completed At** | Date | When the load was completed. | | **Field Approved At** | Date | When someone in the field approved the load. | | **Billing Approved At** | Date | When billing approved the load. | | **Time To Pickup Minutes** | Number | Travel time to the pickup site, in minutes. | | **Time At Pickup Minutes** | Number | Time spent at the pickup site, in minutes. | | **Pickup Time Minutes** | Number | Pickup time for the load, in minutes. | | **Time To Dropoff Minutes** | Number | Travel time to the dropoff site, in minutes. | | **Time At Dropoff Minutes** | Number | Time spent at the dropoff site, in minutes. | | **Dropoff Time Minutes** | Number | Dropoff time for the load, in minutes. | | **Unload To Complete Minutes** | Number | Minutes from unloading to completing the load. | | **Cycle Time Minutes** | Number | Full cycle time in minutes, from pickup through dropoff completion. | | **Duration Minutes** | Number | Total length of the load, in minutes. | | **Gps Minutes / Total Gps Minutes** | Number | Minutes of GPS tracking on the load. | | **Has Gps Data** | Yes / No | Yes if the load has GPS data. | | **Idle Time Seconds** | Number | Seconds the truck sat idle during the load. | | **Travelled Distance Meters** | Number | Distance travelled on the load, in meters. | | **First Geofence … Entry At (Site, Pickup Site, Drop Off Site, Check In, Loading, Scaling, Ticketing, Unloading)** | Date | First time the truck entered each zone: any site, pickup, dropoff, check-in, loading, scale, ticketing, unloading. | | **Last Geofence … Exit At (same 8 zones)** | Date | Last time the truck left each of those zones. | | **Quantity / Quantity Unit** | Number | Quantity of material on the load and its unit of measure. | | **Material** | Text | Material on the load. | | **Material External Id** | Text | The material's ID in your own system (only when your company owns the material). | | **Material Type Name** | Text | Type of the load's material, such as aggregate or asphalt. | | **Phase Code / Phase Name** | Text | Code and name of the project phase for the load. | | **Pickup / Dropoff / Staging Site Name** | Text | Name of the site where the truck picks up, drops off or waits (staging). | | **Pickup / Dropoff / Staging Site Address** | Text | Street address of that site. | | **Pickup / Dropoff / Staging Latitude, Longitude** | Number | Map coordinates of that site. | | **Pickup / Dropoff External Id** | Text | The site's ID in your own system (for example your ERP or accounting software). | | **Pickup / Dropoff / Staging Site Pk** | ID | Tread's internal ID for that site. Use it to count or match sites, not for display. | | **Return Site Name** | Text | Pickup site of the next load in the same job. Empty on the job's last load. | | **Ticket Exists** | Yes / No | Yes if a ticket is attached to the load. | | **Ticket Number** | Text | Number on the ticket. | | **Ticket Pk** | ID | Tread's internal ID for the ticket. | | **Ticket Quantity / Ticket Unit Of Measure** | Number | Quantity on the ticket and its unit of measure. | | **Ticket Quantity Adjusted** | Number | Ticket quantity after someone adjusted it. | | **Ticket Service Date** | Date | Service date written on the ticket. | | **Ticket Source** | Text | Where the ticket came from, such as the driver app or an integration. | | **Ticket Uploaded At** | Date | When the ticket was uploaded. | | **Ticket Flagged** | Yes / No | Yes if the ticket has been flagged for review. | | **Ticket External Vendor Id** | Text | Vendor ID written on the ticket, from the supplier's system. | | **Ticket Material Name / Ticket Material External Id** | Text | Material named on the ticket and its ID in your own system. | | **Ticket Material Pk** | ID | Tread's internal ID for the ticket's material. | | **Ticket Ocr Processed** | Yes / No | Yes if Tread has read the ticket image automatically (OCR). | | **Ticket Ocr Ticket Number / Ticket Ocr Net Quantity Ton** | Text | Ticket number and net tons Tread read from the ticket image. | | **Refreshed At** | Date | When this report data was last refreshed. | | **Load Count** | Measure | Number of unique loads. | | **Load Count Completed** | Measure | Number of completed loads. | | **Dispatched Completed Loads** | Measure | Number of dispatched loads that are completed. | | **Active Loads** | Measure | Loads in progress, on the way to the pickup site. | | **Loads Dispatched** | Measure | Loads on the way to the dropoff site. | | **Loads (Billing Approved)** | Measure | Number of loads with billing approval. | | **% Load Approved** | Measure | Percent of loads with billing approval. | | **Ticket Exists True Count** | Measure | Number of loads that have a ticket. | | **% Ticket Uploaded** | Measure | Percent of loads that have a ticket. | | **Count of unique ticket numbers** | Measure | Number of different ticket numbers. | | **Ticket Numbers Aggregated** | Measure | All ticket numbers in the row, in one list. | | **Ticket Numbers Aggregated Hourly** | Measure | Ticket numbers for hourly work only, in one list. | | **Ticket Quantity Adjusted Sum** | Measure | Total adjusted ticket quantity. | | **Last Load or Ticket Completed At** | Measure | Latest ticket service date, or latest load completion if there is no ticket. | | **Cycle Time Minutes Average / Cycle Time Minutes Median** | Measure | Average and median cycle time, in minutes. | | **Duration Minutes Sum** | Measure | Total load minutes. | | **Time To Pickup Minutes Sum / Time To Dropoff Minutes Sum** | Measure | Total travel minutes to pickup and to dropoff. | | **Time At Pickup Minutes Sum / Time At Dropoff Minutes Sum** | Measure | Total minutes spent at pickup and at dropoff. | | **Time At Pickup Minutes Average / Time At Dropoff Minutes Average** | Measure | Average wait at the pickup and dropoff sites, in minutes. | | **Time at Pickup / Dropoff Minutes Avg (Drill by project ID)** | Measure | The same averages, set up to drill down by project. | | **Logging Count Distinct** | Measure | Number of unique time-logging records. | ## Order Reports One row per order. Customer, material, ordered quantity, and sites. | Field | Type | What it means | | - | - | - | | **Name** | Text | Order name. | | **Order Id** | Text | The order's ID, including any ID from your own system. | | **Order Pk** | ID | Tread's internal ID for the order. | | **External Id** | Text | The order's ID in an integrated system. | | **Status** | Text | Current state of the order. | | **Date Order Created** | Date | When the order was created. | | **Customer Account** | Text | Customer the order is for. | | **Creating Company / Creating Company Pk** | Text | Company that created the order, and its internal ID. | | **Department** | Text | Department the order belongs to. | | **Dispatch Number** | Text | Dispatch number on the order. | | **Po Job Number** | Text | Purchase order or job number. | | **Zone** | Text | Zone set on the order. | | **Project Pk** | ID | Tread's internal ID for the order's project. | | **Requester Pk** | ID | Tread's internal ID for the person who requested the order. | | **Foreman First / Second / Third / Fourth Pk** | ID | Internal IDs of up to four foremen on the order. | | **Material Name** | Text | Material on the order. | | **Order Material Pk** | ID | Tread's internal ID for the order's material. | | **Material Rate Unit Of Measure** | Text | Unit the material rate is charged in, such as ton or yard. | | **Quantity / Quantity Unit** | Number | Ordered quantity and its unit of measure. | | **PG Inventory Flag** | Text | Inventory flag used by one customer's integration. | | **Pickup / Dropoff / Staging Site Name** | Text | Name of the site where the truck picks up, drops off or waits (staging). | | **Pickup / Dropoff / Staging Site Address** | Text | Street address of that site. | | **Pickup / Dropoff / Staging Latitude, Longitude** | Number | Map coordinates of that site. | | **Pickup / Dropoff External Id** | Text | The site's ID in your own system (for example your ERP or accounting software). | | **Pickup / Dropoff / Staging Site Pk** | ID | Tread's internal ID for that site. Use it to count or match sites, not for display. | | **Pickup To Dropoff Distance Meters** | Number | Distance from pickup to dropoff, in meters. | | **Refreshed At** | Date | When this report data was last refreshed. | | **Order Reports Count** | Measure | Number of rows (orders) in your result. | | **Completed Order Count** | Measure | Number of completed orders. | | **Customer Account Count Distinct** | Measure | Number of different customers. | | **Sum of Quantity** | Measure | Total ordered quantity. | ## Project Reports One row per project. Customer, billing, phases, materials, and the defaults new orders and jobs start with. | Field | Type | What it means | | - | - | - | | **Name** | Text | Project name. | | **Project Id** | Text | The project's ID, including any ID from your own system. | | **Project Pk** | ID | Tread's internal ID for the project. | | **External Id** | Text | The project's ID in an integrated system. | | **External Id (4-8)** | Text | Project external IDs that start with 4 through 8. Used in construction reports. | | **Status** | Text | Current state of the project. | | **Effective At / Expires At** | Date | When the project starts and stops being active. | | **Customer Account Name** | Text | Customer the project is for. | | **Customer Account Pk** | ID | Tread's internal ID for that customer account. | | **Creating Company / Company Id** | Text | Company that created the project, and its internal ID. | | **Department / Department Pk** | Text | Department the project belongs to, and its internal ID. | | **Dispatch Number / Dispatch Number Pk** | Text | Dispatch number on the project, and its internal ID. | | **Po Job Number** | Text | Purchase order or job number. | | **Charge To Account** | Text | Account the work is billed to. | | **Service Class Name** | Text | Service class set on the project. | | **Prevailing Wage** | Yes / No | Yes if the project follows prevailing-wage rules. Changing it does not update existing orders. | | **Chase Missing Tickets** | Yes / No | Yes if Tread reminds drivers about missing tickets on this project's jobs. | | **Phase Data** | List | The project's phases, each with a name, a code and whether it is the main phase. | | **Material 1 / 2 / 3 Name** | Text | First, second and third materials on the project. | | **Material 1 / 2 / 3 Quantity** | Number | Total quantity of each of those materials. | | **Material 1 / 2 / 3 Unit Of Measure** | Text | Unit of measure for each of those materials. | | **Default Pickup Sites / Default Dropoff Sites** | List | Sites that new orders on this project start with. | | **Default Order Quantity / Default Order Unit Of Measure** | Number | Quantity and unit new orders start with. | | **Default Job Quantity / Default Job Unit Of Measure** | Number | Quantity and unit new jobs start with. | | **Default Job Time** | Number | Minutes new jobs start with. | | **Default Truck Count** | Number | Number of trucks new orders start with. | | **Default Truck Hours** | Number | Units per hour new orders start with. | | **Default Equipment Type Name** | Text | Equipment type new orders start with. | | **Default Equipment Type Gross Capacity (+ Unit Of Measure)** | Number | Carrying capacity of that equipment type, and its unit. | | **Pickup / Dropoff / Staging Site Name** | Text | Most recent pickup, dropoff and staging sites used on the project. | | **Pickup / Dropoff / Staging Site Address** | Text | Addresses of those sites. | | **Pickup / Dropoff / Staging Site Pk** | ID | Tread's internal IDs for those sites. | | **Refreshed At** | Date | When this report data was last refreshed. | | **Project Reports Count** | Measure | Number of rows (projects) in your result. | | **Completed Project Count** | Measure | Number of completed projects. | ## Company Job Assignments The rate your company pays and the rate it receives on each job. | Field | Type | What it means | | - | - | - | | **Payable Rate Type / Payable Rate Value** | Text | How the rate your company pays is charged (per hour, per ton…) and the rate. Uses the assignment rate if the job has no pricing. | | **Receivable Rate Type / Receivable Rate Value** | Text | How the rate your company is paid is charged, and the rate. Uses the assignment rate if the job has no pricing. | ## Customer Pricing and Vendor Pricing The same four pricing settings, once for the customer side of the job and once for the vendor side. | Field | Type | What it means | | - | - | - | | **Currency** | Text | Currency for all money values on the customer or vendor pricing. | | **Jurisdiction** | Text | Department of Labor prevailing-wage jurisdiction. | | **Material Rate Unit Of Measure** | Text | Unit the material rate is charged in, such as ton, yard or bushel. | | **Prevailing Wage** | Yes / No | Yes if this pricing follows prevailing-wage rules. | ## Driver Pay How the Driver is paid on the job. | Field | Type | What it means | | - | - | - | | **Rate Type / Rate Value** | Text | How the driver is paid on the job (per hour, per load…) and the pay rate. | ## Related * [Reporting](/concepts/omni-reports) — open Build a Report and save a report for your team * [Orders & Projects](/concepts/orders-projects) — how orders and projects relate * [Tickets & Timesheets](/concepts/tickets-timesheets) — where ticket and time fields come from # Companies & Hierarchy Source: https://docs.tread.ai/concepts/companies-hierarchy Single companies vs parent/child structures, and when to use each. ## What it is A Tread account is a Company. Most Tread customers run as one company. A Company can also be a Parent with Child companies underneath — used when a company has true regional splits with separate dispatchers, fleets, or books. ## Why it matters Hierarchy decides where your data lives. Drivers, equipment, customers, vendors, and rates all attach to one Company. ## How Tread models it * **Flat company** — one record. Everything lives at this level. Default for \~90% of customers. * **Parent / Child** — one Parent, two or more Child companies. * Typically the Parent company will act as a "Holding Company", where the operations will live at individual child company levels. * For example * Hold Co 1 - Hold Co users, who should have access to all children, added here * Regional Operating Co A * Dispatch Data & regional Co A users live here * Regional Operating Co B * Dispatch Data & regional Co B users live here * Users assigned to the parent can navigate "down" to every Child company. * Users added directly to Child companies can not see the data at the parent company level. * Child companies can be connected with each other, as vendors and customers to each other * **Sharing** data across companies * Operational Data should be added at the most relevant operational company level * If Trucks and Equipment, Foreman, Drivers, and Sites are all used across child companies, it makes sense to create master data at the Parent level and shared down via [Company Shares](/concepts/connected-ecosystem). * If Child companies are truly independent regions, with minimal to no overlap, data should be managed at each child co level * Connected Vendors, Connected Customers can be shared across the hierarchy * Sites should be shared from the Parent co down to child companies * Drivers, Foreman, and Equipment can be shared to any connected company | Use flat when | Use parent/child when | | - | - | | One office, one fleet, one set of books | Multiple regions with separate P\&Ls | | Dispatchers cover all work | Each region has its own dispatcher | | Single accounting export | Each region exports reports separately | ## Common pitfalls > [!TIP] > > Hierarchy is hard to undo. Confirm the structure with your Tread implementation lead before creating master data. ## Related * [Connected Ecosystem](/concepts/connected-ecosystem) — how shared entities flow between companies * [Roles & Permissions](/concepts/roles-permissions) — who can see and edit data across the hierarchy * [Onboarding: Company Hierarchy](/onboarding/company-hierarchy) — step-by-step setup # Compliance Documents Source: https://docs.tread.ai/concepts/compliance-documents Document Types, expiration tracking, and how Dispatch Gating warns dispatchers at assignment. Tread tracks every document's expiration and checks compliance when work is assigned. Dispatchers see Missing, Expiring, and Expired issues before the dispatch goes out — no manual expiration checks. ## What it is A Compliance Document is a file kept on a [Driver](/onboarding/master-data/drivers) (the user who receives a dispatch and performs it), a [Vendor](/onboarding/master-data/vendors) (an account you send dispatches to), or [Equipment](/concepts/equipment) — for example an insurance certificate, a license, or a tax form. Tread tracks each document's status and checks it when you [assign a Job](/concepts/dispatching-drivers-vendors). ## How Tread models it * **Document Type** — defined once in **Settings → Document Types**. Each type sets: * **Has Expiration** — track an expiration date. Documents show Expiring/Expired status. * **Dispatch Gating** — warn dispatchers when assigning Jobs where a document of this type is expired or missing. * **Applies To** — which records must have it: Internal Drivers, Shared Drivers, Vendors, Equipment. * **Field Type** — an optional value on each document: Text, Number, Date, or Yes/No. * **Compliance Document** — one record per Document Type per Driver, Vendor, or Equipment. Holds the file, the expiration date, and the optional value. Upload it from the Driver, Vendor, or Equipment record. | Status | What it means | At assignment (gated types) | | - | - | - | | Valid | On record, not expired | Passes | | Expiring | Expires within 30 days | Warning shown | | Expired | Past its expiration date | Issue shown | | Missing | Required, no document on record | Issue shown | | Optional | Type not required for this record | Passes | ## Dispatch Gating When you assign a Job, Tread checks every gated Document Type that applies to the Vendor, Driver, and Equipment on the assignment. Issues appear in a dialog. The dispatcher can cancel or **Assign Anyway**; each override is logged with the user and time. Document uploads and edits are also logged. When a document on a gated type is within 30 days of expiring, Tread emails your account's Admins once. Each Admin controls this with the **Compliance Expiration Warning** notification preference. > [!WARNING] > > **Gating runs at assignment.** A document that expires after dispatch does not change Jobs already assigned. The issue appears on the next assignment. ## Related * [Document Management & Dispatch Compliance](/specialized/document-management) — setup walkthrough * [Drivers](/onboarding/master-data/drivers) — where Driver documents live * [Vendors](/onboarding/master-data/vendors) — where Vendor documents live * [Equipment & Equipment Types](/concepts/equipment) — where Equipment documents live * [Roles & Permissions](/concepts/roles-permissions) — who can manage Document Types # Tread's Connected Ecosystem Source: https://docs.tread.ai/concepts/connected-ecosystem How Tread connects you with Customers, Vendors, and Drivers Tread gives every stakeholder real-time visibility and transparency into Dispatch Orders. That cuts phone calls and ETA checks and speeds up billing — every scale Ticket and report is available live, across connected accounts. ## What it is Tread's Connected Ecosystem is the four stakeholders that connect on a Project and its Orders: the Connected Customer, the Tread Customer, the Vendor, and the Driver. Each has their own access in Tread. ## How Tread enables Cross Company Collaboration * **Connected Customer** — a Customer with its own Tread account. On your Project and Order, it's the account requesting the work. * **Tread Customer** — your own account. Creates the Projects and Orders, and sends the dispatches, and receives requests from Connected Customers. * **Vendor** — an account you send dispatches to, instead of assigning your own Driver. Their Drivers reach your dispatch board through a Company Share, a one-way connection you accept. Directly dispatch to a Vendor's drivers, or enable a Vendor to dispatch to their drivers or Sub-Vendors. * **Driver** — the user who receives a dispatch and performs it. * **Owner-Operator (O\&O)** — a Vendor with a single Driver, so you dispatch that Driver directly as a Shared Driver. ## Visibility and access * **Connected Customers** have full visibility into the Orders where they are the Customer — real-time truck data, Tickets as they post, reports, and invoices. They will not have any other access into a Tread Customer's account. * **Vendors** get their own Tread access. They receive dispatches from the Tread Customer, invite and manage their own Drivers, and assign the work. They see data across accounts for the work assigned to them. * Connected Customers and Vendors manage their own users and data. The Tread Customer can also manage it on their behalf. ## Related * [Dispatching to Drivers and Vendors](/concepts/dispatching-drivers-vendors) — Internal, Shared, and Vendor drivers * [Companies & Hierarchy](/concepts/companies-hierarchy) — parent and child companies * [Equipment & Equipment Types](/concepts/equipment) — how Equipment is shared * [Roles & Permissions](/concepts/roles-permissions) — what each stakeholder sees # Custom Labels Source: https://docs.tread.ai/concepts/custom-labels Tag Drivers, Users, Customers, Vendors, and Equipment with your own labels for filtering and search. Filter your lists and reports by the categories your team already uses. ## What it is A Label is a color-coded tag you define and apply to Drivers, Users, Customers, Vendors, and Equipment. Labels are your own categorization layer — Tread does not impose meaning on them. ## How Tread models it * **Label** — a name and a color, owned by your account. Each record holds up to five of your Labels. * **Setup** — create Labels in **Settings → Labels**. * **Apply** — pick from the **Labels** field when you create or edit Drivers, Users, Customers, Vendors, or Equipment. * **Filter** — filter Driver, User, Customer, Vendor, and Equipment lists by Label. * **Private to your account** — on a record shared across accounts (a Shared Driver or shared Equipment), each account sees only the Labels it applied. ## Common use cases | Label set | Example values | | - | - | | Driver crews | Night Crew, Day Crew | | Vendor tiers | Preferred, Backup | | Internal categorization | Seasonal, Training | ## Common pitfalls > [!WARNING] > > **Don't use Labels for data that belongs in a structured field.** If you are labeling records with an Equipment Type, Department, or Service Class, use that field instead. > [!TIP] > > Start with five to ten Labels. Add more only when a real filtering or reporting need shows up. ## Related * [Departments & Service Classes](/onboarding/master-data/departments-labels-classes) — the structured fields Labels should not replace * [Onboarding: Drivers](/onboarding/master-data/drivers) — setting up Drivers * [OmniReports](/concepts/omni-reports) — build custom reports # Dispatching to Drivers and Vendors Source: https://docs.tread.ai/concepts/dispatching-drivers-vendors The three ways to send a dispatch — an internal driver, a shared driver, or a vendor. ## What it is * **Internal Driver** — your own driver, in your company. * **Driver** — an owner operator driver who has their own entity. * **Shared Driver** — a driver another company shares to you, so you assign them like your own. * **Vendor** — a hauling company you dispatch to. Their dispatcher assigns the driver. Each connects through a different stakeholder in the [Connected Ecosystem](/concepts/connected-ecosystem) — your own company, a vendor who shares a driver, or an owner operator. ## Why it matters The driver configuration primarily determines who is responsible for assigning a driver to a dispatch. ## How Tread models it | Assign to | Who it is | In the Assign panel | Billing path | When to use | Setup required | | - | - | - | - | - | - | | **Internal Driver** | Your own driver | **Driver** tab | Customer pays you, you pay your driver | Your own drivers and trucks | Internal User added under your company | | **Driver** | Owner Operator / Driver with own Entity | **Driver** tab | Customer pays you, you pay the Owner Operator Entity | An owner operator who contracts with you through their own entity | Driver added under your company | | **Shared Driver** | A driver a partner shares to you | **Driver** tab | Customer pays you, you pay the partner | A partner whose specific driver you assign yourself | Partner shares the driver to you | | **Vendor** | A hauling company that sub-dispatches | **Vendor** tab | Customer pays you, you pay the vendor | You hired a hauling company and let their dispatcher pick the driver | Vendor invited and connected | An Owner-Operator (O\&O) — a single-truck hauler who owns and drives — is the most common Shared Driver. For a Vendor, the driver's name appears on your board only after their dispatcher accepts and assigns one. ## Common pitfalls > [!WARNING] > > **Vendor jobs need an active connection.** If the vendor has not accepted the connection, your dispatch will not send. Check **Settings → Vendors** first. > [!WARNING] > > **A Shared Driver must be shared to you first.** Without the share, the driver does not appear in your Assign list. The partner shares from their side under **Settings → Drivers**. ## Related * [Connected Ecosystem](/concepts/connected-ecosystem) — how the Customer, Tread Customer, Vendor, and Driver connect * [Driver Lifecycle](/concepts/driver-lifecycle) — invite, vendor moves, deactivation * [Create a Project, Order & Dispatch](/workflows/create-a-project) — where you assign the job * [Roles & Permissions](/concepts/roles-permissions) — who can dispatch # Driver Lifecycle Source: https://docs.tread.ai/concepts/driver-lifecycle How Drivers are invited, moved between Vendors, and deactivated — and why phone numbers stay locked. Create a Driver once and every dispatch, logged hour, and Ticket attaches to that one record. Deactivating keeps that history and frees the phone number for the next Driver — no duplicate records. ## What it is A [Driver](/concepts/connected-ecosystem) is the user who receives a dispatch and performs it. The Driver record is a User with the Driver Role, and it belongs to one account: yours (an [Internal Driver](/concepts/dispatching-drivers-vendors)) or a [Vendor](/concepts/connected-ecosystem)'s. It carries the phone number, name, and equipment assignment. The lifecycle has four stages: invite, first login, day-to-day dispatch, and deactivation. ## How Tread models it * **Invitation** — an Admin creates the Driver, then sends an invite by email or SMS. SMS is the default for Drivers without a work email. The Driver taps the invite link and lands in the [Driver app](/mobile/driver-app). * **First login** — the Driver sees their assigned equipment, the day's Jobs, and a "Start Log" button. With nothing assigned yet, the app shows "Your schedule is clear." * **In review** — at shift end the Driver submits hours and Tickets. The driver-day sits in *In Review* until an [approver](/concepts/roles-permissions) signs off. * **Phone-number lock** — once created, the phone number is locked to that Driver record. This stops two people from authenticating as the same Driver. * **Deactivation** — Deactivate keeps the history (Tickets, settlements, hours) and frees the phone number for reuse. | Action | Path | Effect | | - | - | - | | Driver leaves the company | Deactivate | Phone number freed, history kept | | Driver moves from Vendor X to Vendor Y | Edit the Company on the Driver record | Same record, connected to the new Vendor | | "Phone number already in use" error | Deactivate the old record, then reuse the number | Or edit the existing record | | Driver already works at another Tread company | Contact Tread support — they connect the record across companies | One app login, history preserved. Support can't move a Driver who is active on a job — wait until it ends | | Vendor changes EIN or legal name | Create a new Vendor record | 1099s tie to the EIN — do not edit in place | ## If you're the driver and you changed companies You can't switch your own company in the app. The company that dispatches you owns your Driver record. When you move on, your new company adds you, and your old company keeps its history. What to do: * Give your new company the phone number you log in with. They add you as a Driver on that number. * If they see "phone number already taken," your record still sits with your old company. Ask them to contact Tread support to move it. * Keep the same phone number. You keep one app login, and your past hours and Tickets stay on the record. * Finish any job you have running first. Tread can't move the record while you're active on a job. You don't lose access while this happens. A dispatcher can run your jobs from the web app until your login points to the new company. See [Mobile Troubleshooting](/mobile/troubleshooting). ## Watch it How to remove a Driver, end to end: [How to delete/remove a driver in Tread Horizon](https://www.loom.com/embed/6efccff5c9814d748d4d8dd2e2e390bc) ## Common pitfalls > [!WARNING] > > **"Phone number already in use" means an active Driver record already has that number.** Deactivate the old Driver record — that frees the number — then create the new one. Or edit the existing record instead of creating a duplicate. > [!WARNING] > > **EIN or legal-name changes on a Vendor require a new Vendor record.** 1099s are issued against the EIN at the time of payment. Editing the EIN on an existing Vendor will misreport prior payments. > [!WARNING] > > **A driver's role changed — employee to Owner-Operator, driver to office User? Edit, don't re-create.** A regional hauler's employee driver bought a truck and became an Owner-Operator. Re-creating the Driver split the ticket history across two records and broke pay history. Change the role on the User record instead: open **Settings → Users**, find the person, and edit the role. Phone number, history, and pay records stay on one record. If the edit is blocked with "phone number already taken," contact Tread support — don't delete and re-add. See [Roles & Permissions](/concepts/roles-permissions). > [!WARNING] > > **The driver already worked at another Tread company.** A regional hauler hired an experienced driver and saw "phone number already taken." The existing record sits at the prior company — not yours. Drivers do not have a self-serve Connect flow today (vendors and customers do). Contact Tread support with the driver's name, phone number, and your company. Tread links the record across companies. Your dispatch can then assign the driver and they keep one app login. ## Related * [Connected Ecosystem](/concepts/connected-ecosystem) — how Drivers, Vendors, and Customers connect * [Dispatching to Drivers and Vendors](/concepts/dispatching-drivers-vendors) — Internal, Shared, and Vendor drivers * [Roles & Permissions](/concepts/roles-permissions) — what a Driver sees vs an Admin * [Onboarding: Drivers](/onboarding/master-data/drivers) — step-by-step Driver setup * [Mobile Troubleshooting](/mobile/troubleshooting) — fix login and dispatch issues # Equipment & Equipment Types Source: https://docs.tread.ai/concepts/equipment Trucks, trailers, and the Equipment Types that set capacity and unit of measure. Add your Trucks and Trailers in Tread's Equipment table. You can manage Equipment information, Compliance data with our Document Types feature, Accounting IDs and Ticket Matching IDs. You can additionally pair Trucks and Trailers with your Drivers. Equipment Types allow capacities and unit of measures to be set on an Equipment Type, so that it defaults over based on the truck selection. ## What it is An Equipment Type is a customizable template — "Tri-Axle Dump", "End Dump", "Belly Dump" — that holds a default capacity and unit of measure (UoM). Equipment is an individual truck or trailer record, attached to one Equipment Type. Types come first; every Equipment record requires a Type and inherits capacity and UoM from it. > [!NOTE] > > On the order form this field is labeled **Truck Type**. Truck Type and Equipment Type are the same thing. ## How Tread models it * **Equipment Type** — name, default capacity, and UoM (tons, yards, loads, hours). Tread uses these to calculate quantities on [Tickets](/concepts/tickets-timesheets) and reports. * **Equipment** — an individual truck or trailer record: name, license plate, and the Equipment Type it belongs to. The name appears on Tickets and invoices. * **Sharing** — Equipment can be shared to another account through a Company Share, a one-way connection between accounts, so both accounts see the same Equipment record. See [Connected Ecosystem](/concepts/connected-ecosystem). | Field | Lives on | Function | | - | - | - | | Capacity | Equipment Type | Calculates quantities on Tickets and reports | | UoM | Equipment Type | Sets the unit those quantities use | | Name | Equipment | Appears on Tickets and invoices | | License plate | Equipment | Identifies the individual truck or trailer | ## Common pitfalls > [!WARNING] > > **An Equipment Type without capacity or UoM breaks quantity calculations.** Every Equipment record requires a Type, but capacity and UoM are optional on the Type. > [!WARNING] > > **Equipment names appear on Tickets and invoices.** Renaming Equipment mid-billing-cycle changes what prints on new Tickets and invoices. Set naming conventions before importing. ## Related * [Materials](/concepts/materials) — what Orders move * [Connected Ecosystem](/concepts/connected-ecosystem) — how connected accounts share records * [Onboarding: Equipment Types](/onboarding/master-data/equipment-types) — step-by-step Equipment Type setup * [Onboarding: Equipment](/onboarding/master-data/equipment) — step-by-step Equipment setup # Materials Source: https://docs.tread.ai/concepts/materials The Material record — its fields, how Material Rates price it, and bulk import. Materials give every stakeholder their own materials list. Orders, Tickets, invoice line items, and accounting exports all reference the same Material. ## What it is A Material is the record for what is set on the [Order](/concepts/orders-projects). Each Material has a Name, a Material Type, and an External ID. Pricing lives on separate Material Rate table. ## How Tread models it * **Material** — Name, Material Type, and Material ID. Owned by your account. * **Material Type** — the category the Material belongs to. Defaults to "Other." * **Material ID** — your unique ID for the Material. This ID can only be used 1 per material. Use the same ID as your accounting system so exports match. * **Material Rate** — prices a Material: a unit of measure (Ton, Yard, Load) plus buy and sell prices. Set per [Customer](/concepts/connected-ecosystem), per Project, per [Site](/concepts/sites-geofences), or globally. See [Rates, Add-Ons & Fuel](/concepts/rates-add-ons). * **Bulk import** — Materials can be created one at a time or imported from CSV. | Field | Required | Notes | | - | - | - | | Name | Yes | Unique within your account; the label users see on Orders and [Tickets](/concepts/tickets-timesheets) | | Material Type | No | Defaults to "Other" | | Material ID | No | Unique within your account; match your accounting system so exports line up | ## Related * [Rates, Add-Ons & Fuel](/concepts/rates-add-ons) — how Material Rates are set * [Prevailing Wage](/specialized/prevailing-wage) — the Prevailing Wage workflow * [Onboarding: Materials](/onboarding/master-data/materials) — step-by-step setup # Reporting Source: https://docs.tread.ai/concepts/omni-reports Tread reports cover export files, scheduled report deliveries, dashboards, and visualizations. Build your own with Build a Report. Tread comes with more than a dozen default reports. Build your own with **Build a Report**, or ask Tread to configure a custom report based on your subscription plan. ![Clean Shot 2026 07 12 At 08 04 47@2x](https://mintcdn.com/treadtechnologiesinc/6YBsddpx2sP2RIKn/images/CleanShot-2026-07-12-at-08.04.47@2x.png?fit=max\&auto=format\&n=6YBsddpx2sP2RIKn\&q=85\&s=1b8108e5e8dbd9482b647b79f354699f) ## What it is Reports is Tread's custom report library. Each report renders live inside Tread, alongside the standard reports in [Exports & Reports](/workflows/exports-reports). When your team needs a report that does not exist yet, build it yourself with Build a Report, or ask Tread to configure it for your account. ## How Tread models it * **Report** — a saved report that renders inside Tread. Tread configures reports for your account, or your team builds them with Build a Report. System reports are available to every account. * **Category** — a group of reports. The report list is organized by category. * **Data scope** — a report shows data for your company and its [child companies](/concepts/companies-hierarchy). * **Time zone** — a report renders in the viewing user's time zone. ## When to use Reports vs Exports | Use [Exports & Reports](/workflows/exports-reports) when | Use OmniReports when | | - | - | | The report you need is already there | The report does not exist yet | | You need a scheduled export or an accounting push | You need a custom report, live in Tread: build it yourself or ask Tread | ## Build your own report **Build a Report** opens a report builder inside Tread. Pick fields, filter, and group your own data, then save the report for your team. **1. Open Build a Report** Go to **Reports**. In the **Dashboard** category, click **Build a Report** (1). The builder opens in your company's folder. Click **New** (2), then **Workbook**. ![Reports page with Build a Report selected and the New button highlighted](https://mintcdn.com/treadtechnologiesinc/6YBsddpx2sP2RIKn/images/concepts/build-a-report-open.png?fit=max\&auto=format\&n=6YBsddpx2sP2RIKn\&q=85\&s=cd311fedec19d5d3e0091a35d62eeafa) **2. Pick Customer Reports** Under **Topics**, pick **Customer Reports**. It holds job, load, order, project, and pricing data. Choose fields, then add filters and groupings to shape the results. ![Report builder start screen with the Customer Reports topic highlighted](https://mintcdn.com/treadtechnologiesinc/6YBsddpx2sP2RIKn/images/concepts/build-a-report-builder.png?fit=max\&auto=format\&n=6YBsddpx2sP2RIKn\&q=85\&s=b24f4493bb512a4b9f89dd36eb086b37) **3. Save it for your team** Click **File**, then **Save...**. Save the report to your company's folder. Everyone in your company with report access can open and edit it there. > [!TIP] > > Reports saved to **My documents** are visible only to you. ### Find your data After you pick **Customer Reports**, the left panel lists its views. Each view holds one kind of record. Open a view to see its fields, then click a field to add it as a column. ![Left panel of the report builder listing the eight views in the Customer Reports topic](https://mintcdn.com/treadtechnologiesinc/6YBsddpx2sP2RIKn/images/concepts/build-a-report-views.png?fit=max\&auto=format\&n=6YBsddpx2sP2RIKn\&q=85\&s=8934609293fadd1e1c8a53259038ee48) | View | What it holds | | - | - | | **Customer Reports** | Jobs, one row per job | | **Load Data** | Loads and their tickets, one row per load | | **Order Reports** | Orders, one row per order | | **Project Reports** | Projects and their defaults, one row per project | | **Company Job Assignments** | The rate your company pays and the rate it receives on each job | | **Customer Pricing** | Pricing settings on the customer side: currency, prevailing wage, jurisdiction, and material rate unit | | **Vendor Pricing** | The same pricing settings on the vendor side | | **Driver Pay** | How the Driver is paid on the job, and the pay rate | For every field and what it means, see [Build a Report fields](/concepts/build-a-report-fields). ### Work with fields ![Load Data fields in the left panel, with the options menu open on Cycle Time Minutes showing its description and Filter, Pivot, and Bin](https://mintcdn.com/treadtechnologiesinc/6YBsddpx2sP2RIKn/images/concepts/build-a-report-field-menu.png?fit=max\&auto=format\&n=6YBsddpx2sP2RIKn\&q=85\&s=3806d0d31e87d0902abc328b52a6d4db) | Control | What it does | | - | - | | **Search** | Finds a field by name across every view. | | **In-use** | Shows only the fields already in your report. | | Field icon | **#** is a number, the calendar is a date, and **A** is text. | | **⋮** on a field | Shows the field's description. Also lets you **Filter**, **Pivot**, or **Bin** on it. | | **Run** (▶) | Runs the report and shows the rows. | | **Results**, **Chart**, **Both** | Shows the rows, a chart, or both. | | Formula bar | Type **=** to add a calculated column. | ### What Build a Report shows * **Your data only** — reports show data for your company and its [child companies](/concepts/companies-hierarchy), like every other report. * **Pricing** — rates and pricing fields are included. > [!NOTE] > > Build a Report does not include Omni's AI assistant. For a report you cannot build with the available fields, contact [support@tread.io](mailto:support@tread.io). ## Access > [!WARNING] > > **OmniReports requires report access.** Viewing reports is gated by the user's [Role](/concepts/roles-permissions). If a user cannot open OmniReports, check their Role. ## Related * [Exports & Reports](/workflows/exports-reports) — standard reports, scheduled exports * [Build a Report fields](/concepts/build-a-report-fields) — every field in the Customer Reports topic * [Roles & Permissions](/concepts/roles-permissions) — who can view reports * [Companies & Hierarchy](/concepts/companies-hierarchy) — the data scope for parent and child companies # Orders & Projects Source: https://docs.tread.ai/concepts/orders-projects The work — from a multi-day Project down to a single daily Order. Projects represent long standing work for a Customer. Project allows tracking against more than 1 day of work. The Project ends up acting as a template across required objects — Customer, Sites, Materials, rates — and every daily Order with that project selected inherits it. The Order captures a single day's required trucks or quantity to be dispatched. Orders are utilized on a daily basis, each new day gets a new order. ## What it is A Project is the long-lived record for the work. It may run for a day or a year, and it holds everything the daily work inherits. An Order is one day of that work — the unit you dispatch. A Job is one truck's assignment on an Order. One Project can hold dozens of Orders; one Order can hold many Jobs. ## How Tread models it * **Project** — spans the duration of the project, can be many weeks, months, or years. Holds the [Customer](/concepts/connected-ecosystem), the [Sites](/concepts/sites-geofences) (pickup and dropoff), the [Materials](/concepts/materials), the [rates](/workflows/project-rates), and the date range. * **Order** — single day. Holds the date, shift, [Equipment](/concepts/equipment) requested, Drivers assigned, and the target quantity. * **Job** — Also referred to as a dispatch, or a TRD. One truck's assignment on an Order. Holds the Driver, the Equipment, and the matched rate. An Order with five trucks has five Jobs. * **Dispatch board** — lists every Order for a given day. Can be navigated with a calendar like experience. Fully searchable and filterable. ## When to use Projects Projects can be one of the most powerful, time saving features in Tread. Use a project to create templates for types of work, or to save all information for a customer in a single location. Projects can by duplicated using the Copy & Edit feature. Projects are also the basis for Tread's Quoting features. All rates can be setup in a Project. This allows the daily Order to inherit all templated data across the full project, making the daily order setup as simple as a few clicks. ## Order setup There are three ways our customers most typically create Projects and Orders. * **Running - example "3 Trucks Running"** * When there is no max loads - and when a truck is expected to deliver as many loads as possible, select "Load" as Unit of Measure (UoM) and then select the "Running" option * This allows the drivers to add as many loads as they desire to a given dispatch, and automatically adds another load to the drivers dispatch when they unload their current load * You can also set a Target # of loads while still "Running" → displays as Running (5) ![Clean Shot 2026 07 12 At 16 43 47@2x](https://mintcdn.com/treadtechnologiesinc/6YBsddpx2sP2RIKn/images/CleanShot-2026-07-12-at-16.43.47@2x.png?fit=max\&auto=format\&n=6YBsddpx2sP2RIKn\&q=85\&s=a398affe0d910642c2d66254cc0ea756) * **Load Count - example "3 Trucks 5 Loads each"** * When you are dispatching a specific load count - like 5 loads. The driver will not be able to add more than 5 loads. The mobile app will progress the driver through their 5 loads, and end the job on the 5th load * The driver can not add more than 5 loads to the dispatch ![Clean Shot 2026 07 12 At 16 44 38@2x](https://mintcdn.com/treadtechnologiesinc/6YBsddpx2sP2RIKn/images/CleanShot-2026-07-12-at-16.44.38@2x.png?fit=max\&auto=format\&n=6YBsddpx2sP2RIKn\&q=85\&s=567ed4b8d0c7671a0a1f604ed41af9fc) * **Quantity in a specific Unit of Measure, like Tonnage - example "3 Trucks 125 Tons each"** * When a specific quantity is set with a Unit of Measure (not load) the dispatch is automatically set as running, as trucks may have unique equipment capacities that are unspecified at the time of dispatch * The dispatch will automatically end after a single load if the dispatch is calculated as a "partial load" for example 5 Yards, or 12 Tons * If material tickets are not uploaded, Tread will look to the set equipment capacity on the truck type to automatically track delivered quantities ![Clean Shot 2026 07 12 At 16 44 49@2x](https://mintcdn.com/treadtechnologiesinc/6YBsddpx2sP2RIKn/images/CleanShot-2026-07-12-at-16.44.49@2x.png?fit=max\&auto=format\&n=6YBsddpx2sP2RIKn\&q=85\&s=661f2b56edfb492f1cbacb87d2489f35) Three fields on an Order control how work is measured and when a Job ends: * **Units** — the unit of measure: Load, Ton, Hour, and others. * **Quantity** — the target per truck. On a Load Order with Running unchecked, the Job stops when the Driver reaches the target. * **Running** — the Order keeps adding loads as Drivers complete them, past the target or with no target set. The standard setups — Running, Running with Target, Loads, and Tonnage — are in [Common Types of Orders](/workflows/order-types). ## Order Start Time and Truck Start Time