How to Automate Trux

A hauling day is counted in loads, not hours

An aggregate producer sells stone by the ton and delivers it by the truckload. On a busy day forty trucks leave the quarry, a few owned by the plant and most owned by whoever picked up the phone that morning.

Trux is dump truck logistics software for that trade. Producers of aggregate, asphalt, sand and salt run on it, and so do heavy and civil contractors, fleet owners, owner operators, brokers and the municipalities that push snow in January.

It comes in pieces. TRUX Deliver runs the plant side, TRUX Manage covers a fleet's own and regular haulers, and TRUX Find reaches the Trux Marketplace when you need trucks you do not have. TRUX Drive is the app in the cab and TRUX Delivery Tracker is what the contractor watches.

Between them they hold the whole day: which hauler took which load, when the truck punched in, what the scale said and how long it sat at the site.

Tickets pile up faster than anybody bills them

The office work starts once the last truck is back.

Somebody totals the day, loads and tons by jobsite, by hauler and by material, and types it into the sheet the owners read. Somebody prices those loads into invoices, which means opening each customer's completed tickets and working out tons times rate plus the haul. Somebody compares the scale tickets against what was dispatched and against what was invoiced, because the three do not always agree and the difference is money.

The day itself is a person watching numbers. A truck has been sitting at a jobsite for fifty minutes and nobody has told the super. A hauler who promised eight loads is on four at noon. A round trip that took fifty minutes is taking seventy, and nobody notices until the job runs short. A third party hauler cancels at ten and four loads have no truck under them.

Trux

The day totalled without a clipboard Loads and tons added up by jobsite, hauler and material each evening, and written into the sheet the owners actually open.

Three records that finally agree Scale tickets checked against dispatched loads and against what was invoiced, with every exception listed on one worksheet.

A wait flagged while it is still a wait Jobsite dwell time watched against your threshold, so a truck sitting for fifty minutes is raised rather than discovered on a bill.

Digital dispatching ends when the last truck punches out

None of that is a complaint about the software, which does the hard part properly.

Dispatching is drag and drop, with load stacking, reassignment and automated load planning that works out how many loads and trucks an order needs. Job details and changes are pushed to haulers instead of phoned through. GPS shows where every active hauler is and keeps time stamped route history, so cycle times at the plant and the jobsite are measured rather than guessed. E-ticketing sends scale data straight from the weighbridge to the hauler's app, to dispatch and to the customer, which ends the hunt for a lost paper load slip. Digital punch in and out, automatic shift fee calculation and consolidated invoices cover the third party haulers.

All of it stays inside hauling.

Your accounting system is not in there, nor is the sheet the owners read, the site super's mobile number or last month's cycle times. Trux knows a truck waited fifty five minutes at a jobsite. Turning that into a text to the super, a line in a variance report and an invoice is a person with two tabs open.

Loads that turn into tickets, totals and invoices on their own

Start at the scale house.

A truck loads out, the weigh data is read, the e-ticket is built and logged, and the email to the contractor is drafted before the truck reaches the gate. By evening the day has added itself up: loads and tons by jobsite, hauler and material, posted to the team and drafted as a note to the owners. Scale tickets are matched against dispatched loads and against what was invoiced, and every exception lands on one worksheet. Each customer's tickets are priced into a draft invoice, itemised by tons and haul, and left unsent.

The daytime version is a watch, not a report. Jobsite dwell time compared against your threshold, so a fifty minute wait reaches the owner while it is still happening. Each hauler's completed loads measured against the pace they committed to, so a shortfall shows at eleven, not at six. Quarry to jobsite round trips measured against target every hour. A cancelled hauler turned into a ranked list of replacements with the offer already written.

Keep the split honest. Reading Trux, totalling it and comparing it against another system runs unattended. Anything that reaches a hauler, a site super or a customer is drafted and waits, because a text sent to the wrong super at seven in the morning gets remembered.

Dispatchers move trucks, not spreadsheets

Moving trucks is a skill. Retyping load slips into an accounting system is not, and it takes the same hours out of the same day.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens Trux, reads the tickets, the GPS and the loads, and writes what it finds into the sheet, the channel or the draft invoice your office already uses.

It runs on your schedule in your own private environment, and you can watch a run and stop it. Anything that goes out to a hauler or a customer is drafted and waits for a person.

The workflows below are already built, and each one names what it signs into.