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.
Prevailing Wage support is coming soon. Phase 1 covers California, Nevada, Minnesota, New York, and federal Davis-Bacon work. Reach out to your Tread contact if you have a PW project in flight.
When to use this
Public-works projects often require prevailing wage (PW) — a county-set hourly rate that covers base pay, fringe benefits, and overtime rules. If your work is funded by a government body, PW likely applies.
How it works
A project (a container for related work) gets flagged as prevailing wage. From there, three things happen.
Classification follows the truck. The PW rate is determined by what the truck is doing — a tri-axle dump on hauling work hits a different classification than a tractor-trailer on the same job. When the truck changes, the suggested classification changes too. A dispatcher confirms or overrides it.
Materials carry their own PW flag. A project being PW does not auto-mark its materials as PW. You flag PW materials (the products you haul or supply) on the material itself. Tread treats material PW separately from labor PW.
Corrections happen during approval. Billers can edit the classification, base rate, fringe, benefit credit, and overtime rate on any unlocked invoice. The system auto-fills as a starting point. Humans have the final word.
Common pitfalls
PW classification is per truck, not per driver. The same driver can hit two different PW rates in one shift if they switch trucks. Don’t assume one driver = one rate for the day.
Project PW does not flow to materials. A PW project with non-PW-flagged materials will under-bill. Confirm both the project and each PW material are flagged before going live.
