The submittal log is a timestamped record of the submittal workflow that can become central evidence when a delay claim lands on your desk. Every construction project generates one.
If you've ever had to explain a schedule slip or defend a delay position, you know the submittal log is the record that either protects you or exposes you. I have seen teams treat it as a routine tracking artifact and spend months regretting it.
Per AIA A201–2017, the contractor cannot build without approved submittals (§3.12.7), cannot claim schedule relief without a documented submittal schedule (§3.10.2), and is not relieved of compliance responsibility regardless of architect approval (§3.12.8).
That is three contractual provisions tracked through one record. When the log falls behind, each of those provisions becomes harder to enforce or defend.
What a Submittal Log Tracks
In practice, a submittal log, called a submittal register in federal and institutional practice, is the master tracking record for every required submittal on a project. It serves as a permanent record of the chronology of the submittal workflow: receipt, consultant referral, action taken, and date returned.
The contractor builds it from the project specification book at project initiation, with each submittal tied to a CSI MasterFormat section (Section 01 33 00 governs submittal procedures; Section 01 32 19 governs the submittal schedule).
The standard field structure includes:
submittal number (spec section + sequential decimal, e.g., 061000.01)
specification section and title
description
submittal type (shop drawing, product data, sample, test report)
responsible subcontractor
manufacturer
dates submitted to GC and archite
date returned
status code (Approved, Approved as Noted, Revise and Resubmit, Rejected)
reviewer/consultant referral
revision tracking
Federal projects per UFGS 01 33 00 add CPM activity numbers linking each submittal to a specific schedule activity, a federal requirement that many teams also use for coordination. On mechanical and HVAC-heavy projects, submittals in CSI Divisions 23 and 25 often must document compliance with ASHRAE 62.1 for ventilation and IAQ, and ASHRAE 90.1 for mechanical equipment and systems, adding another layer of documentation the log may need to track through review.
Who Depends on the Submittal Log and Why
Six parties depend on this record at the same time.
The subcontractor prepares and originates. The GC reviews, stamps, and transmits to the architect. The architect reviews for general conformance with design intent, but not dimensional accuracy, and not means and methods.
Specialty consultants (structural, MEP, civil) provide discipline-specific reviews routed by the architect. The construction manager coordinates shop drawings among trades before design professional submittal, per CMAA competencies. The owner monitors workflow health and enforces schedule compliance.
Each handoff event carries its own date field. Miss one and the record is incomplete.
Where Manual Submittal Tracking Breaks and What It Costs
I see the same pattern on almost every job. The submittal log works fine when the list is small. It starts to strain when the volume gets large.
Here is where it breaks:
Version control fractures across inboxes. A design reviewer works from an attachment forwarded two weeks ago. The contractor uploaded a revised file last Tuesday. Field crews reference a printout from the original submission. PlanGrid and FMI research state that a large share of construction professionals' time is spent on non-productive activities, including looking for project information and dealing with mistakes and rework. The same research found that rework causes are often tied to poor project data and miscommunication.
Review deadlines expire without anyone noticing. Contractual review periods are obligations, not suggestions. When the architect misses a review window and the affected work sits on the critical path, the contractor may have grounds for a delay claim. CMAA guidance is clear about how an electronic document management system should track all submittals and alert staff when a submittal has not been responded to in a timely manner. A static spreadsheet sorted by spec section typically does not provide that kind of automated alert unless supplemented by workflow tooling. Switchgear lead times can run long, and a late review on a long-lead item can be difficult to recover without acceleration costs.
Resubmittal cycles compound invisibly. Each rejection adds a full review cycle. On high-volume projects, concurrent rejection cycles across multiple trades, none visible in aggregate on a static spreadsheet, create compounding schedule impact that may only surface when someone manually reconciles the log against the CPM.
The log becomes a weapon in claims. CMAA documented a wastewater treatment facility where the contractor filed a delay claim based on approximately 4,000 RFIs. Forensic analysis revealed nearly 500 were actually submittals or shop drawings required by contract. When submittals are not maintained in a dedicated log with their own timestamps and status history, they become easier to recharacterize. A GC who cannot produce a clean, timestamped submittal log has a weaker defense.
Schedule slippage is common on large projects. The submittal log does not cause all of that slippage. But when the log is stale, teams may not see the delay forming until it is already on the critical path.
Deloitte's outlook points in the same direction as Datagrid's solutions, saying that digital workflows integrating project data "enable more accurate project planning, minimize rework, and accelerate schedules."
What Changes When AI Agents Manage the Log
This is where the operating model shifts.
Instead of a project engineer spending days building a submittal log from a large spec book, then manually updating it every time a project file moves between parties, the log can stay current through the systems where project data already lives.
Human effort shifts toward reviewing exceptions, making judgment calls on flagged items, and focusing on coordination work that still requires experience.
How it works
Cross-check submittals against specs: AI agents compare submitted materials against specification requirements and flag compliance gaps before packages enter review
Search across project records: AI agents analyze specs, drawings, RFIs, and submittals to answer questions from connected project data without manual reconciliation
Sync project files across systems: Datagrid's integration layer connects platforms to reduce manual data entry and version drift across the stack
Compare submittals against drawings: AI agents detect coordination conflicts and version mismatches between submittals and current drawing sets
What Practitioners Are Seeing
Jacob Freitas, Project Executive at Level 10, describes the throughput shift in concrete terms:
"Up to 8 submittals in 1 hour. This would have taken a team of 4 people at least 8 hours if not more."
Moez Jaffer, CIO at Grunley Construction, confirms the deployment pattern: "We like that Datagrid is a true agentic AI platform and very customizable. We have it in two projects with Deep Search, Submittal and Scheduling. We plan to continue expanding it to more projects."
Both describe the same operating shift. Project teams focused on exceptions and coordination decisions while AI agents execute the comparison and tracking work between those decisions.
Keep Your Submittal Log Current
If your submittal log lives in a spreadsheet, your review deadlines live in someone's memory, and your audit trail lives in email threads, you already know what breaks next.
