Long-Lead Items: 10 Ways to Get Ahead of the Delay
A late transformer, pump or package can reshape the whole project. Six guests explain how to connect equipment availability, design decisions, manufacturing and delivery to the date the asset needs to work.
Updated The Major Project Podcast
From the conversations
Voices in this guide
The people and experience behind the insights. Choose a person to jump to their contribution.
PodBOK brings industry guidance together with real-world experience from major projects. Use it to inform your approach, and check the facts and requirements that apply to your project.
1.Find the constraint beyond the price tag
A long-lead item is a package whose full path to availability takes enough time to threaten the work that depends on it. Start by asking what could hold up energisation, testing or startup. The answer may be a major piece of equipment, an enabling connection, specialist support or a small component needed to complete a system.
Build the first watchlist with engineering, procurement, construction and operations in the room. Follow the chain from the operating requirement back to the supply decision. Give each item a named owner and a clear reason it matters; a list of expensive purchases alone will miss some of the most awkward constraints.
Which system or milestone cannot proceed without it?
When must it be usable, rather than simply delivered?
What design, connection, approval or specialist resource does it depend on?
2.Let availability inform the design while choices are still open
A design can be technically sound and still depend on equipment that cannot arrive in time. Take the required performance to the market early enough to compare credible configurations. Keep the engineering decision tied to capacity, compatibility, operating requirements and the delivery window.
Bring each viable option back to a joint engineering and procurement review. Record what changes in interfaces, controls, maintenance, spares, installation and testing. The useful output is an informed design decision, with its delivery consequences visible, rather than a late substitution that quietly pushes work into another package.
3.Know what has actually secured the production capacity
A promising conversation, a quotation, a capacity reservation and a released order are different positions. Make the current position explicit. If the schedule relies on a production slot, identify the commitment that holds it and every condition that could cause it to move.
For an early commitment, put the decision to the people authorised to make it: what needs to be secured now, what design is sufficiently settled, what remains uncertain, and what exposure is created if the project changes direction? Record the supplier confirmation, validity period, release conditions, remaining approvals and the person responsible for satisfying them.
Ask one direct question at the next review: if we did nothing else this week, would the manufacturing slot still be ours?
4.Schedule every step between the need and the usable item
The promised shipping date is only one point in the chain. Work backward from the system need and forward from the design release, then reconcile the two. Include the decisions the owner owes, vendor information needed by engineering, manufacture, inspection, transport, receipt and the work needed to make the equipment usable.
Give each dependency an accountable owner and connect it to the integrated schedule. A procurement register can show a healthy delivery date while an overdue design approval has already consumed the room available to recover. Make that relationship visible before either team reports its own part as on track.
Release basis: specification, interfaces and approvals needed to proceed.
Supplier path: order, vendor data, manufacturing milestones and agreed inspections.
Site path: transport, receipt, preservation, installation, testing and the receiving system.
5.Ask for the evidence behind the promised date
Treat a lead time as a claim with a basis. Establish when it was offered, what it includes and what must happen before its clock starts. Separate a market enquiry from a supplier-confirmed date, and separate either from a forecast that has been checked against actual progress.
When two dates disagree, trace them back to the same equipment scope and assumptions. Check the quantity, specification revision, manufacturing location, order-release conditions and delivery destination. A shorter number may describe a different starting point or exclude work that the project still needs.
Keep a link to the supporting quotation, confirmation or approved schedule beside the forecast. At review, ask what changed since that evidence was issued and whether the supplier has acknowledged the project's required date.
6.Follow manufacture through observable milestones
Once the order is placed, watch the work that produces the delivery date. Identify the manufacturing stages that matter for this package and agree what evidence will show that each is complete. Concentrate attention where a late discovery would leave little room to recover.
Use supplier reviews, relevant records and planned visits to resolve the questions the schedule cannot answer on its own. Is the equipment identifiable as this project's order? Are its own long-lead components available? Has a required review or inspection blocked the next stage? Has the forecast changed?
Bring procurement, engineering and quality together when an exception appears. Expedite the constraint that is holding up the work, with an owner and a decision date. Pressure to ship should not turn an incomplete acceptance requirement into an invisible problem for the site.
7.Plan the journey beyond the factory gate
Equipment does not become available to construction when a supplier marks it ready for dispatch. Map the physical route to its receiving location and the people who must make that route work. Remote projects make this especially visible, but the same problem can appear at a congested port or a site with restricted access.
Check the applicable transport permits, customs process, dimensions, lifting and unloading arrangements, route restrictions and storage conditions with the responsible specialists. Connect their dates to the delivery plan. Identify who receives the item, verifies its condition and records any missing parts or damage.
Review an alternative route or delivery sequence before it becomes urgent. Record the tradeoff in time, cost, handling and site readiness so that a recovery decision can be made with the whole journey in view.
8.Make the site ready to use what arrives
Early delivery can move the problem into storage. A large piece of equipment may arrive while its foundations, access, utilities, drawings or installation crew are still unavailable. Agree the receiving conditions with construction and operations, then track them alongside the item.
Before dispatch, hold a receiving-readiness check. Confirm the workfront, handling plan, preservation requirements, installation information and the resources needed for the next step. If installation must wait, make custody and preservation responsibilities explicit.
Use the next executable activity as the test of success. The purchase can be complete while the package is still unable to contribute to progress.
9.Keep the forecast current, and keep its history
A supplier date can survive in a spreadsheet long after the conditions behind it have changed. Review the assumptions when demand, trade conditions, design, capacity or the delivery route changes. Preserve the previous position so the team can see the movement and its cause.
Separate the required date, the supplier commitment and the current forecast. Give every update an evidence date and an owner. When comparing the procurement register with the schedule, align their reporting cutoffs or clearly explain the difference. A refreshed dashboard should not disguise an older supplier position.
At each review, ask which assumption has become weaker, which date has moved and which decision can still protect the downstream work. Send changes back through engineering, construction and commissioning so each team is working from the same position.
10.Escalate the effect on startup, with a decision to make
A late item deserves attention in proportion to what it changes. Trace the effect through installation, testing and the project objective before choosing a recovery action. Do not let an alarming delivery variance stand in for that analysis, or let available schedule room hide a growing cost or readiness problem.
Bring the decision-maker a small set of executable options: the current forecast and consequence, what each response changes, its cost and knock-on work, and the last useful decision date. Resequencing, an approved alternative or a different delivery arrangement only helps when the receiving teams can use it.
Use this long-lead register as the agenda for that conversation. Keep the detailed supplier records linked to it, and spend review time on changed assumptions and decisions.
Scroll sideways or use the arrow keys to see all columns.
A working long-lead register
Record
What the team needs to know
Item and owner
Equipment or package identity, responsible package owner and supplier contact.
Downstream need
Receiving system, usable-by date and the milestone or objective it supports.
Dates and basis
Required date, supplier commitment, current forecast, evidence date and supporting record.
Release and capacity
Design prerequisites, approval owner, order status and manufacturing-slot conditions.
Manufacture and route
Key production milestones, checks, transport path and delivery responsibilities.
Site readiness
Access, workfront, handling, preservation, installation information and receiving resources.
Exception and decision
Impact, response options, action owner and last useful decision date.
Read further
This top 10's Bookshelf
Explore the sources behind this article and related reading from our Bookshelf.
U.S. Government Accountability Office · Referenced by PodBOK
Why it's on the shelfGAO distinguishes a schedule status date, also called its data date, from the date someone views or saves the file. The status date separates actual progress from remaining work. That distinction matters when a freshly refreshed dashboard contains an older schedule position.
Why it's on the shelfISO describes risk management as part of governance, strategy, planning and reporting. Its overview covers identifying, analysing, evaluating, treating, monitoring and communicating risks, including opportunities as well as threats. This supports treating risk as continuing work connected to project decisions.
“Even though it’s called Capital Projects, that book is all about the front-end planning of projects. It’s not very technical in nature; it talks about the support mechanism required to be successful in the front-end phases. It’s geared towards executives, but still very accessible to anybody interested in capital projects. I definitely highly recommend it.”Roger Farish, on the show
Why it’s on the shelfThe IPA-rooted executive playbook for the exact phase Roger lives in, and the episode’s only book pick.
The connection can be as important as the equipment
James Wiseman
James Wiseman describes an energy-project market where electrical equipment, high-voltage expertise and grid connections all constrain delivery. His example broadens the question from buying a component to getting the whole installation connected and ready to use.
A supply assumption can change after the plan is written
James Wiseman
Wiseman describes how trade changes can redirect demand toward a different set of suppliers and lengthen their queues. The practical lesson from his example is to revisit the basis of a lead time when the market changes, rather than carrying an old quotation unchanged into the next forecast.
Find out what can be bought before fixing the design
Geoff Ryan
In his data-center discussion, Geoff Ryan describes starting with equipment availability, combining that with the required capacity, and designing around what can be procured. Engineering and procurement have to solve the delivery problem together.
Design, supply and construction have to meet in one sequence
Geoff Ryan
Geoff Ryan describes building the schedule around what can be obtained, how long design takes and the desired construction sequence. His path-of-construction discussion brings engineering and procurement into that conversation.
Geoff Ryan puts a strong focus on holding the equipment dates that drive the project schedule. He describes visiting the production facility and seeing the project's equipment being manufactured, rather than relying only on an expected delivery date.
Ryan describes installation work packages that foremen can execute because constraints have been removed. His construction background connects the planning output to the people who receive it in the field.
Test the arrangement behind the manufacturing slot
Akin Oni
Akin Oni recalls an Australian project whose independent reviewers challenged whether people and equipment would actually be available. He describes a supply agreement that kept manufacturing capacity accessible to the business, making the equipment plan more than an assumption in the investment case.
Tarun Gohel describes comparing a contractor's proposed pump delivery with the vendor's own quotation, then asking for the confirmation or signed purchase order behind the shorter promise. His audit also matches procurement and engineering registers to the schedule.
Remote logistics change when planning has to start
Bruno Caldas
Bruno Caldas recalls planning a remote Guinea project where bringing in another excavator took months. The response was to prepare and start procurement earlier. His surrounding account explains how limited local infrastructure and distant delivery capability shaped the work.
A late activity does not automatically mean a late project
Matt Mitchell
Matt Mitchell asks whether a delay actually changes the project objective. His example is equipment arriving late without changing startup, while still potentially creating a cost consequence.