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 it is

A Compliance Document is a file you keep on a driver or vendor — DOT card, insurance certificate, MVR, drug screen, W-9 — with an expiration date. Tread tracks the status of each document and uses it to gate dispatch.

​
Why it matters

Public-works, union, and large-GC jobs require proof that every driver and vendor on site is legal. Manually tracking expirations across a fleet is where compliance breaks. Tread flips it: docs live with the driver or vendor, expiration is tracked automatically, and the next dispatch fails before a non-compliant truck rolls.

​
How Tread models it

  • Document type — master data. Defined once in Settings → Compliance. Examples: Insurance, CDL, Drug Screen, W-9.
  • Document record — one file per type per driver or vendor. Has an upload date, expiration date, and optional notes.
  • Expiration policy — how long a doc is valid (1 year, 3 years, custom).
  • Dispatch gating toggle — per document type, set whether a missing or expired doc blocks dispatch outright or just warns the dispatcher.
  • Audit trail — every upload, edit, and override is logged with the user and timestamp.
Document stateWhat it meansEffect on dispatch
On fileUploaded, not expiredPass
Expiring soon30/14/7 days outReminder sent, dispatch still allowed
ExpiredPast expiration dateBlock or warn (per gating toggle)
MissingNo record existsBlock or warn (per gating toggle)
Drivers upload their own documents from the Driver App. Vendor admins upload through their portal. Office admins can upload on anyone’s behalf. Expiration reminders fire at 30, 14, and 7 days by email or SMS. The audit trail shows who uploaded, who overrode a block, and when.

​
Common pitfalls

Vendor docs are owned by the vendor, not by you. If a vendor refuses to upload, you cannot fix it from your side. Set the expectation during vendor onboarding — no docs, no dispatch.
An expired doc blocks the next dispatch, not the current shift. A document expiring mid-shift will not pull a driver off the active load. The next dispatch attempt will fail. Run a weekly expiration report to avoid Monday-morning surprises.