Procurement risk shows up in a schedule as long-lead activities with no logic, phantom float, and delivery dates that ignore submittal and approval time. Spot it with a DCMA-style logic check on every procurement path, then resolve it by tying real lead times to real successors and re-running the critical path.

Procurement stopped being a purchasing detail and became a scheduling problem. In the AGC of America and Sage 2026 Construction Hiring and Business Outlook, a survey of 951 firms across 49 states and the District of Columbia, 45 percent of respondents reported no supply-chain issues in 2025, which leaves a majority that did. The constraints those firms described were increasingly tied to lead times, specifications, and compliance requirements rather than broad material shortages.

That distinction matters. A material shortage is a market condition. A lead time is a schedule input, which means it belongs in the CPM network where it can be measured, and where a slip can be traced.

What is a procurement risk in a construction schedule?

A procurement risk is any condition in the schedule where an equipment or material package can slip without the schedule showing it, or where a known slip does not translate into a forecast change. It is a modeling failure as much as a supply failure.

The four common forms:

• Compressed representation. The entire package sits in one activity bar, so submittal, review, fabrication release, fabrication, shipping, and site delivery are invisible.
• Detached logic. The delivery milestone has no successor, so the installation work that depends on it does not move when delivery moves.
• Optimistic durations. The lead time in the schedule came from a catalog, a prior project, or an estimate, not from a current written quote.
• Constrained dates. A hard constraint pins the delivery to the date the team needs, which suppresses the negative float that would otherwise expose the problem.

How do you spot procurement risks in a CPM schedule?

Run a logic health check on the procurement subnetwork specifically, not just on the schedule as a whole. Filter the schedule to procurement and long-lead activities, then apply the DCMA 14-point assessment default thresholds to that filtered set. Procurement paths fail these checks far more often than field work does, and a whole-schedule score can pass while the procurement subnetwork is broken.

The checks that catch the most:

• Missing logic (threshold: 5 percent or fewer incomplete activities without a predecessor or successor). Delivery milestones loaded as endpoints are the usual offenders.
• High float (5 percent or fewer incomplete activities above 44 working days of total float). On a procurement path, high float is almost never real slack. It is a missing successor tie.
• Negative float (threshold: zero). Any negative float on a procurement path means the schedule already cannot deliver to its own dates.
• High duration (5 percent or fewer incomplete activities above 44 working days). A single 300-day “procure switchgear” bar passes no useful information and hides where a slip started.
• Hard constraints (5 percent or fewer). A Must Finish On applied to a delivery date is the most common way procurement risk gets hidden.
• Critical path test. Add a deliberate delay to the long-lead delivery and confirm the project finish moves. If it does not, the package is not connected to anything.

Which procurement items carry the most schedule risk right now?

Electrical equipment, consistently. AGC respondents named switchgear, transformers, generators, and control systems as the most frequently mentioned supply-chain problems, followed by HVAC and mechanical systems including chillers, air-handling units, controls, and insulation. Steel and other metal products, ductile iron fittings, specialty valves, and select precast and underground materials also appear.

Published lead-time trackers put the electrical scope for large projects in the range of 12 to 18 months, and some individual categories run longer. CMiC reports generators, transformers, and switchgear frequently carrying 12 to 18 month lead times on data center work. Treat any published range as a starting point for a conversation with the manufacturer, not as a schedule input. The only lead time worth putting in a baseline is one you have in writing, dated, from the supplier who will actually build the unit.

How do you resolve a procurement risk once you have found it?

Fix the model before you fix the plan. A recovery decision made against a broken schedule is a guess.

1. Decompose the package. Replace the single bar with the real chain: submittal preparation, owner and engineer review, approval, fabrication release, fabrication, factory acceptance testing where applicable, shipping, and site delivery.
2. Replace the assumed lead time. Get written confirmation from the manufacturer, with a date on it.
3. Tie delivery to its true first successor. Usually the installation activity, not a floating milestone.
4. Remove the constraint and re-run CPM. Whatever float or negative float appears is the actual exposure.
5. Select a response and record it. Early release or slot reservation, an alternate manufacturer or approved-equal specification, owner-furnished procurement ahead of the trade award, resequencing dependent work off the delivery date, or a formal time extension request.

Document the date the exposure was identified and the date the response was chosen. On a disputed job, that record is often what separates an excusable delay from a compensable one. Stelic builds this into the planning and scheduling process rather than reconstructing it later.

How much float should a long-lead procurement activity have?

Less than you probably see. The DCMA default flags any incomplete activity carrying more than 44 working days of total float, and expects fewer than 5 percent of activities to exceed it. On procurement paths, float above that threshold is usually phantom float created by a missing successor, not genuine margin.

Real procurement contingency should be an explicit, named buffer activity with a documented basis, sitting between delivery and installation. That way it is visible, it can be consumed deliberately, and it can be defended. Float that exists because nobody tied the logic is not contingency. It is an error that happens to look like good news.

How often should procurement logic be reviewed?

Every schedule update cycle, monthly at minimum, and separately from the progress update. Progress updates tend to focus on what moved in the field, which means a procurement path can go stale for months without anyone opening it.

Re-confirm quoted lead times on long-lead packages at least quarterly. Quoted lead times move, and a baseline built on a quote from two quarters ago is carrying an assumption nobody has tested. AGC found firms already reacting to this pressure: 41 percent accelerated purchases after winning contracts, 29 percent turned to alternative suppliers, and 24 percent specified alternative materials or products.

What extra procurement risks apply to federal projects?

Two, on top of everything above.

First, schedule quality is formally assessed. The GAO Schedule Assessment Guide (GAO-16-89G) sets out ten best practices for a reliable schedule, including capturing all activities, sequencing all activities, confirming a valid critical path, ensuring reasonable total float, and conducting a schedule risk analysis. A procurement package that is not decomposed and logically tied will fail more than one of those on review.

Second, domestic sourcing narrows the vendor pool. AGC respondents specifically pointed to Build America, Buy America and American Iron and Steel requirements as drivers of higher costs and longer lead times, particularly for electrical, mechanical, and water-related products. On a federal project, a compliant supplier list may be short enough that a single manufacturer slipping is a program-level event, not a package-level one. That belongs in the risk register with a named alternate, not in a footnote.

The short version

Procurement risk is rarely invisible. It is usually sitting in plain view as a long bar with no successor and a suspicious amount of float. The work is opening the procurement subnetwork on a schedule and treating it with the same logic discipline as the field sequence.

Stelic runs this on owner-side capital projects through project controls and construction management engagements. If your procurement paths have not been tested against a delay, get in touch.

Sources

• Associated General Contractors of America and Sage, The 2026 Construction Hiring and Business Outlook. Survey of 951 firms conducted November 4 to December 15, 2025.
• U.S. Government Accountability Office, Schedule Assessment Guide: Best Practices for Project Schedules, GAO-16-89G, December 2015.
• Deltek, What is the DCMA 14-Point Assessment? Reference for the commonly applied default thresholds.
• CMiC, Data Center Construction Trends. Lead-time ranges for generators, transformers, and switchgear.