Truck Waits at the Crane: The Hidden Cost in Container Terminals

Walk any container yard during a busy shift and you will see it. Three terminal trucks are lined up under one crane, while another crane two blocks along stands still, waiting for a truck. Nobody did anything wrong. The shift plan made sense at 06:00. By 09:30 the vessel work had moved, one crane had stopped for a fault, and the trucks kept going where they were sent.

Most terminals already report on their cranes and their trucks. Those reports are useful, but they are usually averages over a shift, and they arrive after the shift. They tell you the day was slow. They rarely tell you that for most of the morning four trucks queued at one crane while another sat idle, or what to change before lunch.

This article looks at why truck waits are such a good signal for a COO, why shift averages hide them, and what an operations team can change once it can see where trucks wait, per crane and per shift.

Why does a waiting truck cost more than the driver’s time?

Because a truck waiting under one crane usually means another crane is waiting for a truck. Terminal trucks are the link between the quay and the stack, and when too many gather in one place the rest of the operation runs short.

Researchers who studied truck dispatching at a container terminal put the goal plainly in their IEEE paper on dynamic truck dispatching: “In order to service more vessels, any unnecessary idle time between quay crane (QC) operations need to be minimised to speed up the container transfer process.” The same paper notes that a “sufficient supply of trucks ensures that less waiting time will occur between each two of container operations.”

Read the other way round, that is the cost. A crane with no truck under it is your most expensive machine doing nothing. The paper also observes that if one crane has a longer list of work than the others, “its operation speed will heavily affect the vessel departure time.” So the crane that is short of trucks is often the crane that decides when the ship can leave.

There is a second cost at the other end. The trucks in the queue are burning fuel at idle, their drivers are paid to wait, and the hours the trucks spend idling are hours that could have moved boxes.

That is why truck waits are one of the clearest signs of how well a terminal is running. They show where the work and the fleet have drifted apart, while there is still time to do something about it.

Why do shift averages hide the problem?

Because a crane that was starved of trucks for part of the shift and flooded for another part can still post an ordinary average. The average is correct, and it points nowhere.

There are three reasons waits are hard to see from the control room.

First, the radio and the job list say where a truck was sent, not where it is. A job can sit as “assigned” for a long time while the truck stands in a queue.

Second, queues form and clear quickly. By the time a supervisor drives over, the queue has often moved to the next crane, and the supervisor sees an empty lane.

Third, the shift report smooths everything out. It answers “how did we do today?” when the useful question is “where did our trucks wait, at which crane, on which shift, and why?”

Why do trucks end up waiting at one crane?

Usually because the plan was right at the start of the shift and the work moved. A queue is rarely one driver’s fault; it is the shape the plan takes once the day stops matching it.

Some causes come up again and again. Vessel work changes during the shift, but trucks keep following the morning’s plan. A crane stops for a fault or a hatch cover move, and the trucks assigned to it stack up below. Drivers and crane operators change over at different times, so the quay is short for a while and then crowded. The yard side is slow, so trucks wait for a yard crane or a blocked route and then reach the quay in a bunch.

The last cause is easy to miss. A truck that breaks down in the middle of a shift takes capacity out of the plan without warning, and the trucks around it absorb the load. If its service was planned by the calendar rather than by how hard it worked, the breakdown was more likely than it needed to be.

None of these causes is visible in a shift average. Each one leaves a clear trace when you look at waits per crane and per shift, and a clearer one when you replay the hour it happened.

What does seeing the wait look like in practice?

It means four things: waiting time per crane and per shift, an alert when a single wait runs long, a replay of the slow hour, and plain next steps drawn from the last 7 or 30 days.

In Mapsted Yard Watch, the Fleet and machines area shows where trucks waited, for every quay crane and every shift, over the last 7 days. The crane that is always crowded on the night shift, or the one that is always short of trucks in the afternoon, stands out at a glance instead of disappearing into an average.

When a truck has been waiting for more than 15 minutes, Yard Watch raises an alert. It lands in the same inbox as every other alert, so the supervisor hears about it during the shift rather than in next week’s report.

After the shift, Look back lets you pick the shift or a time window and replay it. The camera can follow the truck you choose through that window, and the Look back cards show which crane stopped in it and which trucks waited under it.

Insights then turn the last 7 or 30 days into plain “What to do” cards. Each card is built from that area’s own numbers, so the operations team starts the week with a short list instead of a spreadsheet.

What does a wait look like, step by step?

Take a common case. On a weekday night shift, trucks keep queuing under one quay crane, while a crane at the other end of the berth keeps stopping for lack of trucks.

At 02:10 one truck passes 15 minutes in the queue, and an alert appears in the inbox. The supervisor sees it while the shift is still running and can act on it there and then.

The next morning the operations lead opens Look back for that time window and follows one of the waiting trucks. Look back shows that the crane at the busy end stopped twice while the trucks under it waited, and nobody changed the truck assignments while it was stopped.

Then the lead checks the last 7 days per crane and shift. The same crane and the same night shift show up again and again, so this is not bad luck. It is the plan.

The fix is a change to the night-shift plan and a rule for what supervisors do when a crane stops. A week later the lead looks at the same view again to check that the waits at that crane have gone down, and have not simply moved one crane along.

How does maintenance connect to truck waits?

Once every machine’s movement is recorded, service can follow how hard each machine actually worked, not just the calendar. That matters because an unplanned breakdown is one of the quickest ways to turn a good plan into a queue.

