Aerix

The Queue Outside the Port: What Gate Congestion Really Measures

Lorry queues at port gates are usually blamed on volume. More often the gate itself is the constraint: paper processes, manual checks and cameras that need a network the port doesn't have.

Back to Blog21 August 2026By Aerix Team
5GPortsLogisticsAutomation

In short: Port gate congestion is usually discussed as a volume problem, but the queue outside a container terminal more often measures the gate itself: how many manual checks, paper documents and radio calls stand between a lorry arriving and a lorry driving to the stack. Automated gates shorten the queue, and they stand or fall on the network behind the cameras.

Key Takeaways

  1. The gate is the constraint, not the quay — UK container terminals can turn a lorry in under an hour once inside; the queue forms at a gate still doing with people and paper what cameras and data can do in seconds.
  2. Queue time is paid time — Driver hours rules, haulage day rates and vehicle booking system penalties turn every queued hour into money, and the cost lands on hauliers, shippers and ultimately shelf prices.
  3. An automated gate is a network project — ANPR, container OCR and damage cameras produce continuous video from structures spread across a gate plaza; getting that data to the terminal operating system reliably is the part that decides whether the gate works.

In a nutshell

The Queue Outside the Port: What Gate Congestion Really Measures — infographic summary

What causes port gate congestion?

Ask a haulier and the answer is immediate: because the gate is slow, and because the booking system fines us if we are late but does nothing when the terminal is. Ask the terminal and the answer is different: because hauliers arrive in bunches, because paperwork is wrong, because the yard is congested behind the gate. Both answers are partly right, which is why the argument has run for years without resolving.

The autumn of 2021 gave the UK a public demonstration. Felixstowe, which handles roughly four in ten of the country's containers, saw yard utilisation climb until shipping lines diverted vessels to continental hubs; haulage capacity was short, boxes dwelled longer, and lorries queued on the A14 for slots that the vehicle booking system was rationing. The episode was reported as a shipping crisis, but the mechanism on the ground was mundane: a terminal's throughput is set by its narrowest point, and for the landside flow that point is the gate.

What actually happens at a manual or semi-manual gate is worth spelling out. A lorry stops. Someone, a clerk in a booth or the driver at a kiosk, confirms the booking reference against the vehicle booking system, checks the container number against the manifest, records the seal, notes damage on the box, checks the driver's Level 1 or terminal induction, and only then issues a yard position. Each step is short; together they take minutes; and minutes per lorry, multiplied by a thousand-plus gate moves a day at a large terminal, is a queue with its engine idling on the approach road.

What does an hour in the queue cost?

The costs are unusually easy to name because most of them are contractual.

For the haulier, a container vehicle and driver cost in the region of £50 to £60 an hour to keep on the road, whether moving or stationary; an hour queued is an hour of that money buying nothing. Drivers' hours rules under the retained EU regime compound the loss: queue time counts against the working day, so a long enough queue does not merely delay the job, it cancels the next one. Vehicle booking systems add their own arithmetic; missed slots at the major container terminals attract rebooking fees, and hauliers price terminals' reliability into their rates. The Road Haulage Association has made the point repeatedly during successive congestion episodes: waiting time at ports is a cost the haulage industry cannot absorb and therefore passes on.

For the terminal, the queue costs reputation with shipping lines and hauliers, but it also costs something more direct: gate hours. A gate that turns lorries slowly needs longer opening hours, more booths and more staff for the same volume, and a congested approach road is a standing invitation for the local authority and National Highways to take an interest in the port's traffic management.

For everyone else, the queue is diesel burnt at idle next to communities that notice, and freight that arrives late into supply chains that have been trimmed of slack. Port gate congestion is a small phrase for a cost that lands on several balance sheets at once.

What does an automated gate actually do?

The automated gate inverts the manual sequence: instead of a lorry stopping so that people can collect data, the data is collected while the lorry moves. As the vehicle passes through a portal, ANPR cameras read the number plate, OCR cameras read the container number, ISO code and seal presence from four sides, high-resolution imaging records the condition of the box for later damage disputes, and the system matches the lot against the vehicle booking system entry made hours earlier. The driver, already identified, receives a yard position on a screen or a phone without leaving the cab. Exceptions, a mismatched booking, an unreadable box, visible damage, are filtered to a manual lane; the clean majority never stop at all.

None of this is exotic. Pre-gates and OCR portals of this kind are standard at large European terminals and established at the UK's biggest container ports; DP World London Gateway was designed around an automated gate flow from opening, and Felixstowe and Southampton have both invested in gate technology generations. The pattern that interests us is further down the league table: the UK has dozens of smaller container, ro-ro and bulk terminals where gate volumes are lower but the gate is still the constraint, and where the technology has historically looked like a big-terminal luxury.

Why does the gate fail when the network does?

Because an automated gate is, in data terms, a set of always-on cameras and sensors distributed across a gate plaza, approach roads and out-gates, all of which must deliver imagery and reads to the terminal operating system in the second or two the lorry spends in the portal. A dropped frame is a failed read; a failed read is a lorry diverted to the exception lane; and an exception lane that grows is the old queue reborn with better cameras watching it.

The connectivity options each carry a trade-off. Trenching fibre to every camera structure is the gold standard and painfully expensive across live traffic lanes and land the port may want to reconfigure; gate layouts change, and buried fibre votes against change. WiFi across an outdoor plaza full of moving steel is exactly the environment WiFi handles worst. Public 4G and 5G at a port apron is shared with every phone in the queue and engineered for none of them. This is the gap a private 5G network fills: licensed spectrum the port controls, radios planned around the plaza and out-gates, enough uplink for continuous camera traffic, and the freedom to move or add a portal without civil works. The same network then serves the rest of the landside estate, handhelds for checkers, tablets in shunter cabs, CCTV on the empty stacks, which is why we consistently argue that ports should buy coverage once rather than per project.

We should be candid about sequencing: a private network does not fix a gate whose process is broken. A terminal that automates a bad booking flow gets automated bunching. The vehicle booking system, the gate process and the network are one design problem, and the ports that have done this well treated them as such.

Where should a smaller terminal start?

With measurement, because the gate argument between hauliers and terminals dissolves in the presence of data. Truck turn time, from arrival at the gate queue to exit, is the single figure that captures the landside experience, and most smaller terminals do not measure it end to end; the queue on the public road, in particular, is usually invisible to the terminal's systems.

A modest first deployment does exactly that: ANPR at the back of the queue, at the gate and at the exit, on a private network covering the approach and plaza, produces a continuous, honest record of turn times within weeks. That number then does the arguing. If turn times are short, the terminal has the evidence to defend itself; if they are long, the same cameras and network become the first components of the automated gate that fixes it, and nothing is thrown away. We think that is the right way round to invest: measure with the infrastructure you will keep.