Why Submittals Get Rejected More Often Than PMs Expect

Architects spend years learning how to specify correctly. The specifications they produce are precise. The product data requirements are clearly stated. And yet, the submittal review process still generates a staggering volume of rejections, revisions, and delays that eat into project timelines long before a single piece of equipment gets installed.

This is not a new problem. But it is one that the design community rarely examines from its own perspective. The conversation around submittal rejections tends to default to contractor fault. Products submitted out of spec. Wrong manufacturer. Missing documentation. These things happen, and often. But the full picture is more complicated, and understanding why rejections happen at the scale they do requires looking at the review process itself, not just what gets submitted.

The Scale of the Problem Is Larger Than Most Realize

Industry data puts the average first-round rejection rate for construction submittals at 30 to 40 percent. On a project with 2,000 submittal items, that translates to 600 to 800 items that need to go back to the contractor, get corrected, and come around again. Each of those cycles adds two weeks or more to the approval process for that item. For long-lead equipment sitting on the critical path, those weeks compound.

The Associated General Contractors of America found in its 2024 workforce survey that 78 percent of construction firms experienced at least one project delay in the prior twelve months, with workforce and process bottlenecks among the most commonly cited causes. Submittal review sits at the intersection of both. It demands skilled reviewers who are already stretched across multiple projects, and it operates on a manual process that does not scale well when submittal volumes spike during the early phases of construction.

What surprises most people outside the day-to-day of project engineering is that many rejections are not the result of egregiously non-compliant products. They stem from something quieter: the gap between what a specification requires, what a contractor believed was being submitted, and what a reviewer had time to check thoroughly under real project conditions.

Where the Process Actually Breaks Down

The formal definition of a submittal is deceptively simple: a document, sample, or product data package that the contractor provides to the design team for review and approval before installation. In practice, a single submittal for a rooftop unit might run 60 to 70 pages, with technical characteristics distributed across multiple data sheets from multiple manufacturers. A reviewer checking that unit against the mechanical specs needs to trace voltage ratings, refrigerant type, coil coatings, dimensions, certifications, and a dozen other data points across all of those pages.

Manual review does not fail because reviewers are careless. It fails because the volume and technical depth required on a modern commercial project exceeds what any individual reviewer can sustain at full accuracy across hundreds of submittals. When startup-phase pressure hits and submittal volumes peak, something gives. The items that get thorough reviews are the ones the reviewer knows from experience are highest-risk. The rest move through faster than they should.

That dynamic is invisible in the aggregate rejection rate. What looks like a contractor compliance problem is often partly a review-capacity problem: teams that cannot review every characteristic on every submittal end up approving items that should have been caught, or sending rejections based on incomplete checks that generate unnecessary back-and-forth.

At the industry average of 35% first-round rejections, a 2,000-submittal project absorbs roughly 700 revise-and-resubmit cycles before construction begins. Each adds two or more weeks to that item’s approval clock.

The Hidden Costs That Show Up Later

A rejected submittal does not just cost the time it takes to resubmit. It creates coordination overhead across multiple parties: the contractor revising the documentation, the sub coordinating with the vendor, the project engineer re-reviewing, and in many cases the design team reviewing a second or third time. That overhead accumulates across the project and shows up in budget variances and schedule extensions that get attributed to generic causes.

For architects and engineers, repeat review cycles have a real cost that goes beyond billable hours. They erode the working relationship with the contractor. They create ambiguity about what was communicated in the specifications. And they generate documentation risk: if an approved submittal later turns out to be non-compliant with something that was missed in review, the professional liability exposure sits with the design team, not just the contractor.

McKinsey’s 2024 analysis of construction productivity stagnation and its causes identified inadequate design and review processes as one of the structural contributors to the industry’s inability to improve output per hour. The submittal review cycle, unreformed for decades, fits that description precisely.

What Better Pre-Review Coordination Actually Looks Like

The most effective lever available to reduce rejections is not tighter specifications. Specifications are already detailed. The lever is improving what reaches the design team in the first place.

Contractors who build pre-submission checklists for common equipment types, verify manufacturer compliance before ordering, and cross-reference product data sheets against spec sections before submission consistently achieve lower rejection rates. The improvement is not dramatic in any individual submittal. It compounds across the volume of a project.

This is partly a coordination and training issue, and partly a resource issue. AGC’s 2024 data on construction workforce shortages showed that 62 percent of firms reported available candidates lacked the skills required for open positions. Project engineers handling submittal review are often early in their careers, working without the technical depth to catch every compliance issue on complex MEP submittals. That is not a criticism; it is a structural reality.

For design teams, this means that the quality of what comes in for review is partly a function of the experience and resources on the contractor side. Providing clearer pre-submission guidance, specifying what documentation is required for each submittal category, and flagging high-risk items early in the project can meaningfully reduce the back-and-forth.

Where Technology Is Starting to Make a Difference

The manual submittal review process has remained largely unchanged for decades. A reviewer opens a PDF, works through the data sheets, compares values against the spec, and either approves or rejects. The tools have improved, but the underlying process has not.

What has changed in recent years is the emergence of platforms capable of extracting technical characteristics from submittal documents automatically and checking each one against project specifications. Rather than a reviewer manually tracing a refrigerant type through 70 pages of product data, the system pulls every relevant characteristic and flags what does and does not comply. The reviewer then focuses on the items that require judgment, not the ones that require data extraction.

Teams using this approach have reduced submittal rejection rates from the industry average of 35 percent to around 5 percent. The process works by extracting every technical characteristic from a submittal document and comparing it against the project specs automatically, so reviewers are working from a flagged compliance report rather than raw PDF pages. The time savings are substantial: reviews that previously took days get turned around in hours.

The implications for design teams are meaningful. When contractors do thorough technical reviews before submittals reach the architect or engineer, the quality of what lands on the design team’s desk improves. Reviewers spend less time on basic compliance checks and more time on the judgment calls that actually require design expertise: substitution evaluations, RFI resolution, and the edge cases where specs and field conditions diverge.

A Shared Problem That Needs a Shared Framework

Submittal rejections are typically framed as a contractor problem that inconveniences the design team. The more accurate framing is that they are a process problem that affects everyone, and one that the design community is well-positioned to help solve.

Architects who understand why rejections happen at the scale they do are better equipped to structure the submittal requirements section of their specifications, communicate with contractors about what constitutes a complete submission, and recognize when a rejection reflects a review-capacity gap rather than deliberate non-compliance.

AGC’s most recent survey data shows that 78 percent of firms experienced at least one delayed project in the past twelve months. Submittal bottlenecks are a contributing factor in a meaningful share of those delays. Reducing them is not just a contractor efficiency goal. It is a project delivery goal, and the design team’s role in that outcome is larger than the traditional framing suggests.

Getting submittals right the first time is one of the few levers that can genuinely shorten the gap between specification and installation. It is worth understanding in that light.