Every superintendent has a story about the piece of equipment that showed up three months late. Mine was a set of custom air handlers on a mid-rise senior living job. The submittal sat on an architect's desk for six weeks because nobody flagged it as urgent, the factory quoted 22 weeks after approval, and by the time the units rolled up on the truck we'd already dried in the building and were standing around wondering how to get four 3,000-pound boxes up to a mechanical penthouse whose only opening we'd just framed shut. That delay cost more than any labor overrun on the whole project.
Long lead items are the quiet schedule killers. They don't blow up your weekly work plan the way a rained-out pour or a no-show crew does. They fail slowly, months in advance, in a submittal log nobody's reading. The whole point of running a disciplined look-ahead process is to drag those failures into the daylight while you can still do something about them.
What actually counts as a long lead item
The textbook answer is anything with a long procurement time. The useful answer is anything whose lead time is longer than the window your normal look-ahead can see. If your crew is planning six weeks out and a piece of switchgear takes 30 weeks from release, that item lives entirely outside your field-of-view until it's already a crisis. That gap is the problem, not the lead time itself.
On most commercial and multi-family jobs the usual suspects are:
- Electrical gear — switchgear, transformers, panelboards, and generators. Switchgear routinely runs 20 to 40+ weeks and got dramatically worse after 2021. This is the single most common item that lands projects in delay.
- Mechanical equipment — chillers, cooling towers, custom air handlers, packaged rooftop units, and controls.
- Vertical transportation — elevators and escalators, which carry both a long fabrication window and their own installation crew you have to reserve.
- Building envelope — curtain wall, storefront, and specialty glazing, all of which need engineering and shop time before anything ships.
- Structural and architectural fabrication — structural steel, precast, open-web joists, custom millwork, and specialty stone or tile.
Write your own list for your market and your building type, then keep it. After a few jobs you'll know which items bite you, and that institutional memory is worth more than any published lead-time chart.
Treat the item as a constraint, not a line on a bar chart
In Last Planner terms, a long lead item is a constraint on every downstream activity that can't proceed without it. You can't set the elevator rail if the elevator isn't on site. You can't energize the building without gear. You can't close the exterior wall if the curtain wall panels are still being extruded. The discipline of Last Planner is that you don't put work into a weekly work plan until it's made ready — every constraint removed. A missing long lead item is an unremoved constraint that will sit there for months.
The trap is that these constraints are invisible on a normal look-ahead because the delivery date is beyond the horizon. So the real work isn't tracking the item during the six weeks before you install it. It's working backward from the install date, months earlier, to figure out the last responsible moment to get the order placed. That backward pass is where projects are won or lost.
Work backward from need date to order date
Every long lead item has the same chain of milestones, and each link has to happen on time or the whole thing slips:
- Submittal prepared and submitted by the sub or supplier.
- Submittal reviewed and approved by the design team — budget two to four weeks, longer if it bounces back with comments.
- Purchase order released and the item put into the fabrication queue. Nothing gets built before this. A common and painful mistake is assuming the clock starts at approval when it actually starts at release.
- Fabrication — the long part.
- Ship and deliver.
- Installed and, where required, inspected or commissioned.
Do the arithmetic in reverse. If you need the gear energized in week 60, and the manufacturer quotes 30 weeks from release, plus four weeks of shipping and rigging buffer, plus three weeks for submittal review, plus two weeks for the sub to actually assemble the submittal, you needed that submittal in hand around week 21. On a job that hasn't even broken ground yet. That's the calculation the original schedule almost never surfaces, and it's exactly what a look-ahead process should force you to confront early.
A rule of thumb worth living by: add a real buffer, not a wishful one. Quoted lead times are optimistic. Ports get congested, a chip shortage stalls the controls, the factory's own supplier slips. On a critical item I'll carry two to four weeks of buffer on the delivery and I'll treat the manufacturer's quoted date as the earliest plausible date, not the expected one. If losing the item stops the job, buy the buffer.
Give long lead items their own horizon
This is the piece most crews get wrong. A three-, four-, or six-week look-ahead is the right tool for coordinating trades and clearing near-term constraints — sequencing framers ahead of rough-in, making sure the deck is ready before the roofers show. It is the wrong tool for something 30 weeks out. You can't manage a nine-month procurement in a six-week window.
So run two horizons. Your normal rolling look-ahead handles field coordination. Alongside it, keep a procurement log — often called a long-lead or submittal-and-procurement schedule — that tracks the big items on their own timeline with their own milestone dates. The two connect at exactly one point: the delivery date on the procurement log becomes a make-ready constraint on the install activity in the field look-ahead. When the item is confirmed on site, that constraint clears and the work is allowed into a weekly work plan. Until then, that activity stays out, no matter how much the sub wants to load it.
Good look-ahead scheduling software makes this connection visible instead of leaving it buried in a spreadsheet somebody forgot to open. In LookAheadWall you can flag the delivery as a constraint on the dependent activity, so the item literally can't be pulled into a plan week until it's been marked ready — the tool enforces the discipline your busiest weeks tend to erode.
Track status where the field can see it
A long lead item needs six things tracked, and all six need to live somewhere the whole team can see, not in one person's head:
- What it is — specific enough that there's no confusion (which panelboard, which AHU tag).
- Need date — when the field actually has to have it.
- Order-by date — the last responsible moment to release, from your backward pass.
- Current milestone — where it sits in the chain above.
- Confirmed delivery date — from the vendor, in writing, updated.
- Status flag — on track, at risk, or late.
The status flag is what turns a static log into an early warning system. When an order-by date passes without a release, that item should light up red in front of the superintendent, the PM, and the sub. The failure mode isn't usually that nobody knew the item was long lead — it's that the slip happened quietly and nobody noticed until the need date arrived. Make the slip loud.
Stay on the vendor — silence is not good news
Once an item is in fabrication it's easy to file it under "handled" and move on. Don't. The projects that get burned are the ones where the GC assumed no news meant good news and found out at week 28 that the factory had quietly pushed to week 36. Set a regular cadence — every two to four weeks depending on how critical the item is — where somebody actually asks the vendor for a production update and a reconfirmed ship date. Put the answer in the log. If the vendor gets vague or stops answering, treat that as a red flag in itself.
Have a plan for when it slips anyway
Even a well-run job takes a hit sometimes. The difference between a headache and a disaster is whether you thought about the fallback before you needed it. A few moves worth having in your pocket:
- Re-sequence around the hole. Ask what work can proceed without the item. Can you close and finish the rest of the floor and leave the mechanical room open? Roughing everything you can now shortens the tail once the item lands.
- Temporary measures. A rental generator or temporary power can keep you commissioning while permanent gear is en route. It costs money, but often less than the schedule slip.
- Expedite — with clear eyes. Some manufacturers will accelerate for a premium. Get the real cost and the real new date in writing before you commit; expedite fees have a way of buying less time than promised.
- Substitute. Occasionally an equal product from a supplier with stock will clear the design team. This lives or dies on how fast the architect and engineer will approve it, so start that conversation early.
Make it a subcontractor conversation, not a blame game
Most long lead items belong to a sub — the elevator's on the elevator contractor, the gear's on the electrician. That doesn't get you off the hook. Your job is visibility: knowing exactly who owns each item and pulling their real procurement status into your schedule instead of taking "it's handled" at face value. When the electrician's switchgear slips, it's your building that sits idle. Bake procurement status into your regular sub coordination — pull-plan sessions and weekly meetings are the natural place to ask "where's the gear" and get a straight, dated answer.
The habits that actually prevent the 3 a.m. phone call
Strip away the tools and software and it comes down to a handful of habits. Identify long lead items at buyout, before the ground's even broken — a specification review with your key subs at kickoff catches the big ones. Do the backward pass from need date to order date, and carry a real buffer. Give those items their own horizon so they don't hide behind a six-week window. Keep the status visible and loud, chase your vendors, and build the fallback plan while you still have room to use it.
None of that is glamorous. It's a log, a cadence, and the discipline to look months ahead when everyone around you is fighting today's fire. But the superintendents who never seem to get caught by a late elevator aren't lucky — they just made the invisible constraint visible early, and refused to let it slip quietly. That's the entire game.