When we were designing the RouteLyft coordinator interface, we started from a straightforward assumption: logistics coordinators would primarily use the live map. A real-time map showing the position of every active shipment is visually compelling, immediately graspable, and looks exactly like what a freight visibility platform should provide. Every major visibility tool we studied led with a map. So did our first prototypes.
Three months of structured user research with logistics coordinators at growing EU freight operators challenged that assumption more directly than we anticipated.
How the study was structured
Between February and May 2025, we ran observation sessions with logistics coordinators at three early-access freight operations: a Hamburg-based forwarder managing primarily DE→PL and DE→CZ cross-border lanes with around 60 active shipments per day; a Rotterdam-based 3PL handling NL→DE and NL→AT loads at approximately 40 active shipments per day; and a smaller Düsseldorf-based regional operator running mixed EU lanes at around 25 shipments per day.
These were not controlled usability studies. They were working sessions — coordinators doing their actual jobs while we observed, noted what they clicked, and asked them to narrate their thought process when they were comfortable doing so. We supplemented the observation notes with lightweight session instrumentation: which interface views were opened, in what order, and for how long, during sessions where a shipment had an active exception versus sessions where all shipments were running normally.
Across roughly 400 active shipment management sessions, one pattern emerged with enough consistency to revise our product assumptions.
The finding: coordinators reach for the event log first under pressure
During exception management sessions — defined as any session where the coordinator was actively responding to a delay alert, a customs hold notification, or a customer inquiry about a specific shipment — coordinators opened the timeline event log as their first action in approximately 70% of sessions. The live map was first in around 18% of exception sessions. The remaining sessions went directly to the shipment detail summary card.
This inverted our initial design assumptions. During routine monitoring — coordinators doing a status sweep of all active shipments without a specific alert — the live map was accessed more frequently, in roughly half of sessions. But routine monitoring is not where the platform's value is tested. Exception management is where the critical decisions happen, and there, coordinators consistently preferred temporal context over geographic context.
Why the event log wins under pressure: the coordinator's actual question
The observational sessions gave us the qualitative data to understand the pattern. The reasoning was consistent across coordinators at all three sites and amounted to the same underlying logic: a map tells you where something is; the event log tells you what happened and in what order.
When a coordinator receives an alert that shipment SHP-2025-04137 has a customs hold on the Hamburg→Prague lane at the Bad Brambach crossing, opening the live map shows a stationary dot near the German–Czech border. That is useful confirmation that the vehicle is where it should be — but it does not answer any of the questions the coordinator needs answered to act. When did the vehicle arrive at the border? Was the NCTS pre-declaration submitted and accepted? Has a CC007C arrival notification fired? How long has it been stationary since arrival? Is there a T1 document discrepancy in the event record? What is the carrier's updated ETA?
The timeline event log answers all of these questions in sequence. The coordinator sees: departure Hamburg 06:42, position update A17 motorway 08:19, arrival at Bad Brambach approach 09:51, NCTS CC007C arrival notification 09:57, last position update 09:57, current time 13:20 — two-plus hours since formal customs arrival with no CC025C release message. That is an actionable picture. The map version of the same information is a dot that has not moved for three hours.
The map's actual use cases
We observed two specific scenarios where coordinators reliably reached for the map rather than the event log. The first was situational awareness across the full active fleet: a quick visual scan at the start of a shift or after returning from a break, looking for anything obviously off-course. This is coarse-grained — the coordinator is looking for geographic anomalies visible at fleet zoom level, not investigating specific events. It is a useful first-pass filter but not a decision-making tool.
The second was geography-specific queries during active exceptions: "where is this truck relative to the border crossing?" or "has the vehicle exited the motorway and is it on the approach road?" For these questions, the map provides a more intuitive answer than the event log, particularly when the coordinator is less familiar with the specific route geography.
This is not to say the live map is the wrong tool for freight tracking — it is the right tool for these specific questions. The problem is that most freight visibility platforms are built with the map as the primary interface and the event log as a secondary detail view, when the operational priority for exception management runs the other way.
The design revision: event log as first-class view
In our initial prototypes, the event log was a collapsible section below the shipment summary card — readable but visually subordinate. Based on the user study findings, we redesigned it as the default expanded view in the shipment detail panel, with the live map available as a secondary tab. The coordinator's exception dashboard sorts shipments by exception priority and shows the first relevant timeline event for each flagged shipment without requiring any click-through.
More significantly, we added what we call event expectation tracking to the timeline. For each shipment in active cross-border transit, the system maintains a model of which events are expected and when, based on the shipment's route and the typical customs processing cadence for that border crossing. When an expected event does not arrive on schedule, the gap itself becomes a visible entry in the timeline: CC025C customs release — expected by 11:30, not yet received (now 13:15, 1h 45m overdue).
This negative event flagging — surfacing what did not happen — was the single most consistently requested feature we heard across all three observation sites. It transforms the event log from a record of what occurred into a real-time diagnostic tool that surfaces exceptions as they develop, rather than after they are confirmed.
A note on how coordinators develop workarounds
One observation from the research that surprised us: the coordinators who were most effective at managing concurrent exceptions had all independently developed their own conventions for extracting event context from the map-first interfaces they had used before. They had learned not to trust the map as a primary diagnostic tool. They used the event log first, built personal heuristics for identifying meaningful timeline gaps, and treated the map as confirmation rather than investigation.
This kind of workaround is a signal worth paying attention to. When experienced users consistently route around an interface feature to get to what they actually need, the interface is not aligned with the operational workflow. The workarounds tell you which view should be the primary one.
For growing freight operations that are evaluating visibility tools, the practical test is straightforward: ask the vendor to demonstrate what a coordinator sees when a shipment has a customs hold that fired two hours ago. If the demo shows a map with a stationary dot, ask them to navigate to the event timeline view. If that navigation requires more than one click, the interface is built around the demo case, not the exception management case. The two are not the same thing, and for freight coordinators managing cross-border EU lanes, the exception management case is the one that matters.