A rejected shop drawing submittal doesn’t just cost a redraw — it restarts the review clock. On a steel or precast job where a review cycle commonly runs two weeks, two rejected rounds can burn a month before fabrication even starts. Most of that delay traces back to a handful of recurring, fixable gaps in the drawings themselves.

Cutting the RFI count on a structural submittal mostly comes down to clear, consistent drawings: precise dimensions and material callouts, complete product/code information, standardized formatting, and coordination checks against other trades before submittal rather than after rejection. Delegated-design items like steel connections and precast need the licensed engineer’s seal in place first, since reviewers commonly won’t accept them without it.

Who this is for

This is for GC project executives and engineers managing a steel or precast submittal schedule who want to know specifically what reduces rejected submittals and RFIs — not general advice to “be thorough,” but the actual recurring gaps that trigger rejections.

Why a rejected submittal costs more than it looks like

A construction-process overview puts a concrete number on this: “14 calendar days per review cycle is a common allowance,” which means two rejected cycles consume roughly a month before fabrication can even begin [CLIENT TO CONFIRM — review-cycle duration is contract-specific; confirm the actual allowance in the governing project’s specifications]. The same source frames shop drawings as a checkpoint specifically because errors that get through it “become physical problems on site, often involving long lead-time items already in production” — meaning a gap caught at submittal is cheap, and the same gap caught after fabrication starts is not.

What actually reduces rejections

A shop-drawing-focused industry reference lists five practices tied directly to fewer RFIs and delays: meticulous detailing with precise dimensions, material callouts, and notation that reflects the actual design intent; comprehensive information (product data sheets, installation instructions, relevant codes) so a reviewer isn’t filling gaps with assumptions; standardized formatting across the drawing set so nothing gets missed from inconsistent presentation; early collaboration between the trade and the design team to catch discrepancies before formal submittal; and BIM-based clash detection to catch coordination conflicts digitally before they show up as a field problem [CLIENT TO CONFIRM — these are general industry recommendations; confirm which apply to the specific project’s submittal requirements].

Where coordination failures specifically originate

The same construction-process source is specific about where coordination problems come from: reviews done trade-by-trade, in isolation, miss interdependencies — dimensional conflicts between MEP systems and structural elements, misaligned penetrations, and inconsistent reference points between trades are named as common failure patterns [CLIENT TO CONFIRM — confirm the specific coordination review process the project is using]. A structural shop drawing that’s internally correct can still get rejected because it doesn’t reconcile with another trade’s submittal — which is why a coordination pass against other trades before submittal, not just an internal QA check, matters.

Delegated-design items need the seal before they go in

One specific, checkable gap: the same source notes that “delegated design items such as structural steel connections, precast components, and fire protection systems typically require a licensed engineer’s seal on the submittal before the reviewer accepts it.” A connection detail package that’s otherwise complete but missing the required seal is a predictable, avoidable rejection — see steel connection detail packages and where delegated design starts for how that boundary is determined in the first place.

Building a pre-submittal check into the drafting process

The practices above work best when they’re run as a deliberate step before a submittal goes out, not as a hope that the drawings are clean. A pre-submittal check that walks through dimensions and callouts against the design documents, confirms product data and code references are attached rather than assumed, checks the sheet set against a standard format, and runs a coordination pass against the current federated model catches most of the gaps that would otherwise come back as a formal rejection two weeks later.

PRE-SUBMITTAL CHECK (before sending to reviewer)
[ ] Dimensions and material callouts match the current design documents, not an earlier revision
[ ] Product data sheets, installation instructions, and code references are attached, not assumed
[ ] Sheet formatting is consistent across the full submittal set
[ ] Coordination/clash check run against the current federated model, not just the structural model alone
[ ] Delegated-design items (connections, precast components) carry the required engineer's seal
[ ] Submittal package matches the exact format and numbering the reviewer's specification requires
        

That last step matters as much as the technical content: a submittal that’s technically correct but doesn’t follow the reviewer’s required format or numbering convention can still bounce back as a rejected cycle, adding the same two-week delay as a substantive error would.

If your structural submittal package keeps coming back with the same categories of comments, Request a Scope Review — send the current submittal set and get back a specific read on what’s missing before the next review cycle starts.