A submittal log is the master tracking record listing every submittal required on a project, its current status, and key dates when it was submitted, when it’s due for review, when a response was returned, and whether that response was approval, conditional approval, or rejection requiring resubmission.
A complete submittal log is built early, during preconstruction, by working through the full specification book and identifying every section that requires a submittal. On a project of any real size, this can easily run to several hundred individual line items across every trade and division. Building the log thoroughly up front, rather than adding items reactively when trades happen to remember they need to submit something, prevents late-discovered submittal requirements from becoming last-minute schedule surprises.
Status tracking on an active log needs regular updates to remain useful, since a log with outdated status information gives a false sense of where procurement actually stands. An item logged as submitted three weeks ago with no review response yet should be visibly flagged as overdue against the contractual review window, not sitting quietly in the same status as an item submitted yesterday that hasn’t had time to be reviewed.
The submittal log connects directly to procurement tracking and, by extension, to overall schedule risk; an item stuck in review longer than expected effectively extends that item’s total lead time from the schedule’s perspective, which is exactly why a log showing only submission dates without active status monitoring misses the piece of information that actually matters most for catching a developing delay early.
An improvement to a typical submittal log: a column including the number of resubmission cycles for each item instead of just the current status. The third resubmission of an item would be significantly more concerning for the project schedule than the first approval case, even though both would have the same approved status. Therefore, the item’s history should not disappear after it clears the review process and should be retained.
To facilitate subsequent compliance validation, every entry in the submittal log should be cross-referenced to the specification section, not just a generic trade or item description. A reviewer of the submittal log would not have to examine each entry to determine which specification section applies and could expedite the process by going directly to the applicable requirement. This small upfront investment in log structure pays for itself many times over across the life of an active project.
