A GC does not feel the quality of a submittal register at kickoff. The hit comes later when a product is installed before approval, a certificate is missing at closeout, or a substitution has no review trail. The register is where those risks should be caught before the first submittal is sent.
CMAA guidance describes a submittal register as tracking what needs to be submitted, by whom, when it must be submitted and approved, and the current status. It may also identify where the requirement is derived. At project setup, it is the master list of required submittals, built from the spec book before the first submittal is ever sent.
Build a comprehensive submittal register, and your team can track shop drawings, product data sheets, samples, and certificates from day one. Miss sections during the spec walk, and those gaps surface mid-project as installed work that was never approved.
When the Register Gets Built and Who Owns It
The submittal register is built at project setup, immediately after contract award and before construction activities begin. As the project schedule develops and procurement planning starts, the project manager, project engineer, or document control lead compiles required submittals from the specifications.
The best practice is to input these items at project kickoff. Don't wait until subs start asking what they need to provide.
Who Owns the Register
On most projects, the general contractor (GC) owns this. The GC builds the register from the project specifications, updates it as the job runs, and coordinates with subcontractors and the design team to keep submittals aligned with the schedule.
Trade partners and suppliers feed the content. Manufacturers provide cut sheets and material data, subs prepare the shop drawings, and the GC assembles and tracks the whole thing.
The Contractual Stakes
On projects using AIA A201 or similar general conditions, the contract language puts most of the submittal risk on the GC. AIA A201-2017 Article 3.12 treats shop drawings, product data, and samples as outside the Contract Documents, framing them as the contractor's demonstration of how it intends to conform to the design concept.
Section 3.12.10 narrows the architect's review to that design concept and explicitly excludes accuracy, quantities, and installation methods. And §3.12.8 is the line every operations leader should know: architect approval does not relieve the contractor of responsibility for errors or omissions in submittals.
Taken together, these provisions make the register the GC's primary defense against risk the contract has already assigned to them. Without a complete submittal register, the project starts blind. Requirements that never make it onto the list cannot be tracked centrally, and untracked requirements tend to resurface mid-project as hidden substitutions or unapproved products discovered after installation.
Completeness at the register stage is what keeps those surprises from becoming the GC's problem later.
Submittal Register vs. Submittal Log
The register is the master requirements list; the log tracks each item's status through the review cycle. Keeping those functions separate prevents gaps.
The submittal register enumerates every required submittal pulled from the specs:
what needs to be submitted and by whom
when it must be submitted and approved
current status
where the requirement is derived
It is the baseline, generated before any workflow begins.
The submittal log is the live execution record. It tracks each item through its review cycle (open, under review, approved, revise and resubmit, rejected).
Where the register answers "what does this project require," at the start, the log answers "where does each item stand right now" during project execution.
Attribute | Submittal Register | Submittal Log |
Purpose | Enumerate all required submittals from specs | Track status of each submittal through review cycle |
Created when | Project setup / preconstruction | As submittals are initiated and submitted |
Driven by | Spec book / CSI MasterFormat | Workflow and schedule |
Updates | Added to as omissions surface; rarely deleted | Updated continuously as submittals move through approval |
Once a register item becomes an active submittal, the work shifts from requirement tracking to package assembly. Datagrid's Submittal-Builder Agent assembles formal submittal packages for owner or design team review, including the cover page and required supporting project files.
How to Build a Submittal Register from the Spec Book
Build the register by walking the spec book division by division and capturing every section that requires a submittal. Each line item becomes something your team must track from creation to approval.
Start with Division 01
Division 01 governs the entire submittal workflow. In the 2018 MasterFormat reference, Section 01 33 00 – Submittal Procedures holds the administrative and procedural requirements for processing submittals during construction. Section 01 33 00 contains the submittal schedule and defines the project's overarching format, copy counts, and review timelines. Within 01 33 00 you'll find sections like 01 33 13 Certificates, 01 33 23 Shop Drawings, Product Data, and Samples, and 01 33 26 Source Quality Control Reporting.
Walk Every Technical Division
After Division 01, work through each technical division in CSI MasterFormat. Every spec section with submittal requirements becomes a line item. The submittal article in Part 1 (General) of each section defines what documentation must be submitted, when it's due, and in what format. Division 03 maps to your concrete sub, Division 05 to your steel fabricator, Division 26 to your electrical contractor. For deeper navigation of how the divisions are organized, see Datagrid's CSI divisions guide.
For each section, capture the required submittal type.
Assign Responsible Parties and Dates
Every line needs an owner and a date. Each register entry should capture the specification section number and title, the submittal category, the responsible party, and the scheduled submission date.
When setting dates, account for review, ordering, manufacturing, fabrication, delivery, and resubmittal time, and coordinate the register against the schedule of values and the construction schedule. Federal practice under UFGS 01 33 00 guidance requires the register submitted within 30 calendar days after Notice to Proceed, then updated monthly.
Where Manual Register Building Fails and What It Costs
Manual register building fails in predictable ways, and every gap becomes a downstream liability the GC carries.
The Common Omissions
Sections get skimmed. During a manual spec walk under deadline pressure, requirements can be rushed or missed. The same UFGS guidance tells teams to verify that all submittals are listed and add missing ones because the list may not be all inclusive.
When required items are not listed centrally, they are harder to track against the schedule. The same risk applies to any requirement outside an obvious Submittals heading. Requirements that are not captured are not managed.
What the Gaps Cost
The downstream cost shows up as rework and delay, with exposure staying on the GC. A missed register item can become installed work with no approval behind it, and where AIA A201 applies, the GC retains responsibility for errors or omissions in submittals despite architect approval.
How AI Agents Change Register Building
The operating model shifts when AI agents produce a register draft from the spec book instead of an engineer reading it line by line. The shift matters most where manual walks fail. AI agents process the full spec book, including the sections that often get skipped under deadline pressure, and they flag candidate submittal requirements in less obvious locations. The register becomes a more complete extraction rather than a best-effort transcription.
Instead of building from a blank spreadsheet, the project engineer reviews and adjusts a draft already designed to capture requirements across the spec book. That same register then improves the downstream package workflow. For product-heavy sections, once a requirement is ready to submit, the Submittal-Builder Agent bundles the required files into one ordered PDF so the reviewer is not chasing loose attachments.
How the Workflow Runs
An agentic register workflow turns the spec book into a review-ready draft in a few broad steps:
Read the project files, including the full spec book and any addenda that supersede original sections.
Extract and classify submittal requirements by type, mapped to the correct CSI division and spec section.
Generate a structured draft with spec citations, organized by division and flagged where requirements sit in less obvious locations.
People still review and own the result. AI agents do the reading and the assembly, and the project team decides which items stay, which get added, and how each one maps to the schedule. Once items move out of the register and into submission, the Submittal-Builder Agent carries the package-building workflow forward, producing complete, properly formatted submittal packages from cover page to final PDF.
How Operations Leaders Should Use the Draft
Project teams should use agent-generated register output as a reviewed first draft that still requires team approval. AI agents process the page volume; the team owns which items stay or get added and how each item maps to the schedule.
Up to 98% faster spec reviews — Victaulic, after deploying Datagrid's AI agents.
The same discipline matters when the register turns into a package queue. The Submittal-Builder Agent executes the separate package-assembly step by keeping package components in a consistent order, guiding cover page and attachment assembly, and producing a structured submittal PDF for review.
Build a Complete Register from Day One
A submittal register is only as good as its completeness. Manual spec walks leave gaps, and a single missed line item can compound through the schedule and land on the GC's books.
AI agents close that gap by parsing the spec book and producing a review-ready draft section by section, so the project engineer starts from a complete extraction instead of a blank spreadsheet. Once those line items become formal submissions, Datagrid's Submittal-Builder Agent picks up the next workflow, assembling the cover page, supporting files, and final PDF in a guided handoff. Register generation and package assembly stay distinct workflows, but the connection between them is where consistency is won or lost.
Explore the Submittal-Builder Agent to see how a cleaner register handoff feeds a more consistent package-assembly workflow.
