Share
Submittals are one of the most process-heavy parts of any commercial construction project, and they're almost entirely spec-driven. Every shop drawing, product data sheet, and material sample that flows through a project traces back to a requirement in the spec book. Understanding how specs feed into your submittal log is essential for project managers, estimators, and subcontractors who want to avoid the delays and rework that come from a disorganized submittal process.
What Is a Submittal Log?
A submittal log is a tracking document, usually maintained by the general contractor, that records every submittal required on a project, its current status, who is responsible for it, and key dates including submission, review, and return.

Submittals are documents or physical samples that contractors provide to the design team (architect and engineers) for review and approval before work proceeds. Common submittal types include:
- Shop drawings: Fabrication and installation drawings prepared by the contractor or manufacturer showing how a product or system will be built and installed
- Product data: Manufacturer's data sheets, cut sheets, and product manuals demonstrating that a proposed product meets spec requirements
- Samples: Physical material samples submitted for color, texture, or quality approval
- Certificates: Test reports, certifications, or compliance documentation (mill certifications, fire test reports, etc.)
- Operation and maintenance manuals: Required at project closeout, documenting installed systems for the owner
A large commercial project might have 200 to 500+ individual submittals across all trades. Managing that volume without a well-organized log, and without understanding where each requirement came from, leads to missed submittals, delayed approvals, and work that has to stop and wait.
How Spec Sections Drive Submittal Requirements
Every submittal on a project exists because a spec section requires it. The submittal requirements for each scope of work are documented in Part 1 of the relevant spec section, typically under a heading called "Submittals" or "Action Submittals" and "Informational Submittals."
For example, a spec section for a roofing system might require:
- Product data for roofing membrane, insulation, and cover board
- Shop drawings for edge metal details and penetration flashings
- Samples of roofing membrane and flashing material
- Contractor's qualifications as an approved installer
- Manufacturer's warranty documentation at closeout
Each of those items needs to be on the submittal log, assigned to the roofing sub, with a submission date that accounts for the architect's review period and the material lead time.
The problem is that extracting all of these requirements manually, across every spec section on a large project, is a time-consuming process. Someone has to read every Part 1 of every relevant spec section, identify the submittal items, and transfer them into the log. On a project with 80 spec sections, that's a significant administrative task.
Building a Submittal Log from the Spec Book
The most accurate way to build a submittal log is directly from the spec book, not from a generic template, not from a similar past project. Every project has different submittal requirements based on the design team's preferences, the project delivery method, and the specific products specified. The process looks like this:
- Read Division 01: The General Requirements section almost always contains a Submittal Procedures section that defines the overall submittal process: how many copies, electronic vs. paper, review periods, and the required submittal schedule.
- Work through each relevant spec section: For every trade scope on the project, review Part 1 of the spec section and extract all submittal requirements. Note the type of submittal, the responsible party, and any specific timing requirements.
- Build the log: Enter each submittal item with the spec section reference, responsible subcontractor, required submission date (working backward from the needed-on-site date), and current status.
- Update throughout construction: The submittal log is a living document. Items get added, review periods extend, and resubmittals get required. A log that isn't maintained becomes useless quickly.
How AI Spec Extraction Speeds Up Submittal Log Creation
Building a submittal log from scratch is exactly the kind of task that AI spec review tools are built for. Rather than manually reading every Part 1 of every spec section to find the submittal requirements, an estimator or project manager can upload the spec book and have those requirements extracted and organized automatically.
AI-powered extraction can identify submittal types, responsible parties, and spec section references across the entire project, turning a multi-hour administrative task into a starting point that's ready to populate into your project management system. That means less time building the log and more time managing the process.
Further reading: How to Pull Submittal Requirements from a Spec Book Using AI and What Is a Material Standard.
