Loaded vs empty travel you can prove
The fleet report says utilization is high. Drivers say half the shift is empty looping. Both can be right if nobody measured the path.
Why bookings cannot split loaded from empty
A closed warehouse task or radio job proves someone moved something. It does not prove how many meters (feet) the truck drove without a load before pickup or after drop. That gap is empty travel. Industry telematics and RTLS writing makes the same split: transaction systems describe ownership, movement data describes usage. Plants that still argue empty share in the weekly meeting are usually reading confirmations, not paths.
Logistics tracking closes the argument when movers carry continuous RTLS location, typically at medium precision around 1–3 m (3–10 ft) for aisle and buffer work. While a task is open, or across a shift window, the platform stores route, travel time, and distance. Loaded segments need a task or load signal. Empty segments are the motion without that signal. Engine hours alone count motion. They do not label empty versus loaded.
What proof looks like on the hall
Proof is a path overlay people recognize, not a single utilization percentage. Spaghetti and heat views show where empty loops cluster. A truck that looked busy on hour meters may show long empty triangles between the dock and the north supermarket. twinzo keeps those paths in the spatially oriented dataset under the live map so empty-share cuts, stored history, and correlation and causality analytics on repeating loops share one record.
Event-driven AOS on tracked trucks strengthens the label: acceptance binds a job to a mover, so the path during the open work order is easier to call loaded. Classic ERP guidance without localization still optimizes assignment against assumed distances. That comparison is under AOS on tracked forklifts vs SAP-state forklift guidance. Path impact framing sits under real travel paths on the floor.
A typical empty loop the booking never saw
A driver drops at line 3, hears a radio need at line 7, drives empty across the spine, finds the cage already taken, and loops back toward staging. The WMS may show one closed drop and later one unrelated pickup. The empty kilometres (miles) between them never appear. Continuous location with task context shows the empty spine crossing as a counted segment. Congestion that forms on that spine from many such loops is under congestion on shared aisles from the track.
Free-truck claim that prevents some empty searches in the first place is under where the free forklift actually is. Object choice when you also need load sit after drop is under tagging the mover vs tagging the material.
Limits you should name up front
Mover-only tags cannot see a cage that sits after drop. They can still measure empty truck motion. Inferring load without task acceptance or a weight signal will mislabel some hops. Coarse wing presence is too blunt for empty-share percentage. Fund medium-precision continuous track if empty kilometres (miles) are the decision you will fund against. Accuracy language is under zone presence vs medium-precision logistics track.
How teams decide empty share is measured
1. Ask for last month's empty kilometres (miles) as a number, not a feeling - If the room debates, you have bookings without paths.
2. Require path history on the same hall as open jobs - Separate telematics spreadsheets recreate folklore.
3. Bind load state to acceptance or a load signal - Motion alone is not empty-share proof.
4. Review one repeating empty cluster for two weeks - If layout or call-off changes do not move it, the label or coverage is wrong.
Measured travel and fleet load sit under internal logistics optimization, with depth on the features overview and ordering on material order automation. Pricing is under pricing.
Get in touch if you want to walk whether your empty travel is already a measured path, or still a shift argument.