Most yard equipment is serviced by date, or by an hour meter that someone reads by hand. In Yard Watch, maintenance is planned from real motion hours. The truck that worked double shifts all month gets attention first, and the one that sat in reserve is not serviced early just because its date came round.

The Health and Safety Executive (HSE) makes the business case in its guidance on maintenance of work equipment: “An effective maintenance programme will make plant and equipment more reliable.” It adds that fewer breakdowns mean less dangerous contact with machinery, “as well as having the cost benefits of better productivity and efficiency.” The same page advises: “try to use downtime for maintenance.”

That last point links straight back to waits. If you know which shifts leave trucks idle, you also know when a truck can go to the workshop without taking capacity from a busy crane.

Why should HSE care about truck queues too?

Because a queue of trucks is also a place where people and machines meet. A lane full of waiting vehicles is a lane where a lasher may cut between them, or where a driver climbs down to see what is holding things up.

The HSE’s page on workplace transport in ports and docks opens with a blunt line: “Every year accidents involving transport result in people being killed or seriously injured.” Among the typical hazards it lists are the “movement of vehicles in cargo storage areas, vehicle parks, ships’ holds and quaysides” and “unsegregated vehicle/pedestrian access.”

So a queue that operations wants gone for cost reasons is often one that HSE wants gone for safety reasons. Shorter, rarer queues mean fewer vehicles idling in lanes where crews walk, and fewer drivers out of their cabs. When both teams look at the same waits per crane and shift, the conversation starts from one set of facts, and a single change to the plan can serve both of them.

What can the wider port learn from gate queues?

That queues respond to planning, and that measuring waits is the first step. Regulators have already made this case for trucks queuing outside the terminal, and the same logic applies to trucks queuing inside it.

The Environmental Protection Agency (EPA), in its guidance on port gate management strategies, says that “long truck queues at terminal gates can contribute significantly to emissions, noise, and traffic congestion in and around ports.” It describes how gate management strategies reduce idle emissions “by redistributing truck arrivals away from peak periods and lowering average wait times.”

The EPA also notes that “cost savings may result from reduced fuel consumption from less idling.” Gate queues and crane queues are different problems, but they share a shape: trucks arrive in bunches, wait with engines running, and cost money while doing nothing useful. In both cases the fix starts with knowing where and when the waiting happens.

What are the limits of truck wait data?

Wait data shows where the plan and the work drifted apart; it does not decide what the new plan should be. That decision still belongs to the people who know the vessels, the crews and the yard.

Some waiting is normal. A truck that arrives a minute before its container is ready has done its job well. The aim is not zero waiting, which would mean cranes waiting instead. The aim is to stop the same long waits repeating at the same crane on the same shift.

Read the numbers with the context around them, too. A crane working a large vessel will show more waiting than one working a small feeder, simply because more trucks pass under it. Compare like with like before you change a plan.

What should you ask of any yard platform?

Ask whether it can show where trucks wait per crane and per shift, warn you about long waits during the shift, replay a slow hour, plan service from real motion hours, and turn all of it into plain next steps.

1. Can it show waits per crane and per shift? One average for the day hides the crane that is always short of trucks.

2. Does it raise long waits as alerts during the shift? A wait you hear about next week cannot be fixed tonight.

3. Can you replay a slow hour? You want to follow one truck through it and see which crane stopped.

4. Does it plan maintenance from real motion hours? Calendar servicing over-services the spare truck and under-services the busiest one.

5. Do all alerts land in one inbox? Truck waits, near-misses and machine alerts in separate systems mean nobody sees the whole yard.

6. Does it tell you what to do next? A short list of actions from the last 7 or 30 days is more useful than another dashboard.

Mapsted Yard Watch shows where trucks wait at every quay crane, per shift, raises long waits as alerts, and lets you replay a slow hour with the camera following the truck you choose. It is already used to track 1,000+ assets across multiple sites. Book a private demo to see truck waits go from alert to replay to a better plan.

Mapsted Yard Watch supports, and does not replace, your safety procedures and emergency services.

Frequently asked questions

Why are truck waits at the crane a useful measure for a terminal?

Truck waits show where the work and the fleet have drifted apart. A truck waiting under one crane often means another crane is short of trucks, so the cost is idle crane time as well as driver time. Because waits can be counted per crane and per shift, they point at a specific place and time, which makes them easier to act on than a shift average.

How are truck waits different from crane productivity figures?

Crane productivity figures are usually averages over a shift and describe the result. Truck waits describe one of the causes: how long trucks stood under each crane, and when. A crane can post an ordinary average while being starved of trucks for part of the shift and flooded for another part. Looking at waits per crane and per shift shows that pattern instead of hiding it.

What counts as a long wait?

Every terminal has its own view, but a fixed threshold helps. In Mapsted Yard Watch, a truck that waits at a crane for more than 15 minutes raises an alert in the same inbox as every other alert. The supervisor hears about it during the shift, and the waits are also kept per crane and per shift over 7 days, so repeat patterns stand out.

Does reducing truck waits mean adding more trucks?

Not necessarily. Many long waits come from trucks bunching at one crane while another crane is short, so the same fleet is in the wrong place. Changing the shift plan, agreeing what supervisors do when a crane stops, and servicing machines by real motion hours can all reduce waits without buying a single truck. Adding trucks to a plan that has drifted often just lengthens the queue.