How $50M GCs Cut Submittal Cycle Time From 3 Weeks to 10 Days
Most $50M GCs treat every rejected submittal as bad luck. It is usually a missing pre-submission check, and it costs 2 to 4 weeks per cycle.
TL;DR. A disciplined submittal cycle lands at 10 to 14 business days once a package reaches the reviewer. Most $50M GCs are living closer to three weeks even when nothing gets formally rejected, because slow internal prep and review eat the days a tight process would save, and a single Revise and Resubmit on top of that adds another 2 to 4 weeks. The fix is not chasing the design team harder. It is a written submittal schedule set during preconstruction, a five-minute completeness check before anything leaves your office, and one tracked log instead of five inboxes. On long-lead equipment, that difference is not cosmetic. It is the gap between hitting a pour date and explaining to the owner why it slipped six weeks.
The design team's own review window typically runs 10 to 14 business days under a standard Division 01 33 00 submittal schedule, once a complete package actually reaches them. Most $50M GCs still land closer to three weeks end to end, not because the architect is slow, but because their own prep and internal review absorb the days a tighter process would have saved. And if that submittal comes back Revise and Resubmit, the clock resets: every resubmittal cycle adds another 2 to 4 weeks on top. On long-lead equipment, that extra month does not just shift your schedule. It stacks on top of an 8 to 16 week lead time you already cannot compress.
Submittals Are Not RFIs, and Treating Them the Same Costs You
Every project manager has said some version of "did the architect get back to us on that submittal RFI yet." There is no such thing, and the confusion is not harmless.
An RFI is a question. Your team does not understand something in the contract documents, a detail is missing, a spec section contradicts the drawings, and you need clarification before you can proceed. We wrote about cutting RFI response time separately, because it is a different workflow with different rules.
A submittal is a proposal. You are telling the design team "here is the specific chiller, the specific rebar shop drawing, the specific paint color" and asking them to confirm it satisfies the spec before you cut a purchase order, send it to fabrication, or let a crew install it. It requires your own review and sign-off before it ever reaches the architect. An RFI does not.
The two get routed interchangeably more often than most GCs would admit, and it is expensive when it happens. A substitution request that goes out as an RFI never gets a formal action stamp, which means there is no documented approval path if the product ends up on site and someone asks who approved it. A submittal that gets treated like a quick question skips the completeness review that catches problems before the design team ever sees them. The Construction Management Association of America has flagged this exact failure mode in its guidance on dispute-free project delivery: standardized forms and explicit review timeframes for RFIs and submittals, kept as separate tracked categories, are what keep both processes from becoming ammunition in a later claim.
The 14-Day Myth
Ask ten project engineers how long the architect has to review a submittal and eight of them will say fourteen days. It is one of the most confidently repeated numbers in the industry, and it is not accurate.
The standard-form agreement most commercial projects run on, AIA A201, does not set a universal review deadline. It calls for review with reasonable promptness, and what that means in practice depends entirely on whatever submittal schedule the two sides actually agreed to before construction started. If nobody wrote one, there is no calendar deadline for the design team to miss, which means there is nothing on paper to point to when a submittal sits for three weeks.
The Construction Management Association of America's guidance on dispute-free delivery says this plainly: when contract documents do not specify a review timeframe, owners and contractors need to negotiate one, typically during partnering sessions, because a vague requirement to "review submittals in a timely manner" is a routine source of delay claims precisely because nobody agrees on what timely means until there is already a dispute.
The fix is not a legal argument. It is a document. The Construction Specifications Institute's format for project manuals puts submittal procedures in its own division for a reason: the submittal schedule is supposed to exist as a standalone, dated, sequenced document created during preconstruction, not reconstructed after the fact from email threads. If your last three projects did not have one, that gap is worth more attention than the architect's desk.
The Two Timelines You're Actually Managing
Here is the reframe that matters more than any single tactic in this post: there are two separate clocks running on every submittal, and only one of them is yours.
The first clock is the design team's review time. You can influence it with a written schedule and consistent escalation, but you do not control it. Architects and engineers are reviewing submittals from multiple projects at once, and a submittal without an enforced deadline competes with everything else on their desk.
The second clock is your own preliminary review, the pass your team does before a package leaves your office. This one you control completely, and it is also where most of the actual time goes and where most rejections originate. Depending on complexity, a GC-side review runs from thirty minutes for a simple hardware submittal to eight or more hours for a dense mechanical or electrical package, and during a heavy submittal period a project engineer commonly spends twenty or more hours a week on this review alone. A submittal that reaches the design team with a compliance gap still in it almost always had that gap visible during your own review. It just was not caught, because the review that catches it was informal, inconsistent, or skipped when the week got busy.
That is the part most operators get backwards. They chase the architect for a faster answer when the higher-leverage fix sits on their own side of the desk. Fix what leaves your office and the design team's clock stops being the bottleneck, because you stop feeding it packages that bounce.
What Three Weeks Actually Costs You
Run the arithmetic on a real long-lead item: a custom air handling unit with a ten to twelve week manufacturing lead time. The package looks complete, every page is there, so it goes out. The design team takes its full 10 to 14 business days and returns it Revise and Resubmit over a coil capacity that did not match the schedule, a mismatch a line-by-line spec check would have caught before it left the office. The resubmittal cycle adds another 2 to 4 weeks, and the purchase order cannot release until approval clears. That delay does not just shift the timeline by 2 to 4 weeks. It sits in front of the entire lead time, because the manufacturer will not start building until the PO lands.
"The chiller submittal came back Revise and Resubmit twice. By the time it cleared, we were the reason the mechanical room slipped six weeks, and the review only took twenty minutes each time. We just did not know it needed us for twenty minutes three weeks earlier."
That pattern is not rare. Engineering News-Record has reported on a joint PlanGrid and FMI Corporation study finding that roughly half of all rework on U.S. jobsites traces back to poor project data and miscommunication, at an estimated cost north of $30 billion a year industry-wide. A missed submittal deadline is a small, specific version of that same failure: information that existed somewhere on the team never reached the one place that would have prevented the delay.
The scale problem is not limited to $50M GCs. A 2026 ENR report on the Los Angeles airport people mover project traced part of an $880 million cost increase back to a contractor consortium that flooded the airport authority with more than 200 RFIs while change orders sat contested. The grand jury's recommendation afterward was almost identical to what a $50M GC needs on a much smaller job: a formal schedule of submissions, agreed in advance, so reviewers are not overwhelmed and nobody can credibly claim the deadline was unclear.
The Three-Part Fix
None of this requires new software or a bigger staff. It requires three specific habits, in order.
Write the submittal schedule during preconstruction, not after the first delay. Every submittal required by the spec gets a required-by date, worked backward from the install or pour date it protects, sequenced so long-lead items move first. This is the document that turns "the architect is slow" into a documented, contractual fact you can act on, and it is the one most $50M GCs skip because nobody owns building it before the schedule pressure starts.
Run a five-point completeness check before anything leaves your office. Contractor review stamp present. Field measurements verified, not assumed. Catalog data cross-checked line by line against the spec section it answers. Deviations flagged in writing, not left for the reviewer to discover. Related trade submittals routed together so a mechanical package does not bounce over a structural conflict nobody on the mechanical side could have seen. This is the highest-leverage five minutes on the submittal, and the step that gets cut first when a project engineer is juggling forty open items.
Keep one submittal log with an aging column, not five inboxes. A submittal sitting in an email thread with no visible deadline is a submittal nobody notices until it is already late. A shared log that flags anything within three business days of its review window turns a silent delay into a visible one while there is still time to escalate it. The exact tool does not matter nearly as much as the discipline of using one, but if your team is tracking forty-plus open submittals across a spreadsheet, a shared drive, and three people's inboxes, that tool gap is costing you real weeks, not hours.
This is the kind of workflow gap we build fixed-price tools for at Granular: a single tracked submittal register with automatic aging alerts, tied to your actual project schedule instead of a static spreadsheet nobody updates past week three. If your submittal log currently lives in more than one place, book 30 minutes with us and we will walk through what a four-week build looks like for your team specifically.
FAQ
What is the difference between a submittal and an RFI? An RFI is a question asking the design team to clarify something unclear, missing, or contradictory in the contract documents. A submittal is a proposal, such as a specific product, shop drawing, or sample, that the design team reviews to confirm it meets the project specification before you can order, fabricate, or install it. Submittals require your own internal review and sign-off first; RFIs do not.
How long should a submittal review actually take? The design-team review itself typically runs 10 to 14 business days once a complete package reaches the reviewer. Total elapsed time, including your own prep and internal review, commonly runs two to three weeks even on a clean pass, and any rejection adds another 2 to 4 weeks on top of that.
Does AIA A201 guarantee a 14-day review window? No. AIA A201 calls for review with reasonable promptness rather than a fixed calendar deadline, and the actual expected timeframe depends on the submittal schedule the owner, architect, and contractor agree to during preconstruction. Projects without a written submittal schedule have no enforceable benchmark to point to when a review runs long.
What happens if a submittal is rejected? A rejected submittal, marked Revise and Resubmit or Rejected, sends the item back through the full review cycle again, typically adding 2 to 4 weeks to that item's timeline. If the item is on the procurement critical path, especially a long-lead item, that delay stacks on top of the manufacturing lead time rather than simply shifting it.
Who is responsible for submittal review delays? It depends on where the delay starts. An incomplete or non-compliant package submitted by the GC is generally the contractor's exposure. A complete, compliant submittal held well beyond the agreed review window may support a claim for a schedule extension, but only if a submittal schedule existed to measure the delay against.
Keep Reading
- How to Cut RFI Response Time From Two Weeks to Four Days: The companion workflow, why RFIs run on a different clock than submittals, and how to keep the design team's response time from stalling your schedule.
- How $50M GCs Get Lien Waivers in 48 Hours, Not Two Weeks: Another paperwork bottleneck that quietly costs mid-market GCs weeks per project, and the tracking fix that closes it.