A submittal is a formal compliance checkpoint used across the built world. It is the mechanism by which a contractor, vendor, or supplier submits documentation to a designated reviewer before related work or procurement can proceed.
The specific form varies by project type, from shop drawings and product data in building construction to vendor data packages in industrial EPC projects, material certifications in infrastructure delivery, and equipment submittals in owner-operated facilities.
The underlying principle is consistent across all of them. Work requiring a submittal may not proceed until that submittal has been reviewed and approved.
If you're responsible for standardizing project execution across multiple teams, you know the submittal is more than paperwork. It's the gate between "we think this is right" and "we're authorized to build." Miss that gate, and you're either building at your own risk or watching your schedule slip while the approval loop restarts.
I've watched teams treat submittals as administrative overhead, something the project engineer handles in the background. I've also watched those same teams spend months in dispute when an unapproved substitution shows up in the field, or when a rejected resubmission pushes procurement past the long-lead window.
Ultimately, the submittal workflow functions as risk management with contractual consequences.
Why Submittals Exist
Every built-world contract specifies which submittals are required and what must be included. Miss a required certification, submit the wrong product data, or route a package before the prime contractor has reviewed it, and the approval clock resets.
The contractual framework that governs this most formally in North American construction comes from the American Institute of Architects (AIA), which defines submittals as shop drawings, product data, samples, and similar items submitted by the contractor to the architect regarding some portion of the work.
Equivalent frameworks apply across other built-world contexts, including FIDIC and NEC contracts in infrastructure, FAR and DFARS requirements in federal procurement, and owner-specific vendor data requirements in industrial EPC and owner-operated facilities.
The purposes below reflect the language of the AIA A201 general conditions, but the underlying logic applies across all of them.
There are six specific purposes why submittals exist:
Design intent verification before fabrication. The contractor's interpretation of contract documents gets confirmed before materials are fabricated or installed. This catches costly errors early, since rework on a typical project can consume a significant share of total contract value.
Mandatory work gate enforcement. AIA's standard general conditions create an enforceable prerequisite, meaning no work may proceed on submittal-required elements until the architect's review is complete. It is a condition precedent to performing affected work.
Contractor compliance without contract modification. Approval of a submittal does not modify the contract. Under AIA's general conditions, submittals are explicitly not Contract Documents. If a contractor installs something different from what the specs require, approval of the submittal does not provide cover unless the deviation was specifically flagged at the time of submission and either the Architect gave written approval as a minor change, or a Change Order or Construction Change Directive was issued.
Scoped liability allocation. The architect's review is limited to "general conformance with design concept." The contractor retains responsibility for dimensions, field conditions, fabrication processes, coordination, and safety. This scope limitation is reflected in the stamp language.
Multi-party coordination. The review workflow coordinates input across the contractor, architect, engineering consultants, owner, and authority having jurisdiction. On a complex project, a single submittal might touch structural, mechanical, and architectural reviewers before it returns.
Permanent owner documentation. Submittals and related record documentation often support owner closeout turnover, facilities management, and future renovation.
For operations leaders across the built world, there's a critical legal point here. If a deviation was included in a submittal but not called out, the submitting party remains fully responsible for the non-conformance even after approval.
The submittal does not transfer risk. It documents intent.
Types of Submittals
Every submittal type carries different review requirements, lead times, and consequences when it arrives late or incomplete.
In building construction, CSI MasterFormat organizes what is required by specification section. Submittal procedures live in Division 01, Section 01 33 00, and each technical section in Divisions 02–49 specifies which submittals apply to that scope.
In industrial EPC, infrastructure, and owner-operated facilities, the same categories appear under different labels, including vendor data submittals, material certification packages, inspection and test plans, and engineering deliverable schedules.
The gatekeeping function is the same across all of them.
Standard specification formats recognize several submittal categories, but two are fundamental across built-world contexts:
Action submittals require a formal architect response before affected work may proceed
Informational submittals are submitted for the record only and do not require formal approval before work proceeds
Submittal Types by SD Code
Within construction specifically, the U.S. federal government's Unified Facilities Guide Specifications provide the most comprehensive publicly available submittal classification, organized by SD code. The types below follow that framework. Teams in industrial, infrastructure, and EPC contexts will recognize equivalent types under different labels.
Shop drawings (SD-02) are project-specific drawings showing how a particular element will be fabricated or installed on this project with these materials (e.g., structural steel connections, curtain wall system details, MEP coordination drawings, above-ceiling layouts). Unlike product data, shop drawings reflect site-specific conditions and trade coordination.
Product data (SD-03) is the manufacturer's pre-published information (e.g., cut sheets, performance charts, catalog pages) with contractor annotations identifying proposed products and applicable options. Common examples include HVAC equipment specs, roofing membrane technical data, luminaire specification sheets, and finish schedules.
Samples (SD-04) are physical examples of materials, equipment, or workmanship that establish quality standards (e.g., carpet tiles, brick veneer, paint chips, hardware finish samples, full-scale exterior wall assembly mockup panels).
Design data and engineering calculations (SD-05) demonstrate that a system meets specified performance criteria (e.g., structural connection calculations, glazing thermal performance, HVAC load calculations, delegated design for specialty systems).
Test reports (SD-06) document testing performed on materials or systems to verify compliance (e.g., concrete compressive strength, curtain wall air/water infiltration, fire resistance testing).
Certificates and certifications (SD-07) certify compliance with specified standards, codes, or regulatory requirements (e.g., UL listing certificates, ICC evaluation reports, ASTM compliance certifications, welder certification records).
Manufacturer's instructions (SD-08) and field reports (SD-09) cover installation procedures and manufacturer representative site verification.
Operation and maintenance data (SD-10) compiles documentation for ongoing operation of installed systems, delivered to the owner at closeout.
Closeout submittals (SD-11) are the complete package at project completion, including as-built drawings, record specifications, O&M manuals, warranties, spare parts, and final lien waivers. Everything the owner needs to operate and maintain the facility.
Sustainability submittals carry an "S" designation in the UFGS framework and verify compliance with green building rating systems (e.g., Environmental Product Declarations, Health Product Declarations, recycled content documentation, VOC compliance certifications).
Preconstruction submittals (SD-01) are the administrative documents required before construction begins, including the construction schedule, the submittal schedule itself, quality control plans, safety plans, and the project directory.
Each type carries different review requirements, lead times, and consequences when it arrives late or incomplete. A material submittal missing a single compliance certification can trigger a rejection-resubmission cycle that delays procurement by weeks.
The Submittal Workflow
The submittal workflow is a multi-stage, multi-party sequence that must complete before fabrication or installation of affected work can begin. At a high level, it moves through six stages:
Specification/contract review to identify every required submittal, its type, format, and deadline
Submittal schedule creation coordinated with the project schedule
Package preparation by subcontractors and suppliers
Prime contractor review and transmittal to the design team
Architect/engineer review resulting in a formal disposition (approved, approved as noted, revise and resubmit, or rejected)
Resubmission cycles where required, followed by procurement and fabrication authorization once approval is confirmed
No work may proceed on submittal-required elements until review is complete. Delays at any stage cascade into project delays. The submittal log that tracks this sequence is both an operational record and, in the event of a dispute, a claims document.
Where the Workflow Breaks Down
On active projects, the workflow breaks in predictable ways. Rejection cycles driven by incomplete packages or misaligned spec references delay procurement on the critical path.
Fragmented tracking across project systems, email, and spreadsheets creates log gaps that become claims exposure. Design deviations that pass through review without being caught translate into field rework.
AI Agents in Submittal Workflows
Most GCs already have Procore, ACC, Aconex, or SharePoint in their project stack. The bottleneck rarely sits in the platform itself but in the coordination layer, where manual cross-referencing, log maintenance, and compliance checks still depend on a project engineer working through every package by hand.
As submittal volumes grow across active projects, that coordination layer is where delays accumulate and review cycles compound.
AI agents execute across that coordination work. The use cases below cover the primary ways agent-executed workflows are changing how project teams handle submittals.
Submittal log automation. Building and maintaining the submittal register is one of the most labor-intensive tasks in construction administration, and one of the most prone to error when managed across disconnected systems.
Construction submittal management. The compliance and tracking layer of submittal management, from extracting spec requirements and cross-checking submissions to surfacing deadline risks, can run as an agent-executed workflow, freeing PMs to focus on exception handling rather than coordination overhead.
Submittal review. Cross-checking every package against applicable spec sections before it reaches the design team is where rejection cycles either start or get caught early.
Material submittal compliance. Material-specific compliance requires comparing submitted product data and cut sheets against the spec's material requirements, substitution criteria, and approval conditions, a check that applies to nearly every submittal type.
Shop drawing review. Shop drawings require comparison against spec requirements to identify deviations, missing required callouts, and material mismatches before packages reach the PE for formal review.
Submittals Are the Compliance Backbone
Across the built world (e.g., engineering, manufacturing, infrastructure), the submittal is the mechanism that converts design intent into verified construction. It exists because the gap between what's specified and what gets built is where projects fail, whether in cost, schedule, or disputes.
For VPs of Operations standardizing project execution across multiple teams, the submittal workflow is where company-wide standards either hold or collapse. For business development leaders pursuing repeat clients, consistent submittal management is what separates firms that deliver clean closeouts from firms that generate claims.
The workflow is longstanding. The tools executing it have evolved. Datagrid's agents are positioned to apply the same compliance checks your best project engineer would look for, across every submittal, on every project, without the same manual bottleneck.
FAQ
Are submittals contract documents? No. Submittals are not Contract Documents. They show how the contractor proposes to comply with the Contract Documents.
Can work begin before a submittal is approved? For work requiring submittal review, no. Approval is a prerequisite before that portion of the work proceeds.
What's the difference between action and informational submittals? Action submittals require a formal response before affected work proceeds. Informational submittals are submitted for the record and generally do not require formal approval before work proceeds.
Why do submittals matter so much on complex projects? Because they function as a compliance gate, coordination tool, and legal record. They catch design deviations before fabrication or installation, and they document what was reviewed, returned, and approved.
What does 'Approved as Noted' mean? It means the submittal can move forward, but the contractor still has to comply with the review comments and corrections noted on the returned package.
How do AI agents change submittal workflows? AI agents analyze specifications, build registers, cross-check submittals against requirements, maintain logs, and route exceptions, reducing manual project-file handling while keeping humans in control of final decisions.
Who is still responsible after a submittal is approved? The contractor. Approval does not shift responsibility for dimensions, field conditions, fabrication, coordination, safety, or unflagged deviations from the contract requirements.
AI Agents for Submittal Management
Datagrid offers specialized AI agents that automate key parts of the submittal workflow, from spec compliance checks to building complete submittal packages.
