The 20-column submittal log commercial GCs use to track shop drawings, product data, samples, and mock-ups from spec section through A/E approval. With live formulas for days-in-review, long-lead flagging, and procurement triggers.
Why this template exists
Every commercial construction project lives or dies by the submittal log. Not because submittals are exotic, they’re the most ordinary document on the job, but because they’re the document the schedule sits on top of. The owner won’t release the GMP until shop drawings on critical equipment are approved. The fabricator won’t cut steel until the connection details are stamped. The MEP rough-in can’t start until the air handler is approved-as-noted and a release-for-fabrication is issued. The submittal log is where every long-lead procurement decision, every A/E review cycle, and every scheduled milestone meets the calendar, and most GCs run it on a tab in someone’s project Excel that nobody else can see.
The pain is the same on every project. A spec section says “submit shop drawings 30 days after Notice to Proceed.” The PM asks the sub for the submittal package, the sub responds two weeks late with an incomplete file, the GC’s project engineer logs it in their personal spreadsheet, the package goes out to the architect, the architect sits on it for 18 days, it comes back “revise & resubmit” with red marks the sub now has to address, and the equipment that was supposed to be released for fabrication on day 60 is now released on day 110. Multiply by 200 line items on a $40M project and you understand why submittal-log mismanagement is the single most common reason commercial-construction schedules slip.
The fix isn’t a tighter spec or a more aggressive submittal schedule. The fix is a working submittal log. A live tracker that captures every package the moment it enters the system, computes days-in-review automatically, flags long-lead items before they hit the critical path, and tells the procurement team when an approved-or-approved-as-noted disposition triggers a release-for-fabrication. SAM.gov-style “submit and wait” is dead in commercial construction. The submittal log is the project-management discipline that replaces it.
This template is that working tracker. The 20 columns capture everything a commercial GC’s project engineer needs to run submittals as a managed system instead of a reactive scramble: the spec section reference (formatted in CSI MasterFormat. 03 30 00, 07 27 26, 23 09 23), the submittal type (shop drawing, product data, sample, mock-up, calculation, certificate), the responsible subcontractor, the dates submitted by the sub, received by the GC, transmitted to the A/E, and returned with disposition, the disposition itself (approved, approved as noted, revise & resubmit, rejected, for record only), the resubmittal counter, the lead-time impact in days, a long-lead flag for items >12 weeks fab, the required-by date pulled from the construction schedule, the procurement-trigger column that tells the buyer “release this for fab,” and the closeout binder reference for the final O&M turnover.
What this log is NOT: it’s not the spec section, and it’s not the contract. The spec dictates what gets submitted; the contract dictates the review-time obligation (typically 14 days for the A/E). The log is the operational layer that sits between the two. The running record of who has what, when it was last touched, what it’s blocking, and what comes next. It’s also not the procurement schedule. The submittal log feeds the procurement schedule via the procurement-trigger column, but the procurement schedule itself is a separate artifact owned by the buyout team.
Use this log on every active commercial project. Open it at Notice to Proceed and don’t close it until the closeout O&M binders are turned over. Update it daily. The moment a submittal comes in, the moment a transmittal goes out, the moment a disposition comes back. The discipline is not weekly. It’s continuous.
Who uses this
- Project engineers at commercial general contractors who own the submittal-log discipline day-to-day
- Project managers running $10M-$100M commercial projects with 100-400 active submittal line items
- Federal GCs and prime contractors managing FAR-driven submittal review cycles on military, GSA, or VA work
- Buyout / procurement teams who use the procurement-trigger column to release long-lead equipment for fabrication
- A/E coordinators and design managers auditing review-cycle turnaround time across portfolio
If you’re tracking submittals on the same project where you’re tracking subcontractor COIs, you’ll want our Subcontractor COI expiration tracker running in parallel. Same operational discipline, different document type.
Every package you transmit to the A/E should also travel with a drawing transmittal form template, so the log tracks the content and the transmittal proves the distribution.
What’s included. 20 columns the project engineer runs
The submittal log captures 20 columns for every submittal package on every project. Opened at NTP, updated continuously through closeout:
- Submittal number with project-level uniqueness. Format:
- - , e.g., 0330-001-0 for the first concrete reinforcement submittal, revision 0. The numbering is project-unique (not industry-unique) and is the primary key the entire log keys off. Every transmittal, RFI, and procurement record references this number. Don’t let two different subs submit under the same number. Assign sequentially as packages enter the system. - CSI MasterFormat spec section reference. The 6-digit CSI MasterFormat number the submittal is responding to, e.g., 03 30 00 for cast-in-place concrete, 07 27 26 for fluid-applied air barriers, 23 09 23 for instrumentation and control devices. This column ties the submittal back to the spec book and the design intent. Multi-section submittals (e.g., a curtain-wall package covering 08 41 13 storefront and 08 44 13 glazed aluminum curtain walls) should reference the primary section with the secondary in the description.
- Submittal description. A one-line plain-English description of what the package contains, “Rebar shop drawings, slab on grade and foundation walls,” “Air-handler product data and submittal sheets, AHU-1 through AHU-4,” “Curtain-wall mock-up, exterior elevations 3/A201 and 4/A201.” Descriptions matter because they’re what the field team scans when they’re trying to find a submittal three months after it was approved.
- Submittal type classification. One of: shop drawing, product data, sample, mock-up, calculation, certificate, schedule, manufacturer’s instructions, qualification statement, color selection, or “for record only.” The type drives the review process. Shop drawings get full A/E review, certificates may only need the consulting engineer’s review, color selections route to the interior designer. Misclassifying the type is the most common reason submittals get returned without review.
- Responsible subcontractor or supplier. The trade or sub-tier responsible for producing the package. Not the GC’s project engineer who’s logging it. The actual entity that owes the submittal. Include the company name and the primary point of contact (typically the sub’s project manager or shop-drawing coordinator). For supplier-direct submittals (curtain wall fabricator, elevator manufacturer), capture the supplier directly even if the package is routed through the trade sub.
- Item or equipment number. The schedule mark or tag from the construction documents, e.g., AHU-1, P-2, F1.0 (1-hour fire-rated door type), CL-3 (curtain-wall type 3). For non-equipment submittals (rebar drawings, color selections), this column is optional. For equipment submittals, the schedule mark is critical. It’s how the field installer matches the approved submittal to the physical item.
- Date submitted by sub to GC. The date the sub or supplier delivered the submittal package to the GC’s project engineer. This is the start of the GC’s clock. Capture even when the package is incomplete; an incomplete-date entry plus a follow-up complete-date is more accurate than waiting for completeness to log it. Days late from the contract submittal schedule are calculated against this date.
- Date received complete by GC for transmittal. The date the GC’s project engineer marked the package complete and ready to send to the A/E. The gap between column 7 and column 8 is the GC’s pre-check time. A reasonable target is 1-2 business days. Longer gaps signal either an overloaded project engineer or a sub turning in incomplete packages that require multiple back-and-forth cycles before the package can be transmitted.
- Date transmitted to A/E. The date the GC sent the submittal package to the architect/engineer for review. This is when the A/E’s contractually-obligated review clock starts (typically 14 calendar days, sometimes 10 business days, per the GC’s prime contract with the owner). Capture the transmittal number from the GC’s transmittal log. Every submittal goes out under a transmittal, and the transmittal number is the audit trail.
- Date returned by A/E with disposition. The date the A/E returned the submittal with a stamp/disposition. This closes the A/E’s review cycle. The gap between column 9 and column 10 is “days in review”. The most-watched metric on the entire log. Live formula in the XLSX computes this automatically (=column10 - column9); conditional formatting flags items with >14 days in review.
- A/E stamp / disposition code. The disposition stamp the A/E applied: A for Approved (no exceptions taken), B for Approved as Noted (minor corrections noted, no resubmittal required), C for Revise & Resubmit (corrections required, resubmittal required), D for Rejected (not in compliance, redesign and resubmit), E for For Record Only (no action required by A/E). A and B advance procurement; C and D trigger the resubmittal counter and reset the clock.
- Resubmittal number. Starts at 0 for the original submittal; increments by 1 for every resubmittal triggered by a C or D disposition. Resubmittal-number 2+ on a critical-path item is a yellow flag. The package is bouncing between the sub and the A/E and is at risk of running out of float. Resubmittal 3+ is a red flag and should trigger a sub-A/E coordination meeting before another cycle is wasted.
- Date resubmitted (per resubmittal cycle). For resubmittal cycles, the date the corrected package was re-submitted by the sub and re-transmitted to the A/E. The full resubmittal cycle restarts columns 7-11 for the new submittal number with the incremented revision suffix (e.g., 0330-001-1). The original submittal row stays as historical record; the new revision gets its own row.
- Date final approved. The date the submittal received its final A or B disposition. The cycle is closed and procurement can proceed. For approved-as-noted submittals, this is the date the noted exceptions are accepted by the GC and recorded in the closeout binder. For approved-no-exceptions, this is the same as column 10. This date is what the procurement team keys off when deciding to release for fabrication.
- Days in review (live formula). The number of calendar days between transmittal to A/E (column 9) and return from A/E (column 10), or, if still open, the running count from column 9 to today. The XLSX uses =IF(K2=“”,TODAY()-I2,J2-I2) (where I=transmittal date, J=returned date, K=disposition). Conditional formatting: green ≤14, yellow 15-21, red >21. This is the column the project manager scans first in every weekly subcontractor coordination meeting.
- Lead-time impact (days). The estimated procurement and fabrication lead time once the submittal is approved. Typically pulled from the sub’s bid or the supplier’s quote. Long-lead items (>12 weeks fabrication after final approval) get flagged in column 17. The required-by date in column 19 minus today minus this lead-time tells you whether the submittal is on track to land equipment by required-by; the procurement-trigger column 20 is the action the trigger creates.
- Long-lead flag. Boolean (TRUE/FALSE). TRUE for any item with lead-time impact >12 weeks (84 days) from final approval. Long-lead items are the schedule’s leading edge: switchgear (typically 30-50 weeks today), generators (40-60 weeks), structural steel for tall buildings (12-20 weeks), curtain-wall systems (16-30 weeks), large air handlers (14-22 weeks), elevators (24-40 weeks). Long-lead-flagged items get reviewed in every weekly project-controls meeting until released for fabrication.
- Status (current state). One of: Pending sub submission, In GC review, In A/E review, Resubmittal pending, Approved/released for fab, Approved-fab in progress, Delivered/received, Installed/closeout binder filed. The status drives the daily project-engineer triage. What’s pending action from each party, what’s blocking what, and what’s overdue. Conditional formatting in the XLSX colors each status row distinctly.
- Required-by date (from construction schedule). The date the equipment or material is required on site per the construction schedule (Primavera P6, Microsoft Project, ASTA Powerproject, etc.). This is the working backwards date. Final approval must occur required-by minus lead-time-impact, transmittal to A/E must occur required-by minus lead-time minus 14 days review, and submission by sub must occur required-by minus lead-time minus 14 days minus the GC’s pre-check time. The XLSX flags items where the math no longer works.
- Procurement trigger / closeout binder reference. Two-purpose column. During the active phase, this captures the date the procurement team was notified to release the equipment for fabrication (typically same day as final approval for long-lead items, or held for a coordinated buy-package release for non-critical-path items). At project closeout, this column is repurposed to capture the closeout O&M binder section reference where the approved submittal has been filed for owner turnover (e.g., “Section 7. Mechanical: AHU 1-4 approved submittals, pages 47-103”).
How to use the log
Open the log at Notice to Proceed. Pre-populate the spec section column (column 2) by walking through the spec book and creating one row per submittal item the spec requires. For a $40M commercial project this is typically 200-400 line items pre-populated before the first submittal even arrives. Sort by required-by date once you’ve populated lead-time-impact estimates from the bid documents.
Update the log continuously, daily, not weekly. Every submittal that comes in gets a date in column 7 the same day it’s received. Every transmittal out gets a date in column 9 the same day it’s sent. Disposition returns from the A/E get logged the same day they hit the inbox. The discipline is “no submittal action goes unlogged for more than 24 hours.” If you fall behind by a week, the days-in-review formulas lose their meaning and the procurement triggers stop firing on time.
Run the log in two views every Monday morning. View 1: filter for status = “In A/E review” sorted by days-in-review descending. These are the packages running long with the architect. View 2: filter for long-lead-flag = TRUE and status ≠ “Approved/released for fab”. These are the long-lead items still pending and at risk. Bring both filtered views to the weekly subcontractor coordination meeting and to the weekly OAC meeting with the owner and architect.
At project closeout, reformat the procurement-trigger column (column 20) to its second-purpose use as the closeout binder reference. Run a final filter for any rows not in status “Installed/closeout binder filed”. These are the open items blocking O&M turnover.
Stop running the submittal log in someone’s head.
The 20 columns above take a commercial GC project engineer 30-45 minutes a day to maintain across a 200-line-item project, plus 2 hours of weekly cleanup before the OAC meeting. Multiply by 4 active commercial projects per project engineer and the log alone is consuming 15-20 hours a week per PE, and that’s when it’s being run with discipline. When it slips (and on most projects it slips), the cost shows up six weeks later when a long-lead item misses required-by and the schedule slips with it. Contracts Connected’s approval-workflow engine routes every submittal package through the right reviewers automatically, computes days-in-review live, fires procurement triggers the moment a final approval lands, and surfaces long-lead items before they hit the critical path, so your project engineers spend their time coordinating the work, not maintaining the log.
For educational purposes. These templates, checklists, and trackers are operator-built starting points designed to help you move faster on the kind of work that usually drowns construction admins in email chains. They are not legal, insurance, accounting, or tax advice. Each project, jurisdiction, and contract has its own quirks. Review the document, refine the language, and consult your attorney, broker, CPA, or compliance officer before relying on it for a live project decision.
Frequently asked questions about the construction submittal log
What’s the difference between a submittal log and a submittal schedule?
The submittal schedule is the up-front planning artifact, typically required by the spec to be delivered within 30 days of Notice to Proceed, that lists every required submittal with target submission and approval dates working backwards from the construction schedule. The submittal log is the running operational tracker that captures actual dates against those targets. The schedule is the plan; the log is the actual. A well-run project uses the schedule to populate the required-by column of the log on day one, then runs the log against it for the next 18 months.
How long does an A/E typically have to review a submittal?
The standard contractual review window is 14 calendar days from receipt by the architect, though some contracts specify 10 business days, 21 calendar days, or in rare cases 30 calendar days. Federal projects under FAR-driven contracts often specify a different window per the prime contract. Verify against the actual contract terms before populating the days-in-review thresholds in the XLSX. Most commercial GC contracts assess liquidated-damage exposure if the GC fails to meet the submittal schedule but do not flow that exposure through to the A/E, which is why “in A/E review for 30+ days” is a common pain point worth tracking and escalating to the owner.
What does a “C. Revise & Resubmit” disposition mean for the schedule?
A C disposition means the A/E identified one or more issues that require the sub to revise the submittal and resubmit a corrected package. The original submittal’s review cycle ends and the resubmittal counter increments to the next revision. The new revision gets its own row in the log with a new submittal number suffix (e.g., 0330-001-1 for revision 1) and a fresh column-7 entry the day the corrected package comes back from the sub. From a schedule perspective, a C disposition is the worst-case branch. It adds the full sub-correction time plus another 14-day A/E review cycle to the procurement-release date for that item.
What are the long-lead items I should flag automatically?
On commercial construction in 2025-2026, the consistent long-lead items are: electrical switchgear (30-50 weeks lead time, sometimes longer for specialty 480V or 4160V gear), generators (40-60 weeks for diesel; longer for natural gas with current emissions packaging), large rooftop air handlers and chillers (14-22 weeks), elevators (24-40 weeks; longer for hospital-grade or destination-dispatch), curtain-wall systems (16-30 weeks for fabricator-engineered packages), structural steel on tall buildings (12-20 weeks), large transformers (30-60 weeks), and any specialty MEP equipment requiring custom engineering. Anything >12 weeks of lead time should auto-flag the long-lead column so the procurement team is reviewing it weekly.
How does the submittal log connect to the procurement schedule?
The date-final-approved column and the lead-time-impact column are the two inputs the procurement schedule reads from the submittal log. The procurement-trigger column captures the date the procurement team was notified to release the long-lead item for fabrication. Typically same-day as final approval for critical-path items. The procurement schedule lives in a separate artifact (often a Primavera P6 schedule or an Excel buy-package tracker) but its dates feed off the submittal log’s approval dates. Most commercial GCs run the two side-by-side in weekly project-controls meetings and reconcile mismatches before the procurement team commits the buy.
What’s the right cadence for closing the submittal log at project closeout?
Repurpose the procurement-trigger column starting at substantial completion. Walk through every approved submittal and record the closeout O&M binder section it’s been filed under. Run a final filter for status ≠ Installed/closeout binder filed. These are the items blocking O&M turnover. The owner won’t sign off on substantial completion (or in some contracts won’t release final retainage) until the closeout O&M binder is complete, so the submittal log doubles as the closeout-binder tracker for the final 60-90 days of the project.