Shop Drawing

Definition

A shop drawing is a detailed, dimensioned drawing produced by the party who will fabricate or install the work — a steel fabricator, a rebar detailer, a curtain-wall subcontractor, an MEP contractor — that translates the designer's intent drawings into the exact information needed to build. Shop drawings capture connections, tolerances, sequencing, and interface information that the designer's contract drawings deliberately leave out. Every mid-scale or large construction project runs on shop drawings; the design drawings alone are never buildable.

Origin

The tradition dates back to nineteenth-century mechanical and shipbuilding practice, when engineering drawings issued by naval architects were reworked in the shop by fabricators who added the dimensioned realities of plate sizes, rivet spacing, and shop equipment. The pattern moved into commercial construction as steel framing and MEP systems grew complex enough that designers could not — and should not — draw every screw. The core division of responsibility survives today: designers own intent; contractors own means and methods.

The Review Cycle

• Contractor prepares — often through a specialist detailer or the fabricator's engineering team.
• Contractor internal review — coordinate with adjacent trades before submission.
• Submit to engineer of record — usually via a formal submittal register.
• Engineer reviews — for conformance with design intent, not for correctness of dimensions.
• Return with status — approved, approved as noted, revise and resubmit, or rejected.
• Contractor resubmits if required — cycles typically run one to three times per package.

Real-World Construction Example

A 42-storey office tower had 3,200 shop drawing submittals over 28 months. The steel package alone was 810 submittals. The project's biggest lesson: the average review cycle target of 14 days slipped to 26 days by month six because the engineer's queue was uncontrolled. The team implemented three fixes — a submittal register with priority coding, a weekly submittal meeting between contractor and engineer, and a joint pre-submittal review for the 40 most complex packages. Average cycle time dropped to 12 days and the ripple into fabrication and delivery closed a projected six-week schedule slip.

Real-World IT / Agile Example

The IT analogue is the detailed technical design document (TDD) that translates a solution architecture (the intent) into buildable code and configuration (the fabrication). A payments platform team required a TDD for every service larger than one engineer-week. The TDDs were peer-reviewed by an architect, comparable to a shop drawing review. Cycle time was three business days. When the review queue stretched to eight days, delivery velocity dropped visibly; the team dedicated a rotating "architect on call" to shorten the queue and velocity recovered within two iterations. The parallel with construction shop drawing queues was direct.

Best Practices

• Coordinate with adjacent trades before submission — an uncoordinated shop drawing wastes an entire review cycle.
• Prioritise submittals ruthlessly by fabrication lead time and installation date.
• Publish an agreed cycle-time target — typically 14 calendar days — and measure adherence.
• Hold pre-submittal working meetings for the most complex packages.
• Use BIM coordination models to catch clashes before shop drawings are produced.

Common Mistakes

• Treating shop drawing review as a passive queue; the engineer's team gets buried and cycle times explode.
• Engineers using review as an opportunity to redesign; the intent drawings should have been complete enough already.
• Contractors submitting uncoordinated drawings; adjacent-trade conflicts show up mid-fabrication.
• Missing the fabrication lead time when scheduling submittals; a 14-day cycle for a 24-week lead-time item is fine, the same cycle for a two-week lead-time item is fatal.
• No status tracking. The register becomes unreliable and the project loses visibility of its own approvals.

Expert Tips

• Publish the register weekly. Everyone sees what is late, whose queue it is in, and what is next.
• Colour-code by risk. Late fabrication-critical drawings deserve red urgency; simple substitutions do not.
• Reject sloppy submittals fast. Detailed line-by-line reviews of poor drawings train contractors to submit worse next time.
• Distinguish "approved" from "no exceptions taken". The words carry different liability implications in most jurisdictions.
• Never let the engineer redesign in the review. Any change beyond conformance is a change to the contract documents and belongs in an RFI or change order.

Practical Lessons Learned

• Submittal cycle time is the second-most-common cause of construction schedule slip after late procurement, and the two are usually related.
• A weekly submittal meeting between contractor and engineer is one of the highest-return coordination habits in the industry.
• The best contractors invest in in-house detailing capability; it collapses submittal cycles and prevents fabrication defects.

Key Takeaways

• Shop drawings translate design intent into buildable instructions.
• Designers own intent; contractors own means and methods; the review is for conformance, not correction of dimensions.
• Cycle time is critical — 14 calendar days is the widely accepted benchmark.
• Coordination and prioritisation matter more than raw review speed.
• The submittal register is a project-management artefact, not paperwork.

Related Encyclopedia Entries

• BIM Coordination
• Request For Information
• Procurement Log
• Quality Gate

Related Research Articles, Case Studies & Tools

• Submittal Register Template
• Project Controls Academy: Submittals
• High-rise submittal turnaround case study
• Submittal cycle time and schedule impact