On a typical Tuesday you have between 40 and 60 external drivers at your plant gate. Many are subcontractors working simultaneously for three different haulage companies. Some come from Poland, Romania or the Czech Republic, have a German client, and drive for a company you’ve never directly commissioned. The question is simple: how many of these drivers have your plant app installed? The honest answer at almost every industrial operation is under 5%—if any at all.
The Plant App Promise and Its Silent Surrender
Somewhere between 2018 and 2022, almost every mid-sized industrial plant gave thought to an app for external lorry drivers. The logic was sound: the driver installs the app, notifies before arrival, confirms his time-window, enters the registration number and load reference—dispatch is in the picture. Clean. Digital.
You know what actually happened.
The app launches. A handful of regular drivers from the two biggest hauliers install it. For the first four weeks, notification rates do climb. Then the first driver leaves. Then a new subcontractor joins. Then holiday season. Six months later, app usage is confined to the drivers who were already ringing ahead reliably.
This isn’t a failure of the idea. It’s a structural pattern—and understanding that pattern before you attempt to break it with new technology is worth the effort.
Why External Drivers Don’t Install Plant Apps—A Sober Assessment
An external driver who regularly calls at your plant may visit you four to eight times a month. In parallel, he supplies seven other customers, three of whom might have or want their own app. If every customer demanded an app, he’d need seven different portals on his work phone—assuming he has one and isn’t using his personal device—five with expired passwords and two with registration issues.
Add the subcontractor chain on top: you engage haulier A. Haulier A has no driver available for this route and forwards the job to subcontractor B. The driver who finally arrives at your gate has never spoken directly to you—he has the job details from B, maybe on a scrap of paper, maybe by SMS. Nobody explained app registration to him because nobody in that chain knew you’d expect it.
“The driver pulling up often doesn’t even know we have an app. The haulier knows. But the haulier isn’t behind the wheel.”
You hear this sentence repeatedly in goods-in teams—it captures the core problem precisely.
According to industry data, 40 to 70% of DACH inbound deliveries are organised on FCA terms. That means: the supplier arranges the haulage themselves; you have no direct booking contract with the carrier. You also have no direct registration relationship with the driver. You stand at the end of a chain—and at the gate.
97% Smartphone Penetration, 3% App Usage: What Explains the Gap?
Here lies the real paradox. Industry surveys show that 97% of lorry drivers across Europe own their own smartphone. Device reachability would therefore be almost universal.
So why isn’t it being used?
Because reachability and app installation are two different things.
A smartphone means WhatsApp. Almost without exception. Not your plant app, not the haulier’s portal, not the time-window booking system you’ve been running for three years. WhatsApp is the application every driver has on every device—private or professional—regardless of whether he’s a regular or a one-off subcontractor, regardless of language, nationality or contractor chain.
This isn’t a technology verdict. It’s a behavioural observation.
And it points to an uncomfortable question many logistics leaders haven’t explicitly asked themselves yet:
Have you deliberately chosen your communication channel—or have you inherited the channel your system uses?
The Cost of Non-Reachability: A Micro-Calculation
You can leave this topic abstract. Or you can do the maths.
Suppose: 45 external deliveries per day, 250 working days per year. At a typical app non-adoption rate of 95%, about 43 deliveries daily lack reliable advance information on arrival time or load status. Your goods-in team compensates—through calls, enquiries to the haulier, waiting.
If each of these 43 deliveries takes an average of 8 minutes of reactive coordination (call, query, status update in the system), that’s roughly 344 minutes daily—nearly six hours—of pure coordination effort resulting from missing advance information.
43 deliveries × 8 min × 250 days = 86,000 minutes/year ≈ 1,433 hours
At an internal hourly rate of €35, that’s roughly €50,000 annual coordination cost—from the structural communication vacuum between time-window booking and actual arrival. Not included: gate setup times, knock-on costs during morning peak congestion, lost rescheduling opportunities.
This isn’t a Heylog figure. It’s a methodology—apply it to your own delivery numbers.
The Morning Peak as a Magnifying Glass
Roughly 40% of all daily deliveries at manufacturing plants arrive in the first 90 minutes after the gates open. This is a structural fact, not an exception.
Picture a Wednesday morning: plant opens 06:00. Between 06:00 and 07:30, 17 lorries arrive. Three of them booked your 06:30 time-window but neither sent advance notice. Two more are booked for 08:00 but arrive early—they drove the motorway overnight and are now waiting in the yard. One driver can’t find the plant gate because his sat-nav shows a different entrance, so he rings the main office.
Your goods-in manager is standing at 06:20 with four open issues simultaneously. None would have arisen if the drivers had sent a brief confirmation 60 minutes before arrival.
The problem isn’t congestion. The problem is nobody knew before the congestion when which driver was coming.
What Time-Window Systems Deliver—And Where They Stop
Portals for time-window booking structure planning. They allocate slots, display capacity, help dispatch plan the day ahead. That’s their value, and it’s real.
But the slot is where planning ends—not where delivery begins. What happens between booking and actual arrival lies outside the portal. The driver booked for 06:30 might arrive at 05:45 or 08:10. The portal doesn’t know. You don’t know. And until you do, you’re reacting—you’re not steering.
An internal survey by Cargoclix found that around 50% of users measured no genuine process improvement from the system. This isn’t a weakness of any single product—it describes the systemic limit of all slot-booking systems: they end at the booking. Arrival stays uncontrolled.
Channel Choice Is a Leadership Decision
Back to the opening question: how many of your external drivers have your app installed?
If the answer is below 10%, that’s not an IT problem. It’s a channel decision that was made implicitly—and materialises daily in coordination effort, gate congestion and reactive dispatch work.
The channel that works is the channel the driver already uses. Not the channel you designated for him.
This doesn’t mean time-window portals should be abolished. It means the gap between slot and arrival needs its own channel—one that works without app installation, without registration, without language barriers.
Heylog automatically sends the driver a WhatsApp—before he arrives. He confirms his ETA. You see it on your dashboard. No call, no app, no portal. The channel is already installed: on every smartphone, in every country, with every subcontractor.
What Remains
The technology to reach external drivers reliably isn’t the problem. It’s existed for years. The question is whether you make a deliberate channel choice—or keep waiting for external drivers to adapt to your system.
Up to 80% of advance notices in German plants still run through Excel and email. That shows how far the sector is from full adoption. But it also shows this: whoever develops a clear channel strategy here first gains a real operational advantage.
What channel do your external drivers use today—and did you choose that deliberately?
Frequently Asked Questions
Why don’t external lorry drivers install plant-specific apps?
External drivers supply multiple customers daily for different hauliers. If they installed every plant app, they’d need a dozen different applications. There’s also the subcontractor chain: up to 70% of DACH inbound deliveries run under FCA terms, so the driver never communicates directly with the receiving plant and often doesn’t even know an app exists.
Which communication channel reliably reaches external drivers at the plant gate?
Industry data shows that 97% of lorry drivers own a smartphone and use WhatsApp almost universally—regardless of nationality, language or contractor chain. Plants that reach external drivers via this existing channel achieve significantly higher response rates than through proprietary apps or portals.
What does missing advance information from external drivers cost?
A simple micro-calculation provides guidance: with 43 uncommunicated deliveries daily and average 8 minutes of reactive coordination per case, roughly 1,400 hours of annual coordination effort accumulate. At an internal hourly rate of €35, that’s around €50,000—from the communication vacuum between time-window booking and actual plant gate arrival alone.