Submittal log template
A submittal log (or submittal register) is the tracking document that lists every submittal a construction project requires — with its spec section, responsible party, dates, and review status. Below is the column structure every log needs, and how to keep it from becoming the thing that holds up procurement.
The columns every submittal log needs
| Column | What it tracks |
|---|---|
| Submittal # | Unique ID for the item (often spec-section based, e.g. 26 05 19-01). |
| Spec section | The CSI MasterFormat section that requires the submittal. |
| Description | What the item is (e.g. 'wire and cable — product data'). |
| Type | Shop drawing, product data, or sample. |
| Responsible party | Sub or supplier preparing it. |
| Date required | When it must be approved to protect the long-lead item. |
| Date submitted | When the GC forwarded it to the design team. |
| Date returned | When the reviewer sent it back. |
| Review action | Approved, approved as noted, revise & resubmit, or rejected. |
| Status | Current state — open, in review, approved, closed. |
How to build and manage the log
Start the log at the beginning of the project by pulling the required submittals straight from the specifications — every spec section states what must be submitted. List them all, assign each to the sub or supplier responsible, and set a "date required" by working backward from procurement and fabrication lead times. The submittals that gate your longest lead items should be prepared and approved first, not whenever they happen to come in.
From there the log is a living document: update the submitted, returned, and review-action columns as items move through the cycle, and keep the status current so anyone can see what is open, in review, or approved. For the full workflow behind the log, see our complete guide to construction submittals and submittal requirements by spec section.
Frequently asked questions
What is a submittal log?
A submittal log — also called a submittal register — is the tracking document that lists every submittal a project requires, along with its spec section, responsible party, dates, and review status. It is how the team manages the process end to end and makes sure no required submittal is missed or left stalled.
What columns should a submittal log have?
At minimum: submittal number, spec section, description, type (shop drawing / product data / sample), responsible party, date required, date submitted, date returned, review action, and current status. Sequencing the 'date required' column against long-lead procurement is what keeps a late approval from delaying the job.
What is the difference between a submittal log and a submittal register?
They are the same thing — 'log' and 'register' are used interchangeably for the document that tracks all required submittals and their review status across a project.