A truck is not late because it is driving slowly.
It is late because a document was rejected at a border post, or a customs broker was unreachable on a public holiday, or a permit quota was exhausted, or a driver's visa expired mid-route. Transit delay is overwhelmingly administrative, and it accumulates at a small number of predictable points.
This matters for how visibility should be built. A GPS trace tells you where the vehicle is. It does not tell you why it has not moved for eleven hours, which is the only question anyone actually wants answered.
What "supply chain visibility" usually means, and why it disappoints
Most fleet visibility deployments track vehicle position, speed, and route adherence, and present it on a map. That is genuinely useful for domestic operations, where the constraints are driver hours, fuel, and traffic.
Across international corridors, the picture is incomplete in ways that matter commercially.
Position without status is not information. A vehicle stationary at a border crossing might be in a normal queue, might be under inspection, might be held on a documentation defect, or might be waiting on a payment. Four states, four different responses, one identical map pin.
Position also does not predict. The commercial value of visibility is the ability to tell a customer today that a delivery scheduled for Thursday will arrive Monday. That requires modelling the delay drivers ahead of the vehicle — crossing congestion, documentation status, permit availability — not the position behind it.
Useful transit visibility therefore combines three layers: where the vehicle is, what state the consignment's documentation is in, and what conditions lie ahead on the route. Deployments that build only the first layer generate dashboards nobody consults after the first month.
The TIR system, and why it defines the workflow
For road freight across Europe, Central Asia, the Middle East and beyond, the TIR system is the framework that makes multi-country transit workable. Goods move under customs seal, with a guarantee chain that allows intermediate countries to permit transit without full customs procedure at each border.
The system works well. What creates operational risk is the workflow around it: the carnet must be valid and correctly completed, the vehicle must hold a valid approval certificate, the seals must be intact and correctly recorded, and each transit country's entry and exit must be properly discharged.
A defect at any of those points produces an outcome that is disproportionate to the error. A discharge that fails to register does not delay one shipment — it can expose the guarantee chain and create liability that surfaces weeks after the goods have been delivered. Operators discover this through claims, not through dashboards.
Our advisory role sits on this workflow: verifying document readiness before departure rather than at the border, coordinating with brokers at each crossing point, and confirming discharge at each stage rather than assuming it.
The principle is that document verification is cheap before departure and expensive at a border post. Most operational transit failure is a scheduling error about when checks happen, not a knowledge gap about what they are.
Corridor by corridor
Each corridor fails differently, and treating them as one operational problem is a common and costly simplification.
Europe. The most procedurally mature and the most rule-bound. Delay drivers are documentation precision, driver hours regulation, and entry system requirements. Errors here are usually detected quickly and correctable — but the tolerance for imprecision is low, and the same defect that passes elsewhere will stop a vehicle at an EU crossing.
Middle East corridors. Relationship density matters more than in Europe. Broker quality varies significantly and is the single largest determinant of clearance time. Security and route conditions can change quickly, requiring rerouting capability rather than route optimisation. Documentation requirements are less uniformly published, which makes local knowledge a genuine operational asset rather than a soft advantage.
China and Central Asia. Long transit distances, multiple transit states, and multimodal handoffs. The failure point is typically the handoff itself — road to rail, or one operator to another — where custody and documentation both change hands and neither party's system covers the seam.
Africa. Port and inland clearance procedures dominate the timeline far more than road transit does. Visibility investment concentrated on the vehicle rather than on the clearance process measures the smaller part of the delay.
The consequence for operators: a single visibility standard applied uniformly across all four will over-instrument one and under-instrument another. Instrumentation should follow where the delay actually accumulates in each corridor.
What we build for clients
Three components, deployed together.
Real-time fleet telemetry panels. Position, route adherence, stationary-time alerting, and — critically — status annotation, so a stop is classified rather than merely recorded. A stationary vehicle with an unexplained state is an open operational question; a stationary vehicle tagged "awaiting broker, documents submitted 14:20" is a managed one.
TIR and documentation workflow. Pre-departure verification checklists, carnet status tracking, per-crossing discharge confirmation, and escalation paths when a discharge does not register within an expected window.
Customs and broker coordination. Named contacts per crossing, expected clearance windows, and a defined escalation route. This is the least technological component and the one that most reliably determines transit time.
The proportions are worth stating honestly: the telemetry is the visible part and roughly a third of the value. The documentation workflow and the broker coordination carry the rest.
Measuring it
Metrics that reflect what operators are actually managing:
Border dwell time by crossing. The single most actionable number available. It identifies which crossings and which brokers are underperforming, and it supports rerouting decisions on evidence rather than on habit.
Documentation defect rate at departure. Defects caught pre-departure versus at a border. A rising pre-departure catch rate is the leading indicator that the process is working.
Discharge confirmation lag. Time between transit completion and confirmed discharge. Growing lag is an early warning of a guarantee-chain exposure that will otherwise surface as a claim.
Delivery date accuracy. Not average transit time — the accuracy of the date communicated to the customer against the date achieved. Customers plan against the commitment, and a consistently accurate five-day quote is commercially worth more than an unreliable four-day one.
That last metric is the one clients recognise immediately and the one visibility programmes least often report.
Where this connects to the rest of the operation
Transit visibility is not a standalone technology purchase. It sits between commercial contracting — where delivery terms and liability are set — and settlement, where payment terms frequently depend on delivery evidence.
Groups that treat these as three separate functions produce a familiar pattern: contracts committing to delivery windows the transit operation cannot support, and payment disputes over delivery evidence the visibility system was never designed to produce.
Our business units cover trade execution, transit logistics, and settlement advisory as connected functions for exactly this reason, with our compliance framework governing the customs and AML dimensions. Related engagements are documented under case studies.
To discuss a specific corridor, contact the team in Istanbul.
