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 Label is a color-coded tag you define and apply to orders, projects, or jobs. Labels are your own categorization layer — Tread does not impose meaning on them.Why it matters
Every operator has cuts of their work that don’t fit a standard field. Priority. Customer-specific tags. Internal categorization. Dispatch flow exceptions. Labels give dispatchers, billers, and reports a way to filter on those cuts without inventing new fields.How Tread models it
- Label — a name, a color, and the entity types it applies to (orders, projects, jobs).
- Setup — create labels in Settings → Labels.
- Apply — pick from a dropdown when creating an order or project. Bulk-apply via the bulk-edit action on the dispatch board.
- Filter — every list view (dispatch board, project list, approvals queue) accepts label filters.
- Search — labels show up in global search results.
Common use cases
| Label set | Example values | Used by |
|---|---|---|
| Priority | Hot, Standard, Backfill | Dispatchers |
| Customer-specific | KP Top Account, NDA Required | Sales, billing |
| Internal categorization | Test Job, Internal Move | Ops |
| Dispatch flow | Foreman Created, Manual Approval | Approvers |
Common pitfalls
Related
- Departments & Service Classes — the structured cousins of labels
- Orders & Projects — where labels apply
- OmniReports — filter custom reports by label