A submittal log is the document that tracks every submittal on a construction project — from the moment it is identified to the moment it receives final approval. It records who submitted it, when it was sent, when it was returned, what action was taken, and whether a resubmission is required.
Without a maintained submittal log, teams lose visibility into where approvals stand. Reviews get delayed. Materials get ordered before drawings are approved. Projects hit compliance issues during closeout because no one can confirm what was formally reviewed and by whom.
This guide explains what a construction submittal log includes, who maintains it, what fields matter, and how to keep it from falling behind as the project scales.
What Is a Submittal Log in Construction?
A submittal log is a centralized tracking record for all submittals required on a project. It documents the status of every shop drawing, product data sheet, sample, cut sheet, or warranty document that must be reviewed and approved before work can proceed or materials can be installed.
The log is typically maintained by the project engineer, project coordinator, or document control administrator. On larger projects, it may be managed jointly by the general contractor’s admin team and the project manager.
Think of it as the master control sheet for the entire submittal process. If the log is accurate and current, the PM and superintendent always know what is approved, what is pending, and what is holding up a trade.
Why the Submittal Log Matters for Construction Projects
The submittal log is not a formality. It is an active project management tool. When it is maintained properly, it protects the schedule, reduces rework, and keeps approvals from stalling.
Here is what a well-maintained log actually does for the team:
- Prevents material procurement before drawings are approved
- Identifies bottlenecks in the architect or engineer review cycle
- Supports RFI coordination by clarifying what has and has not been approved
- Protects the general contractor during owner audits or disputes
- Feeds directly into closeout documentation and O&M submittals
When the log is not maintained, the problems compound. PMs have to chase status by email. Submittals get lost in routing. Trades proceed on unreviewed drawings. At closeout, missing approvals create delays that push final payment.
What Fields a Submittal Log Should Include
Every project has its own requirements, but these are the core fields that belong in any construction submittal log:
| Field | Purpose |
| Submittal Number | Unique identifier tied to the spec section |
| Spec Section / Division | Links the submittal to the relevant specification |
| Description | What is being submitted (e.g., structural steel shop drawings) |
| Submitted By | Subcontractor or supplier responsible for the submittal |
| Date Submitted to GC | When the GC received it from the sub |
| Date Submitted to A/E | When the GC forwarded it to the architect or engineer |
| Required Return Date | Contractual review deadline |
| Actual Return Date | When the A/E returned the reviewed submittal |
| Review Action | Approved / Approved as Noted / Revise and Resubmit / Rejected |
| Revision Number | Tracks how many times a submittal has cycled |
| Notes / Comments | Internal notes on delays, partial approvals, or follow-up |
| Status | Open / Closed / Pending / On Hold |
Some teams also include a column for the required lead time, which helps link the submittal to procurement. If a structural steel fabricator needs six weeks from approval to delivery, that lead time needs to appear somewhere in the log so the schedule team can account for it.
How to Maintain a Submittal Log Throughout the Project
Maintaining the log is not a once-a-week task. It is an ongoing responsibility that needs to happen in real time as submittals move through the review cycle.
Here is how a functional submittal log maintenance process works:
Step 1: Build the log at project kickoff
The log should be created during preconstruction or at the latest during the first week of active submittals. Start by pulling the submittal requirements from the specifications. Each spec section that requires a submittal becomes a row in the log. Assign preliminary submittal numbers at this stage.
Step 2: Log every submittal as it comes in
When a subcontractor submits shop drawings or product data, the log should be updated the same day. Record the submission date, what was received, who submitted it, and the target return date based on the contract review period.
Step 3: Track the A/E review cycle
Once the submittal is forwarded to the architect or engineer, the clock starts on the contractual review period. Log the transmittal date and the required return date. Flag submittals that are approaching or past their review deadline.
Step 4: Record the review action and return date
When the A/E returns a submittal, update the log immediately. Record the return date and the action taken. If the action is Revise and Resubmit, create a new row for the resubmittal and link it to the original.
Step 5: Close out the log at project completion
Before turnover, every line in the log should have a closed status. Open or pending items need to be resolved or documented. The log becomes part of the closeout package the owner receives.
Common Submittal Log Mistakes That Delay Projects
Most submittal log problems are not technical. They are administrative. The log falls behind because no one owns it consistently, or because updates happen in someone’s email instead of the actual log.
These are the most common failures:
- Updating the log only during weekly meetings
Status information becomes stale within days. Trades proceed on assumptions rather than confirmed approvals. - Not logging resubmittals as separate entries
Revision history disappears. It becomes impossible to tell if the current drawing is Rev 0 or Rev 3 without chasing down emails. - Skipping the required return date column
Nobody knows when to follow up. Reviews sit past their contractual deadline without anyone noticing until it affects procurement. - Failing to link submittals to procurement
A fabricator starts production before shop drawings are approved. The GC gets stuck with non-compliant materials. - Letting subs track their own submittals in isolation
The GC loses visibility into what has been submitted and what has not. Subs assume approval when no response has come back.
Best Practices for Submittal Log Management
- Assign clear ownership. One person is responsible for the log. Everyone else contributes to it, but one person audits it.
- Use consistent numbering tied to the spec section. Submittal 03-001 means Division 3, first submittal. This makes cross-referencing faster and reduces confusion.
- Set internal deadlines that are tighter than the contractual deadline. If the contract allows 14 days for review, flag submittals at day 10.
- Send weekly status reports from the log to the project team. A short email summarizing open, pending, and overdue items keeps everyone aligned.
- Keep the log in a shared location. If it lives only on one coordinator’s laptop, it becomes a single point of failure.
- Connect the log to the schedule. Submittals that govern long-lead items should appear in the project schedule with their review deadlines.
- Document every transmittal. Each time a submittal moves from sub to GC or GC to A/E, generate a transmittal and log it. This creates a paper trail that protects all parties.
How Construction Virtual Assistants Can Help Maintain the Submittal Log
Once the submittal workflow is defined, the recurring admin tasks that keep the log current are often the first things that fall through the cracks on busy projects. PMs are pulled into the field. Project engineers are managing RFIs at the same time. Coordinators are handling multiple projects simultaneously.
A submittal construction VA can take ownership of the day-to-day log maintenance tasks so the team stays current without adding headcount.
What a Construction VA handles:
- Logging incoming submittals from subs and suppliers the same day they arrive
- Updating return dates and review actions when the A/E responds
- Flagging submittals that are approaching or past the contractual review deadline
- Creating and tracking resubmittal entries when a Revise and Resubmit action is returned
- Preparing weekly submittal status reports for the PM and superintendent
- Coordinating transmittals to ensure every handoff is documented
- Supporting closeout by verifying that all submittals are closed before turnover
Construction VA works within the systems the project team already uses — whether that is Procore, Autodesk Construction Cloud, Excel, or a shared drive — so there is no workflow disruption. The log stays current, the team stays informed, and nothing falls through the cracks during a busy review cycle.
Frequently Asked Questions
Who is responsible for maintaining the submittal log?
On most projects, the project engineer or project coordinator at the general contractor level maintains the submittal log. On larger projects, a dedicated document control administrator may own it. The key is that responsibility is assigned to one person and reviewed regularly by the PM.
How often should the submittal log be updated?
The log should be updated in real time as submittals move through the process. At minimum, it should be reviewed and updated daily during active submittal periods. A once-a-week update cycle is not sufficient on a fast-moving project.
What is the difference between a submittal log and a submittal register?
The terms are often used interchangeably, but in some organizations, the submittal register is the initial list of required submittals pulled from the specifications, while the submittal log is the active tracking document that records status. Think of the register as the baseline and the log as the live record.
What happens if a submittal is approved but the log is not updated?
The team loses visibility into what has been approved. Trades may hold off on proceeding because no one can confirm the status. At closeout, incomplete records can delay the final payment or create disputes with the owner over what was formally reviewed.
Can virtual assistants manage a submittal log remotely?
Yes. A construction virtual assistant with document control experience can maintain and update the submittal log remotely, prepare transmittals, send follow-up communications, and flag items for the PM — all without being on site. The key is having clear access to the project management platform and a well-defined handoff process.
What software is commonly used to track submittals?
Procore and Autodesk Construction Cloud both have built-in submittal management modules. Many teams also use Excel-based logs, especially on smaller projects. The tool matters less than the process — a well-maintained Excel log beats a poorly maintained Procore setup.
Need Help Keeping Your Submittal Log Current?
A submittal log only protects your project if it is maintained consistently. If your team is stretched across multiple projects, a virtual assistant from Virtual Construction Assistants (VCA) can own the daily log updates, track review cycles, and make sure nothing falls through the cracks.
Contact Virtual Construction Assistants (VCA) to learn how we support construction document control and project coordination for contractors, GCs, and construction management firms.
