Load Status
Load Status is the wall a dispatcher watches all day — every shipment in the company shown as a card in a lane, on a map, or on a driver calendar, so that moving a load from "booked" to "on the truck" to "delivered" is one drag, and the system refuses the moves that would corrupt the money behind them.
From the Lanexa 2.0 capability register · version 2.0.37 · reviewed 2026-08-24
What happens on its own.
The work nobody does. These run in the database rather than the browser, which is why they still happen when someone forgets, closes the tab, or was never told they were supposed to.
An audit line is written for every status change
Phrased as a sentence — "*name* changed *load* from *A* to *B*" — and stamped with the acting user's id and name (). Audit writing is deliberately fail-quiet: if the log write fails, the business operation is not blocked ().
That audit line becomes a Journey event
A database rule reads each new activity row for a load, takes the *destination* status out of the fixed "… from A to B" sentence shape, and files a matching event on the load's timeline (). The earlier version searched the sentence for stat
An assignment is narrated too
Changing a driver, co-driver or truck writes its own audit line containing the word "assigned", so the projector types it correctly (). Before this, assignment left no trace at all — measured at 6 of 1,319 driver-carrying loads having a liv
The status trail is appended atomically, by the database
Sanctioned routines append it themselves inside the same statement that changes the status, so two dispatchers acting at once cannot lose an entry; any other writer has an entry appended for it by the trigger, marked (, ).
What you can do here.
Every item below is live in production today. Anything not yet built is listed further down rather than left out.