I've watched project engineers file a transmittal cover sheet and assume the submittal was logged. I've seen subcontractors email shop drawings with a PDF transmittal attached, fabricate materials while waiting for a response that was never triggered, and then lose leverage on a delay claim because the review clock was never clearly established in the project record.
The distinction between a transmittal and a submittal is one of the most consequential lines in construction document control, and one of the most consistently blurred.
This article will breakdown what each document actually is under contract, where teams conflate them, what that confusion costs, and how AI agents are beginning to shift the workflow around both.
Who Touches These Documents
Every submittal and transmittal flows through a specific chain of responsibility. Confusing which document does what creates real contractual exposure.
How Submittals Differ from Transmittals
A submittal is the substance. A201 definition defines it to include shop drawings, product data, and samples submitted by the contractor to the architect "regarding some portion of the Work." Under the A201 workflow, the architect reviews the submittal before the affected scope proceeds. A201 review rule is explicit, stating that no portion of the Work requiring submittal review may proceed until the architect has approved it. That's a contractual stop-work condition for the affected scope.
A transmittal is the wrapper. The "Transmittal Letter" creates a written record of the exchange of project information and acts as a checklist reminding the sender to identify what is being sent, how it is being sent, and why it is being sent. Any party generates it (e.g., contractor, architect, owner, or subcontractor) at any project phase.
When Transmittals Carry Contractual Weight
Transmittals can function as more than administrative cover sheets. EJCDC guidance notes, in discussion of EJCDC C-700–2018 ¶7.16.A.3, that the contractor's notice of proposed deviations from Contract Documents be set forth in a written communication separate from the submittal. The transmittal letter is often that vehicle, which means it can carry a specific contractual communication alongside its routing function.
MasterFormat divisions govern submittals under Division 01 33 00 and Division 01 32 19. Transmittals have no dedicated MasterFormat section. They're generated on demand at every handoff in the chain, from sub to GC with an attached transmittal to GC to architect with a new transmittal when forwarding. Any project party may originate a transmittal.
ASHRAE's commissioning guidelines add another layer for mechanical scope. They require approved submittals as a component of the permanent Systems Manual. For projects using transmittals to document distribution and approval routing, that record documents the chain of custody around those approved submittals.
Transmittal vs. Submittal at a Glance
Attribute | Submittal | Transmittal |
What it is | Technical content requiring formal review | Cover letter documenting the act of sending |
AIA governing document | A201 sections | G810–2001 , "Transmittal Letter" |
CSI MasterFormat section | Division 01 33 00 | None (administrative wrapper) |
Who originates | Contractor (or sub/supplier routed through GC) | Any project party |
Required response | Yes, architect reviews and returns the submittal through the project's review workflow | No |
Deviation notice role | Deviations must be flagged in the submittal itself and in the transmittal letter | Transmittal letter is commonly used as the separate written deviation notice |
Scheduling requirement | Yes, per A201 schedule rule | None (generated on demand) |
Is it a Contract Document? | No, per A201 §3.12.4 | No (administrative record) |
Typical content | Shop drawings, product data, samples, test reports, warranties, O&M manuals | Project name, date, sender/recipient, enclosed items, transmission method, action requested |
Project phase | Primarily construction administration | All phases (e.g., design, bidding, construction) |
Liability bearing | Architect review does not relieve contractor responsibility | No direct bearing on work quality liability |
Where Teams Conflate the Two and What It Actually Costs
The most damaging confusion I see is operational, not definitional. Project teams generally know what a submittal is, but they treat the transmittal as a substitute for a formal submittal log entry.
The approval clock may never start clearly. A sub sends shop drawings to the GC with a transmittal cover sheet via email. The GC's project engineer files the transmittal but never enters the item into the submittal log or initiates the formal review workflow. The architect never receives a formal submittal package. CMAA guidance states that if a contract stipulates a 30-day review period and the owner takes 38 days, the contractor may be entitled to a time extension for the 8-day overage. Without a formally logged submittal record, establishing review-period entitlement and supporting a delay claim becomes much harder.
Real money, real cases. ENR on Judlau reported that subcontractor allegations on the Second Avenue Subway project included failure to coordinate work and shop drawings, and that Judlau later tied $60M in adverse verdicts across related claims to alleged malpractice by its counsel. ENR on Woodbury reported that an "insufficient review process" on completed work, including documented deficiencies at 38 damper locations and 313 ductwork locations, drove a $5.7M lawsuit and a 17-month schedule overrun on a $70M project.
The audit trail dissolves. PlanGrid and FMI found that construction employees spend up to 35% of their working time, roughly 14 hours per week, on non-productive activities including searching for project data and handling rework. When submittals live in email threads rather than logged systems, the chain of custody disappears. In practitioner claims analysis, three recurring data points from the submittal log are the submission date, contractual review period, and actual response date. Without a complete, timestamped log, that analysis becomes difficult to perform.
The gap between a transmittal filed and a submittal logged can become one place where that profit erosion begins.
Datagrid's Summary Spec Submittal Agent compares submittals against the applicable specification sections and flags missing or non-compliant components before they turn into a resubmission cycle or field rework.
AGC outlook found that 52% of contractors with annual volume over $500M are increasing investment in document management software, the highest-ranked technology investment category in that segment. The investment signal matches the operational urgency.
What Changes When AI Agents Own the Document Workflow
A useful way to frame the shift isn't just faster software. It's a change in who initiates the workflow step.
Traditional project management platforms require a human to log every submittal, route every transmittal, and chase every disposition. Agentic AI initiates actions based on project state.
Datagrid's AI agents work across connected project files and systems to execute multi-step workflows rather than simply answer questions.
The Summary Spec Submittal Agent reviews submittals against applicable specification sections and generates a compliance summary and checklist showing what's required versus what's actually in the package. The Deep Dive Spec Submittal Agent evaluates those same sections against submitted product data and shop information, surfacing compliance gaps, scope misalignment, and required corrective actions before they become a review-cycle dispute.
For operations leaders standardizing workflows across multiple project teams, this is the difference between writing procedures people sometimes follow and encoding standards agents enforce consistently.
What These AI Agents Automate
Datagrid's submittal-focused AI agents take over the repetitive cross-checking and assembly work that slows down review cycles:
Spec compliance checks: Flagging gaps and non-compliant components before the package reaches the architect.
Structured review summaries: Generating checklists so reviewers focus on technical judgment, not manual assembly.
Scope alignment verification: Surfacing scope gaps earlier in the review process.
What Practitioners Are Seeing
"With Datagrid we are able to review 8 submittals in 1 hour. This would have taken a team of 4 people at least 8 hours if not more." — Jacob Freitas, Project Executive at Level 10
Speed alone isn't the point. That kind of shift reflects a structural change in how a project team allocates reviewers' time, moving them from assembly and cross-checking to exception handling and technical judgment.
Standardize the Workflow Before You Automate It
If your teams are still assembling submittal packages manually and tracking dispositions through email threads, the gap between your documented procedures and your actual execution is where risk accumulates.
Datagrid's AI agents close that gap. Agents can be used to automate package assembly from cover page to final PDF. The Summary Spec Submittal Agent generates a compliance summary and checklist that makes missing components visible earlier and gives PMs and PEs a cleaner technical review starting point. With 100+ connectors to platforms like Procore and Autodesk ACC, these workflows stay synchronized across your existing project systems.
Request a demo or see the full agent library for RFI validation, document comparison, and deep search across connected project files.
