Submittal review is the gate between design intent and what actually gets built. A contractor assembles a package, routes it to the design team, waits for a stamp, and either proceeds with procurement or starts the cycle over.
The cycle restarts more often than it should. CMAA's submittal register guidance notes that slow approvals, requests for information, and rejection can lead to project delays. First-pass packages fail for a handful of predictable reasons: required documentation is missing, GC coordination is incomplete, or a substitution gets slipped through the wrong process.
This guide walks that workflow end to end. Who reviews structural versus MEP versus finish submittals, what AIA A201 actually requires on review timing, the rejection causes that send packages back, and how to fix them on resubmittal. I will also cover where agentic AI can standardize package assembly before a package ever reaches an architect's desk.
Where Submittal Review Sits in the Project Lifecycle
Submittal approval controls procurement and the start of fabrication or installation. AIA Contracts' design collaboration guidance places that planning during pre-construction, long before the first package moves. An AIA Community Hub discussion of AIA A201 §3.12.7 confirms the rule, stating that no work requiring a submittal can proceed until the architect approves it.
The AIA A201 contract splits review obligations between the two sides. Under AIA §3.12.5 and AIA §3.12.6, the contractor reviews and approves each submittal and verifies field measurements, materials, and trade coordination. Packages not marked as contractor-reviewed may be returned by the architect without action, and the contractor owns the resulting delay.
The architect's review is narrower. AIA §4.2.7 limits it to conformance with the design concept and information in the Contract Documents. Dimensions, quantities, and installation instructions remain the contractor's responsibility.
How the Submittal Review Workflow Actually Runs
Every submittal moves through three review handoffs before procurement can start. The GC pre-reviews the assembled package against the spec, the design team routes it to the discipline reviewer who owns that system, and that reviewer marks it up, stamps it, and returns it with the action required.
Contractor Assembles and the GC Pre-Reviews
Subcontractors prepare the required submittal types and test reports against the spec requirements. The GC reviews each submission for compliance before forwarding it to the architect. That review verifies field measurements and catalog numbers, and it notes deviations in writing.
The contractor's approval requires independent evaluation before the contractor stamps the submittal. The GC submits with a transmittal form identifying what is being submitted and what action is requested.
The Submittal-Builder Agent applies this assembly step. It assembles complete, properly formatted submittal packages from cover page through final PDF before the GC forwards the package for design-team review.
The Design Team Routes by Discipline
Under a standard prime-consultant arrangement, each submittal goes to the consultant who owns that building system, with the architect responsible for design impact, coordination, and general familiarity with each trade. The architect relies on its engineers for technical expertise and reviews their submittals for design impact and coordination rather than discipline-specific detail.
On projects run by a construction manager (CM), the contractor submits to the CM, who copies the architect and program manager. The architect then forwards to the relevant engineer. Typical discipline routing is contract- and project-dependent, but often looks like this:
Architect: finishes, doors, glazing, roofing, color and finish selections, plus design-level coordination across disciplines
Structural Engineer: structural steel, concrete, connections
MEP Engineers: mechanical, electrical, plumbing equipment
Fire Protection Engineer: fire alarm and sprinkler systems, where assigned for the project
Where submittals affect more than one trade, the CM or GC should forward interrelated packages to the other affected contractors for comment before the discipline reviewer stamps. That side-routing closes the coordination gaps the discipline review alone won't catch.
Reviewer Marks Up, Stamps, and Returns
The reviewer marks the package, affixes the review stamp, and indicates the action taken. The marked submittal then flows back to the contractor for distribution to the responsible subcontractor. Approved submittals should be published and accessible to the entire project team so nobody installs work off a superseded version.
Datagrid's Submittal-Builder Agent also assembles the package before the reviewer ever sees it. It delivers a single, properly structured submittal PDF, reducing the manual PDF editing and stitching that often leaves reviewers navigating a patched-together package.
AIA A201 Review Timelines and What the "14-Day Default" Really Means
The "14-day default" is a myth. AIA A201-2017 does not set a 14-day window for submittal review. It ties review timing to the approved submittal schedule, with action required "with reasonable promptness." The 14-day reference in §3.7.4 covers concealed-condition reporting, not submittal review. When no approved submittal schedule exists, §4.2.7 only requires the architect to act in the time their professional judgment deems adequate. That is not a calendar deadline.
The written submittal schedule is therefore the contractor's primary protective mechanism. A project-specific schedule typically sets a 10-14 business-day window, and per AIA §3.10.2, a contractor who fails to submit one (or to follow it) forfeits any increase in contract sum or time extension based on review duration.
When review runs long, overdue does not mean approved. Under §3.12.7, approval has to come before the work proceeds, so the contractor must treat a late review as a potential delay event rather than a green light. Depending on the contract and facts, the path forward is a §8.3 claim for delay and time extension due to an act or neglect of the architect, with the contractor carrying the burden under Article 15.
Common Review Issues That Trigger Rejection
First-pass rejections trace back to a handful of avoidable failures. Reviewers and GCs must check package contents against construction-document requirements before approval decisions affect procurement, fabrication, or installation.
Incomplete Submittals
Reviewers return incomplete submittals without action. Missing product data sheets, absent spec-section references, omitted photometric data, or a missing or incorrectly completed transmittal form all land here.
Spec Mismatches and Slipped-In Substitutions
A submitted product that does not match the spec section it is filed against gets rejected. So does any substitution slipped in through the submittal channel. For example, reviewers may reject product data when warranty terms do not match the specified warranty period. Submitting a substituted product through shop drawings at the last minute should be treated as nonconforming work. The standard vehicle is CSI Form 13.1A, the Substitution Request After Bidding.
Trade Coordination Conflicts
A submittal that conflicts with another trade's approved work creates coordination failures that surface in the field. Related assembly items should be submitted together. This is why the GC should route interrelated submittals to affected contractors before forwarding. For long-lead items, an approval delay pushes delivery back on top of the full lead time, because orders cannot be placed until approval clears.
How to Fix the Most Common Rejection Reasons on Resubmittal
Fixing a rejected submittal starts with reading every reviewer comment before responding. Partial responses generate another full revision cycle.
Notify the subcontractor the same day, set an internal deadline, and log the action with a linked resubmittal entry (e.g., reuse the original number with a letter suffix for resubmittals).
For spec compliance gaps, show exactly where the item sits in the contract documents. To prevent another mismatch, run a compliance check during package assembly rather than after the stamp comes back. The contractor owns obtaining and correcting dimensions, and any deviation must be flagged explicitly. Under AIA §3.12.9, the contractor must direct specific written attention to revisions other than those the architect requested. Otherwise, the architect's approval will not apply to them.
For substitution justifications, follow Division 01 timing and submit a complete request describing what is being substituted and why it is equal. If the owner accepts a substitution the architect does not consider equal, it often becomes owner-approved nonconforming work and gets listed as an exception in the certificate of substantial completion.
Standardize Submittal Review With Agentic AI
Pre-submission completeness checks are the highest-leverage place to catch a rejection. When that check is manual, consistency depends on whoever happens to be assembling the package that day. A missing item or absent spec reference turns into a return without review, another resubmittal cycle, and lost time before procurement or installation.
Datagrid moves that review step upstream by adding a pre-submission assembly and review layer before the package leaves the GC's desk. The agents pull directly from Procore, Autodesk Construction Cloud, SharePoint, and the other project systems where your specs, drawings, and submittal logs already live, so the same standard runs against every submittal regardless of who builds it. People still make the decisions. The agents handle the assembly and the cross-checks between them.
How Datagrid agents support the submittal review workflow
Datagrid's agents apply your package and review standards before the file reaches the design team:
Package assembly: the Submittal-Builder Agent bundles cover page, product data, shop drawings, and attachments into one consistently structured PDF.
Specification cross-check: Datagrid's Summary Spec Submittal Agent and Deep Dive Spec Submittal Agent compare the assembled package against the spec and flag compliance gaps before the package goes out.
The team reviews every finding against the source project files and decides what proceeds.
Example From the Field
Datagrid's agentic approach to spec and submittal work is already changing review cycles for teams. Victaulic and Datagrid presented a 2025 industry session on agentic AI for built-world workflows. The session positioned agentic AI as a working compliance layer that cross-references product data against requirements so engineers review findings instead of hunting for them.
Victaulic reported dramatically faster spec reviews after deploying Datagrid's agents, with engineers shifting from manual hunting to reviewing flagged findings.
"In specification review, we've had a 70% reduction. And I'd say 90% information accuracy gain."
— Brad Klick, Estimator at Victaulic
Catch Completeness Gaps Before They Reach the Design Team
Your submittal standards already exist. Whether every package meets them before it leaves your office is the open question. See how the Submittal-Builder Agent builds complete, properly formatted submittal packages from cover page to final PDF, so your team spends its time on coordination and engineering rather than chasing resubmittal loops. Turn your documented review standard into a consistent package-building workflow on every project.
