How a Broken Submittal Log Delays Your Schedule
A poorly maintained submittal log doesn't just cause administrative headaches—it cascades into missed long lead items, approval backlogs, and schedule slippage that costs projects weeks and thousands in delay costs.
The Submittal Log as a Schedule Control Document
Most project teams view the submittal log as an administrative chore—a spreadsheet to track what's been submitted and when approvals came back. But the submittal log is actually one of the most critical schedule control documents on a construction project. It's the map of dependencies: which items must be approved before fabrication or installation can begin, which suppliers need lead time, which approvals unlock downstream work.
When the submittal log is broken—disorganized, incomplete, not updated, or poorly communicated—the consequences ripple through the schedule. Long lead items aren't ordered on time. Approvals slip through the cracks. Field crews show up to install something that hasn't been approved yet. Change orders accumulate.
What We're Covering
- How a disorganized submittal log kills schedule
- Long lead item tracking and the approval gate
- Common submittal approval bottlenecks
- The cost of approval delays to the critical path
- Building a submittal process that protects schedule
The Schedule Impact of Missing or Late Submittals
Consider a typical mechanical project. The mechanical contractor's schedule shows that HVAC equipment must be ordered in month 2 to arrive in month 5, allowing time for installation and commissioning before occupancy in month 8. But the shop drawing submittal for the HVAC equipment isn't due until week 6—which is already late. The design team takes 10 days to review. Another 5 days for revisions. By the time approval is issued, 3 weeks have passed, and the equipment supplier's lead time has slipped from 12 weeks to 9 weeks. The equipment now arrives in month 6, compressing the installation window and potentially delaying commissioning.
This scenario plays out on nearly every project because the submittal log doesn't clearly identify which items are critical path and which approval windows are non-negotiable.
Long Lead Item Collapse
Long lead items—custom fabrications, specialized equipment, materials with extended delivery windows—are schedule drivers. They typically require shop drawing approvals before the supplier commits to a fabrication schedule. If the submittal process is slow or unreliable, suppliers don't order materials. When the GC finally presses for the item, the supplier says "We need approval before we can order steel," but the approval hasn't been given yet. The wait cascades, and weeks or months of schedule are lost.
Approval Backlog and Bottlenecks
A disorganized submittal log means the design team doesn't have visibility into what's pending or when it's due. Submittals arrive in a trickle, some with insufficient detail. The architect or engineer responds to whichever submittal is most recent, not in order of schedule criticality. Critical items languish in the queue while less important submittals get reviewed first.
Worse: when the GC doesn't track what's been submitted, submittals get lost—sent to the wrong person, forwarded to the wrong email, or simply forgotten. The design team thinks it's under review. The contractor thinks it's been approved. Three weeks go by before anyone realizes the submittal never made it to the right reviewer.
Field Installation Blocked by Missing Approvals
The framing is done. The mechanical crew is ready to install. But the ductwork submittal hasn't been approved yet. The crew is told to wait. They sit idle for 3 days, then 5 days, then a week. Meanwhile, the general contractor's schedule assumes they'd be installing and moving downstream work along. The crew is reassigned. When the submittal finally gets approved, the mechanical crew has moved to another project. Getting them back delays the whole schedule.
Why Submittal Logs Fail
Most projects start with good intentions. A submittal log is created, distributed, and everyone commits to tracking items. But over time, discipline erodes.
1. No Single Owner or Process
The log is supposed to be maintained by the contractor's project engineer. But sometimes the PE is in the field. Sometimes they're in the office. The log lives in Excel on their desktop and isn't backed up. When the PE changes jobs, the log disappears. There's no clear process: Who submits? Who's the approval authority? What's the review timeline? Who follows up if approval is late?
2. Submittals Aren't Scheduled; They Just Happen
The submittal schedule isn't integrated with the construction schedule. Trades submit when they're ready, not necessarily when it's critical. The submittal process doesn't align with the sequence of work. Long lead items get submitted late because nobody flagged them as critical path in a kickoff meeting.
3. Submissions Are Incomplete
A submittal arrives missing specs, test reports, certifications, or other required documents. The design team rejects it. The contractor resubmits, causing additional delays. Without a clear submittal checklist, incomplete submissions are routine.
4. Review Timelines Aren't Defined
The contract might say "architect shall review and respond to submittals within 10 days," but there's no enforcement. Some submittals get reviewed in 2 days. Others sit for 3 weeks. Without defined review SLAs and escalation triggers, critical items can languish while the design team focuses on less important work.
5. Revisions Aren't Tracked
A submittal comes back marked "Resubmit with revisions." The contractor makes changes and resubmits. But the log doesn't capture this revision cycle. Weeks later, nobody's sure if the final version was ever approved, or if it's still pending revisions.
Building a Submittal Process That Protects Schedule
Step 1: Create a Submittal Schedule at Preconstruction
During the preconstruction meeting, align the submittal schedule with the construction schedule. Identify which items are critical path. Assign due dates to each submittal that provide adequate lead time for review and approval before the item is needed on site. Assign these dates to the general contractor and trades contractually.
A submittal log guide should outline the process and expectations.
Step 2: Define Submission Requirements Upfront
For each submittal category (HVAC shop drawings, paint schedules, door schedules, structural connections), create a checklist of what must be included. Does it need test reports? Certifications? Cost information? Coordinate with the design team to ensure the checklist is realistic and complete. Share it with the contractor and trades so they know what to include before submitting.
Step 3: Assign Clear Ownership and Review SLAs
Designate one person at the contractor to manage the submittal log (typically the project engineer or an administrator). That person is responsible for submitting on time, tracking status, and escalating late approvals. On the design side, assign specific people to review specific categories. Define review timelines: 5 days for simple submittals, 10 days for complex ones. Include escalation: if a submittal isn't approved within the timeline, it goes to a project manager or principal for priority.
Step 4: Use a Centralized, Accessible System
Don't rely on email or shared drives. Use a project management platform or submittal tracking system where all stakeholders can see status in real time. The log should show:
- Item name and description
- Schedule due date and criticality (critical path or not)
- Submission date and responsible party
- Review status (submitted, in review, approved, resubmit, approved)
- Review completion date
- Any notes or issues
Step 5: Monitor and Escalate Regularly
Review the submittal log at every project meeting. Identify items nearing the due date that haven't been submitted. Identify submittals in review that are approaching their SLA deadline. Call them out explicitly: "HVAC shop drawings are due in 3 days; where are we?" Escalate items that miss deadlines to the project manager and architect immediately, not weeks later when the delay is already baked into the schedule.
The Cost of Getting Submittals Right
A well-managed submittal process costs almost nothing in administrative overhead. The real cost of a broken submittal log is in schedule delay, idle crews, and missed lead times. Industry data suggests that a single week of schedule delay on a $10 million project costs $25,000 to $50,000 in labor, equipment, and indirect costs. A submittal process that prevents even one week of delay—which it easily can—pays for itself many times over.
The preconstruction phase is the time to nail down the submittal process. Investing in clear procedures, communication, and governance prevents the chaos that derails schedules later.
Related Resources
Submittal Log Guide
Setting up and maintaining an effective submittal tracking system
Drawing Transmittal Guide
Best practices for document distribution and tracking
Construction Schedule Delays
Understanding root causes of schedule slip
Preconstruction ROI
Value of upfront planning and coordination
How to Reduce RFIs
Minimizing clarification requests through better coordination
Clash Detection
Identifying coordination issues early in preconstruction