Ask any superintendent what actually blows a schedule and you'll rarely hear "we couldn't swing hammers fast enough." You'll hear that the switchgear showed up eleven weeks late, or the storefront glass was approved-as-noted and nobody caught the noted part until the fabricator had already cut it wrong. Submittals are where a job gets quietly murdered weeks before anyone feels the wound. The framing looks fine, the drywall looks fine, and then you hit a wall you can't build past because a piece of paper never got signed.
The frustrating part is that submittal delays are almost always predictable. Unlike weather or a labor no-show, the approval clock is knowable months out. The problem isn't that submittals are unpredictable — it's that most teams treat the submittal log as an office document living in the PM's world and the schedule as a field document living in the super's world, and the two never talk until the gap between them becomes a hole in the ground with nothing in it.
Why submittals break schedules and not the other way around
Here's the sequence that hurts, and it's worth internalizing because every long-lead disaster follows it: the sub prepares the submittal, the architect or engineer reviews it, it comes back approved or rejected, the sub releases the material for fabrication, the shop builds it, it ships, and only then does it land on your site ready to install. Installation is the very last link in that chain. By the time a foreman can touch the material, four or five other things had to happen on someone else's clock — mostly the design team's and the fabricator's, neither of whom answer to your daily huddle.
So when you're planning work three or four weeks out, the real question is never "can the crew get to it?" It's "will the material physically be here, approved and correct, on the day I need it?" That's a procurement question that lives entirely upstream of the field. A look-ahead schedule is only honest if every activity on it has a clear path to material — and submittal status is the first place that path can be blocked.
Work the math backward from the need date
The single most useful habit you can build is calculating submittal need dates in reverse. Start with the day the material has to be installed. Then subtract, in order:
- Installation lead: how long before install you need it physically on site, staged and inspected. Usually a few days to a week for anything that needs unloading and staging.
- Shipping: transit time from the shop or supplier. Domestic trucking might be a week; overseas or specialty freight can be a month or more.
- Fabrication: the shop's actual build time after they have an approved release. This is the number people forget to ask about. Structural steel, custom millwork, elevators, and switchgear can run eight to twenty weeks here alone.
- Approval turnaround: the design team's review window. Your spec probably says fourteen calendar days. Plan on it taking longer, because it usually does, and because a rejection resets the clock.
- Sub preparation: the time the trade needs to assemble the submittal in the first place, which nobody ever gives them and everybody complains about.
Add those up and you get the day the submittal must be in the architect's hands to protect the install date. For a lot of long-lead items, when you actually run this math on a job that broke ground last month, that date is already behind you. That's not a scheduling failure — that's the schedule finally telling you the truth. Better to know it in week two than in month five.
The rejection loop is where good schedules go to die
The plan everyone builds in their head assumes a submittal goes out and comes back approved. Reality is that a meaningful share come back revise and resubmit, and each round trip is a full reset of the approval clock plus however long the sub sits on the markups. Two rounds of rejection on a fourteen-day review cycle is a month gone, and it's a month you didn't budget because your baseline assumed a clean first pass.
Two things reduce this. First, get your submittals in early on purpose — not because early is virtuous, but because early builds a buffer that absorbs one rejection without touching your install date. Second, catch the "approved as noted" trap. That stamp is not a green light; it means the reviewer changed something, and if the fab shop runs with the original the material comes back wrong and you're now in a resubmittal you didn't even know you were in. Read the noted part. Make the sub read the noted part. Confirm in writing that the fabrication release reflects the notes.
Long-lead items get their own list, permanently
Every job has a handful of items where the procurement timeline, not the construction sequence, sets the schedule. Switchgear and electrical distribution equipment. Elevators. Custom curtain wall and storefront. Structural steel. Rooftop units and large air handlers. Generators. Anything with a factory queue in front of it.
These do not belong buried in a general submittal log with the paint colors and the door hardware. Pull them onto their own long-lead tracker at buyout and review it every single week, because on most jobs one of these is your true critical path whether the bar chart admits it or not. The test is simple: if this item's approval slips one week, does my finish date slip one week? If yes, it's long-lead, and it gets watched like it can hurt you — because it can.
Make the constraint visible on the wall
This is the coordination gap that software actually closes, and it's why submittal status belongs in the same view as your weekly work plan rather than in a separate spreadsheet nobody opens. When an activity on your three- or four-week look-ahead is waiting on a submittal, that activity should be flagged as constrained right where the crews and subs can see it — not planned as if it's ready to go.
The whole point of short-interval and look-ahead scheduling is to only commit to work that's genuinely ready — material on hand, prerequisites done, area available, information approved. A submittal that hasn't cleared is an open constraint, full stop, and an activity sitting on an open constraint has no business being promised in this week's plan. Tools like LookAheadWall earn their place here by letting you tie an activity to its constraints and see, at a glance, which of next week's planned work is actually clear and which is riding on an approval that hasn't landed. That's the difference between a plan and a wish.
Practically, that means your weekly planning huddle should include a pass through pending submittals against the upcoming activities. Walk the next three weeks of the look-ahead and for each meaningful activity ask: is the submittal approved, is the material released, is it on site? If any answer is no, the activity is constrained, and either you resolve the constraint this week or you don't plan the work. That five-minute discipline catches the problem while there's still runway to fix it.
Samples, mock-ups, and shop drawings each carry their own trap
Not every submittal is a spec sheet you can email. Physical samples have to be produced, shipped, and physically reviewed — you can't email a masonry sample or a terrazzo panel, and the review can't happen until it's in the room. Mock-ups are worse: a mock-up is a small construction project with its own sequence and its own approval, and if the design team requires an approved exterior mock-up before you close the building envelope, that mock-up is on your critical path and needs to be on the schedule as real work with real duration, not an afterthought.
Shop drawings are their own animal because they're where coordination lives or dies. Ductwork, plumbing, structural steel connections, precast — the shop drawing is where the trade commits to exactly what they'll build, and it's the last cheap place to catch a clash before it becomes a field conflict that costs ten times as much to fix. Give shop drawings the review attention they deserve and coordinate them against each other, not just against the spec. The ceiling that "worked" on every individual shop drawing but can't fit ducts, sprinkler, lights, and structure in the same plenum is a submittal-coordination failure, not a field failure.
Track review times and hold people to them
Log how long each reviewer actually takes. Not to be petty — to plan honestly and to have a record. If your spec says fourteen days and the architect is averaging twenty-five, that's not a complaint, it's a planning input, and your future need-date math has to use the real number, not the contract number. It's also leverage: a documented pattern of slow reviews is a defensible basis for a time-impact analysis when a delay claim comes around, and it's a lot easier to have that conversation with data than with grievance.
The habits that actually hold
Strip away the software talk and submittal discipline comes down to a few things a superintendent can run on any job:
- Buyout with need dates, not just line items. Every submittal on the log should carry the date it must be approved by, worked backward from install.
- A living long-lead list reviewed weekly, separate from the general log, treated as critical path until proven otherwise.
- Submittal status inside the look-ahead, so constrained activities are visibly flagged and never planned as ready.
- Early submission on purpose to bank a buffer against the rejection loop.
- Read the notes on "approved as noted" before anything gets released to fabrication.
- Real review-time data, used to plan and, if it comes to it, to defend your schedule.
None of this is glamorous, and none of it happens during the exciting part of the job. It happens in the quiet weeks right after buyout, when the site is still mostly dirt and the temptation is to worry about things you can see. But the material that shows up on time and correct in month six was won or lost by the submittal you did or didn't chase in week three. Get that chain visible, tie it to the schedule your crews actually work from, and you stop finding walls you can't build past — because you saw them coming while there was still time to move.