What Is a Submittal in Construction? The Document That Approves Materials Before They're Installed
A submittal in construction is a formal package the contractor provides to the design team — the architect, engineers, and specialty consultants — for review and approval before specific materials, products, or shop-fabricated items go into the project. The submittal lets the design team verify that what the contractor intends to install actually meets the specifications, and catches substitutions or misinterpretations before they become installed and expensive.
Submittals are one of the highest-volume documentation streams on any project. A midsize commercial building might have 300-800 submittals across its life. Mechanical, electrical, structural steel, curtain wall, equipment — every scope with manufactured components generates submittals. Keeping the log moving is one of the core project management functions during the construction phase.
Specifications call for several kinds of submittals, each with its own purpose:
Submittal types commonly required
- Product data — manufacturer cut sheets, catalog data, installation instructions for products listed in the specifications. Verifies the specific product meets the spec's performance, dimensional, and aesthetic requirements.
- Shop drawings — detailed fabrication drawings for components custom-fabricated to the project (steel connections, precast pieces, custom casework, curtain wall details). Shows how the fabricator interpreted the design drawings into manufacturable detail.
- Samples — physical or photographic samples of finishes, materials, and colors. Carpet samples, paint chips, tile samples, stone lookups. Verifies the aesthetic specification.
- Mockups — full-scale assemblies of critical details, usually exterior envelope or interior finish features. Tests the specified system in three dimensions before it's built permanently.
- Quality control submittals — welding procedures, concrete mix designs, structural testing plans, commissioning schedules. Documents the quality control approach.
- Closeout submittals — maintenance manuals, as-built documentation, warranty certificates, extra stock delivery. Required at project end, not during construction.
Submittals flow in a defined sequence: the sub or supplier prepares the package, the GC reviews and stamps it, the GC transmits to the architect, the architect (and consultants, if relevant) reviews and stamps, the response flows back through the GC to the sub, and the sub either proceeds with fabrication or addresses any markups and resubmits.
Each step is a workflow checkpoint. The GC's review verifies the submittal is complete and matches the contract requirements before the architect sees it (prevents the architect from rejecting incomplete packages). The architect's review verifies compliance with the design intent. The consultant reviews (mechanical engineer for mechanical submittals, structural engineer for steel, etc.) verify technical details within their discipline.
Contracts specify a review turnaround — typically 10-14 calendar days from the architect's receipt. The clock starts when the architect receives a complete submittal, not when the sub first hands it to the GC. Incomplete submittals get returned without review and don't start the clock.
Slow submittal turnaround is a common source of schedule impact claims. When the architect takes 6 weeks on a 2-week review, the contractor can argue schedule impact for the delta. Contractors routinely track submittal turnaround as a metric precisely because it builds the evidence for future delay or cost claims.
The architect's review returns with one of a few standard dispositions:
Common submittal review dispositions
- Approved / Approved as Submitted — the submittal meets requirements; fabrication and installation may proceed as shown
- Approved as Noted — approved with minor notations; contractor incorporates the notations but doesn't need to resubmit
- Revise and Resubmit / Returned for Revision — significant issues require changes; contractor must revise and resubmit for another review
- Rejected / Not Approved — the submittal doesn't meet the specification; a different product or approach is needed
- Reviewed — limited to informational review; doesn't constitute approval of specific content (used when submittal is outside the specification's review scope)
Approval isn't unconditional. Most submittal stamps include language saying that approval doesn't relieve the contractor of responsibility for errors, deviations from contract documents, or coordination with other trades. The architect's approval verifies design intent is met; the contractor remains responsible for the overall coordination and correctness.
A submittal log is the master tracking document for the project. Every expected submittal is listed with its specification reference, the responsible party, the submission deadline, the date actually submitted, the architect's response date, the disposition, and any resubmit cycles.
The submittal schedule is usually one of the first things the GC develops after contract execution. It's driven by the construction schedule working backward — a product needs to be installed in Month 8, fabrication takes 6 weeks, architect review takes 2 weeks, GC review takes 1 week, so the submittal has to be in the GC's hands in Month 6 at the latest. Multiply this by hundreds of submittals and you get the log.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
A well-maintained submittal log is one of the strongest tools a GC has for schedule management. Items falling behind the log schedule are early warning signs that specific trades will miss their installation windows.
When a contractor wants to propose an alternate product to what the specification calls for, the substitution request is usually handled through the submittal process with specific substitution paperwork. The spec either says "approved equal" products are acceptable (in which case the architect reviews for equivalence), or it names specific products without "or equal" language (in which case substitutions require formal approval).
Substitution requests typically require: the specific substitution proposed, a side-by-side comparison to the specified product, reasons for the substitution (cost, availability, lead time), any cost or schedule impact, and acknowledgment that the substitution doesn't affect adjacent trades. The architect evaluates these factors and approves, conditionally approves, or denies.
Submittal status affects AP in a few ways:
How submittals interact with pay applications and AP
- Stored materials billing — materials may not be billable as stored materials until the product submittal is approved; billing for materials purchased against unapproved submittals is common ground for pay application pushback
- Deposits and advance payments — specifications sometimes allow bonded deposits on long-lead-time items (e.g., elevator equipment), but typically contingent on submittal approval
- Change orders arising from submittals — a submittal review that flags a constructability issue can trigger a change order if the fix costs money
- Credits from substitutions — an approved substitution for a less-costly product creates a credit change order back to the owner
Modern construction management platforms (Procore, PlanGrid, Submittal Exchange, and others) handle the submittal workflow digitally. The sub uploads the package, the GC reviews and annotates, the architect reviews and stamps, all with timestamps and audit trails. This replaces the older paper-based process where submittals got mailed or emailed and version control was a constant risk.
Digital tools make submittal log maintenance near-automatic — the log populates from the actual workflow, showing current status without manual updates. For projects with 500+ submittals, this is the difference between a manageable process and a chaotic one.
A submittal is the mechanism that gets materials and shop-fabricated items approved before they're installed. It protects the owner's specification, lets the architect catch substitutions before they're built, and gives the contractor a paper trail that what they installed was approved. The process runs on discipline — complete packages submitted on schedule, reviewed within contractual turnaround windows, and tracked in a master log that ties back to the construction schedule. When the submittal process runs well, the project runs well; when it breaks down, schedule and quality both suffer.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts