Submittals in Construction: What They Are, Why They Matter, and How to Manage Them
Submittals in Construction: What They Are, Why They Matter, and How to Manage Them
Submittals in construction are one of the most routine parts of project delivery and one of the most expensive when mismanaged. A rejected submittal rarely stays contained. It triggers an RFI, backs up a subcontractor's fabrication lead time, and, if the schedule has no float, it moves your substantial completion date. This reference covers the full submittal lifecycle, the real reasons rejections happen, and what good management looks like in practice.
What Are Submittals in Construction?
Definition and Purpose
A submittal is documentation that a contractor provides to the design team confirming that proposed materials, products, equipment, or methods conform to the contract documents. Submittals are not shop creativity. They are verification. The architect or engineer of record reviews them to confirm that what is being ordered, fabricated, or installed actually matches what was specified and detailed.
How Submittals Fit Into the Construction Workflow
Submittals live between award and installation. Before a subcontractor orders structural steel, curtain wall glazing, or mechanical equipment, the contractor packages relevant documentation, routes it through the general contractor for review, and submits it to the design team. Approval is the green light to fabricate or purchase. Without it, the contractor proceeds at risk.
Types of Submittals in Construction
Not all submittals carry the same weight. The five categories below cover the vast majority of what flows through a commercial project's submittal log.
Shop Drawings
Fabrication-level drawings produced by a subcontractor or supplier showing exact dimensions, connections, finishes, and installation details for a specific product or system. Structural steel, precast concrete, curtain wall, and millwork are common sources. Shop drawings must be cross-referenced against the contract drawing set and spec sections before the design team reviews them.
Product Data and Cut Sheets
Manufacturer data sheets, product catalogs, and performance specifications confirming that a proposed product meets spec section requirements. These are submitted for everything from mechanical equipment to door hardware to roofing membranes. A cut sheet that doesn't confirm the specified MERV rating or fire rating will come back rejected.
Material Samples
Physical samples of materials proposed for installation, typically required by spec sections for finishes, flooring, masonry, and other visible or performance-critical assemblies. Samples are reviewed for color, texture, finish quality, and conformance to referenced standards.
Certificates and Test Reports
Third-party certifications, laboratory test reports, and compliance documentation required by the spec. Common examples include welder certifications, concrete mix design approvals, and fire-resistance test reports for assemblies governed by spec section 07 84 00. Missing or expired certificates are a straightforward rejection.
Operation and Maintenance Manuals
O&M manuals are submitted near project closeout and document how installed systems are operated, maintained, and serviced. They are frequently underscoped in the submittal register and become a closeout bottleneck when not tracked from the start.
The Submittal Process Step by Step
1. Contractor Prepares and Submits
The general contractor, typically through a project engineer or superintendent, assembles the submittal package based on requirements called out in each spec section. The submittal register drives this. Every required submittal should be logged with a spec section reference, responsible subcontractor, required submission date, and required approval date based on the procurement schedule.
2. Architect or Engineer Reviews
Once the GC has stamped and reviewed the submittal internally, it goes to the architect or engineer of record. For complex systems, the structural or MEP engineer of record may need to review separately. Contractual turnaround windows are typically defined in the General Conditions, most commonly 10 to 15 business days.
3. Approval, Rejection, or Revision
The design team returns the submittal with one of four standard stamps: Approved, Approved as Noted, Revise and Resubmit, or Rejected. "Revise and Resubmit" is effectively a rejection for scheduling purposes. The subcontractor must revise and resubmit, and the clock resets.
4. Approved Submittals Returned to Field
Stamped, approved submittals are returned to the contractor and distributed to the field team. Copies go to the relevant foreman, the project file, and often the owner. Work performed without an approved submittal is at risk of rejection during inspection or at closeout.
Why Submittals Get Rejected - and What It Costs
Common Reasons for Submittal Rejection
The most frequent drivers of rejection are product substitutions that don't meet spec requirements, shop drawings that conflict with design intent, missing certifications or test data, and incomplete documentation packages. Many of these are avoidable with thorough internal review before the submittal leaves the GC's office.
The Downstream Impact: RFIs, Change Orders, and Schedule Delays
A single rejection adds at minimum one full review cycle. On a fast-track project with long equipment lead times, that can mean a missed fabrication window of four to six weeks. Rejections also generate RFIs when the contractor needs clarification before revising. Projects average roughly 800 RFIs, and a significant portion trace back to submittal problems. If an RFI produces a design change, a change order follows. One undetected contradiction on a typical commercial project costs $340,000.
How Document Inconsistencies Trigger Submittal Problems
Contradictions Between Drawings and Specifications
The drawing set says one thing. The spec section says another. The contractor submits based on the drawing. The architect reviews against the spec. Rejection. This is not a rare edge case. Contradictions between the drawing set and spec sections are embedded in virtually every large document package at bid time, and they surface at the worst possible moment.
Scope Gaps That Surface During Submittal Review
A scope gap is missing scope, an assembly or system that the contract documents neither fully detail nor specify. Scope gaps are often discovered during submittal review when neither the GC nor the design team can point to a spec section governing the submitted product. The result is a hold, an RFI, and frequently a change order.
Lintel analysis of commercial construction document sets shows that over 60% of submittal rejections can be traced back to contradictions or ambiguities present in the original drawing and specification package - issues detectable before a single submittal is prepared.
Best Practices for Managing Construction Submittals
Build a Submittal Register Early
Pull every required submittal directly from the spec sections during preconstruction. Each spec section that requires submittals lists them explicitly. A complete register, built at or before notice to proceed, gives the project team a defensible schedule and makes it possible to identify long-lead items before they become critical path problems.
Set Clear Review Turnaround Windows
The General Conditions define the review period, but the project team should confirm those windows are realistic given the design team's capacity. A 10-business-day window during a period with 40 concurrent submittals in review is a fiction. Sequence submittals to manage the design team's load and flag any anticipated bottlenecks early.
Coordinate Submittals With the Project Schedule
Every submittal required approval date should be back-calculated from the installation date, accounting for fabrication lead time and delivery. Submittals that aren't tied to the construction schedule are logged but not managed. When the schedule slips, uncoordinated submittals become emergencies.
Use Technology to Track and Flag Issues
A submittal log in a spreadsheet works until it doesn't. Construction management platforms that integrate the submittal register with the schedule and RFI log make it possible to identify conflicts before they become delays. The next step, flagging problems in the source documents before submittals are even prepared, is where AI-assisted document review adds direct value. Teams that catch document conflicts before they reach the submittal stage spend less time managing rejections and resubmittals.
How AI Is Changing Submittal Management
Catching Document Conflicts Before Submittals Are Even Prepared
The traditional model is reactive. A contractor prepares a submittal, the design team finds a conflict, and the team resolves it under schedule pressure. AI document review flips this. By reading the entire drawing set and all spec sections together at preconstruction, it identifies contradictions and scope gaps before any party has committed to a product, a fabrication schedule, or an installation sequence.
How Lintel Reduces Submittal-Related RFIs
Lintel reads commercial construction document sets and surfaces contradictions, scope gaps, and compliance risks across the full package. When a spec section calls for one fire-stopping system and the drawing details show another, Lintel flags it before the affected submittal is prepared. That means fewer resubmittals, fewer RFIs, and fewer change orders generated by conflicts that were always in the documents.
FAQ
What is the difference between a submittal and an RFI in construction?
A submittal is contractor-prepared documentation confirming that materials or methods conform to the contract documents. An RFI is a formal question sent to the design team requesting clarification on the contract documents. Submittals verify compliance; RFIs resolve ambiguity. A rejected submittal often generates an RFI if the contractor needs design guidance before revising.
Who is responsible for managing submittals on a construction project?
The general contractor owns the submittal process. A project engineer or project manager typically maintains the submittal register, coordinates with subcontractors, reviews packages before routing them to the design team, and tracks approval status. The architect or engineer of record is responsible for timely review within the contractual window.
How long does the submittal review process typically take?
Most contracts specify 10 to 15 business days per review cycle. Complex submittals involving structural or specialty engineering may take longer. A "Revise and Resubmit" response resets the clock, so a single submittal requiring two review cycles can consume four to six weeks before approval.
See what Lintel finds in your document set - Book a demo