The lorry that arrives two hours late does not just delay unloading. It holds a crew standing around, forces a rescheduling conversation with the groundworks team, and in the worst cases, determines whether a slab pours that day or waits until next week. Most contractors have absorbed this as background noise. We would argue it is one of the most undercosted sources of margin erosion running through UK construction projects at the moment.
It is not a drama, which is partly why it does not get measured. It is a slow leak.
What actually happens when a delivery is late
The mechanics are familiar to anyone who has run a site. A supplier confirms a morning delivery window. The bricklaying gang arrives at 7:30 AM, ready to go. The lorry shows up at 11:00. The gang stands around for three and a half hours, or is diverted to prep work that was not originally scheduled for that day, which then pushes something else back by an afternoon.
The direct cost of three and a half hours of idle labour for an eight-person gang is not trivial. At a blended rate for mixed bricklaying and labouring, you are looking at direct wage costs somewhere between £400 and £600 for that window, depending on the trades and rates in play. Across a project, if this pattern recurs several times, those sums accumulate without ever appearing on a single line of a cost report.
The indirect cost is harder to measure but often larger. If the day's output target is not reached because materials arrived late, the following day carries extra load. Overtime gets authorised. The following week's concrete pour has to be brought forward. The plant hire extension runs another two days. None of these appear on the procurement ledger.
The compounding problem across a project timeline
A single delivery failure is annoying. A pattern of them reshapes the project schedule in ways that are hard to unpick cleanly.
The problem is that construction schedules are interdependent. The scaffolding cannot come down until the cladding is complete. The cladding cannot go on until the structural frame is signed off. The structural frame cannot be inspected until the last steel section is in place. If that last section is sitting on a delayed lorry, the whole chain is waiting.
In a residential development in Sheffield that we were involved with last year, a series of three late precast lintel deliveries over six weeks pushed the first-fix inspection back by nine days. The knock-on to second-fix trades, who had been scheduled around the original inspection date, resulted in a programme extension and additional costs that were not recoverable from the original fixed-price contract. The lintels themselves were not expensive items. The coordination failure around them was.
Where coordination actually breaks down
Delivery coordination fails at three consistent points. Understanding which one applies on your site determines what you actually need to fix.
The first is information asymmetry between the supplier and the site. The supplier knows their vehicle has been delayed, but the notification system is a phone call that goes to the site manager's voicemail at 6:45 AM before they are on site. By the time anyone knows, the gang is already standing there.
The second is booking window ambiguity. "Morning delivery" can mean anything from 7:00 AM to noon, depending on the supplier's run and who else is on the round. If a site manager books four morning deliveries across four different suppliers on the same day, the probability of them all arriving when expected is low. But because each booking was confirmed, there is no obvious flag that a scheduling conflict has been created.
The third is on-site receiving. If the designated unloading person is not present when the lorry arrives, some suppliers will leave materials, some will take them back. A return trip to re-deliver can take two to five days depending on the supplier's route schedule. That gap, caused by thirty minutes of miscommunication, costs far more than the delivery charge.
What contractors can do to reduce the failure rate
The practical fixes are not complicated, but they require a bit of discipline to maintain.
First, tighten the booking window and document it in writing. "Morning" is not a booking. A three-hour window with a confirmed arrival range is a booking. Most suppliers will agree to this, particularly if you are a regular account. It means committing to a specific day, not just a general period.
Second, make sure someone is responsible for receiving. On a small site, this is usually the site manager. On a larger site, there may be a general operative whose morning task includes logistics. The person responsible should know what is arriving, when, and what bay or area it goes to. A simple morning delivery sheet, even just a whiteboard note, reduces the probability of a lorry arriving to an empty yard with no one to sign for it.
Third, build a brief buffer into your schedule between material arrival and trade start. If bricklayers are scheduled to begin at 8:00 AM and the block delivery is booked for 7:30, any minor variance creates a problem. If the delivery is booked for the afternoon before, the morning start is insulated from the delivery variable entirely. This is obvious, but it gets squeezed out when programmes are tight.
Fourth, track the pattern. If a particular supplier has a habitual late delivery rate on afternoon runs, that information is useful in planning. Most contractors do not systematically record delivery performance because it feels like overhead, but a simple log of actual vs confirmed arrival time for each delivery on a project, reviewed once a month, tells you where the problem is concentrated.
A word on what this is not
We are not saying suppliers are generally unreliable or that delays are always avoidable. Road conditions, vehicle breakdowns, consolidation changes at merchant yards, traffic on the A1 at 7:00 AM on a Friday morning, all of these are real factors and most suppliers are making genuine efforts within them.
The problem is not that deliveries are occasionally late. It is that the coordination layer between the supplier's dispatch and the site's scheduling is thin, usually informal, and not treated as a managed process. When a project has six or eight active suppliers at once, that thin layer compounds in ways that become genuinely costly.
Building delivery reliability into the procurement layer
One of the things we have been working on at Prolo is making delivery scheduling a first-class part of the ordering process rather than an afterthought. When you place an order, the delivery window is confirmed as part of the quote acceptance, not as a separate phone call the following day. Changes to that window come through the same channel, so someone on site has a record rather than a voicemail.
It does not eliminate delivery failures. Nothing does. But it puts the coordination information in one place, accessible to whoever needs to act on it, rather than distributed across five phone call histories and a WhatsApp thread that three people are half-following.
The contractors we work with who manage high delivery reliability do not have magic relationships with their suppliers. They have cleaner information flows. That is a process problem, and it is a solvable one.
