SEH Ltd All articles
Opinion

Lead Times Are Promises Until They Are Slots: A Programme Confidence Test for UK Commercial Projects

SEH Ltd
Lead Times Are Promises Until They Are Slots: A Programme Confidence Test for UK Commercial Projects

Photo: Thomas Nugent , CC BY-SA 2.0, via Wikimedia Commons

Programmes rarely fail at the moment a delay becomes visible. They fail earlier, when a lead time is repeated in a meeting as if it were a confirmed slot. In UK commercial projects, the most dangerous dates are often not the ones that are missing from the programme. They are the ones that are present, tidy and wrong.

The distinction matters in 2026 because commercial teams are still working with supply chains that can quote quickly and confirm slowly. A supplier may give a lead time in good faith, based on current capacity and standard materials. That is not the same as a manufacturing slot, a delivery booking or a firm commitment. When the programme treats the first number as the third, risk is absorbed silently into the schedule.

The confirmation ladder

A useful starting point is to place every significant lead time on a four-rung ladder. The first rung is quoted: a supplier has given an indicative period based on today's assumptions. The second is planned: the supplier has checked the period against a proposed order date and current workload. The third is confirmed: a slot, capacity allocation or delivery window has been identified, subject to agreed conditions. The fourth is committed: the order is placed, the conditions are met and the date is contractually or operationally owned.

Many programmes confuse rung one with rung three. The programme shows a date, the team treats the date as real, and the commercial risk is not discussed until the supplier says capacity has moved. The test is simple: for each long-lead item, can the team state which rung it occupies and what evidence supports that position? If the answer is a quotation email from several weeks ago, the programme may be less confident than it appears.

Test the item, not just the trade

Long-lead risk is often discussed by trade package, but it should be tested by item. A mechanical package may be broadly available while one valve, control panel or specialist pump is not. An electrical package may have ample labour but a constrained switchgear slot. The programme should identify the specific items that could stop installation, commissioning or handover, then test each one separately.

This is not an exercise in listing every component. It is an exercise in finding the items that carry schedule leverage. A useful question is: if this item arrived four weeks late, what would stop? If the answer is 'nothing', it may still matter commercially, but it is not the first priority for programme confidence. If the answer is 'the ceiling closes, the commissioning sequence moves and the client's fit-out date slips', the item belongs on the watchlist.

Questions that expose the truth

A supplier's first answer is often a lead time. The second answer is more useful. Ask what the lead time assumes about material availability, drawing approval, order placement, payment terms and factory capacity. Ask whether the period includes fabrication, testing, packing and transport, or whether those are separate. Ask what the current variance is between quoted and achieved dates for similar orders.

Then ask the question that many commercial teams avoid: what would make the date move? A supplier who can name the triggers is easier to manage than one who offers reassurance without conditions. The triggers may include drawing approval deadlines, deposit payment, access to test facilities, certification or shipping slots. Each trigger should become a programme dependency with an owner.

Look for the quiet assumptions

Programme risk rarely announces itself. It sits in phrases such as 'standard lead time', 'subject to survey', 'ex works', 'drawing approval required' and 'delivery to site by others'. These phrases are not dishonest. They are conditional. The problem is that conditions have a habit of being dropped when the programme is compressed into a single date.

Another warning sign is a programme with no float around procurement. If every order is placed at the last responsible moment and every delivery arrives just in time, the schedule has no tolerance for ordinary commercial life. A drawing comment, a revised specification or a supplier's quality check can consume the buffer before the first installation shift begins.

A third warning sign is a supplier capacity statement that is really a sales forecast. 'We can meet your programme' is not the same as 'we have reserved capacity for your order on these dates'. The former is an intention; the latter is a commercial position. The programme should be built on positions, not intentions.

A simple confidence test

For each critical item, record five things: the required onsite date, the current confirmation rung, the evidence behind it, the dependency that could move it, and the contingency if it moves. This can be held in a short schedule reviewed alongside the main programme. It does not need to be bureaucratic, but it does need to be honest.

The test should be repeated at each major stage: before tender return, before order placement, after drawing approval and before delivery. Lead times are not static. A date that was credible at tender may be stale by the time the order is placed. A programme that is not refreshed is not a plan; it is a record of earlier optimism.

The commercial conclusion

A realistic programme is not one with the shortest lead times. It is one that knows which dates are quoted, which are confirmed and which are committed. That knowledge allows the client and delivery team to make decisions early: to procure sooner, to redesign around a constraint, to accept a different sequence or to price the risk openly.

The alternative is to let the programme look calm until it is not. By then, the delay is visible, the options are fewer and the commercial conversation is harder. The better discipline is to challenge the lead time before it becomes a line in the schedule. A date is only a programme date when someone can explain what stands behind it. Until then, it is a promise, and promises need testing.

All Articles

Related Articles

The Inherited Project: Ten Tests for a Handover Pack That Earns Its Signature

The Inherited Project: Ten Tests for a Handover Pack That Earns Its Signature

The Casual Yes: How Informal Approvals Undermine UK Commercial Projects

The Casual Yes: How Informal Approvals Undermine UK Commercial Projects

Seven Metrics That Separate a Good Supplier from a Great One, and Why Most Scorecards Miss Them

Seven Metrics That Separate a Good Supplier from a Great One, and Why Most Scorecards Miss Them