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 this solves

A 50-truck day generates 400 tickets. Most billing teams spend the next morning typing them into a spreadsheet — and then a person spends another four hours reconciling weights against dispatch. That’s where the headcount problem starts: every ticket is a person-hour. This workflow puts two AI agents on it. Ticket Chaser reads the ticket image and pulls the fields. AI Auto Approvals scores each load against tolerance rules and queues the clean ones. You only touch the exceptions.

​
Walkthrough

1

Open the Approvals queue

Go to Approvals → Loads. Every captured load lands here, grouped by job and date. The AI confidence score sits next to each row.
2

Review what Ticket Chaser pulled

Each load shows the parsed ticket fields — number, gross, tare, net, material, timestamps — beside the ticket image. Click a row to see the side-by-side comparison and any flags.
3

Let AI Auto Approvals score the load

The agent compares the ticket weight, time onsite, cycle time, and material against the order’s tolerances. Loads inside tolerance get a green check. Loads outside tolerance get an amber flag with the reason.
4

Bulk-approve the clean loads

Filter to Auto-Approved and click Approve All. These move straight to the next stage — billing, settlements, or driver pay. Most operators approve 70-90% of a day’s loads in one click.
5

Resolve the flagged loads

Open Needs Review. Each flagged load shows the rule it broke (e.g., “weight 24% over capacity”) and a recommended action. Edit, accept, or reject. The agent learns from each decision.
6

Send approved loads downstream

Approved loads flow into Settlements & Driver Pay and into customer invoices. No re-export, no re-keying.

​
Watch it

​
Common pitfalls

Tolerances drive everything — set them before you trust the agent. AI Auto Approvals only flags what falls outside the rules you configured. A producer onboarding without setting per-material weight tolerances will see every load auto-approve, including the bad ones. Configure tolerances in Settings → Agent Configurations before turning the agent on.
OCR is informational — it doesn’t gate the approval. Ticket Chaser parses ticket fields fast, but a misread doesn’t block the load. If a ticket image is blurry or tilted, the parsed weight may be wrong. Always glance at the image on flagged loads.