The problem
A submittal that comes back marked revise and resubmit restarts the clock for everyone. The subcontractor revises, the GC re-reviews, and the design team reviews again, while procurement on long-lead equipment waits. On a project with hundreds of submittals, even a modest first-pass rejection rate turns into dozens of extra review cycles, each carrying engineering review time, schedule exposure, and resubmission labor. It is part of a broader pattern: construction professionals spend 3.9 hours a week dealing with mistakes and rework, and another 5.5 hours looking for project data. (FMI and PlanGrid, 2018)
The review burden itself is significant regardless of rejection rate. Complex commercial projects generate a heavy volume of submittals, each requiring technical review against project specifications. The review window written into the contract documents is typically far longer than the technical review itself requires. Not because that's how long the technical review takes, but because that's how long the administrative process takes: receiving the submittal, routing it to the right reviewer, completing the review, documenting the decision, and routing the response back through the GC.
MEP submittals carry specific technical complexity. Equipment submittals for mechanical systems require cross-referencing against specified performance criteria, energy compliance requirements, and spatial constraints documented in the coordination drawings. An electrical submittal for a switchgear assembly requires verification against the specifications, the one-line diagram, and the equipment schedule. The technical review is legitimate work. The administrative overhead wrapped around it is not.
What's driving it
A common bottleneck in submittal review sits between the GC review and the design team submission, at the point where a GC reviewer recognizes that product data may not fully match specifications but lacks the time or technical background to verify it completely before forwarding. The submittal reaches the design team partially reviewed, and the design team absorbs the full technical verification burden.
Volume compounds the problem. When a project has hundreds of active submittals, tracking what has been received, what is in review, what has been returned, and what is awaiting resubmission becomes a management task in itself. Manual tracking across spreadsheets and email introduces the risk of items falling through: submittals that were received but not logged, review periods that expired without a response, and resubmissions that were overlooked.
High rejection rates also often reflect specification problems upstream. Submittals rejected for specifying discontinued products or products that don't meet the current specification point back to the documentation deficiencies covered in the specification writing article in this series.
What resolution looks like
AI-assisted submittal review tools support the technical verification process by cross-referencing submitted product data against specification requirements, flagging discrepancies for engineer review rather than requiring the engineer to identify them manually. Routine submittals (products that clearly meet specifications with no significant deviations) can be prepared for approval with review flagged as confirmatory. Non-routine submittals requiring engineering judgment get prioritized accordingly.
Status tracking becomes systematic rather than manual. Open submittals are tracked against review deadlines, resubmission cycles are monitored, and overdue responses are flagged before they become schedule events. The engineer still reviews and approves every submittal. The administrative process surrounding that review is no longer a bottleneck.
Teams that structure their submittal review this way see fewer first-pass rejections. That reduction doesn't come from different engineers. It comes from a process that surfaces specification discrepancies before the submittal is forwarded rather than after it arrives.
QP's submittal workflow design starts from a measurable baseline: current rejection rate, average cycle time, and review hours per submittal. The target is documented, and the improvement is verifiable. "We reduced our rejection rate from 30 percent to under 10 percent" should be a statement you can make with data.
The bottom line
On a 500-submittal project, every 10 points of first-pass rejection rate is 50 more resubmission cycles. Each cycle avoided is review time saved and schedule recovered, and the project arrives at closeout measurably earlier with proportionally lower administrative overhead.
The technical quality of the review doesn't change. The process efficiency around it does.
Sources: FMI and PlanGrid, Construction Disconnected (2018): construction professionals spend 3.9 hours a week dealing with mistakes and rework and 5.5 hours looking for project data. The 500-submittal figures in this article are an illustrative calculation, not survey data.
If your submittal rejection rate is running above 10 percent or your review tracking lives in a spreadsheet, there's a more reliable approach.
Quantum Precision helps MEP firms design submittal workflows that reduce rejection rates and eliminate the tracking overhead that manual processing creates.
See how submittal rejection rates get reduced →