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 (the user who receives a dispatch and performs it), a Vendor (an account you send dispatches to), or 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.
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.
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.
Gating runs at assignment. A document that expires after dispatch does not change Jobs already assigned. The issue appears on the next assignment.
