Common Reasons Submittals Are Rejected — and How to Avoid Them
A rejected submittal can cost a project weeks and thousands of dollars. Most rejections are preventable. Here are the patterns that experienced project teams have learned to watch for — and what to do about them.
· 9 min read
A rejected submittal is one of the most avoidable sources of delay on a construction project. When a product data sheet is returned as Revise and Resubmit, or a shop drawing comes back Rejected, the consequences extend well beyond the inconvenience of preparing a new submission. If the product has a 12-week manufacturing lead time and the rejection was returned in week eight of that cycle, the procurement timeline has just been extended significantly. If the affected trade was scheduled to begin installation in week 14, that installation date is now at risk. If the general contractor cannot demonstrate that the submittal was deficient — rather than that the reviewer was unreasonable — the delay will likely be attributed to the contractor, with no entitlement to an extension of time or additional cost. Most submittal rejections share recognizable patterns. Understanding those patterns is the most practical thing a project team can do to protect its schedule and reduce the administrative burden of the submittal process.
Submitting a Product That Does Not Meet the Specification
The most straightforward reason a submittal is rejected is that the proposed product genuinely does not meet the requirements of the applicable specification section. This is more common than it should be, for several reasons. Procurement teams are often under cost pressure and may propose substitutions without fully evaluating specification compliance. Subcontractors may default to a preferred supplier or a product they have used on previous projects without checking whether that product meets the requirements of the current project specification. Specifications may also be unfamiliar to the person preparing the submittal — particularly on projects where a specialty specification format, a client-specific standard, or a referenced technical standard has requirements that differ from typical practice. The correct way to catch a non-compliant product before submission is to read the specification section carefully before selecting the product, identify every performance requirement, dimensional constraint, and referenced standard, and verify that the proposed product meets each item explicitly. If a product meets most but not all requirements, the discrepancy should be flagged in a cover letter and, if appropriate, an RFI should be submitted asking the design team whether the deviation is acceptable before the submittal is prepared. Submitting a non-compliant product without disclosing the deviation is the fastest way to generate a rejection and the slowest way to resolve a procurement issue.
Missing Required Documentation
Many submittal rejections are not rejections of the proposed product itself — they are rejections of an incomplete package. Specification sections typically list every document that must accompany a submittal: product data sheets, installation instructions, test reports demonstrating compliance with referenced standards, energy efficiency certifications, third-party inspection certifications, structural calculations stamped by a licensed engineer, samples, warranty documentation, or coordination drawings. When a submittal package omits one or more of these required items, the reviewer has two choices: return the entire package as Revise and Resubmit with a note identifying the missing documents, or approve the submittal conditionally and follow up on the missing documentation. Most experienced reviewers return the package rather than approve it with outstanding documentation, because approving an incomplete submittal creates the risk that the missing documentation is never provided and the project proceeds without confirming that all requirements were met. The most effective way to avoid this type of rejection is to read the submittal paragraph of the applicable specification section before preparing the package, create a checklist of every required document, and confirm that every item is included before the transmittal is sent.
Generic Product Data Instead of Project-Specific Documentation
A common source of first-round rejections is the submission of generic manufacturer's literature — a standard brochure or a comprehensive product catalog — instead of project-specific product data that clearly identifies the proposed model, configuration, options, and performance characteristics. A reviewer looking at a 40-page product catalog from a pump manufacturer cannot efficiently verify that the specific pump the contractor intends to use meets the specified flow rate, head, horsepower, and efficiency requirements. When the submittal does not clearly identify the exact model being proposed and show its specific performance data, the reviewer typically returns it asking for a specific product data sheet with the proposed model highlighted or clearly indicated. This is a common and easily avoidable delay. Every submittal package should clearly identify the exact product being proposed — manufacturer name, model number, specific options and configurations — and should highlight or mark the data sheet to direct the reviewer's attention to the values that demonstrate specification compliance.
Shop Drawings That Do Not Reflect the Contract Documents
Shop drawing rejections are often more serious than product data rejections because shop drawings represent proposed fabrication or installation, and a rejected shop drawing may require rework that affects other trades or the construction schedule. Shop drawings are rejected for several recurring reasons. First, the shop drawings may show dimensions, connections, or approaches that do not match the architectural or engineering drawings — either because the drafter made an error, because the subcontractor is proposing a different approach than what was designed, or because the shop drawings were prepared without adequately reviewing the current contract documents. Second, the shop drawings may not address coordination with adjacent systems. A structural steel shop drawing that does not account for the mechanical equipment clearances shown on the mechanical drawings, or a ductwork shop drawing that does not clear the steel framing shown on the structural drawings, will be returned with coordination comments. Third, the general contractor may submit shop drawings to the design team without first reviewing and stamping them, which is a contractual requirement under most standard agreements. Unstamped shop drawings signal that the GC has not fulfilled its own review obligation — and experienced reviewers will return them immediately.
Proposing a Substitution Without Following the Correct Process
Substitution requests — situations where the contractor proposes a product other than those specifically named in the specification — are a frequent source of submittal complications. Most specifications include a formal substitution request process that is separate from and prior to the submittal process. The contractor must submit a substitution request identifying the specified product, the proposed substitute, and a comparison of performance, quality, and compatibility demonstrating that the substitute is genuinely equivalent. The design team then reviews the substitution request and either accepts or rejects it. Only after a substitution request has been formally accepted should the contractor proceed with the submittal for the accepted substitute. Contractors who skip the substitution request process and simply submit an alternative product through the regular submittal process — without disclosing that it is a substitution — risk several outcomes: the reviewer may approve the submittal without noticing the deviation, creating a record that could later be disputed; the reviewer may reject the submittal as non-compliant, triggering a delay; or the reviewer may identify the issue and require a formal substitution request before the submittal can be reviewed, adding additional time. Following the correct substitution process is both the contractually required approach and the fastest path to getting an alternative product approved.
Submitting After the Required Date
Late submittals are not always rejected outright, but they create a situation where the consequences of any rejection or revision cycle are significantly worse. When a submittal is submitted on schedule, there is enough time in the procurement and construction timeline to accommodate one or even two rounds of resubmittal if needed. When a submittal is submitted late — because the contractor did not develop a front-loaded submittal schedule, did not identify the required submission dates during project planning, or delayed preparation because other priorities took precedence — even a first-round rejection can threaten the installation schedule. Reviewers are also generally less willing to expedite reviews for submittals that are submitted late; the contractor created the schedule pressure by submitting late, and the reviewer's obligation is typically to provide the contractually specified review period regardless of when the submittal was received. Preventing late submittals requires treating the submittal schedule as a procurement management activity — identifying all required submittals at project kick-off, working backward from required-on-site dates through installation schedules and procurement lead times to determine required approval dates, and then calculating submission dates that allow for one complete review cycle plus time for any resubmittal.
Resubmittals That Do Not Address All Review Comments
A resubmittal that addresses only some of the comments from the first review round is one of the most frustrating — and most preventable — sources of repeat rejections. When a reviewer returns a submittal as Revise and Resubmit, the review comments represent every identified deficiency that must be resolved before the submittal can be approved. A resubmittal that fixes the most obvious comment while overlooking a secondary comment, or that addresses the comment in the transmittal without actually revising the data sheet or drawing, will be returned again — with the remaining comments still unresolved and likely an additional comment noting that the previous comments were not fully addressed. Before a resubmittal is transmitted, the person preparing it should create a response matrix: a table that lists every comment from the previous review, describes exactly what was done to address it, and identifies where in the revised submittal the resolution can be found. Transmitting this response matrix with the resubmittal demonstrates that every comment was read and addressed, makes the reviewer's job faster and easier, and significantly increases the probability of approval on the resubmission.
How Better Tracking Prevents Repeated Mistakes
Many of the rejection patterns described in this article persist because teams lack the systematic visibility to identify them as patterns. When every project uses a different tracking approach — one PM uses a spreadsheet, another uses email folders, a third uses memory — it is impossible to build institutional knowledge about which subcontractors consistently submit incomplete packages, which specification sections generate the most resubmittals, or which reviewers return submittals most quickly. Structured submittal tracking software addresses this by maintaining a consistent, searchable record of every submittal across every project: what was submitted, when, what action was returned, how many rounds it took, and what the comments were. Over time, this record allows project managers to identify which preparation steps consistently reduce rejection rates, which subcontractors need additional guidance before submitting, and where specification requirements are consistently causing confusion — valuable information that directly reduces the administrative cost and schedule risk of the submittal process on future projects. PlanSpan's submittal tracking is designed to give construction teams this kind of structured visibility, connecting the submittal log to the rest of the project record so that nothing falls through the cracks.
