Every project has a schedule problem hiding inside the submittal process. Most teams do not see it coming until it has already cost them weeks.
The mechanics are straightforward. A subcontractor submits product data for a piece of mechanical equipment. The GC’s project engineer reviews it, or tries to, against a spec section that runs 30 pages. Something gets missed. The submittal goes to the design team, comes back rejected, and now the clock on procurement has not started yet. For equipment with a 20-week lead time, a two-round rejection cycle does not just add two weeks to the review. It can push delivery past the installation window and pull the critical path with it.
Schedule delays in construction come from many directions. But the submittal phase is one of the few where a process change, applied early, can prevent cascading downstream consequences before they happen.
Why the submittal phase carries outsized schedule risk
The submittal phase sits at an awkward intersection. It happens during mobilization and early construction, when project teams are already stretched across RFI responses, subcontractor coordination, scheduling updates, and a dozen other concurrent demands. At the same time, the decisions made during this window have long downstream consequences that do not become visible until much later.
The AGC’s 2024 workforce survey found that 80% of contractors experienced project delays in the prior year, with workforce constraints cited as the top cause. The teams responsible for submittal review are operating in that same environment. When experienced project engineers are stretched thin across multiple projects, review depth suffers. Items that would have been caught in a thorough read get waved through, and the consequences surface later when equipment arrives on site that does not match what the spec required.
The equipment categories that carry the most schedule risk are long-lead mechanical and electrical items: chillers, air handling units, switchgear, generators, and similar equipment that requires manufacturing lead times of 16 weeks or more. Vizient’s analysis of construction supply chain lead times found that custom air handling units, which once took around 15 weeks from submittal approval to delivery, now run closer to 30 weeks. Large electrical generators have stretched from 35 to 40 weeks to 65 to 75 weeks. A single rejection cycle on any of these items does not add two weeks to the review process. It adds two weeks to an already compressed procurement window.
How submittal rejections translate into schedule impact
A rejected submittal is not a paperwork problem. It is a procurement freeze. Until a submittal is approved, a purchase order cannot be issued. Until the purchase order is issued, the manufacturer does not begin production. For long-lead equipment, that sequence is the critical path.
Industry data puts first-round submittal rejection rates at 30 to 40% across commercial construction. Each rejection adds at least two weeks to the review cycle. On a project running 500 submittals, a 35% rejection rate means roughly 175 items cycling through a second review before procurement can begin. The aggregate schedule exposure across those items is not distributed evenly. A handful of rejections on critical-path equipment can absorb most of the project’s schedule float before foundation work is complete.
The pattern is consistent: rejections happen not because subcontractors ignore specifications, but because the technical comparison between submitted product data and project requirements is genuinely difficult to do well under time pressure. A spec section for a variable air volume unit references dozens of performance requirements across multiple subsections. A project engineer working through that review manually, while managing a full workload, is unlikely to catch every mismatch on the first pass.
Teams that have reduced their rejection rates significantly tend to have one thing in common: they treat the GC’s preliminary review as a real technical checkpoint, not a routing step. That means verifying individual product characteristics against specifications before the submittal leaves the GC’s desk, rather than relying on the design team to catch what was missed. Tools built for submittal package review and preparation support that process by extracting technical characteristics from product data and running the comparison against project specifications automatically, so teams catch non-compliance at the stage where it costs the least to fix.
Key stat: Custom air handling units now carry lead times of up to 30 weeks from submittal approval to delivery. A single rejection cycle on critical-path mechanical equipment can consume weeks of schedule float that teams assumed they had.
Front-loading review to protect the procurement schedule
The most effective schedule protection strategy during the submittal phase is not faster review. It is earlier review, applied to the right items.
Long-lead equipment should be identified in preconstruction, before the submittal schedule is finalized. That identification drives a sequencing decision: which submittals need to be submitted, reviewed, and approved first, so that purchase orders can be issued before lead time windows close? The answer is almost always the mechanical and electrical equipment on the critical path.
When that sequencing is clear, the GC’s review process can be prioritized accordingly. Instead of reviewing submittals in the order they arrive, teams review the items that carry the most schedule risk first. A rejection on a lighting fixture can be absorbed. A rejection on a chiller that has a 24-week lead time requires immediate escalation, a fast turnaround from the sub, and an expedited re-review, and even then, the schedule may not recover fully.
Front-loading also changes how subcontractors prepare packages. When subs understand that their mechanical submittals are on the critical path and that the GC intends to review them thoroughly before forwarding to the design team, they tend to be more careful about pre-screening for compliance before submission. The knowledge that a rejection will have visible schedule consequences raises the bar on submittal quality before it enters the review cycle.
Where review quality breaks down under pressure
Even teams with strong submittal processes see quality degrade in specific conditions. The most common is the startup rush, when a large volume of submittals arrives in a short window and the review team does not have capacity to work through all of them thoroughly.
In that environment, the items most likely to receive a shallow review are the complex ones, because they take the most time. A multi-product mechanical submittal with 60 or more technical characteristics to verify against plans and specifications can take hours to review correctly. Under deadline pressure, that review gets compressed. The reviewer checks the obvious items, notes that the product appears to be the right manufacturer, and approves it. The subtle mismatches, a refrigerant type that does not match the spec, a missing coating requirement for a corrosive environment, a warranty term shorter than what was specified, get through.
Each of those mismatches is a potential rejection when the submittal reaches the design team. Each rejection is a procurement delay. And each procurement delay on a long-lead item is a schedule risk that was created at the review stage and will not be visible until weeks later.
Building a process that holds up under load
Schedule delays during the submittal phase are rarely the result of a single failure. They accumulate from a pattern of shallow reviews, late submissions, and slow turnaround cycles that compound across dozens or hundreds of items over the course of mobilization.
Addressing that pattern requires changes at the process level, not just effort at the individual review level. That means sequencing submittals by schedule criticality, not just division order. It means establishing clear turnaround expectations with subcontractors so that re-submittals on critical-path items move quickly. It means building review capacity that does not collapse under the volume of a busy startup phase.
And it means recognizing that the submittal phase is not administrative work that runs alongside the real project. It is the mechanism that either clears the path for procurement, fabrication, and installation to proceed on schedule, or creates the bottlenecks that show up in every delay claim filed six months later.
The teams that protect their schedules through the submittal phase treat it that way from the beginning.