Long-Lead Items Can Delay the Site Before Work Begins. What Should Procurement Release First?
Project procurement should start from programme need dates, package scope, approved specifications, tender allowances and supplier lead times. Releasing the wrong package early can lock in cost or design risk; releasing too late can stop the site.
The short answer
The procurement clock should start from the date the site needs the package — not from the date someone wants to issue a purchase order.
Long-lead procurement becomes dangerous when “buy early” replaces judgement. Order too late and the workfront stops. Order too early and the project can lock in the wrong quantity, specification or package boundary.
The real management task is to decide when the programme risk of waiting becomes greater than the commercial and technical risk of committing.
The phrase “long lead” can create false urgency
Once an item is labelled long lead, teams often assume the answer is obvious: order it immediately.
That instinct is understandable. Nobody wants to be responsible for a late critical package.
But lead time is only one part of the decision.
The design may still be moving. Client approval may not have started. Quantities may still depend on coordination. The supplier quotation may be outside the tender allowance. Logistics may not be ready to receive the item even if it arrives on time.
The project can therefore protect the programme and still create a future cost problem.
A stronger approach begins by asking what has to be true before commitment becomes sensible.
The site need date is the only procurement date that really matters
A purchase-order date is an internal milestone. The site need date is the business consequence.
Work backwards from the point at which the package must be available to the workfront.
That backward plan may include transport, inspection, manufacturing, supplier drawings, technical approval and internal commercial review.
The sequence often reveals that the true constraint is not manufacturing lead time at all. It may be design approval, a client decision or a missing specification.
This is where procurement stops being a buying function and becomes part of project control.
A package can only be managed properly when its commercial, technical and programme dependencies are visible together.
Early commitment is sometimes the right answer — but it should be a conscious trade-off
Projects are often forced to buy before every detail is complete.
There may be no perfect option.
Waiting could threaten the programme. Ordering could expose the project to change cost.
In that situation, management should compare the scenarios honestly.
Could only the stable portion of the package be released? Could a supplier reserve capacity before final quantity is fixed? Could the order be structured with a controlled change mechanism? Could approval be accelerated instead?
The objective is not to eliminate risk. It is to choose which risk the project is willing to carry.
That choice becomes much easier to manage later when the reason is documented.
Supplier milestones tell the truth earlier than a promised delivery date
A supplier can continue to promise the final date even while the package is already slipping.
For critical manufactured items, the project should watch intermediate milestones: design submission, approval, material release, manufacture, test, inspection and dispatch.
These stages provide earlier warning.
They also help distinguish supplier delay from project-caused delay.
If approval was late, the project can see it. If raw material was not released on time, the supplier issue becomes visible before the final delivery is missed.
This kind of milestone evidence gives management more recovery options than waiting for the delivery date to fail.
The cheapest supplier can still be the highest programme risk
Price comparisons rarely show the whole project consequence.
A supplier may offer the lowest number but have weak design capacity, limited manufacturing slots, poor documentation or unrealistic lead-time assumptions.
For a critical package, those weaknesses can cost far more than the original saving.
Supplier selection should therefore reflect the job the supplier actually has to perform.
Can the supplier support submittals? Can it meet the required quality process? Does it have real manufacturing capacity? Can it provide commissioning or documentation where needed?
The aim is not to make procurement subjective. It is to acknowledge that programme reliability and project capability have economic value.
Logistics can turn an early delivery into a late project
A supplier delivering on time does not guarantee the site can use the material.
Large equipment may need special transport, storage, lifting or protection. An early shipment can create double handling or off-site storage cost if the workfront is not ready.
This is especially common where teams focus on supplier delivery but not on site receipt.
The procurement plan should therefore continue beyond dispatch.
How will the item arrive? Where will it go? What plant is needed? Is the site ready to store or install it? Does the sequence still make sense?
The best procurement date is the one that supports the project, not simply the one that satisfies the purchase order.
Long-lead management should focus on the critical few
A large procurement schedule can become a reporting exercise.
The value comes from identifying the relatively small number of packages whose delay or cost movement could materially affect the project.
For those packages, management should know the current constraint, the owner, the next decision and the remaining recovery options.
That is far more useful than a list in which every item has equal status.
The procurement process becomes stronger when the project can distinguish normal buying activity from the few packages that genuinely threaten programme or margin.
This is also why long-lead procurement should be judged as part of the wider question of whether the project is genuinely ready to start. A project can appear ready while one unmade procurement decision is already threatening the first meaningful workfront.
The commercial consequence can be just as important as the programme consequence. Early orders may consume contingency, create storage or expose the project to later design change. Late orders may lead to premium freight, acceleration, resequencing or idle labour.
The procurement decision is therefore not simply “when should we place the PO?” It is “what risk are we buying down, and what new risk are we accepting?”
That framing is particularly useful when management is asked to approve early commitment. The team can explain the programme consequence of waiting, the design uncertainty that remains, the supplier options available and the expected cost exposure.
A decision made in that form is easier to defend later. If the design changes, the project can see that the early commitment was a conscious programme choice rather than an uncontrolled procurement error.
It also helps prevent a common organisational problem: procurement being blamed for a decision that was actually driven by programme pressure, or planning being blamed for a supplier constraint that was never visible.
When the trade-off is explicit, responsibility becomes clearer and future estimating can learn from the outcome.
There is also a portfolio effect. Contractors often repeat the same categories of long-lead procurement across projects. If switchgear, lifts, façade systems or specialist equipment repeatedly create the same approval and supplier-capacity problems, the business should learn from that pattern.
Historical evidence can improve tender lead-time assumptions, preferred-supplier strategy and early-warning rules on future jobs. Long-lead control should therefore create organisational learning, not just save one project.
The final test is simple: if the package slips tomorrow, does the project already know which workfront, cost and customer commitment will be affected? If not, the procurement plan is still too isolated from delivery.
How Epicor Saturn connects procurement with project delivery
Epicor provides the enterprise-grade ERP foundation for purchasing, approvals, suppliers and financial commitments. Epicor Saturn adds the construction and engineering project context that connects procurement to package budgets, project need dates, approvals and site delivery.
This combination matters because long-lead procurement is not simply a supplier transaction. It is a project decision involving time, design, cost and execution.
Epicor Saturn provides the industry layer for that project-centric control while Epicor supplies the enterprise-grade transactional backbone. Explore Epicor Saturn for construction and engineering.
Frequently asked questions
Should every long-lead item be ordered immediately after award?
No. Release depends on programme need, lead time, design maturity and commercial risk.
What if design is not fully approved?
Management should make the trade-off explicit and understand the residual risk before committing.
Why track supplier milestones instead of only delivery date?
Because intermediate milestones provide earlier warning and more recovery time.
Is the lowest supplier price always the best procurement decision?
No. Capability, lead-time credibility and project risk can materially affect the real outcome.